[28903] in North American Network Operators' Group
Re: That pesky AS path corruption bug...
daemon@ATHENA.MIT.EDU (Vijay Gill)
Tue May 23 14:09:37 2000
Date: Tue, 23 May 2000 14:02:29 -0400 (EDT)
From: Vijay Gill <wrath@cs.umbc.edu>
To: Vadim Antonov <avg@kotovnik.com>
Cc: nanog@merit.edu
In-Reply-To: <200005231741.KAA02092@kitty.kotovnik.com>
Message-ID: <Pine.SOL.3.95.1000523135809.7522A-100000@mailserver-ng.cs.umbc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
On Tue, 23 May 2000, Vadim Antonov wrote:
> This is not only practical, but, in fact, the only sane way to do things.
> Dropping BGP session causes withdrawal of hundreds or thousands of
> acceptable routes. When the BGP session is reestablished, these routes
> will be acquired again, causing a wave of announcements. When the
> invalid route shows up, the cycle is repeated.
>
> What a perfect way to kill the Internet :)
This is what BGP dampening is for. Dropping a few prefixes here and there
is a good way to make operational debugging of a network of any size,
hell.
With a NOTIFY and a drop, there is a definite positive feedback that
something is majorly wrong and allows people to open top level cases with
vendors.
/vijay
