[50603] in North American Network Operators' Group
Re: Deaggregating for emergency purposes
daemon@ATHENA.MIT.EDU (Stephen J. Wilcox)
Mon Aug 5 18:46:30 2002
Date: Mon, 5 Aug 2002 23:45:05 +0100 (BST)
From: "Stephen J. Wilcox" <steve@opaltelecom.co.uk>
To: Phil Rosenthal <pr@isprime.com>
Cc: nanog@merit.edu
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA/zNkI7d3EEmn3+v5DgN/l8KAAAAQAAAAl/BI/YXsaUm4C+EnQ7Q2swEAAAAA@isprime.com>
Errors-To: owner-nanog-outgoing@merit.edu
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
>
>
