[28905] in North American Network Operators' Group
Re: That pesky AS path corruption bug...
daemon@ATHENA.MIT.EDU (Vijay Gill)
Tue May 23 14:38:32 2000
Date: Tue, 23 May 2000 14:36:20 -0400 (EDT)
From: Vijay Gill <wrath@cs.umbc.edu>
To: Kai Schlichting <kai@pac-rim.net>
Cc: nanog@merit.edu
In-Reply-To: <4.2.2.20000523133645.029f3c50@mail.speedus.net>
Message-ID: <Pine.SOL.3.95.1000523142217.7522E-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, Kai Schlichting wrote:
> >Insist on correct behavior, not on cruftery.
>
> more conceivable and robust "ignore (log) corrupted message, continue
> with regular operation" ? Given route flap dampening, dropping the BGP
Byzantine failures perhaps? If I am getting some corrupt updates, how
confident am I that the rest of the updates are valid? In any case, it
would appear that the process on the other side has some issues since
theoretically, a malformed update should never (for most values of never)
arrive.
> session is hardly the desirable outcome here. On that note: under what
> circumstances should or shouldn't the BGP session come back up without
> mnual intervention?
A combination of bgp dampening and exponential backoff timing for retry on
sessions that were dropped because of an error should take care of the
rest.
/vijay
