[50611] in North American Network Operators' Group
Re: Deaggregating for emergency purposes
daemon@ATHENA.MIT.EDU (John M. Brown)
Mon Aug 5 20:12:28 2002
Date: Mon, 5 Aug 2002 17:12:07 -0700
From: "John M. Brown" <jmbrown@ihighway.net>
To: Phil Rosenthal <pr@isprime.com>
Cc: nanog@merit.edu
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA/zNkI7d3EEmn3+v5DgN/l8KAAAAQAAAAl/BI/YXsaUm4C+EnQ7Q2swEAAAAA@isprime.com>; from pr@isprime.com on Mon, Aug 05, 2002 at 06:41:22PM -0400
Errors-To: owner-nanog-outgoing@merit.edu
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
>
