[50661] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Deaggregating for emergency purposes

daemon@ATHENA.MIT.EDU (Omachonu Ogali)
Tue Aug 6 18:28:25 2002

Date: Tue, 6 Aug 2002 18:29:48 -0400
From: Omachonu Ogali <nanog@missnglnk.com>
To: nanog@merit.edu
Mail-Followup-To: nanog@merit.edu
In-Reply-To: <200208062216.WAA21215@vacation.karoshi.com>; from bmanning@karoshi.com on Tue, Aug 06, 2002 at 10:16:41PM +0000
Errors-To: owner-nanog-outgoing@merit.edu


On Tue, Aug 06, 2002 at 10:16:41PM +0000, bmanning@karoshi.com wrote:
> > 
> > On Tue, 6 Aug 2002 bmanning@karoshi.com wrote:
> > 
> > > > 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.
> > > 	Hum.  I take ~4 calls each day for things that are some other
> > > 	ISPs problem.  Folks are -politely- told that the issues
> > > 	are either with their ISP or someone upstream of their ISP.
> > > 	When they get pushy, I offer them a service contract. 99.999%
> > > 	(hey Sean, there are your five 9's!) of them then choose to
> > > 	work with thier ISPs.  I suspect that you have more than enough
> > > 	clue to never have to give me a call, but if you do, be prepared
> > > 	to be re-directed... :)
> > 
> > I hope you pay better attention on the phone then you do on lists. :)
> > 
> > The point was calling up the upstream of the AS who is generating bogus
> > routes.  The upstream of the caller is not at all involved.
> > 
> 
> 	But the upstream of the caller is involved.  They passed
> 	the route(s) on, no?
> 
> --bill

Not necessarily, I could be the victim of a leak calling up
an ISP to report it. Or some bored person connected to
route-server.* constantly checking prefixes.
-- 
Omachonu Ogali
missnglnk@informationwave.net
http://www.informationwave.net

home help back first fref pref prev next nref lref last post