Draft-chakrabarti-idr-rfc4893-mod-00.txt. Samita Chakrabarti [email protected] What is it?. RFC 4893 clarification points A proposal for handling AS_PATH/AS4_PATH etc. Proposals for additional clarification texts A proposal for specifying a OPEN message notification.
section 4.2.1 RFC 4893 states:
"Note that peering between a NEW BGP speaker and an OLD one is
possible only if the NEW BGP speaker has a 2-octet AS number.
However, this document does not assume that an Autonomous System with
NEW speakers has to have a globally unique 2-octet AS number -
AS_TRANS could be used instead (even if a multiple Autonomous System
would use it).“
R3 views R2 and R4 as part of same Autonomous domain; Some clarification or recommendation needed in the specification
careful considerations are required such that it does not
affect the routing path of the traffic due to some local policy on AS
number at the OLD BGP speaker. During transition to NEW BGP speaker from an OLD BGP speaker, the above scenario should be avoided.
Comment (Enke Chen): Reference to RFC 2270 could be provided as guidance
OPEN without Capability and AS 23456
Proposal : Notification Error
(from RFC 4271)
AS 23456 (Human error)
Acknowledgement: Satish Vardwarajula from Cisco Systems for AS Override transition issue