Deaggregating for emergency purposes

Tue Aug 6 00:12:07 UTC 2002

Hmm, this would be a "Bad Idea" (TM) (C) 2002, DMCA Protected

Having had this happen to me several different times, I'd have to 
recommend, calling the NOC of the advertising party. as the pref'd
way of handling it.

On Mon, Aug 05, 2002 at 06:41:22PM -0400, 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
> 