Re: [Idr] RFC5065 - Section 5.3

[David Freedman <david.freedman at uk.clara.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> 
> There is nothing stopping a vendor from providing a knob to accomplish
> this very feature.  

Other than the RFC is now explicit about this behaviour (where RFC3065
was not previously).

> 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.

Thanks, I do indeed understand but believe it makes it harder now to
convince vendors to "enhance" implementations now that there is an
explicit "SHOULD NOT"

Dave.


> 
> -- Jeff


- --
David Freedman
Group Network Engineering
Claranet Limited
http://www.clara.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIc3jZtFWeqpgEZrIRAmOsAJ9qKG7nXG3ij4EBndVvSdaxRmuvVQCgswTA
sz72qZZoxbdSLenYNX7/cXg=
=xdBo
-----END PGP SIGNATURE-----
_______________________________________________
Idr mailing list
Idr at ietf.org
https://www.ietf.org/mailman/listinfo/idr