[50606] in North American Network Operators' Group
Re: Deaggregating for emergency purposes
daemon@ATHENA.MIT.EDU (Richard A Steenbergen)
Mon Aug 5 18:55:38 2002
Date: Mon, 5 Aug 2002 18:53:06 -0400
From: Richard A Steenbergen <ras@e-gerbil.net>
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
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...
Seems like a remarkable waste of time and IRR resources. That is why NOCs
exist, so you can contact them quickly and make those announcements stop.
--
Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras
PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6)
