[129140] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Did your BGP crash today?

daemon@ATHENA.MIT.EDU (Jeffrey S. Young)
Fri Aug 27 17:22:31 2010

From: "Jeffrey S. Young" <young@jsyoung.net>
To: Richard A Steenbergen <ras@e-gerbil.net>
In-Reply-To: <20100827191324.GJ1946@gerbil.cluepon.net>
Date: Sat, 28 Aug 2010 07:22:17 +1000
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

About the same time the operators get back into the 
IETF and become involved again.  There was a time
when operators played a large role in the development
of things BGP (e.g. Tony Bates, Enke Chen, both at
iMCI).

No one is stopping us, the 'ivory tower' has no gate.

jy

On 28/08/2010, at 5:13 AM, Richard A Steenbergen <ras@e-gerbil.net> wrote:

> On Fri, Aug 27, 2010 at 01:29:15PM -0400, Jared Mauch wrote:
>> 
>> Unknown BGP attribute 99 (flags: 240)
>> Unknown BGP attribute 99 (flags: 240)
>> Unknown BGP attribute 99 (flags: 240)
>> Unknown BGP attribute 99 (flags: 240)
>> Unknown BGP attribute 99 (flags: 240)
> 
> Just out of curiosity, at what point will we as operators rise up 
> against the ivory tower protocol designers at the IETF and demand that 
> they add a mechanism to not bring down the entire BGP session because of 
> a single malformed attribute? Did I miss the memo about the meeting? 
> I'll bring the punch and pie.
> 
> -- 
> Richard A Steenbergen <ras@e-gerbil.net>       http://www.e-gerbil.net/ras
> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
> 
> 


home help back first fref pref prev next nref lref last post