[21635] in North American Network Operators' Group

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

Re: Strange BGP announcement

daemon@ATHENA.MIT.EDU (I Am Not An Isp)
Tue Nov 17 15:37:21 1998

Date: Tue, 17 Nov 1998 12:04:16 -0800
To: Andrew Bangs <andrewb@demon.net>
From: I Am Not An Isp <patrick@ianai.net>
Cc: nanog@merit.edu
In-Reply-To: <911332072.0029732.0@office.demon.net>

At 07:47 PM 11/17/98 +0000, Andrew Bangs wrote:
>patrick@ianai.net wrote:

>I don't recall saying that, or anything about route selection.
>I don't want all backbone routers (or any of them, for that matter)
>ignoring Update messages (or worse, propagating the announcements) with
>malformed AS_PATH attributes when they should be returning a NOTIFY and
>closing the BGP session. 

You said you wanted routers that followed the RFC.  The RFC does not
mention list AS_PATH length as a route selection criteria.  I have been
told that the draft for the next rev specifically prohibits using AS_PATH
length as a route selection criteria.

I kinda like using AS_PATH length.  It's not perfect - and I'm definitely
open to suggestions - but for now it's working.  And changing that in
today's environment would be ... monumental to say the least.

OTOH, I completely agree that the routers should have *not* passed on
malformed announcements, and behaving improperly to certain errors.

>Andrew Bangs, Network Engineering Manager, Demon Internet Ltd

TTFN,
patrick

I Am Not An Isp
www.ianai.net
"Think of it as evolution in action." - Niven & Pournelle

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