RFC 4276
BGP-4 Implementation Report
Pages: 97
Informational
Informational
Part 3 of 4 – Pages 30 to 67
3.14. LOCAL_PREF / Section 5.1.5 [RFC4271]
3.14.69. LOCAL_PREF
Functionality/Description: Included in all UPDATE messages that a given BGP speaker sends to the other internal peers RFC2119: SHALL Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.14.70. Degree of Preference
Functionality/Description: Calculated for each external route based on the locally configured policy, and included when advertising a route to its internal peers RFC2119: SHALL Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.14.71. LOCAL_PREF
Functionality/Description: Higher degree of preference MUST be preferred RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.14.72. LOCAL_PREF
Functionality/Description: Not included in UPDATE messages sent to external peers, except for the case of BGP Confederations [RFC3065] RFC2119: MUST NOT Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.14.73. LOCAL_PREF
Functionality/Description: Ignored if received from an external peer, except for the case of BGP Confederations [RFC3065] RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.15. ATOMIC_AGGREGATE / Section 5.1.6 [RFC4271]
3.15.74. ATOMIC_AGGREGATE
Functionality/Description: Included if an aggregate excludes at least some of the AS numbers present in the AS_PATH of the routes that are aggregated as a result of dropping the AS_SET RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.15.75. Received ATOMIC_AGGREGATE
Functionality/Description: BGP speaker SHOULD NOT remove the attribute from the route when propagating it to other speakers RFC2119: SHOULD NOT Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.15.76. Received ATOMIC_AGGREGATE
Functionality/Description: BGP speaker MUST NOT make any NLRI of that route more specific (as defined in 9.1.4) RFC2119: MUST NOT Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.16. AGGREGATOR / Section 5.1.7 [RFC4271]
3.16.77. AGGREGATOR
Functionality/Description: Included in updates which are formed by aggregation (see Section 9.2.2.2) RFC2119: MAY Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.16.78. AGGREGATOR
Functionality/Description: Added by the BGP speaker performing route aggregation RFC2119: MAY Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.16.79. AGGREGATOR
Functionality/Description: Contain local AS number and IP address RFC2119: SHALL Alcatel Y/N/O/Comments: Y Default behavior. Can be configured different from BGP ID. Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.16.80. AGGREGATOR IP Address
Functionality/Description: The same as the BGP Identifier of the speaker RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.17. BGP Error Handling / Section 6 [RFC4271]
3.17.81. Error Handling
Functionality/Description: Is your implementation compatible with the error handling procedures described in this section? RFC2119: N/A Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.17.82. Error Subcode
Functionality/Description: Zero, if it is not specified RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.18. Message Header Error Handling / Section 6.1 [RFC4271]
3.18.83. Message Header Errors
Functionality/Description: Indicated by sending the NOTIFICATION message with Error Code Message Header Error RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.18.84. Synchronization Error
Functionality/Description: Error Subcode MUST be set to Connection Not Synchronized RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.18.85. Message Length
Functionality/Description: Use the Bad Message Length Error Subcode to indicate an incorrect message length RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.18.86. Bad Message Length
Functionality/Description: The Data field MUST contain the erroneous Length field RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.18.87. Type Field
Functionality/Description: If the Type field of the message header is not recognized, then the Error Subcode MUST be set to Bad Message Type RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.18.88. Bad Message Type
Functionality/Description: The Data field MUST contain the erroneous Type field RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.19. OPEN Message Error Handling / Section 6.2 [RFC4271]
3.19.89. OPEN Message Errors
Functionality/Description: Indicated by sending the NOTIFICATION message with Error Code OPEN Message Error RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.19.90. Version Number Not Supported
Functionality/Description: The Error Subcode MUST be set to Unsupported Version Number RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.19.91. Unacceptable Autonomous System Field
Functionality/Description: The Error Subcode MUST be set to Bad Peer AS RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.19.92. Unacceptable Hold Time Error Subcode
Functionality/Description: Used if the Hold Time field of the OPEN message is unacceptable RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.19.93. Hold Time Rejection
Functionality/Description: Values of one or two seconds RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.19.94. Hold Time Rejection
Functionality/Description: An implementation may reject any proposed Hold Time RFC2119: MAY Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: N NextHop Y/N/O/Comments: Y3.19.95. Hold Time
Functionality/Description: If accepted, then the negotiated value MUST be used RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.19.96. Syntactically Incorrect BGP Identifier
Functionality/Description: The Error Subcode MUST be set to Bad BGP Identifier RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.19.97. Not Recognized Optional Parameters
Functionality/Description: The Error Subcode MUST be set to Unsupported Optional Parameters RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: N We may fix this. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.19.98. Recognized but Malformed Optional Parameters
Functionality/Description: The Error Subcode MUST be set to 0 (Unspecific) RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: N Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20. UPDATE Message Error Handling / Section 6.3 [RFC4271]
3.20.99. UPDATE Message Errors
Functionality/Description: Indicated by sending the NOTIFICATION message with Error Code UPDATE Message Error RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.100. Too Large
Functionality/Description: If the Withdrawn Routes Length or Total Attribute Length is too large, then the Error Subcode MUST be set to Malformed Attribute List RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.101. Conflicting Flags
Functionality/Description: If any recognized attribute has Attribute Flags that conflict with the Attribute Type Code, then the Error Subcode MUST be set to Attribute Flags Error RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20.102. Conflicting Flags
Functionality/Description: The Data field MUST contain the erroneous attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.103. Conflicting Length
Functionality/Description: If any recognized attribute has Attribute Length that conflicts with the expected length, then the Error Subcode MUST be set to Attribute Length Error RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.104. Conflicting Length
Functionality/Description: The Data field MUST contain the erroneous attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20.105. Missing Mandatory Well-Known Attributes
Functionality/Description: The Error Subcode MUST be set to Missing Well-known Attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.106. Missing Mandatory Well-Known Attributes
Functionality/Description: The Data field MUST contain the Attribute Type Code of the missing well-known attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: N We plan to fix this in future. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.107. Unrecognized Mandatory Well-Known Attributes
Functionality/Description: The Error Subcode MUST be set to Unrecognized Well-known Attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: N We set error subcode to Attribute Flags Error, but we intend to correct this soon. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20.108. Unrecognized Mandatory Well-Known Attributes
Functionality/Description: The Data field MUST contain the unrecognized attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.109. Undefined ORIGIN
Functionality/Description: The Error Sub-code MUST be set to Invalid Origin Attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.110. Undefined ORIGIN
Functionality/Description: The Data field MUST contain the unrecognized attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20.111. Syntactically Incorrect NEXT_HOP
Functionality/Description: The Error Subcode MUST be set to Invalid NEXT_HOP Attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: N Ignores the prefix in case of martian nexthop, and in case of length not equal to IPv4 address-length, we send NOTIFICATION with error subcode Attribute Length error. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.112. Syntactically Incorrect NEXT_HOP
Functionality/Description: The Data field MUST contain the incorrect attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.113. NEXT_HOP Semantic Correctness
Functionality/Description: NEXT_HOP is checked for semantic correctness against the criteria in this section RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20.114. NEXT_HOP Semantic Correctness
Functionality/Description: Not be the IP address of the receiving speaker RFC2119: MUST NOT Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.115. NEXT_HOP Semantic Correctness
Functionality/Description: In the case of an EBGP where the sender and receiver are one IP hop away from each other, either the IP address in the NEXT_HOP MUST be the sender's IP address (that is used to establish the BGP connection), or the interface associated with the NEXT_HOP IP address MUST share a common subnet with the receiving BGP speaker RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.116. Semantically Incorrect NEXT_HOP
Functionality/Description: Error logged RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20.117. Semantically Incorrect NEXT_HOP
Functionality/Description: Route Ignored RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: N NextHop Y/N/O/Comments: Y3.20.118. Semantically Incorrect NEXT_HOP
Functionality/Description: NOTIFICATION not sent RFC2119: SHOULD NOT Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.119. Semantically Incorrect NEXT_HOP
Functionality/Description: Connection not closed RFC2119: SHOULD NOT Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.120. Syntactically Incorrect AS_PATH
Functionality/Description: The Error Subcode MUST be set to Malformed AS_PATH RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20.121. First Neighbor in AS_PATH Check
Functionality/Description: If the UPDATE message is received from an external peer, the local system MAY check whether the leftmost AS in the AS_PATH attribute is equal to the autonomous system number of the peer that sent the message RFC2119: MAY Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: N NextHop Y/N/O/Comments: Y3.20.122. First Neighbor in AS_PATH Check
Functionality/Description: If the check determines that this is not the case, the Error Subcode MUST be set to Malformed AS_PATH RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: n/a NextHop Y/N/O/Comments: Y3.20.123. Optional Attributes
Functionality/Description: Value MUST be checked if the attribute is recognized RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20.124. Optional Attribute Error
Functionality/Description: The attribute MUST be discarded RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.125. Optional Attribute Error
Functionality/Description: The Error Subcode MUST be set to Optional Attribute Error RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: N What exactly is optional attribute e.g., If error is flag related, we send update flag error subcode, if it is length related, we send update length error subcode. These granular subcodes are better in terms of debugging than optional attribute error. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y Only optional attribute error that doesn't have a more specific error, is the version 3 to version 4 error for the atomic aggregate. All others default to more specific error codes if implementation.3.20.126. Optional Attribute Error
Functionality/Description: The Data field MUST contain the attribute RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20.127. Duplicate Attributes
Functionality/Description: If any attribute appears more than once in the UPDATE message, then the Error Subcode MUST be set to Malformed Attribute List RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.128. Syntactically Incorrect NLRI Field
Functionality/Description: The Error Subcode MUST be set to Invalid Network Field RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.129. Semantically Incorrect NLRI Field
Functionality/Description: An error SHOULD be logged locally RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.20.130. Semantically Incorrect NLRI Field
Functionality/Description: The prefix SHOULD be ignored RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.20.131. UPDATE with no NLRI
Functionality/Description: An UPDATE message that contains correct path attributes, but no NLRI, SHALL be treated as a valid UPDATE message RFC2119: SHALL Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.21. NOTIFICATION Message Error Handling / Section 6.4 [RFC4271]
3.21.132. Error in NOTIFICATION Message
Functionality/Description: Noticed, logged locally, and brought to the attention of the administration of the peer RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: N Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.22. Hold Timer Expired Error Handling / Section 6.5 [RFC4271]
3.22.133. Hold Timer Expired
Functionality/Description: Is your implementation compatible with the error handling procedures described in this section? RFC2119: N/A Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.23. Finite State Machine Error Handling / Section 6.6 [RFC4271]
3.23.134. Finite State Machine Errors
Functionality/Description: Is your implementation compatible with the error handling procedures described in this section? RFC2119: N/A Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: N Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.24. Cease / Section 6.7 [RFC4271]
3.24.135. Cease NOTIFICATION
Functionality/Description: Used in absence of any fatal errors if a BGP peer chooses at any given time to close its BGP connection RFC2119: MAY Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: N We close the TCP session without CEASE NOTIFICATION. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.24.136. Cease NOTIFICATION
Functionality/Description: Not used for specified fatal errors RFC2119: MUST NOT Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.24.137. Upper bound on the number of address prefixes the speaker is willing to accept from a neighbor
Functionality/Description: Support by local configuration RFC2119: MAY Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.24.138. Upper bound on the number of address prefixes the speaker is willing to accept from a neighbor
Functionality/Description: If exceeded and the BGP speaker decides to terminate its BGP connection, the Cease NOTIFICATION MUST be used RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: N We don't send CEASE but we plan to correct that soon. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y No termination of peers is supported We are considering support with the maximum prefix document for later releases.
3.24.139. Upper bound on the number of address prefixes the speaker is willing to accept from a neighbor
Functionality/Description: Log locally RFC2119: MAY Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.25. BGP Connection Collision Detection / Section 6.8 [RFC4271]
3.25.140. Connection Collision
Functionality/Description: One of the connections MUST be closed RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.25.141. Receipt of an OPEN Message
Functionality/Description: The local system MUST examine all of its connections that are in the OpenConfirm state RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: O We detect collision through some other implementation specific way and resolve by method specified in the document. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.25.142. Receipt of an OPEN Message
Functionality/Description: Examine connections in an OpenSent state if it knows the BGP Identifier of the peer by means outside of the protocol RFC2119: MAY Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.26. BGP Version Negotiation / Section 7 [RFC4271]
3.26.143. Version Negotiation
Functionality/Description: Multiple attempts to open a BGP connection, starting with the highest version number each supports RFC2119: MAY Alcatel Y/N/O/Comments: N Supports only version 4 Cisco Y/N/O/Comments: O We resolve it through config. If Config is for version 3, and we get version 4, OPEN will always fail. Similarly, if configed (default) is version 4 and peers configured is 3, we don't try to negotiate version 3 unless we have configured it. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: N Supports only version 4.3.26.144. Future Versions of BGP
Functionality/Description: MUST retain the format of the OPEN and NOTIFICATION messages RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.27. BGP Finite State Machine (FSM) / Section 8 [RFC4271]
3.27.145. FSM
Functionality/Description: Is your implementation compatible with the conceptual FSM described in this section? RFC2119: N/A Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.28. Administrative Events / Section 8.1.2 [RFC4271]
3.28.146. Optional Session Attribute Settings
Functionality/Description: Each event has an indication of what optional session attributes SHOULD be set at each stage RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: O Its rather vague. We have an option Of manually starting or stopping sessions but not an option for all optional session attributes that are listed in the document. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y The following optional attributes are implied in this implementation: 1) Automatic start, 2) Automatic Stop, 3)3.28.147. Event1: ManualStart
Functionality/Description: The PassiveTcpEstablishment attribute SHOULD be set to FALSE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.28.148. Event3: AutomaticStart
Functionality/Description: The AllowAutomaticStart attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.28.149. Event3: AutomaticStart
Functionality/Description: The PassiveTcpEstablishment optional session attribute SHOULD be set to FALSE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.28.150. Event3: AutomaticStart
Functionality/Description: DampPeerOscillations SHOULD be set to FALSE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Don't support DampPeerOscillations attribute, so it is always FALSE. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.28.151. Event4: ManualStart_with_PassiveTcpEstablishment
Functionality/Description: The PassiveTcpEstablishment attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y We wait for some fixed time before initiating OPEN. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.28.152. Event4: ManualStart_with_PassiveTcpEstablishment
Functionality/Description: The DampPeerOscillations attribute SHOULD be set to FALSE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Don't support DampPeerOscillations attribute so it is FALSE. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: O We don't support DampPeerOscilation attribute with a setting of off, and hence Event 4. Future version will support Event 43.28.153. Event5: AutomaticStart_with_PassiveTcpEstablishment
Functionality/Description: The AllowAutomaticStart attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.28.154. Event5: AutomaticStart_with_PassiveTcpEstablishment
Functionality/Description: The PassiveTcpEstablishment attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.28.155. Event5: AutomaticStart_with_PassiveTcpEstablishment
Functionality/Description: The DampPeerOscillations SHOULD be set to FALSE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Don't support DampPeerOscillations attribute, so always FALSE. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: O We don't support DampPeerOscilation attribute with a setting of off, and hence Event 5. Future version will support Event 53.28.156. Event6: AutomaticStart_with_DampPeerOscillations
Functionality/Description: The AllowAutomaticStart attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: O Don't support DampPeerOscillations attribute. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.28.157. Event6: AutomaticStart_with_DampPeerOscillations
Functionality/Description: The DampPeerOscillations attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: N Don't support DampPeerOscillations attribute. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.28.158. Event6: AutomaticStart_with_DampPeerOscillations
Functionality/Description: The PassiveTcpEstablishment attribute SHOULD be set to FALSE RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: O Don't support DampPeerOscillations attribute and hence Event6. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.28.159. Event7: AutomaticStart_with_DampPeerOscillations_and_PassiveTcpEstablishment
Functionality/Description: The AllowAutomaticStart attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: O Don't support DampPeerOscillations attribute and hence Event7 Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.28.160. Event7: AutomaticStart_with_DampPeerOscillations_and_PassiveTcpEstablishment
Functionality/Description: The DampPeerOscillations attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: O Don't support DampPeerOscillations attribute and hence Event7 Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.28.161. Event7: AutomaticStart_with_DampPeerOscillations_and_PassiveTcpEstablishment
Functionality/Description: The PassiveTcpEstablishment attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: O Don't support DampPeerOscillations attribute and hence Event7 Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.28.162. Event8: AutomaticStop
Functionality/Description: The AllowAutomaticStop attribute SHOULD be TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.29. Timer Events / Section 8.1.3 [RFC4271]
3.29.163. Event12: DelayOpenTimer_Expires
Functionality/Description: DelayOpen attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: n/a NextHop Y/N/O/Comments: Y3.29.164. Event12: DelayOpenTimer_Expires
Functionality/Description: DelayOpenTime attribute SHOULD be supported RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: n/a NextHop Y/N/O/Comments: Y3.29.165. Event12: DelayOpenTimer_Expires
Functionality/Description: DelayOpenTimer SHOULD be supported RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: n/a NextHop Y/N/O/Comments: Y
3.29.166. Event13: IdleHoldTimer_Expires
Functionality/Description: DampPeerOscillations attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: O Don't support DampPeerOscillations attribute and hence Event13 Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.29.167. Event13: IdleHoldTimer_Expires
Functionality/Description: IdleHoldTimer SHOULD have just expired RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: O Don't support DampPeerOscillations attribute and hence Event13 Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.30. TCP Connection-Based Events / Section 8.1.4 [RFC4271]
3.30.168. Event14: TcpConnection_Valid
Functionality/Description: BGP's destination port SHOULD be port 179 RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.30.169. Event14: TcpConnection_Valid
Functionality/Description: The TrackTcpState attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: O GateD NGC 2.0 provides hooks for the TCP state tracking, but use of this option depends OS support. Future versions will have additional hooks.3.30.170. Event15: Tcp_CR_Invalid
Functionality/Description: BGP destination port number SHOULD be 179 RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: O GateD NGC 2.0 provides hooks for the TCP state tracking, but use of this option depends OS support. Future versions will have additional hooks.3.31. BGP Messages-Based Events / Section 8.1.5 [RFC4271]
3.31.171. Event19: BGPOpen
Functionality/Description: The DelayOpen optional attribute SHOULD be set to FALSE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: n/a NextHop Y/N/O/Comments: Y
3.31.172. Event19: BGPOpen
Functionality/Description: The DelayOpenTimer SHOULD not be running RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.31.173. Event20: BGPOpen with DelayOpenTimer Running
Functionality/Description: The DelayOpen attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: N Not applicable Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: n/a NextHop Y/N/O/Comments: Y3.31.174. Event20: BGPOpen with DelayOpenTimer Running
Functionality/Description: The DelayOpenTimer SHOULD be running RFC2119: SHOULD Alcatel Y/N/O/Comments: N Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: n/a NextHop Y/N/O/Comments: Y
3.31.175. Event23: OpenCollisionDump
Functionality/Description: If the state machine is to process this event in Established state, the CollisionDetectEstablishedState optional attribute SHOULD be set to TRUE RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Collision detection event is logged. Cisco Y/N/O/Comments: O We always detect collision before we go to established state. Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: O GateD NGC 2.0 does not support Collision Detection in Established state. This option attribute is always set to FALSE.3.32. FSM Definition / Section 8.2.1 [RFC4271]
3.32.176. FSM
Functionality/Description: Separate FSM for each configured peer RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.32.177. TCP Port 179
Functionality/Description: A BGP implementation MUST connect to and listen on TCP port 179 for incoming connections in addition to trying to connect to peers RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
3.32.178. Incoming Connections
Functionality/Description: A state machine MUST be instantiated RFC2119: MUST Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.33. FSM and Collision Detection / Section 8.2.1.2 [RFC4271]
3.33.179. Connection Collision
Functionality/Description: The corresponding FSM for the connection that is closed SHOULD be disposed of RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.34. FSM Event numbers / Section 8.2.1.4 [RFC4271]
3.34.180. Event Numbers
Functionality/Description: Used to provide network management information RFC2119: MAY Alcatel Y/N/O/Comments: Y Not visible to operator. Cisco Y/N/O/Comments: N Laurel Y/N/O/Comments: N NextHop Y/N/O/Comments: N Future Release of GateD NGC may support event numbers.
3.35. Finite State Machine / Section 8.2.2 [RFC4271]
3.35.181. ConnectRetryTimer
Functionality/Description: Sufficiently large to allow TCP initialization RFC2119: SHOULD Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y3.35.182. Second Connection Tracking
Functionality/Description: In response to a TCP connection succeeds [Event 16 or Event 17], the 2nd connection SHALL be tracked until it sends an OPEN message RFC2119: SHALL Alcatel Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
(page 67 continued on part 4)