nanog mailing list archives
Deaggregating for emergency purposes
From: "Phil Rosenthal" <pr () isprime com>
Date: Mon, 5 Aug 2002 18:41:22 -0400
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
Current thread:
- Deaggregating for emergency purposes Phil Rosenthal (Aug 05)
- Re: Deaggregating for emergency purposes Richard A Steenbergen (Aug 05)
- RE: Deaggregating for emergency purposes Phil Rosenthal (Aug 05)
- Re: Deaggregating for emergency purposes Stephen J. Wilcox (Aug 05)
- Re: Deaggregating for emergency purposes Simon Lockhart (Aug 05)
- Re: Deaggregating for emergency purposes bmanning (Aug 05)
- Re: Deaggregating for emergency purposes John M. Brown (Aug 05)
- RE: Deaggregating for emergency purposes Phil Rosenthal (Aug 05)
- Re: Deaggregating for emergency purposes jnull (Aug 05)
- Re: Deaggregating for emergency purposes John M. Brown (Aug 05)
- Re: Deaggregating for emergency purposes john (Aug 05)
- RE: Deaggregating for emergency purposes Phil Rosenthal (Aug 05)
- Re: Deaggregating for emergency purposes Richard A Steenbergen (Aug 05)