BGP Confederations - Next-Hop Processing (RFC 3065)

From: Ken.Farrington@barclayscapital.com
Date: Sat Sep 27 2003 - 13:41:03 GMT-3


Hello,

on the RFC below

RFC 3065
   
   It shall be legal for a BGP speaker to advertise an unchanged
   NEXT_HOP and MULTI_EXIT_DISCRIMINATOR (MED) attribute to peers in a
   neighboring AS within the same confederation. In addition, the
   restriction against sending the LOCAL_PREFERENCE attribute to peers
   in a neighboring AS within the same confederation is removed.

Just testing on my lab, this appears to be the default behavior of Cisco
routers peering between two sub-ASs.
So, peering between as 65xx1 and 65xx2, the next-hop does not change as you
would normally see with an eBGP non-confed configuration.

Please can someone just confirm that this is the default behaviour over all
Cisco IOS, or do I have a bug in IOS?

Many thx indeed,
Ken

------------------------------------------------------------------------
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.

Internet communications are not secure and therefore the Barclays
Group does not accept legal responsibility for the contents of this
message. Although the Barclays Group operates anti-virus programmes,
it does not accept responsibility for any damage whatsoever that is
caused by viruses being passed. Any views or opinions presented are
solely those of the author and do not necessarily represent those of the
Barclays Group. Replies to this email may be monitored by the Barclays
Group for operational or business reasons.

------------------------------------------------------------------------

***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***



This archive was generated by hypermail 2.1.4 : Wed Oct 01 2003 - 07:24:38 GMT-3