Re: [Idr] RFC5065 - Section 5.3

[Jeffrey Haas <jhaas at pfrc.org>]

David,

Some of this is my opinion and some my recollection of the events at the
time.  Your mileage may vary.

On Tue, Jul 08, 2008 at 02:44:21PM +0100, David Freedman wrote:
> I would rather have said:
> 
> When comparing routes using AS_PATH length, an implementation MAY
> provide the ability to count CONFED_SEQUENCE and CONFED_SET.
> 
> 
> Looking back through the archives, I see Ilya Varlashkin has commented
> on this previously :

And a few other people, including me.

There is nothing stopping a vendor from providing a knob to accomplish
this very feature.  However, as with everything else regarding BGP path
selection, the important thing is that route selection is done
consistently AS-wide.  As long as that is the case, you can do pretty
much anything you like.

The more widely deployed implementations of BGP ignored confederation
segment length as part of its route selection by default.  Thus this
became somewhat a matter of doing what the big vendors did.

The language thus was written to heavily favor interoperability over
flexibility.  This avoids having to discuss the picky issues of
consistent route selection across the AS within a specific extension.

-- Jeff
_______________________________________________
Idr mailing list
Idr at ietf.org
https://www.ietf.org/mailman/listinfo/idr