Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: Deaggregating for emergency purposes

  • From: Derek Samford
  • Date: Tue Aug 06 16:26:09 2002

This was by far the most clued post in the entire thread. 
1. For the most part, engineers are happy to talk to engineers.
2. See one.
3. A Tier-1 lives and dies by its reputation. If they let hijacks go
unnoticed, then that's a black tarnish, and all of NANOG will know.
Besides they are generally extremely helpful. I speak from experience,
as I've had to deal with this on a few occasions. Generally speaking, 30
minutes is the longest you'll have to wait for something as easy to stop
as this.

Derek



-----Original Message-----
From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of
Omachonu Ogali
Sent: Tuesday, August 06, 2002 4:15 PM
To: nanog@merit.edu
Subject: Re: Deaggregating for emergency purposes


On Tue, Aug 06, 2002 at 03:56:32PM -0400, Daniel Senie wrote:
> 
> At 02:50 PM 8/6/02, you wrote:
> 
> >Phil,
> >         You would think, after hearing about 30 people with clue+++
> >talk, you may realize that this is a patently *bad* thing and should
not
> >be done.
> 
> Actually, what the many people have said sounded a lot more like "it
won't 
> help very much."
> 
> >  If your route's are being hijacked you can generally solve your
> >problems in 2-5 phone calls...That's all it's *ever* taken me.
> >1. Call their NOC.
> 
> typical response: you're not our customer, go away.

Typical response: You're not our customer, who are you?
I'm Omachonu Ogali with XYZ Networks, and I'd like to speak to
a network engineer regarding a routing problem.
-- Ah ok, please hold.
 
> >2. If not helpful call their upstream.
> 
> typical response: you're not our customer, go away.

See above.
 
> >3. Call a couple of Tier 1's who are transit for their upstream, and
> >have them filter it.
> 
> response: who the hell are you?

Cut the crap, when US/CKS was leaking Digex to UUnet, I
called UUnet, and within 30 minutes the problem was resolved.
Plus when I called, I wasn't representing any company or
calling any magic numbers.
 
> Until you get back to the people you buy transit from, or peer with,
and 
> try to get them to take on your cause. When you can't get your own 
> upstreams to understand what you're talking about, you post to NANOG,
and 
> the problem gets solved in short order.

No, most of you post to NANOG about irrelevant drivel that brings
the S/N ratio lower each year, or you post 3-4 hops out of a 12
hop traceroute, or you resort to NANOG instead of calling your
upstream first, or you talk about implementing the most wacked out
routing policy to exist on the planet.
 
> This tends to be the sad reality.

Yes, the above tends to be the sad reality.

> -----------------------------------------------------------------
> Daniel Senie                                        dts@senie.com
> Amaranth Networks Inc.                    http://www.amaranth.com
> 
-- 
Omachonu Ogali
missnglnk@informationwave.net
http://www.informationwave.net





Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.