[50610] in North American Network Operators' Group
Re: Deaggregating for emergency purposes
daemon@ATHENA.MIT.EDU (bmanning@karoshi.com)
Mon Aug 5 19:56:39 2002
From: bmanning@karoshi.com
To: steve@opaltelecom.co.uk (Stephen J. Wilcox)
Date: Mon, 5 Aug 2002 23:51:48 +0000 (UCT)
Cc: pr@isprime.com (Phil Rosenthal), nanog@merit.edu
In-Reply-To: <Pine.LNX.4.21.0208052344250.27309-100000@staff.opaltelecom.net> from "Stephen J. Wilcox" at Aug 05, 2002 11:45:05 PM
Errors-To: owner-nanog-outgoing@merit.edu
Well.... I can announce /27s or even /32s...
but who will listen?
>
>
> seems a hack. what if they announce a /24 from your space and they mostly have
> shorter path lengths? you still lose...
>
> Steve
>
> On Mon, 5 Aug 2002, Phil Rosenthal wrote:
>
> >
> > I am currently announcing only my aggregate routes, but I have lately
> > thought about the possibility of someone mistakenly, or maliciously,
> > announcing more specifics from my space.
> > The best solution for an emergency response to that (that I can think
> > of), is registering all of the /24's that make up my network, so if
> > someone should announce a more-specific, I can always announce the most
> > specific that would be accepted (assuming they don't announce the /24's
> > too, it should be a problem avoided)
> >
> > Does anyone else have any other ideas on ways to quickly deal with
> > someone else announcing your more specifics, since contacting their NOC
> > is likely going to take a long time...
> >
> > --Phil
> >
> >
>
