[50602] in North American Network Operators' Group
Deaggregating for emergency purposes
daemon@ATHENA.MIT.EDU (Phil Rosenthal)
Mon Aug 5 18:41:56 2002
Reply-To: <pr@isprime.com>
From: "Phil Rosenthal" <pr@isprime.com>
To: <nanog@merit.edu>
Date: Mon, 5 Aug 2002 18:41:22 -0400
Errors-To: owner-nanog-outgoing@merit.edu
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
