idnits 2.17.1 draft-ietf-idr-bgp-implementation-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3667, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 4024. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 4000. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 4008. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 4014. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 86 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) == There are 3 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document has an RFC 3978 Section 5.2(a) Derivative Works Limitation clause. == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 2662 has weird spacing: '...tribute is...' -- The exact meaning of the all-uppercase expression 'MAY NOT' is not defined in RFC 2119. If it is intended as a requirements expression, it should be rewritten using one of the combinations defined in RFC 2119; otherwise it should not be all-uppercase. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: Functionality/Description: The DelayOpenTimer SHOULD not be running == The expression 'MAY NOT', while looking like RFC 2119 requirements text, is not defined in RFC 2119, and should not be used. Consider using 'MUST NOT' instead (if that is what you mean). Found 'MAY NOT' in this paragraph: Functionality/Description: The route MAY NOT serve as an input to the next phase of route selection -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 2004) is 7224 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 49 == Missing Reference: 'RFC 2796' is mentioned on line 131, but not defined ** Obsolete undefined reference: RFC 2796 (Obsoleted by RFC 4456) == Missing Reference: 'RFC 2918' is mentioned on line 132, but not defined -- Looks like a reference, but probably isn't: '2' on line 312 == Unused Reference: 'RFC3667' is defined on line 3949, but no explicit reference was found in the text == Unused Reference: 'RFC3668' is defined on line 3952, but no explicit reference was found in the text == Outdated reference: A later version (-26) exists of draft-ietf-idr-bgp4-24 ** Obsolete normative reference: RFC 1771 (Obsoleted by RFC 4271) ** Obsolete normative reference: RFC 2385 (Obsoleted by RFC 5925) ** Obsolete normative reference: RFC 2796 (Obsoleted by RFC 4456) ** Obsolete normative reference: RFC 3065 (Obsoleted by RFC 5065) ** Obsolete normative reference: RFC 3667 (Obsoleted by RFC 3978) ** Obsolete normative reference: RFC 3668 (Obsoleted by RFC 3979) Summary: 14 errors (**), 0 flaws (~~), 13 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Interdomain Working Group 3 Internet Draft S. Hares 4 Document: draft-ietf-idr-bgp-implementation-01.txt NextHop 5 A. Retana 6 Cisco 7 Expires: August 2004 July 2004 9 BGP 4 Implementation Report 11 Status of this Memo 13 By submitting this Internet-Draft, we certify that any applicable 14 patent or other IPR claims of which we are aware have been 15 disclosed, or will be disclosed, and any of which we become aware 16 will be disclosed, in accordance with RFC 3668. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as 21 Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other 25 documents at any time. It is inappropriate to use Internet-Drafts 26 as reference material or to cite them other than as "work in 27 progress". 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt . 32 This document may not be modified, and derivative works of it may 33 not be created, except to publish it as an RFC and to translate it 34 into languages other than English. 36 Abstract 38 This document provides a survey of the BGP-4 implementation draft- 39 ietf-idr-bgp4-24.txt. After a brief summary, each response is 40 listed. The editor makes no claim as to the accuracy of the 41 information provided. 43 Conventions used in this document 45 ^L 46 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 47 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 48 document are to be interpreted as described in RFC-2119 [1]. 50 TABLE of CONTENTS 52 1. Introduction...................................................3 53 2. Results of Survey..............................................4 54 2.1 Differences................................................5 55 2.2 Implementations and interoperability.......................6 56 2.3 BGP Implementation Identification..........................7 57 3. BGP4 Implementation Report.....................................7 58 2.0 Summary of Operation / Section 3...........................7 59 3.1 Routes: Advertisement and Storage / Section 3.1............8 60 3.2 Routing Information Bases / Section 3.2....................9 61 3.3 Message Formats / Section 4................................9 62 3.4 Message Header Format / Section 4.1........................9 63 3.5 OPEN Message / Section 4.2................................11 64 3.6 UPDATE Message Format / Section 4.3.......................11 65 3.7 KEEPALIVE Message Format / Section 4.4....................15 66 3.8 NOTIFICATION Message Format / Section 4.5.................15 67 3.9 Path Attributes /Section 5................................16 68 3.10 ORIGIN / Section 5.1.1...................................19 69 3.11 AS_PATH / Section 5.1.2..................................20 70 3.12 NEXT_HOP / Section 5.1.3.................................21 71 3.13 MULTI_EXIT_DISC / Section 5.1.4..........................24 72 3.14 LOCAL_PREF / Section 5.1.5...............................26 73 3.15 ATOMIC_AGGREGATE / Section 5.1.6.........................28 74 3.16 AGGREGATOR / Section 5.1.7...............................29 75 3.17 BGP Error Handling / Section 6...........................30 76 3.18 Message Header Error Handling / Section 6.1..............30 77 3.19 OPEN message error handling / Section 6.2................32 78 3.20 UPDATE message error handling / Section 6.3..............35 79 3.21 NOTIFICATION message error handling / Section 6.4........44 80 3.22 Hold Timer Expired error handling / Section 6.5..........44 81 3.23 Finite State Machine error handling / Section 6.6........45 82 3.24 Cease / Section 6.7......................................45 83 3.25 BGP connection collision detection / Section 6.8.........46 84 3.26 BGP Version Negotiation / Section 7......................47 85 3.27 BGP Finite State machine (FSM) / Section 8...............48 86 3.28 Administrative Events / Section 8.1.2....................48 87 3.29 Timer Events / Section 8.1.3.............................53 88 3.30 TCP Connection based Events / Section 8.1.4..............55 89 3.31 BGP Messages based Events / Seciton 8.1.5................56 90 3.32 FSM Definition / Section 8.2.1...........................57 91 3.33 FSM and collision detection / Section 8.2.1.2............58 92 3.34 FSM Event numbers / Section 8.2.1.4......................58 93 3.35 Finite State Machine / Section 8.2.2.....................59 95 ^L 96 3.36 UPDATE Message Handling / Section 9......................59 97 3.37 Decision Process / Section 9.1...........................61 98 3.38 Phase 1: Calculation of Degree of Preference / Section 9.1.1 99 ..............................................................62 100 3.39 Phase 2: Route Selection / Section 9.1.2.................62 101 3.40 Route Resolvability Condition / Section 9.1.2.1..........64 102 3.41 Breaking Ties (Phase 2) / Section 9.1.2.2................65 103 3.42 Phase 3: Route Dissemination / Section 9.1.3.............66 104 3.43 Overlapping Routes / Section 9.1.4.......................67 105 3.44 Update-Send Process / Section 9.2........................69 106 3.45 Frequency of Route Advertisement / Section 9.2.1.1.......71 107 3.46 Aggregating Routing Information / Section 9.2.2.2........72 108 3.47 Route Selection Criteria / Section 9.3...................76 109 3.48 Originating BGP routes / Section 9.4.....................77 110 3.49 BGP Timers / Section 10..................................77 111 3.50 TCP options that may be used with BGP / Appendix E.......80 112 3.51 Reducing route flapping / Appendix F.2...................80 113 3.52 Complex AS_PATH aggregation / Appendix F.6...............81 114 3.53 Security Considerations..................................81 115 4. Additional BGP implementations Information....................81 116 4.1 Avici.....................................................81 117 4.2 Data Connection Ltd.......................................82 118 4.3 Nokia BGP.................................................83 119 Security Considerations..........................................84 120 Normative References.............................................84 121 Acknowledgments..................................................85 122 Authors' Addresses...............................................85 123 Copyright Statement..............................................86 125 1. Introduction 127 This revision of the BGP-4 standard [BGP4] updates the BGP standard 128 [RFC1771] to be in alignment with the deployments of the BGP-4 129 protocols. BGP-4 as deployed in the Internet encompasses both this 130 base specification and additional specifications such as TCP MD5 131 [RFC2385], BGP Route Reflectors [RFC 2796], BGP Confederations 132 [RFC3065], and BGP Route Refresh [RFC 2918]. 134 BGP as a widely deployed cornerstone of Internet technology 135 continues to add additional functionality as the needs within the 136 Internet requires. This survey has 259 detailed questions on the 137 compliance with the revised standard. 4 implementers (Alcatel, 138 Cisco, Laurel, NextHop) sent in implementation reports. Section 2 139 provides a compilation of those results. 141 Section 1.3 provides the quick survey results on inter-operability. 142 Section 1.4 provides an inter-operability of the 4 implementations. 144 ^L 145 Due to the large number of BGP implementations and the small number 146 of responses, the editors took an informal survey to determine if 147 the length of survey was an issue. Three implementers responded, 148 and all indicated the length of the survey was the issue. Section 3 149 gives this informal survey results. 151 The editors have compiled the submitted survey results and the 152 informal survey results. We do not guarantee the accuracy of the 153 responses. 155 2. Results of Survey 157 Significant Differences 159 For every item listed (259 questions), the respondents indicated 160 whether their implementation supports the Functionality/Description 161 or not (Y/N) indicated by the RFC2199 [RFC2119] language. Of the 259 162 questions in the survey, had two implementations giving an 163 affirmative response(two "y" or "y" and "O") except the following: 165 a) Must - Linked questions 212/213, regarding section 9.1.4 167 The linking of the questions lead to question 213 having three 168 vendors (Cisco, Laurel, and NextHop) give a "no" as the second 169 half of a question due to the format of the survey question. 170 (See the next section for details). 172 b) SHALL NOT - Question 228, regarding section 9.2.2.2 174 Three vendors (Alcatel, Cisco, Laurel), answered "N" to shall 175 not (meaning they did). One vendor (NextHop) indicated "O" 176 matching the specification. 178 Text: Routes that have different MULTI_EXIT_DISC attribute 179 SHALL NOT be aggregated. 181 c) SHOULD - 2 in appendix F (questions 257, 258) 183 Three vendors said no, one vendor said yes to question 257. 184 All four vendors indicated no to question 258. (Please note 185 that Appendix F is text section for optional support. 187 Text: Section F.2 - A BGP speaker which needs to withdraw a 188 destination and send an update about a more specific or 190 ^L 191 less specific route SHOULD combine them into the same 192 UPDATE message. 194 Text: Section F.6: The last instance (rightmost occurrence) of 195 that AS number is kept. 197 d) MAY - 1 in section 8.1.2.4, 1 in Section 10 (question 254) 199 Section 8: 3 "No", 1 yes 201 Text: "The Event numbers (1-28) utilized in this state machine 202 description aid in specifying the behavior of the BGP 203 state machine. Implementations MAY use these numbers to 204 provide network management information. The exact form of 205 a FSM or the FSM events are specific to each 206 implementation." 208 Editors note: Section 8.1.2.4 was written to allow existing 209 implementations to transition to the new event 210 numbering. It was expected over time (3 years) 211 that the FSM event numbering would be updated to 212 the new numbering. 214 Section 10: 3 "no" 215 Three vendors answered "no" configurable jitter time values. 216 One vendor indicated a configurable jitter timer value. 218 Text: A given BGP speaker MAY apply the same jitter to each of 219 these quantities regardless of the destinations to 220 which the updates are being sent; that is, jitter need 221 not be configured on a "per peer" basis. 223 Question: Is the jitter range configurable? 225 2.1 Differences 227 The following section provides a list of sections where all answers 228 were not "yes". This section is provided to allow the reader a short 229 cut to the interesting points. 231 Differences are found in Subsections: 233 ^L 234 MUST 235 97, 106, 107, 111, 122, 125, 138, 141, 213 237 SHALL 238 233, 239 240 SHALL NOT 241 228 243 SHOULD 244 42, 117, 132, 146, 152, 155, 156, 157, 158, 159, 160, 161, 163, 245 164, 165, 169, 170, 171, 173, 174, 175, 202, 225, 250, 255, 256 247 SHOULD NOT 248 226 250 MAY 251 67, 94, 121, 143, 180, 223, 247, 254 253 Other 254 236, 238 256 Linked Questions 258 212/213 260 Question 213 about the aggregation of routes had 3 "N" and 1 261 "Y". Questions 212 and 213 are grouped together. 263 Question 212 states: 264 "The decision process MUST either install both routes" or 265 Question 213: 266 "Aggregate the two routes and install the aggregated route, 267 provided that both routes have the same value of the 268 NEXT_HOP attribute" 270 The four respondents that said "Y" to question 212, said "N" to 271 questions 213. Given the context of the question, the "N" to 272 question 213 is appropriate. 274 2.2 Implementations and interoperability 276 Alcatel Cisco Laurel NextHop 277 Alcatel Y Y 278 Cisco Y 279 Laurel Y Y 280 NextHop Y Y 282 ^L 284 2.3 BGP Implementation Identification 286 1.6.0 Alcatel 287 Implementation Name/Version: 288 Alcatel 7750 BGP Implementation Release 1.3 289 Date: July 2003 290 Contact Name: Devendra Raut 291 Contact Email: Devendra.raut@Alcatel.com 293 1.6.1 Cisco 294 Implementation Name/Version: Cisco BGP Implementation, 12.0(27)S 295 Contact Name: Alvaro Retana 296 Date: 11/26/2003 298 1.6.2 Laurel 299 Implementation Name/Version: Laurel Networks 3.0 300 Contact Name: Manish Vora 301 Contact Email: vora@laurelnetworks.com 302 Date: 2/1/2004 304 1.6.3 NextHop Technologies 305 Implementation Name/Version: Gated NGC 2.0, 2.2 306 Date: January 2004 308 3. BGP4 Implementation Report 310 For every item listed, the respondents indicated whether their 311 implementation supports the Functionality/Description or not (Y/N) 312 according to the RFC2119 [2] language indicated. Any respondent 313 comments are included. If appropriate, the respondents indicated 314 with O the fact that the support is neither Y/N (an alternate 315 behavior, for example). Refer to the appropriate sections in [BGP4] 316 for additional details. 318 2.0 Summary of Operation / Section 3 320 2.0.1 Base Behavior 322 Functionality/Description: Is your implementation compatible with 323 the base behavior described in this section? 325 RFC2119: N/A 327 ^L 328 Alcatel Y/N/O/Comments: Y 329 Cisco Y/N/O/Comments: Y 330 Laurel Y/N/O/Comments: Y 331 NextHop Y/N/O/Comments: Y 333 2.0.2 Local Policy Changes 335 Functionality/Description: To allow local policy changes to have 336 the correct effect without resetting any BGP connections, a BGP 337 speaker SHOULD either (a) retain the current version of the 338 routes advertised to it by all of its peers for the duration of 339 the connection, or (b) make use of the Route Refresh extension 340 [RFC2918] 342 RFC2119: SHOULD 344 Alcatel Y/N/O/Comments: Y 345 Cisco Y/N/O/Comments: Y 346 Laurel Y/N/O/Comments: Y 347 NextHop Y/N/O/Comments: Y 349 3.1 Routes: Advertisement and Storage / Section 3.1 351 2.1.3 Withdraw routes from service 353 Functionality/Description: Does your implementation support the 354 three methods described in this section? 356 RFC2119: N/A 358 Alcatel Y/N/O/Comments: Y 359 Cisco Y/N/O/Comments: Y 360 Laurel Y/N/O/Comments: Y 361 NextHop Y/N/O/Comments: Y 363 2.1.4 Path attributes 365 Functionality/Description: Added to or modified before 366 advertising the route 368 RFC2119: MAY 370 Alcatel Y/N/O/Comments: Y 371 Cisco Y/N/O/Comments: Y 372 Laurel Y/N/O/Comments: Y 373 NextHop Y/N/O/Comments: Y 375 ^L 377 3.2 Routing Information Bases / Section 3.2 379 2.2.5 Routing Information Bases 381 Functionality/Description: Is your implementation compatible 382 with the RIB structure described in this section? 384 RFC2119: N/A 386 Alcatel Y/N/O/Comments: Y 387 Cisco Y/N/O/Comments: Y 388 Laurel Y/N/O/Comments: Y 389 NextHop Y/N/O/Comments: Y 391 2.2.6 Next Hop Resolution 393 Functionality/Description: The next hop for each route in the 394 Loc-RIB MUST be resolvable via the local BGP speaker's Routing 395 Table 397 RFC2119: MUST 399 Alcatel Y/N/O/Comments: Y 400 Cisco Y/N/O/Comments: Y 401 Laurel Y/N/O/Comments: Y 402 NextHop Y/N/O/Comments: Y 404 3.3 Message Formats / Section 4 406 2.3.7 Message Size 408 Functionality/Description: Does your implementation support the 409 message sizes described in this section? 411 RFC2119: N/A 413 Alcatel Y/N/O/Comments: Y 414 Cisco Y/N/O/Comments: Y 415 Laurel Y/N/O/Comments: Y 416 NextHop Y/N/O/Comments: Y 418 3.4 Message Header Format / Section 4.1 420 2.4.8 Marker 422 ^L 423 Functionality/Description: MUST be set to all ones 425 RFC2119: MUST 427 Alcatel Y/N/O/Comments: Y 428 Cisco Y/N/O/Comments: Y 429 Laurel Y/N/O/Comments: Y 430 NextHop Y/N/O/Comments: Y 432 2.4.9 Length 434 Functionality/Description: MUST always be at least 19 and no 435 greater than 4096 437 RFC2119: MUST 439 Alcatel Y/N/O/Comments: Y 440 Cisco Y/N/O/Comments: Y 441 Laurel Y/N/O/Comments: Y 442 NextHop Y/N/O/Comments: Y 444 2.4.10 Length 446 Functionality/Description: MAY be further constrained, depending 447 on the message type 449 RFC2119: MAY 451 Alcatel Y/N/O/Comments: Y 452 Cisco Y/N/O/Comments: Y 453 Laurel Y/N/O/Comments: Y 454 NextHop Y/N/O/Comments: Y 456 2.4.11 Message "padding" 458 Functionality/Description: No "padding" of extra data after the 459 message is allowed, so the Length field MUST have the smallest 460 value required given the rest of the message 462 RFC2119: MUST 464 Alcatel Y/N/O/Comments: Y 465 Cisco Y/N/O/Comments: Y 466 Laurel Y/N/O/Comments: Y 467 NextHop Y/N/O/Comments: Y 469 ^L 471 3.5 OPEN Message / Section 4.2 473 2.5.12 Hold Timer Calculation 475 Functionality/Description: Use the smaller of its configured 476 Hold Time and the Hold Time received in the OPEN message 478 RFC2119: MUST 480 Alcatel Y/N/O/Comments: Y 481 Cisco Y/N/O/Comments: Y 482 Laurel Y/N/O/Comments: Y 483 NextHop Y/N/O/Comments: Y 485 2.5.13 Minimum Hold Time 487 Functionality/Description: MUST be either zero or at least three 488 seconds 490 RFC2119: MUST 492 Alcatel Y/N/O/Comments: Y 493 Cisco Y/N/O/Comments: Y 494 Laurel Y/N/O/Comments: Y 495 NextHop Y/N/O/Comments: Y 497 2.5.14 Connection Rejection 499 Functionality/Description: Based on the Hold Time 501 RFC2119: MAY 503 Alcatel Y/N/O/Comments: Y 504 Cisco Y/N/O/Comments: Y Sends notification. 505 Laurel Y/N/O/Comments: Y 506 NextHop Y/N/O/Comments: Y 508 3.6 UPDATE Message Format / Section 4.3 510 2.6.15 UPDATE 512 Functionality/Description: Simultaneously advertise a feasible 513 route and withdraw multiple unfeasible routes from service 515 ^L 516 RFC2119: MAY 518 Alcatel Y/N/O/Comments: Y 519 Cisco Y/N/O/Comments: O We have capability to process this 520 functionality on receiving end but 521 we don't send feasible & unfeasible 522 simultaneously. 523 Laurel Y/N/O/Comments: Y 524 NextHop Y/N/O/Comments: Y 526 2.6.16 Transitive Bit Setting 528 Functionality/Description: For well-known attributes, the 529 Transitive bit MUST be set to 1 531 RFC2119: MUST 533 Alcatel Y/N/O/Comments: Y 534 Cisco Y/N/O/Comments: Y 535 Laurel Y/N/O/Comments: Y 536 NextHop Y/N/O/Comments: Y 538 2.6.17 Partial Bit Setting 540 Functionality/Description: For well-known attributes and for 541 optional non-transitive attributes the Partial bit MUST be set 542 to 0 544 RFC2119: MUST 546 Alcatel Y/N/O/Comments: Y 547 Cisco Y/N/O/Comments: Y 548 Laurel Y/N/O/Comments: Y 549 NextHop Y/N/O/Comments: Y 551 2.6.18 Attribute Flags octet sending 553 Functionality/Description: Lower-order four bits set to zero 555 RFC2119: MUST 557 Alcatel Y/N/O/Comments: Y 558 Cisco Y/N/O/Comments: Y 559 Laurel Y/N/O/Comments: Y 560 NextHop Y/N/O/Comments: Y 562 ^L 564 2.6.19 Attribute Flags octet receiving 566 Functionality/Description: Lower-order four bits ignored 568 RFC2119: MUST 570 Alcatel Y/N/O/Comments: Y 571 Cisco Y/N/O/Comments: Y 572 Laurel Y/N/O/Comments: Y 573 NextHop Y/N/O/Comments: Y 575 2.6.20 NEXT_HOP 577 Functionality/Description: Used as the next hop to the 578 destinations listed in the NLRI field of the UPDATE message 580 RFC2119: SHOULD 582 Alcatel Y/N/O/Comments: Y 583 Cisco Y/N/O/Comments: Y 584 Laurel Y/N/O/Comments: Y 585 NextHop Y/N/O/Comments: Y 587 2.6.21 MULTI_EXIT_DISC 589 Functionality/Description: Used by a BGP speaker's decision 590 process to discriminate among multiple entry points to a 591 neighboring autonomous system 593 RFC2119: MAY 595 Alcatel Y/N/O/Comments: Y 596 Cisco Y/N/O/Comments: Y 597 Laurel Y/N/O/Comments: Y 598 NextHop Y/N/O/Comments: Y 600 2.6.22 AGGREGATOR IP Address 602 Functionality/Description: Same address as the one used for the 603 BGP Identifier of the speaker 605 RFC2119: SHOULD 607 Alcatel Y/N/O/Comments: Y Default behavior. Can be configured 608 different from BGP ID. 610 ^L 612 Cisco Y/N/O/Comments: Y 613 Laurel Y/N/O/Comments: Y 614 NextHop Y/N/O/Comments: Y 616 2.6.23 UPDATE messages that include the same address prefix in the 617 WITHDRAWN ROUTES and Network Layer Reachability Information fields 619 Functionality/Description: UPDATE messages SHOULD NOT include 620 that information 622 RFC2119: SHOULD NOT 624 Alcatel Y/N/O/Comments: Y 625 Cisco Y/N/O/Comments: Y 626 Laurel Y/N/O/Comments: Y 627 NextHop Y/N/O/Comments: Y 629 2.6.24 UPDATE messages that include the same address prefix in the 630 WITHDRAWN ROUTES and Network Layer Reachability Information fields 632 Functionality/Description: The BGP speaker MUST be able to handle 633 them 635 RFC2119: MUST 637 Alcatel Y/N/O/Comments: Y 638 Cisco Y/N/O/Comments: Y 639 Laurel Y/N/O/Comments: Y 640 NextHop Y/N/O/Comments: Y 642 2.6.25 UPDATE messages that include the same address prefix in the 643 WITHDRAWN ROUTES and Network Layer Reachability Information fields 645 Functionality/Description: Treated as if the WITHDRAWN ROUTES 646 doesn't contain the address prefix 648 RFC2119: SHOULD 650 Alcatel Y/N/O/Comments: Y Withdrawn routes are processed 651 before NLRI fields. Hence we get the 652 desired behavior. 653 Cisco Y/N/O/Comments: Y 654 Laurel Y/N/O/Comments: Y 655 NextHop Y/N/O/Comments: Y 657 ^L 659 3.7 KEEPALIVE Message Format / Section 4.4 661 2.7.26 Maximum KEEPALIVE frequency 663 Functionality/Description: Not greater than one second 665 RFC2119: MUST NOT 667 Alcatel Y/N/O/Comments: Y 668 Cisco Y/N/O/Comments: Y 669 Laurel Y/N/O/Comments: Y 670 NextHop Y/N/O/Comments: Y 672 2.7.27 KEEPALIVE messages rate 674 Functionality/Description: Adjusted as a function of the Hold 675 Time interval 677 RFC2119: MAY 679 Alcatel Y/N/O/Comments: Y 680 Cisco Y/N/O/Comments: Y 681 Laurel Y/N/O/Comments: Y 682 NextHop Y/N/O/Comments: Y 684 2.7.28 Negotiated Hold Time of 0 686 Functionality/Description: No KEEPALIVEs sent 688 RFC2119: MUST NOT 690 Alcatel Y/N/O/Comments: Y 691 Cisco Y/N/O/Comments: Y 692 Laurel Y/N/O/Comments: Y 693 NextHop Y/N/O/Comments: Y 695 3.8 NOTIFICATION Message Format / Section 4.5 697 2.8.29 NOTIFICATION Message 699 Functionality/Description: Does your implementation support the 700 NOTIFICATION Message as described in this section? 702 RFC2119: N/A 704 Alcatel Y/N/O/Comments: Y 706 ^L 707 Cisco Y/N/O/Comments: Y 708 Laurel Y/N/O/Comments: Y 709 NextHop Y/N/O/Comments: Y 711 3.9 Path Attributes /Section 5 713 2.9.30 Path attributes 715 Functionality/Description: Does your implementation support the 716 path attributes as described in this section? 718 RFC2119: N/A 720 Alcatel Y/N/O/Comments: Y 721 Cisco Y/N/O/Comments: Y 722 Laurel Y/N/O/Comments: Y 723 NextHop Y/N/O/Comments: Y 725 2.9.31 Well-known attributes 727 Functionality/Description: Recognized by all BGP implementations 729 RFC2119: MUST 731 Alcatel Y/N/O/Comments: Y 732 Cisco Y/N/O/Comments: Y 733 Laurel Y/N/O/Comments: Y 734 NextHop Y/N/O/Comments: Y 736 2.9.32 Mandatory Attributes 738 Functionality/Description: Included in every UPDATE message that 739 contains NLRI 741 RFC2119: MUST 743 Alcatel Y/N/O/Comments: Y 744 Cisco Y/N/O/Comments: Y 745 Laurel Y/N/O/Comments: Y 746 NextHop Y/N/O/Comments: Y 748 2.9.33/34 Discretionary Attributes 750 Functionality/Description: Sent in a particular UPDATE message 752 ^L 753 RFC2119: MAY or MAY NOT 755 Alcatel Y/N/O/Comments: Y 756 Cisco Y/N/O/Comments: Y 757 Laurel Y/N/O/Comments: Y 758 NextHop Y/N/O/Comments: Y 760 2.9.35 Well-known attributes 762 Functionality/Description: Passed along (after proper updating, 763 if necessary) to other BGP peers 765 RFC2119: MUST 767 Alcatel Y/N/O/Comments: Y 768 Cisco Y/N/O/Comments: Y 769 Laurel Y/N/O/Comments: Y 770 NextHop Y/N/O/Comments: Y 772 2.9.36 Optional Attributes 774 Functionality/Description: In addition to well-known attributes, 775 each path MAY contain one or more optional attributes 777 RFC2119: MAY 779 Alcatel Y/N/O/Comments: Y 780 Cisco Y/N/O/Comments: Y 781 Laurel Y/N/O/Comments: Y 782 NextHop Y/N/O/Comments: Y 784 2.9.37 Unrecognized transitive optional attributes 786 Functionality/Description: Accepted 788 RFC2119: SHOULD 790 Alcatel Y/N/O/Comments: Y 791 Cisco Y/N/O/Comments: Y 792 Laurel Y/N/O/Comments: Y 793 NextHop Y/N/O/Comments: Y 795 2.9.38 Partial Bit for unrecognized transitive optional attributes 797 Functionality/Description: Set to 1 if the attribute is accepted 799 ^L 800 and passed to other BGP speakers 802 RFC2119: MUST 804 Alcatel Y/N/O/Comments: Y 805 Cisco Y/N/O/Comments: Y 806 Laurel Y/N/O/Comments: Y 807 NextHop Y/N/O/Comments: Y 809 2.9.39 Unrecognized non-transitive optional attributes 811 Functionality/Description: Quietly ignored and not passed along 812 to other BGP peers 814 RFC2119: MUST 816 Alcatel Y/N/O/Comments: Y 817 Cisco Y/N/O/Comments: Y 818 Laurel Y/N/O/Comments: Y 819 NextHop Y/N/O/Comments: Y 821 2.9.40 New transitive optional attributes 823 Functionality/Description: Attached to the path by the 824 originator or by any other BGP speaker in the path 826 RFC2119: MAY 828 Alcatel Y/N/O/Comments: Y 829 Cisco Y/N/O/Comments: Y 830 Laurel Y/N/O/Comments: Y 831 NextHop Y/N/O/Comments: Y 833 2.9.41 Optional Attributes 835 Functionality/Description: Updated by BGP speakers in the path 837 RFC2119: MAY 839 Alcatel Y/N/O/Comments: Y 840 Cisco Y/N/O/Comments: Y 841 Laurel Y/N/O/Comments: Y 842 NextHop Y/N/O/Comments: Y 844 2.9.42 Path Attributes 846 ^L 847 Functionality/Description: Ordered in ascending order of 848 attribute type 850 RFC2119: SHOULD 852 Alcatel Y/N/O/Comments: Y 853 Cisco Y/N/O/Comments: O All attributes are ordered in 854 ascending order except Extended 855 Community, which is type 16 but we 856 send it out after community 857 attribute. 858 Laurel Y/N/O/Comments: Y except for MBGP which is always last 859 NextHop Y/N/O/Comments: Y 861 2.9.43 Out of order received path attributes 863 Functionality/Description: Receiver MUST be able to handle 865 RFC2119: MUST 867 Alcatel Y/N/O/Comments: Y 868 Cisco Y/N/O/Comments: Y 869 Laurel Y/N/O/Comments: Y 870 NextHop Y/N/O/Comments: Y 872 2.9.44 Mandatory Attributes 874 Functionality/Description: Present in all exchanges if NLRI are 875 contained in the UPDATE message 877 RFC2119: MUST 879 Alcatel Y/N/O/Comments: Y 880 Cisco Y/N/O/Comments: Y 881 Laurel Y/N/O/Comments: Y 882 NextHop Y/N/O/Comments: Y 884 3.10 ORIGIN / Section 5.1.1 886 2.10.45 ORIGIN 888 Functionality/Description: Value SHOULD NOT be changed by any 889 speaker, except the originator 891 RFC2119: SHOULD NOT 893 ^L 894 Alcatel Y/N/O/Comments: Y 895 Cisco Y/N/O/Comments: Y 896 Laurel Y/N/O/Comments: Y 897 NextHop Y/N/O/Comments: Y 899 3.11 AS_PATH / Section 5.1.2 901 2.11.46 AS_PATH 903 Functionality/Description: Not modified when advertising a route 904 to an internal peer 906 RFC2119: SHALL NOT 908 Alcatel Y/N/O/Comments: Y 909 Cisco Y/N/O/Comments: Y 910 Laurel Y/N/O/Comments: Y 911 NextHop Y/N/O/Comments: Y 913 2.11.47 Segment Overflow 915 Functionality/Description: If the act of prepending will cause 916 an overflow in the AS_PATH segment, i.e. more than 255 ASs, it 917 SHOULD prepend a new segment of type AS_SEQUENCE and prepend its 918 own AS number to this new segment 920 RFC2119: SHOULD 922 Alcatel Y/N/O/Comments: Y 923 Cisco Y/N/O/Comments: Y 924 Laurel Y/N/O/Comments: Y 925 NextHop Y/N/O/Comments: Y 927 2.11.48 Prepending 929 Functionality/Description: The local system MAY include/prepend 930 more than one instance of its own AS number in the AS_PATH 931 attribute 933 RFC2119: MAY 935 Alcatel Y/N/O/Comments: Y 936 Cisco Y/N/O/Comments: Y 937 Laurel Y/N/O/Comments: Y 938 NextHop Y/N/O/Comments: Y 940 ^L 942 3.12 NEXT_HOP / Section 5.1.3 944 2.12.49 NEXT_HOP 946 Functionality/Description: Used as the next hop to the 947 destinations listed in the UPDATE message 949 RFC2119: SHOULD 951 Alcatel Y/N/O/Comments: Y 952 Cisco Y/N/O/Comments: Y 953 Laurel Y/N/O/Comments: Y 954 NextHop Y/N/O/Comments: Y 956 2.12.50 NEXT_HOP 958 Functionality/Description: When sending a message to an internal 959 peer, if the route is not locally originated, the BGP speaker 960 SHOULD NOT modify the NEXT_HOP attribute, unless it has been 961 explicitly configured to announce its own IP address as the 962 NEXT_HOP 964 RFC2119: SHOULD NOT 966 Alcatel Y/N/O/Comments: Y 967 Cisco Y/N/O/Comments: Y 968 Laurel Y/N/O/Comments: Y 969 NextHop Y/N/O/Comments: Y 971 2.12.51 NEXT_HOP 973 Functionality/Description: When announcing a locally originated 974 route to an internal peer, the BGP speaker SHOULD use as the 975 NEXT_HOP the interface address of the router through which the 976 announced network is reachable for the speaker 978 RFC2119: SHOULD 980 Alcatel Y/N/O/Comments: Y 981 Cisco Y/N/O/Comments: Y 982 Laurel Y/N/O/Comments: Y 983 NextHop Y/N/O/Comments: Y 985 2.12.52 NEXT_HOP 987 ^L 988 Functionality/Description: If the route is directly connected to 989 the speaker, or the interface address of the router through 990 which the announced network is reachable for the speaker is the 991 internal peer's address, then the BGP speaker SHOULD use for the 992 NEXT_HOP attribute its own IP address (the address of the 993 interface that is used to reach the peer) 995 RFC2119: SHOULD 997 Alcatel Y/N/O/Comments: Y 998 Cisco Y/N/O/Comments: Y 999 Laurel Y/N/O/Comments: Y 1000 NextHop Y/N/O/Comments: Y 1002 2.12.53 "first party" NEXT_HOP 1004 Functionality/Description: If the external peer to which the 1005 route is being advertised shares a common subnet with one of the 1006 interfaces of the announcing BGP speaker, the speaker MAY use 1007 the IP address associated with such an interface in the NEXT_HOP 1008 attribute 1010 RFC2119: MAY 1012 Alcatel Y/N/O/Comments: Y 1013 Cisco Y/N/O/Comments: Y 1014 Laurel Y/N/O/Comments: Y 1015 NextHop Y/N/O/Comments: Y 1017 2.12.54 Default NEXT_HOP 1019 Functionality/Description: IP address of the interface that the 1020 speaker uses to establish the BGP connection to peer X 1022 RFC2119: SHOULD 1024 Alcatel Y/N/O/Comments: Y 1025 Cisco Y/N/O/Comments: Y 1026 Laurel Y/N/O/Comments: Y 1027 NextHop Y/N/O/Comments: Y 1029 2.12.55 NEXT_HOP Propagation 1031 Functionality/Description: The speaker MAY be configured to 1032 propagate the NEXT_HOP attribute. In this case when advertising 1034 ^L 1035 a route that the speaker learned from one of its peers, the 1036 NEXT_HOP attribute of the advertised route is exactly the same 1037 as the NEXT_HOP attribute of the learned route (the speaker just 1038 doesn't modify the NEXT_HOP attribute) 1040 RFC2119: MAY 1042 Alcatel Y/N/O/Comments: O 1043 Cisco Y/N/O/Comments: Y 1044 Laurel Y/N/O/Comments: Y 1045 NextHop Y/N/O/Comments: Y 1047 2.12.56 Third party NEXT_HOP 1049 Functionality/Description: MUST be able to support disabling it 1051 RFC2119: MUST 1053 Alcatel Y/N/O/Comments: Y 1054 Cisco Y/N/O/Comments: Y 1055 Laurel Y/N/O/Comments: Y 1056 NextHop Y/N/O/Comments: Y 1058 2.12.57 NEXT_HOP 1060 Functionality/Description: A route originated by a BGP speaker 1061 SHALL NOT be advertised to a peer using an address of that peer 1062 as NEXT_HOP 1064 RFC2119: SHALL NOT 1066 Alcatel Y/N/O/Comments: Y 1067 Cisco Y/N/O/Comments: Y 1068 Laurel Y/N/O/Comments: Y 1069 NextHop Y/N/O/Comments: Y 1071 2.12.58 NEXT_HOP 1073 Functionality/Description: A BGP speaker SHALL NOT install a 1074 route with itself as the next hop 1076 RFC2119: SHALL NOT 1078 Alcatel Y/N/O/Comments: Y 1079 Cisco Y/N/O/Comments: Y 1080 Laurel Y/N/O/Comments: Y 1082 ^L 1083 NextHop Y/N/O/Comments: Y 1085 2.12.59 NEXT_HOP 1087 Functionality/Description: Used to determine the actual outbound 1088 interface and immediate next-hop address that SHOULD be used to 1089 forward transit packets to the associated destinations 1091 RFC2119: SHOULD 1093 Alcatel Y/N/O/Comments: Y 1094 Cisco Y/N/O/Comments: Y 1095 Laurel Y/N/O/Comments: Y 1096 NextHop Y/N/O/Comments: Y 1098 2.12.60 Resolved NEXT_HOP IP Address 1100 Functionality/Description: If the entry specifies an attached 1101 subnet, but does not specify a next-hop address, then the 1102 address in the NEXT_HOP attribute SHOULD be used as the 1103 immediate next-hop address 1105 RFC2119: SHOULD 1107 Alcatel Y/N/O/Comments: Y 1108 Cisco Y/N/O/Comments: Y 1109 Laurel Y/N/O/Comments: Y 1110 NextHop Y/N/O/Comments: Y 1112 2.12.61 Resolved NEXT_HOP IP Address 1114 Functionality/Description: If the entry also specifies the 1115 next-hop address, this address SHOULD be used as the immediate 1116 next-hop address for packet forwarding 1118 RFC2119: SHOULD 1120 Alcatel Y/N/O/Comments: Y 1121 Cisco Y/N/O/Comments: Y 1122 Laurel Y/N/O/Comments: Y 1123 NextHop Y/N/O/Comments: Y 1125 3.13 MULTI_EXIT_DISC / Section 5.1.4 1127 2.13.62 Preferred metric 1129 ^L 1130 Functionality/Description: Lowest value 1132 RFC2119: SHOULD 1134 Alcatel Y/N/O/Comments: Y 1135 Cisco Y/N/O/Comments: Y 1136 Laurel Y/N/O/Comments: Y 1137 NextHop Y/N/O/Comments: Y 1139 2.13.63 MULTI_EXIT_DISC 1141 Functionality/Description: If received over EBGP, the 1142 MULTI_EXIT_DISC attribute MAY be propagated over IBGP to other 1143 BGP speakers within the same AS 1145 RFC2119: MAY 1147 Alcatel Y/N/O/Comments: Y 1148 Cisco Y/N/O/Comments: Y 1149 Laurel Y/N/O/Comments: Y 1150 NextHop Y/N/O/Comments: Y 1152 2.13.64 MULTI_EXIT_DISC 1154 Functionality/Description: If received from a neighboring AS, it 1155 MUST NOT be propagated to other neighboring ASes 1157 RFC2119: MUST NOT 1159 Alcatel Y/N/O/Comments: Y 1160 Cisco Y/N/O/Comments: Y 1161 Laurel Y/N/O/Comments: Y 1162 NextHop Y/N/O/Comments: Y 1164 2.13.65 Remove MULTI_EXIT_DISC 1166 Functionality/Description: Local configuration mechanism to 1167 remove the attribute from a route 1169 RFC2119: MUST 1171 Alcatel Y/N/O/Comments: Y 1172 Cisco Y/N/O/Comments: Y 1173 Laurel Y/N/O/Comments: Y 1174 NextHop Y/N/O/Comments: Y 1176 ^L 1178 2.13.66 Remove MULTI_EXIT_DISC 1180 Functionality/Description: Done prior to determining the degree 1181 of preference of the route and performing route selection 1183 RFC2119: MAY 1185 Alcatel Y/N/O/Comments: Y 1186 Cisco Y/N/O/Comments: Y 1187 Laurel Y/N/O/Comments: Y 1188 NextHop Y/N/O/Comments: Y 1190 2.13.67 MULTI_EXIT_DISC Alteration 1192 Functionality/Description: An implementation MAY also (based on 1193 local configuration) alter the value of the MULTI_EXIT_DISC 1194 attribute received over EBGP 1196 RFC2119: MAY 1198 Alcatel Y/N/O/Comments: O 1199 Cisco Y/N/O/Comments: Y 1200 Laurel Y/N/O/Comments: Y 1201 NextHop Y/N/O/Comments: Y 1203 2.13.68 MULTI_EXIT_DISC Alteration 1205 Functionality/Description: Done prior to determining the degree 1206 of preference of the route and performing route selection 1208 RFC2119: MAY 1210 Alcatel Y/N/O/Comments: Y 1211 Cisco Y/N/O/Comments: Y 1212 Laurel Y/N/O/Comments: Y 1213 NextHop Y/N/O/Comments: Y 1215 3.14 LOCAL_PREF / Section 5.1.5 1217 2.14.69 LOCAL_PREF 1219 Functionality/Description: Included in all UPDATE messages that 1220 a given BGP speaker sends to the other internal peers 1222 ^L 1223 RFC2119: SHALL 1225 Alcatel Y/N/O/Comments: Y 1226 Cisco Y/N/O/Comments: Y 1227 Laurel Y/N/O/Comments: Y 1228 NextHop Y/N/O/Comments: Y 1230 2.14.70 Degree of Preference 1232 Functionality/Description: Calculated for each external route 1233 based on the locally configured policy, and included when 1234 advertising a route to its internal peers 1236 RFC2119: SHALL 1238 Alcatel Y/N/O/Comments: Y 1239 Cisco Y/N/O/Comments: Y 1240 Laurel Y/N/O/Comments: Y 1241 NextHop Y/N/O/Comments: Y 1243 2.14.71 LOCAL_PREF 1245 Functionality/Description: Higher degree of preference MUST be 1246 preferred 1248 RFC2119: MUST 1250 Alcatel Y/N/O/Comments: Y 1251 Cisco Y/N/O/Comments: Y 1252 Laurel Y/N/O/Comments: Y 1253 NextHop Y/N/O/Comments: Y 1255 2.14.72 LOCAL_PREF 1257 Functionality/Description: Not included in UPDATE messages sent 1258 to external peers, except for the case of BGP Confederations 1259 [RFC3065] 1261 RFC2119: MUST NOT 1263 Alcatel Y/N/O/Comments: Y 1264 Cisco Y/N/O/Comments: Y 1265 Laurel Y/N/O/Comments: Y 1266 NextHop Y/N/O/Comments: Y 1268 ^L 1270 2.14.73 LOCAL_PREF 1272 Functionality/Description: Ignored if received from an external 1273 peer, except for the case of BGP Confederations [RFC3065] 1275 RFC2119: MUST 1277 Alcatel Y/N/O/Comments: Y 1278 Cisco Y/N/O/Comments: Y 1279 Laurel Y/N/O/Comments: Y 1280 NextHop Y/N/O/Comments: Y 1282 3.15 ATOMIC_AGGREGATE / Section 5.1.6 1284 2.15.74 ATOMIC_AGGREGATE 1286 Functionality/Description: Included if an aggregate excludes at 1287 least some of the AS numbers present in the AS_PATH of the 1288 routes that are aggregated as a result of dropping the AS_SET 1290 RFC2119: SHOULD 1292 Alcatel Y/N/O/Comments: Y 1293 Cisco Y/N/O/Comments: Y 1294 Laurel Y/N/O/Comments: Y 1295 NextHop Y/N/O/Comments: Y 1297 2.15.75 Received ATOMIC_AGGREGATE 1299 Functionality/Description: BGP speaker SHOULD NOT remove the 1300 attribute from the route when propagating it to other speakers 1302 RFC2119: SHOULD NOT 1304 Alcatel Y/N/O/Comments: Y 1305 Cisco Y/N/O/Comments: Y 1306 Laurel Y/N/O/Comments: Y 1307 NextHop Y/N/O/Comments: Y 1309 2.15.76 Received ATOMIC_AGGREGATE 1311 Functionality/Description: BGP speaker MUST NOT make any NLRI of 1312 that route more specific (as defined in 9.1.4) 1314 RFC2119: MUST NOT 1316 ^L 1317 Alcatel Y/N/O/Comments: Y 1318 Cisco Y/N/O/Comments: Y 1319 Laurel Y/N/O/Comments: Y 1320 NextHop Y/N/O/Comments: Y 1322 3.16 AGGREGATOR / Section 5.1.7 1324 2.16.77 AGGREGATOR 1326 Functionality/Description: Included in updates which are formed 1327 by aggregation (see Section 9.2.2.2) 1329 RFC2119: MAY 1331 Alcatel Y/N/O/Comments: Y 1332 Cisco Y/N/O/Comments: Y 1333 Laurel Y/N/O/Comments: Y 1334 NextHop Y/N/O/Comments: Y 1336 2.16.78 AGGREGATOR 1338 Functionality/Description: Added by the BGP speaker performing 1339 route aggregation 1341 RFC2119: MAY 1343 Alcatel Y/N/O/Comments: Y 1344 Cisco Y/N/O/Comments: Y 1345 Laurel Y/N/O/Comments: Y 1346 NextHop Y/N/O/Comments: Y 1348 2.16.79 AGGREGATOR 1350 Functionality/Description: Contain local AS number and IP 1351 address 1353 RFC2119: SHALL 1355 Alcatel Y/N/O/Comments: Y Default behavior. Can be configured 1356 different from BGP ID. 1357 Cisco Y/N/O/Comments: Y 1358 Laurel Y/N/O/Comments: Y 1359 NextHop Y/N/O/Comments: Y 1361 2.16.80 AGGREGATOR IP Address 1363 ^L 1364 Functionality/Description: The same as the BGP Identifier of the 1365 speaker 1367 RFC2119: SHOULD 1369 Alcatel Y/N/O/Comments: Y 1370 Cisco Y/N/O/Comments: Y 1371 Laurel Y/N/O/Comments: Y 1372 NextHop Y/N/O/Comments: Y 1374 3.17 BGP Error Handling / Section 6 1376 2.17.81 Error Handling 1378 Functionality/Description: Is your implementation compatible 1379 with the error handling procedures described in this section? 1381 RFC2119: N/A 1383 Alcatel Y/N/O/Comments: Y 1384 Cisco Y/N/O/Comments: Y 1385 Laurel Y/N/O/Comments: Y 1386 NextHop Y/N/O/Comments: Y 1388 2.17.82 Error Subcode 1390 Functionality/Description: Zero, if it is not specified 1392 RFC2119: MUST 1394 Alcatel Y/N/O/Comments: Y 1395 Cisco Y/N/O/Comments: Y 1396 Laurel Y/N/O/Comments: Y 1397 NextHop Y/N/O/Comments: Y 1399 3.18 Message Header Error Handling / Section 6.1 1401 2.18.83 Message Header Errors 1403 Functionality/Description: Indicated by sending the NOTIFICATION 1404 message with Error Code Message Header Error 1406 RFC2119: MUST 1408 Alcatel Y/N/O/Comments: Y 1410 ^L 1411 Cisco Y/N/O/Comments: Y 1412 Laurel Y/N/O/Comments: Y 1413 NextHop Y/N/O/Comments: Y 1415 2.18.84 Synchronization Error 1417 Functionality/Description: Error Subcode MUST be set to 1418 Connection Not Synchronized 1420 RFC2119: MUST 1422 Alcatel Y/N/O/Comments: Y 1423 Cisco Y/N/O/Comments: Y 1424 Laurel Y/N/O/Comments: Y 1425 NextHop Y/N/O/Comments: Y 1427 2.18.85 Message Length 1429 Functionality/Description: Use the Bad Message Length Error 1430 Subcode to indicate an incorrect message length 1432 RFC2119: MUST 1434 Alcatel Y/N/O/Comments: Y 1435 Cisco Y/N/O/Comments: Y 1436 Laurel Y/N/O/Comments: Y 1437 NextHop Y/N/O/Comments: Y 1439 2.18.86 Bad Message Length 1441 Functionality/Description: The Data field MUST contain the 1442 erroneous Lentgh field 1444 RFC2119: MUST 1446 Alcatel Y/N/O/Comments: Y 1447 Cisco Y/N/O/Comments: Y 1448 Laurel Y/N/O/Comments: Y 1449 NextHop Y/N/O/Comments: Y 1451 2.18.87 Type Field 1453 Functionality/Description: If the Type field of the message 1454 header is not recognized, then the Error Subcode MUST be set to 1455 Bad Message Type 1457 ^L 1458 RFC2119: MUST 1460 Alcatel Y/N/O/Comments: Y 1461 Cisco Y/N/O/Comments: Y 1462 Laurel Y/N/O/Comments: Y 1463 NextHop Y/N/O/Comments: Y 1465 2.18.88 Bad Message Type 1467 Functionality/Description: The Data field MUST contain the 1468 erroneous Type field 1470 RFC2119: MUST 1472 Alcatel Y/N/O/Comments: Y 1473 Cisco Y/N/O/Comments: Y 1474 Laurel Y/N/O/Comments: Y 1475 NextHop Y/N/O/Comments: Y 1477 3.19 OPEN message error handling / Section 6.2 1479 2.19.89 OPEN Message Errors 1481 Functionality/Description: Indicated by sending the NOTIFICATION 1482 message with Error Code OPEN Message Error 1484 RFC2119: MUST 1486 Alcatel Y/N/O/Comments: Y 1487 Cisco Y/N/O/Comments: Y 1488 Laurel Y/N/O/Comments: Y 1489 NextHop Y/N/O/Comments: Y 1491 2.19.90 Version Number not Supported 1493 Functionality/Description: The Error Subcode MUST be set to 1494 Unsupported Version Number 1496 RFC2119: MUST 1498 Alcatel Y/N/O/Comments: Y 1499 Cisco Y/N/O/Comments: Y 1500 Laurel Y/N/O/Comments: Y 1501 NextHop Y/N/O/Comments: Y 1503 ^L 1505 2.19.91 Unnacceptable Autonomous System Field 1507 Functionality/Description: The Error Subcode MUST be set to Bad 1508 Peer AS 1510 RFC2119: MUST 1512 Alcatel Y/N/O/Comments: Y 1513 Cisco Y/N/O/Comments: Y 1514 Laurel Y/N/O/Comments: Y 1515 NextHop Y/N/O/Comments: Y 1517 2.19.92 Unacceptable Hold Time Error Subcode 1519 Functionality/Description: Used if the Hold Time field of the 1520 OPEN message is unacceptable 1522 RFC2119: MUST 1524 Alcatel Y/N/O/Comments: Y 1525 Cisco Y/N/O/Comments: Y 1526 Laurel Y/N/O/Comments: Y 1527 NextHop Y/N/O/Comments: Y 1529 2.19.93 Hold Time Rejection 1531 Functionality/Description: Values of one or two seconds 1533 RFC2119: MUST 1535 Alcatel Y/N/O/Comments: Y 1536 Cisco Y/N/O/Comments: Y 1537 Laurel Y/N/O/Comments: Y 1538 NextHop Y/N/O/Comments: Y 1540 2.19.94 Hold Time Rejection 1542 Functionality/Description: An implementation may reject any 1543 proposed Hold Time 1545 RFC2119: MAY 1547 Alcatel Y/N/O/Comments: Y 1548 Cisco Y/N/O/Comments: Y 1549 Laurel Y/N/O/Comments: N 1551 ^L 1552 NextHop Y/N/O/Comments: Y 1554 2.19.95 Hold Time 1556 Functionality/Description: If accepted, then the negotiated 1557 value MUST be used 1559 RFC2119: MUST 1561 Alcatel Y/N/O/Comments: Y 1562 Cisco Y/N/O/Comments: Y 1563 Laurel Y/N/O/Comments: Y 1564 NextHop Y/N/O/Comments: Y 1566 2.19.96 Syntactically Incorrect BGP Identifier 1568 Functionality/Description: The Error Subcode MUST be set to Bad 1569 BGP Identifier 1571 RFC2119: MUST 1573 Alcatel Y/N/O/Comments: Y 1574 Cisco Y/N/O/Comments: Y 1575 Laurel Y/N/O/Comments: Y 1576 NextHop Y/N/O/Comments: Y 1578 2.19.97 Not recognized Optional Parameters 1580 Functionality/Description: The Error Subcode MUST be set to 1581 Unsupported Optional Parameters 1583 RFC2119: MUST 1585 Alcatel Y/N/O/Comments: Y 1586 Cisco Y/N/O/Comments: N We may fix this. 1587 Laurel Y/N/O/Comments: Y 1588 NextHop Y/N/O/Comments: Y 1590 2.19.98 Recognized but Malformed Optional Parameters 1592 Functionality/Description: The Error Subcode MUST be set to 0 1593 (Unspecific) 1595 RFC2119: MUST 1597 ^L 1598 Alcatel Y/N/O/Comments: Y 1599 Cisco Y/N/O/Comments: N 1600 Laurel Y/N/O/Comments: Y 1601 NextHop Y/N/O/Comments: Y 1603 3.20 UPDATE message error handling / Section 6.3 1605 2.20.99 UPDATE Message Errors 1607 Functionality/Description: Indicated by sending the 1608 NOTIFICATION message with Error Code UPDATE Message Error 1610 RFC2119: MUST 1612 Alcatel Y/N/O/Comments: Y 1613 Cisco Y/N/O/Comments: Y 1614 Laurel Y/N/O/Comments: Y 1615 NextHop Y/N/O/Comments: Y 1617 2.20.100 Too Large 1619 Functionality/Description: If the Withdrawn Routes Length or 1620 Total Attribute Length is too large, then the Error Subcode MUST 1621 be set to Malformed Attribute List 1623 RFC2119: MUST 1625 Alcatel Y/N/O/Comments: Y 1626 Cisco Y/N/O/Comments: Y 1627 Laurel Y/N/O/Comments: Y 1628 NextHop Y/N/O/Comments: Y 1630 2.20.101 Conflicting Flags 1632 Functionality/Description: If any recognized attribute has 1633 Attribute Flags that conflict with the Attribute Type Code, then 1634 the Error Subcode MUST be set to Attribute Flags Error 1636 RFC2119: MUST 1638 Alcatel Y/N/O/Comments: Y 1639 Cisco Y/N/O/Comments: Y 1640 Laurel Y/N/O/Comments: Y 1641 NextHop Y/N/O/Comments: Y 1643 ^L 1645 2.20.102 Conflicting Flags 1647 Functionality/Description: The Data field MUST contain the 1648 erroneous attribute 1650 RFC2119: MUST 1652 Alcatel Y/N/O/Comments: Y 1653 Cisco Y/N/O/Comments: Y 1654 Laurel Y/N/O/Comments: Y 1655 NextHop Y/N/O/Comments: Y 1657 2.20.103 Conflicting Length 1659 Functionality/Description: If any recognized attribute has 1660 Attribute Length that conflicts with the expected length, then 1661 the Error Subcode MUST be set to Attribute Length Error 1663 RFC2119: MUST 1665 Alcatel Y/N/O/Comments: Y 1666 Cisco Y/N/O/Comments: Y 1667 Laurel Y/N/O/Comments: Y 1668 NextHop Y/N/O/Comments: Y 1670 2.20.104 Conflicting Length 1672 Functionality/Description: The Data field MUST contain the 1673 erroneous attribute 1675 RFC2119: MUST 1677 Alcatel Y/N/O/Comments: Y 1678 Cisco Y/N/O/Comments: Y 1679 Laurel Y/N/O/Comments: Y 1680 NextHop Y/N/O/Comments: Y 1682 2.20.105 Missing Mandatory Well-Known Attributes 1684 Functionality/Description: The Error Subcode MUST be set to 1685 Missing Well-known Attribute 1687 RFC2119: MUST 1689 Alcatel Y/N/O/Comments: Y 1690 Cisco Y/N/O/Comments: Y 1692 ^L 1693 Laurel Y/N/O/Comments: Y 1694 NextHop Y/N/O/Comments: Y 1696 2.20.106 Missing Mandatory Well-Known Attributes 1698 Functionality/Description: The Data field MUST contain the 1699 Attribute Type Code of the missing well-known attribute 1701 RFC2119: MUST 1703 Alcatel Y/N/O/Comments: Y 1704 Cisco Y/N/O/Comments: N We plan to fix this in future. 1705 Laurel Y/N/O/Comments: Y 1706 NextHop Y/N/O/Comments: Y 1708 2.20.107 Unrecognized Mandatory Well-Known Attributes 1710 Functionality/Description: The Error Subcode MUST be set to 1711 Unrecognized Well-known Attribute 1713 RFC2119: MUST 1715 Alcatel Y/N/O/Comments: Y 1716 Cisco Y/N/O/Comments: N We set error subcode to Attribute 1717 Flags Error, but we intend to 1718 correct this soon. 1719 Laurel Y/N/O/Comments: Y 1720 NextHop Y/N/O/Comments: Y 1722 2.20.108 Unrecognized Mandatory Well-Known Attributes 1724 Functionality/Description: The Data field MUST contain the 1725 unrecognized attribute 1727 RFC2119: MUST 1729 Alcatel Y/N/O/Comments: Y 1730 Cisco Y/N/O/Comments: Y 1731 Laurel Y/N/O/Comments: Y 1732 NextHop Y/N/O/Comments: Y 1734 2.20.109 Undefined ORIGIN 1736 Functionality/Description: The Error Sub-code MUST be set to 1737 Invalid Origin Attribute 1739 ^L 1740 RFC2119: MUST 1742 Alcatel Y/N/O/Comments: Y 1743 Cisco Y/N/O/Comments: Y 1744 Laurel Y/N/O/Comments: Y 1745 NextHop Y/N/O/Comments: Y 1747 2.20.110 Undefined ORIGIN 1749 Functionality/Description: The Data field MUST contain the 1750 unrecognized attribute 1752 RFC2119: MUST 1754 Alcatel Y/N/O/Comments: Y 1755 Cisco Y/N/O/Comments: Y 1756 Laurel Y/N/O/Comments: Y 1757 NextHop Y/N/O/Comments: Y 1759 2.20.111 Syntactically Incorrect NEXT_HOP 1761 Functionality/Description: The Error Subcode MUST be set to 1762 Invalid NEXT_HOP Attribute 1764 RFC2119: MUST 1766 Alcatel Y/N/O/Comments: Y 1767 Cisco Y/N/O/Comments: N Ignores the prefix in case of 1768 martian nexthop, and in case of 1769 length not equal to IPv4 1770 address-length, we send 1771 NOTIFICATION with error subcode 1772 Attribute Length error. 1773 Laurel Y/N/O/Comments: Y 1774 NextHop Y/N/O/Comments: Y 1776 2.20.112 Syntactically Incorrect NEXT_HOP 1778 Functionality/Description: The Data field MUST contain the 1779 incorrect attribute 1781 RFC2119: MUST 1783 Alcatel Y/N/O/Comments: Y 1784 Cisco Y/N/O/Comments: Y 1785 Laurel Y/N/O/Comments: Y 1787 ^L 1788 NextHop Y/N/O/Comments: Y 1790 2.20.113 NEXT_HOP Semantic Correctness 1792 Functionality/Description: NEXT_HOP is checked for semantic 1793 correctness against the criteria in this section 1795 RFC2119: MUST 1797 Alcatel Y/N/O/Comments: Y 1798 Cisco Y/N/O/Comments: Y 1799 Laurel Y/N/O/Comments: Y 1800 NextHop Y/N/O/Comments: Y 1802 2.20.114 NEXT_HOP Semantic Correctness 1804 Functionality/Description: Not be the IP address of the 1805 receiving speaker 1807 RFC2119: MUST NOT 1809 Alcatel Y/N/O/Comments: Y 1810 Cisco Y/N/O/Comments: Y 1811 Laurel Y/N/O/Comments: Y 1812 NextHop Y/N/O/Comments: Y 1814 2.20.115 NEXT_HOP Semantic Correctness 1816 Functionality/Description: In the case of an EBGP where the 1817 sender and receiver are one IP hop away from each other, either 1818 the IP address in the NEXT_HOP MUST be the sender's IP address 1819 (that is used to establish the BGP connection), or the interface 1820 associated with the NEXT_HOP IP address MUST share a common 1821 subnet with the receiving BGP speaker 1823 RFC2119: MUST 1825 Alcatel Y/N/O/Comments: Y 1826 Cisco Y/N/O/Comments: Y 1827 Laurel Y/N/O/Comments: Y 1828 NextHop Y/N/O/Comments: Y 1830 2.20.116 Semantically incorrect NEXT_HOP 1832 Functionality/Description: Error logged 1834 ^L 1835 RFC2119: SHOULD 1837 Alcatel Y/N/O/Comments: Y 1838 Cisco Y/N/O/Comments: Y 1839 Laurel Y/N/O/Comments: Y 1840 NextHop Y/N/O/Comments: Y 1842 2.20.117 Semantically incorrect NEXT_HOP 1844 Functionality/Description: Route Ignored 1846 RFC2119: SHOULD 1848 Alcatel Y/N/O/Comments: Y 1849 Cisco Y/N/O/Comments: Y 1850 Laurel Y/N/O/Comments: N 1851 NextHop Y/N/O/Comments: Y 1853 2.20.118 Semantically incorrect NEXT_HOP 1855 Functionality/Description: NOTIFICATION not sent 1857 RFC2119: SHOULD NOT 1859 Alcatel Y/N/O/Comments: Y 1860 Cisco Y/N/O/Comments: Y 1861 Laurel Y/N/O/Comments: Y 1862 NextHop Y/N/O/Comments: Y 1864 2.20.119 Semantically incorrect NEXT_HOP 1866 Functionality/Description: Connection not closed 1868 RFC2119: SHOULD NOT 1870 Alcatel Y/N/O/Comments: Y 1871 Cisco Y/N/O/Comments: Y 1872 Laurel Y/N/O/Comments: Y 1873 NextHop Y/N/O/Comments: Y 1875 2.20.120 Syntactically Incorrect AS_PATH 1877 Functionality/Description: The Error Subcode MUST be set to 1878 Malformed AS_PATH 1880 ^L 1881 RFC2119: MUST 1883 Alcatel Y/N/O/Comments: Y 1884 Cisco Y/N/O/Comments: Y 1885 Laurel Y/N/O/Comments: Y 1886 NextHop Y/N/O/Comments: Y 1888 2.20.121 First Neighbor in AS_PATH check 1890 Functionality/Description: If the UPDATE message is received 1891 from an external peer, the local system MAY check whether the 1892 leftmost AS in the AS_PATH attribute is equal to the autonomous 1893 system number of the peer that sent the message 1895 RFC2119: MAY 1897 Alcatel Y/N/O/Comments: Y 1898 Cisco Y/N/O/Comments: Y 1899 Laurel Y/N/O/Comments: N 1900 NextHop Y/N/O/Comments: Y 1902 2.20.122 First Neighbor in AS_PATH check 1904 Functionality/Description: If the check determines that this is 1905 not the case, the Error Subcode MUST be set to Malformed AS_PATH 1907 RFC2119: MUST 1909 Alcatel Y/N/O/Comments: Y 1910 Cisco Y/N/O/Comments: Y 1911 Laurel Y/N/O/Comments: n/a 1912 NextHop Y/N/O/Comments: Y 1914 2.20.123 Optional Attributes 1916 Functionality/Description: Value MUST be checked if the 1917 attribute is recognized 1919 RFC2119: MUST 1921 Alcatel Y/N/O/Comments: Y 1922 Cisco Y/N/O/Comments: Y 1923 Laurel Y/N/O/Comments: Y 1924 NextHop Y/N/O/Comments: Y 1926 ^L 1928 2.20.124 Optional Attribute Error 1930 Functionality/Description: The attribute MUST be discarded 1932 RFC2119: MUST 1934 Alcatel Y/N/O/Comments: Y 1935 Cisco Y/N/O/Comments: Y 1936 Laurel Y/N/O/Comments: Y 1937 NextHop Y/N/O/Comments: Y 1939 2.20.125 Optional Attribute Error 1941 Functionality/Description: The Error Subcode MUST be set to 1942 Optional Attribute Error 1944 RFC2119: MUST 1946 Alcatel Y/N/O/Comments: Y 1947 Cisco Y/N/O/Comments: N What exactly is optional attribute 1948 e.g If error is flag related, we send 1949 update flag error subcode, if it is 1950 length related, we send update length 1951 error subcode. These granular 1952 subcodes are better in terms of 1953 debugging than optional attribute 1954 error. 1955 Laurel Y/N/O/Comments: Y 1956 NextHop Y/N/O/Comments: Y Only optional attribute error that 1957 doesn't have a more specific error, 1958 is the version 3 to version 4 error 1959 for the atomic aggregate. All others 1960 default to more specific error codes 1961 if implementation. 1963 2.20.126 Optional Attribute Error 1965 Functionality/Description: The Data field MUST contain the 1966 attribute 1968 RFC2119: MUST 1970 Alcatel Y/N/O/Comments: Y 1971 Cisco Y/N/O/Comments: Y 1972 Laurel Y/N/O/Comments: Y 1973 NextHop Y/N/O/Comments: Y 1975 ^L 1977 2.20.127 Duplicate Attributes 1979 Functionality/Description: If any attribute appears more than 1980 once in the UPDATE message, then the Error Subcode MUST be set 1981 to Malformed Attribute List 1983 RFC2119: MUST 1985 Alcatel Y/N/O/Comments: Y 1986 Cisco Y/N/O/Comments: Y 1987 Laurel Y/N/O/Comments: Y 1988 NextHop Y/N/O/Comments: Y 1990 2.20.128 Syntactically Incorrect NLRI Field 1992 Functionality/Description: The Error Subcode MUST be set to 1993 Invalid Network Field 1995 RFC2119: MUST 1997 Alcatel Y/N/O/Comments: Y 1998 Cisco Y/N/O/Comments: Y 1999 Laurel Y/N/O/Comments: Y 2000 NextHop Y/N/O/Comments: Y 2002 2.20.129 Semantically Incorrect NLRI Field 2004 Functionality/Description: An error SHOULD be logged locally 2006 RFC2119: SHOULD 2008 Alcatel Y/N/O/Comments: Y 2009 Cisco Y/N/O/Comments: Y 2010 Laurel Y/N/O/Comments: Y 2011 NextHop Y/N/O/Comments: Y 2013 2.20.130 Semantically Incorrect NLRI Field 2015 Functionality/Description: The prefix SHOULD be ignored 2017 RFC2119: SHOULD 2019 Alcatel Y/N/O/Comments: Y 2020 Cisco Y/N/O/Comments: Y 2022 ^L 2023 Laurel Y/N/O/Comments: Y 2024 NextHop Y/N/O/Comments: Y 2026 2.20.131 UPDATE with no NLRI 2028 Functionality/Description: An UPDATE message that contains 2029 correct path attributes, but no NLRI, SHALL be treated as a 2030 valid UPDATE message 2032 RFC2119: SHALL 2034 Alcatel Y/N/O/Comments: Y 2035 Cisco Y/N/O/Comments: Y 2036 Laurel Y/N/O/Comments: Y 2037 NextHop Y/N/O/Comments: Y 2039 3.21 NOTIFICATION message error handling / Section 6.4 2041 2.21.132 Error in NOTIFICATION message 2043 Functionality/Description: Noticed, logged locally, and brought 2044 to the attention of the administration of the peer 2046 RFC2119: SHOULD 2048 Alcatel Y/N/O/Comments: Y 2049 Cisco Y/N/O/Comments: N 2050 Laurel Y/N/O/Comments: Y 2051 NextHop Y/N/O/Comments: Y 2053 3.22 Hold Timer Expired error handling / Section 6.5 2055 2.22.133 Hold Timer Expired 2057 Functionality/Description: Is your implementation compatible 2058 with the error handling procedures described in this section? 2060 RFC2119: N/A 2062 Alcatel Y/N/O/Comments: Y 2063 Cisco Y/N/O/Comments: Y 2064 Laurel Y/N/O/Comments: Y 2065 NextHop Y/N/O/Comments: Y 2067 ^L 2069 3.23 Finite State Machine error handling / Section 6.6 2071 2.23.134 Finite State Machine Errors 2073 Functionality/Description: Is your implementation compatible 2074 with the error handling procedures described in this section? 2076 RFC2119: N/A 2078 Alcatel Y/N/O/Comments: Y 2079 Cisco Y/N/O/Comments: N 2080 Laurel Y/N/O/Comments: Y 2081 NextHop Y/N/O/Comments: Y 2083 3.24 Cease / Section 6.7 2085 2.24.135 Cease NOTIFICATION 2087 Functionality/Description: Used in absence of any fatal errors 2088 if a BGP peer chooses at any given time to close its BGP 2089 connection 2091 RFC2119: MAY 2093 Alcatel Y/N/O/Comments: Y 2094 Cisco Y/N/O/Comments: N We close the TCP session without 2095 CEASE NOTIFICATION. 2096 Laurel Y/N/O/Comments: Y 2097 NextHop Y/N/O/Comments: Y 2099 2.24.136 Cease NOTIFICATION 2101 Functionality/Description: Not used for specified fatal errors 2103 RFC2119: MUST NOT 2105 Alcatel Y/N/O/Comments: Y 2106 Cisco Y/N/O/Comments: Y 2107 Laurel Y/N/O/Comments: Y 2108 NextHop Y/N/O/Comments: Y 2110 2.24.137 Upper bound on the number of address prefixes the speaker is 2111 willing to accept from a neighbor 2113 Functionality/Description: Support by local configuration 2115 ^L 2116 RFC2119: MAY 2118 Alcatel Y/N/O/Comments: Y 2119 Cisco Y/N/O/Comments: Y 2120 Laurel Y/N/O/Comments: Y 2121 NextHop Y/N/O/Comments: Y 2123 2.24.138 Upper bound on the number of address prefixes the speaker is 2124 willing to accept from a neighbor 2126 Functionality/Description: If exceeded and the BGP speaker 2127 decides to terminate its BGP connection, the Cease NOTIFICATION 2128 MUST be used 2130 RFC2119: MUST 2132 Alcatel Y/N/O/Comments: Y 2133 Cisco Y/N/O/Comments: N We don't send CEASE but we plan to 2134 correct that soon. 2135 Laurel Y/N/O/Comments: Y 2136 NextHop Y/N/O/Comments: Y No termination of peers is supported 2137 We are considering support with the 2138 maximum prefix draft for later 2139 releases. 2141 2.24.139 Upper bound on the number of address prefixes the speaker is 2142 willing to accept from a neighbor 2144 Functionality/Description: Log locally 2146 RFC2119: MAY 2148 Alcatel Y/N/O/Comments: Y 2149 Cisco Y/N/O/Comments: Y 2150 Laurel Y/N/O/Comments: Y 2151 NextHop Y/N/O/Comments: Y 2153 3.25 BGP connection collision detection / Section 6.8 2155 2.25.140 Connection Collision 2157 Functionality/Description: One of the connections MUST be closed 2159 RFC2119: MUST 2161 Alcatel Y/N/O/Comments: Y 2163 ^L 2164 Cisco Y/N/O/Comments: Y 2165 Laurel Y/N/O/Comments: Y 2166 NextHop Y/N/O/Comments: Y 2168 2.25.141 Receipt of an OPEN message 2170 Functionality/Description: The local system MUST examine all of 2171 its connections that are in the OpenConfirm state 2173 RFC2119: MUST 2175 Alcatel Y/N/O/Comments: Y 2176 Cisco Y/N/O/Comments: O We detect collision through some 2177 other implementation specific way 2178 and resolve by method specified in 2179 draft. 2180 Laurel Y/N/O/Comments: Y 2181 NextHop Y/N/O/Comments: Y 2183 2.25.142 Receipt of an OPEN message 2185 Functionality/Description: Examine connections in an OpenSent 2186 state if it knows the BGP Identifier of the peer by means 2187 outside of the protocol 2189 RFC2119: MAY 2191 Alcatel Y/N/O/Comments: Y 2192 Cisco Y/N/O/Comments: Y 2193 Laurel Y/N/O/Comments: Y 2194 NextHop Y/N/O/Comments: Y 2196 3.26 BGP Version Negotiation / Section 7 2198 2.26.143 Version Negotiation 2200 Functionality/Description: Multiple attempts to open a BGP 2201 connection, starting with the highest version number each 2202 supports 2204 RFC2119: MAY 2206 Alcatel Y/N/O/Comments: N Supports only version 4 2207 Cisco Y/N/O/Comments: O We resolve it through config. If 2208 Config is for version 3, and we get 2209 version 4, OPEN will always fail. 2211 ^L 2212 Similarly, if configed (default) is 2213 version 4 and peers configured is 3, 2214 we don't try to negotiate version 3 2215 unless we have configured it. 2216 Laurel Y/N/O/Comments: Y 2217 NextHop Y/N/O/Comments: N Supports only version 4. 2219 2.26.144 Future versions of BGP 2221 Functionality/Description: MUST retain the format of the OPEN 2222 and NOTIFICATION messages 2224 RFC2119: MUST 2226 Alcatel Y/N/O/Comments: Y 2227 Cisco Y/N/O/Comments: Y 2228 Laurel Y/N/O/Comments: Y 2229 NextHop Y/N/O/Comments: Y 2231 3.27 BGP Finite State machine (FSM) / Section 8 2233 2.27.145 FSM 2235 Functionality/Description: Is your implementation compatible 2236 with the conceptual FSM described in this section? 2238 RFC2119: N/A 2240 Alcatel Y/N/O/Comments: Y 2241 Cisco Y/N/O/Comments: Y 2242 Laurel Y/N/O/Comments: Y 2243 NextHop Y/N/O/Comments: Y 2245 3.28 Administrative Events / Section 8.1.2 2247 2.28.146 Optional Session Attribute Settings 2249 Functionality/Description: Each event has an indication of what 2250 optional session attributes SHOULD be set at each stage 2252 RFC2119: SHOULD 2254 Alcatel Y/N/O/Comments: Y 2255 Cisco Y/N/O/Comments: O Its rather vague. We have an option 2256 Of manually starting or stopping 2257 sessions but not an option for all 2259 ^L 2260 optional session attributes that are 2261 listed in draft. 2262 Laurel Y/N/O/Comments: Y 2263 NextHop Y/N/O/Comments: Y The following optional attributes 2264 are implied in this implementation: 2265 1) Automatic start, 2) Automatic 2266 Stop, 3) 2268 2.28.147 Event1: ManualStart 2270 Functionality/Description: The PassiveTcpEstablishment attribute 2271 SHOULD be set to FALSE 2273 RFC2119: SHOULD 2275 Alcatel Y/N/O/Comments: Y 2276 Cisco Y/N/O/Comments: Y 2277 Laurel Y/N/O/Comments: Y 2278 NextHop Y/N/O/Comments: Y 2280 2.28.148 Event3: AutomaticStart 2282 Functionality/Description: The AllowAutomaticStart attribute 2283 SHOULD be set to TRUE 2285 RFC2119: SHOULD 2287 Alcatel Y/N/O/Comments: Y 2288 Cisco Y/N/O/Comments: Y 2289 Laurel Y/N/O/Comments: Y 2290 NextHop Y/N/O/Comments: Y 2292 2.28.149 Event3: AutomaticStart 2294 Functionality/Description: The PassiveTcpEstablishment optional 2295 session attribute SHOULD be set to FALSE 2297 RFC2119: SHOULD 2299 Alcatel Y/N/O/Comments: Y 2300 Cisco Y/N/O/Comments: Y 2301 Laurel Y/N/O/Comments: Y 2302 NextHop Y/N/O/Comments: Y 2304 2.28.150 Event3: AutomaticStart 2306 ^L 2307 Functionality/Description: DampPeerOscillations SHOULD be set to 2308 FALSE 2310 RFC2119: SHOULD 2312 Alcatel Y/N/O/Comments: Y 2313 Cisco Y/N/O/Comments: Y Don't support DampPeerOscillations 2314 attribute, so it is always FALSE. 2315 Laurel Y/N/O/Comments: Y 2316 NextHop Y/N/O/Comments: Y 2318 2.28.151 Event4: ManualStart_with_PassiveTcpEstablishment 2320 Functionality/Description: The PassiveTcpEstablishment attribute 2321 SHOULD be set to TRUE 2323 RFC2119: SHOULD 2325 Alcatel Y/N/O/Comments: Y 2326 Cisco Y/N/O/Comments: Y We wait for some fixed time before 2327 initiating OPEN. 2328 Laurel Y/N/O/Comments: Y 2329 NextHop Y/N/O/Comments: Y 2331 2.28.152 Event4: ManualStart_with_PassiveTcpEstablishment 2333 Functionality/Description: The DampPeerOscillations attribute 2334 SHOULD be set to FALSE 2336 RFC2119: SHOULD 2338 Alcatel Y/N/O/Comments: Y 2339 Cisco Y/N/O/Comments: Y Don't support DampPeerOscillations 2340 attribute so it is FALSE. 2341 Laurel Y/N/O/Comments: Y 2342 NextHop Y/N/O/Comments: O We don't support DampPeerOscilation 2343 attribute with a setting of off, and 2344 hence Event 4. Future version will 2345 support Event 4 2347 2.28.153 Event5: AutomaticStart_with_PassiveTcpEstablishment 2349 Functionality/Description: The AllowAutomaticStart attribute 2350 SHOULD be set to TRUE 2352 ^L 2353 RFC2119: SHOULD 2355 Alcatel Y/N/O/Comments: Y 2356 Cisco Y/N/O/Comments: Y 2357 Laurel Y/N/O/Comments: Y 2358 NextHop Y/N/O/Comments: Y 2360 2.28.154 Event5: AutomaticStart_with_PassiveTcpEstablishment 2362 Functionality/Description: The PassiveTcpEstablishment attribute 2363 SHOULD be set to TRUE 2365 RFC2119: SHOULD 2367 Alcatel Y/N/O/Comments: Y 2368 Cisco Y/N/O/Comments: Y 2369 Laurel Y/N/O/Comments: Y 2370 NextHop Y/N/O/Comments: Y 2372 2.28.155 Event5: AutomaticStart_with_PassiveTcpEstablishment 2374 Functionality/Description: The DampPeerOscillations SHOULD be 2375 set to FALSE 2377 RFC2119: SHOULD 2379 Alcatel Y/N/O/Comments: Y 2380 Cisco Y/N/O/Comments: Y Don't support DampPeerOscillations 2381 attribute, so always FALSE. 2382 Laurel Y/N/O/Comments: Y 2383 NextHop Y/N/O/Comments: O We don't support DampPeerOscilation 2384 attribute with a setting of off, and 2385 hence Event 5. Future version will 2386 support Event 5 2388 2.28.156 Event6: AutomaticStart_with_DampPeerOscillations 2390 Functionality/Description: The AllowAutomaticStart attribute 2391 SHOULD be set to TRUE 2393 RFC2119: SHOULD 2395 Alcatel Y/N/O/Comments: N 2396 Cisco Y/N/O/Comments: O Don't support DampPeerOscillations 2397 attribute. 2398 Laurel Y/N/O/Comments: Y 2400 ^L 2401 NextHop Y/N/O/Comments: Y 2403 2.28.157 Event6: AutomaticStart_with_DampPeerOscillations 2405 Functionality/Description: The DampPeerOscillations attribute 2406 SHOULD be set to TRUE 2408 RFC2119: SHOULD 2410 Alcatel Y/N/O/Comments: N 2411 Cisco Y/N/O/Comments: N Don't support DampPeerOscillations 2412 attribute. 2413 Laurel Y/N/O/Comments: Y 2414 NextHop Y/N/O/Comments: Y 2416 2.28.158 Event6: AutomaticStart_with_DampPeerOscillations 2418 Functionality/Description: The PassiveTcpEstablishment attribute 2419 SHOULD be set to FALSE 2421 RFC2119: SHOULD 2423 Alcatel Y/N/O/Comments: N 2424 Cisco Y/N/O/Comments: O Don't support DampPeerOscillations 2425 attribute and hence Event6. 2426 Laurel Y/N/O/Comments: Y 2427 NextHop Y/N/O/Comments: Y 2429 2.28.159 Event 7: 2430 AutomaticStart_with_DampPeerOscillations_and_PassiveTcpEstablishment 2432 Functionality/Description: The AllowAutomaticStart attribute 2433 SHOULD be set to TRUE 2435 RFC2119: SHOULD 2437 Alcatel Y/N/O/Comments: N 2438 Cisco Y/N/O/Comments: O Don't support DampPeerOscillations 2439 attribute and hence Event7 2440 Laurel Y/N/O/Comments: Y 2441 NextHop Y/N/O/Comments: Y 2443 2.28.160 Event 7: 2444 AutomaticStart_with_DampPeerOscillations_and_PassiveTcpEstablishment 2446 ^L 2447 Functionality/Description: The DampPeerOscillations attribute 2448 SHOULD be set to TRUE 2450 RFC2119: SHOULD 2452 Alcatel Y/N/O/Comments: N 2453 Cisco Y/N/O/Comments: O Don't support DampPeerOscillations 2454 attribute and hence Event7 2455 Laurel Y/N/O/Comments: Y 2456 NextHop Y/N/O/Comments: Y 2458 2.28.161 Event 7: 2459 AutomaticStart_with_DampPeerOscillations_and_PassiveTcpEstablishment 2461 Functionality/Description: The PassiveTcpEstablishment attribute 2462 SHOULD be set to TRUE 2464 RFC2119: SHOULD 2466 Alcatel Y/N/O/Comments: N 2467 Cisco Y/N/O/Comments: O Don't support DampPeerOscillations 2468 attribute and hence Event7 2469 Laurel Y/N/O/Comments: Y 2470 NextHop Y/N/O/Comments: Y 2472 2.28.162 Event8: AutomaticStop 2474 Functionality/Description: The AllowAutomaticStop attribute 2475 SHOULD be TRUE 2477 RFC2119: SHOULD 2479 Alcatel Y/N/O/Comments: N 2480 Cisco Y/N/O/Comments: Y 2481 Laurel Y/N/O/Comments: Y 2482 NextHop Y/N/O/Comments: Y 2484 3.29 Timer Events / Section 8.1.3 2486 2.29.163 Event12: DelayOpenTimer_Expires 2488 Functionality/Description: DelayOpen attribute SHOULD be set to 2489 TRUE 2491 RFC2119: SHOULD 2493 ^L 2494 Alcatel Y/N/O/Comments: N 2495 Cisco Y/N/O/Comments: Y 2496 Laurel Y/N/O/Comments: n/a 2497 NextHop Y/N/O/Comments: Y 2499 2.29.164 Event12: DelayOpenTimer_Expires 2501 Functionality/Description: DelayOpenTime attribute SHOULD be 2502 supported 2504 RFC2119: SHOULD 2506 Alcatel Y/N/O/Comments: N 2507 Cisco Y/N/O/Comments: Y 2508 Laurel Y/N/O/Comments: n/a 2509 NextHop Y/N/O/Comments: Y 2511 2.29.165 Event12: DelayOpenTimer_Expires 2513 Functionality/Description: DelayOpenTimer SHOULD be supported 2515 RFC2119: SHOULD 2517 Alcatel Y/N/O/Comments: N 2518 Cisco Y/N/O/Comments: Y 2519 Laurel Y/N/O/Comments: n/a 2520 NextHop Y/N/O/Comments: Y 2522 2.29.166 Event13: IdleHoldTimer_Expires 2524 Functionality/Description: DampPeerOscillations attribute SHOULD 2525 be set to TRUE 2527 RFC2119: SHOULD 2529 Alcatel Y/N/O/Comments: N 2530 Cisco Y/N/O/Comments: O Don't support DampPeerOscillations 2531 attribute and hence Event13 2532 Laurel Y/N/O/Comments: Y 2533 NextHop Y/N/O/Comments: Y 2535 2.29.167 Event13: IdleHoldTimer_Expires 2537 Functionality/Description: IdleHoldTimer SHOULD have just 2538 expired 2540 ^L 2541 RFC2119: SHOULD 2543 Alcatel Y/N/O/Comments: N 2544 Cisco Y/N/O/Comments: O Don't support DampPeerOscillations 2545 attribute and hence Event13 2546 Laurel Y/N/O/Comments: Y 2547 NextHop Y/N/O/Comments: Y 2549 3.30 TCP Connection based Events / Section 8.1.4 2551 2.30.168 Event14: TcpConnection_Valid 2553 Functionality/Description: BGP's destination port SHOULD be port 2554 179 2556 RFC2119: SHOULD 2558 Alcatel Y/N/O/Comments: Y 2559 Cisco Y/N/O/Comments: Y 2560 Laurel Y/N/O/Comments: Y 2561 NextHop Y/N/O/Comments: Y 2563 2.30.169 Event14: TcpConnection_Valid 2565 Functionality/Description: The TrackTcpState attribute SHOULD be 2566 set to TRUE 2568 RFC2119: SHOULD 2570 Alcatel Y/N/O/Comments: Y 2571 Cisco Y/N/O/Comments: Y 2572 Laurel Y/N/O/Comments: Y 2573 NextHop Y/N/O/Comments: O GateD NGC 2.0 provides hooks for 2574 the TCP state tracking, but use of 2575 this option depends OS support. 2576 Future versions will have additional 2577 hooks. 2579 2.30.170 Event15: Tcp_CR_Invalid 2581 Functionality/Description: BGP destination port number SHOULD be 2582 179 2584 RFC2119: SHOULD 2586 ^L 2587 Alcatel Y/N/O/Comments: Y 2588 Cisco Y/N/O/Comments: Y 2589 Laurel Y/N/O/Comments: Y 2590 NextHop Y/N/O/Comments: O GateD NGC 2.0 provides hooks for 2591 the TCP state tracking, but use of 2592 this option depends OS support. 2593 Future versions will have additional 2594 hooks. 2596 3.31 BGP Messages based Events / Seciton 8.1.5 2598 2.31.171 Event19: BGPOpen 2600 Functionality/Description: The DelayOpen optional attribute 2601 SHOULD be set to FALSE 2603 RFC2119: SHOULD 2605 Alcatel Y/N/O/Comments: Y 2606 Cisco Y/N/O/Comments: Y 2607 Laurel Y/N/O/Comments: n/a 2608 NextHop Y/N/O/Comments: Y 2610 2.31.172 Event19: BGPOpen 2612 Functionality/Description: The DelayOpenTimer SHOULD not be 2613 running 2615 RFC2119: SHOULD 2617 Alcatel Y/N/O/Comments: Y 2618 Cisco Y/N/O/Comments: Y 2619 Laurel Y/N/O/Comments: Y 2620 NextHop Y/N/O/Comments: Y 2622 2.31.173 Event20: BGPOpen with DelayOpenTimer running 2624 Functionality/Description: The DelayOpen attribute SHOULD be set 2625 to TRUE 2627 RFC2119: SHOULD 2629 Alcatel Y/N/O/Comments: N Not applicable 2630 Cisco Y/N/O/Comments: Y 2631 Laurel Y/N/O/Comments: n/a 2632 NextHop Y/N/O/Comments: Y 2634 ^L 2636 2.31.174 Event20: BGPOpen with DelayOpenTimer running 2638 Functionality/Description: The DelayOpenTimer SHOULD be running 2640 RFC2119: SHOULD 2642 Alcatel Y/N/O/Comments: N 2643 Cisco Y/N/O/Comments: Y 2644 Laurel Y/N/O/Comments: n/a 2645 NextHop Y/N/O/Comments: Y 2647 2.31.175 Event23: OpenCollisionDump 2649 Functionality/Description: If the state machine is to process 2650 this event in Established state, the 2651 CollisionDetectEstablishedState optional attribute SHOULD be set 2652 to TRUE 2654 RFC2119: SHOULD 2656 Alcatel Y/N/O/Comments: Y Collision detection event is logged. 2657 Cisco Y/N/O/Comments: O We always detect collision before we 2658 go to established state. 2659 Laurel Y/N/O/Comments: Y 2660 NextHop Y/N/O/Comments: O GateD NGC 2.0 does not support 2661 Collision Detection in Established 2662 state. This option attribute is 2663 always set to FALSE. 2665 3.32 FSM Definition / Section 8.2.1 2667 2.32.176 FSM 2669 Functionality/Description: Separate FSM for each configured peer 2671 RFC2119: MUST 2673 Alcatel Y/N/O/Comments: Y 2674 Cisco Y/N/O/Comments: Y 2675 Laurel Y/N/O/Comments: Y 2676 NextHop Y/N/O/Comments: Y 2678 2.32.177 TCP Port 179 2680 ^L 2681 Functionality/Description: A BGP implementation MUST connect to 2682 and listen on TCP port 179 for incoming connections in addition 2683 to trying to connect to peers 2685 RFC2119: MUST 2687 Alcatel Y/N/O/Comments: Y 2688 Cisco Y/N/O/Comments: Y 2689 Laurel Y/N/O/Comments: Y 2690 NextHop Y/N/O/Comments: Y 2692 2.32.178 Incoming Connections 2694 Functionality/Description: A state machine MUST be instantiated 2696 RFC2119: MUST 2698 Alcatel Y/N/O/Comments: Y 2699 Cisco Y/N/O/Comments: Y 2700 Laurel Y/N/O/Comments: Y 2701 NextHop Y/N/O/Comments: Y 2703 3.33 FSM and collision detection / Section 8.2.1.2 2705 2.33.179 Connection Collision 2707 Functionality/Description: The corresponding FSM for the 2708 connection that is closed SHOULD be disposed of 2710 RFC2119: SHOULD 2712 Alcatel Y/N/O/Comments: Y 2713 Cisco Y/N/O/Comments: Y 2714 Laurel Y/N/O/Comments: Y 2715 NextHop Y/N/O/Comments: Y 2717 3.34 FSM Event numbers / Section 8.2.1.4 2719 2.34.180 Event Numbers 2721 Functionality/Description: Used to provide network management 2722 information 2724 RFC2119: MAY 2726 Alcatel Y/N/O/Comments: Y Not visible to operator. 2728 ^L 2729 Cisco Y/N/O/Comments: N 2730 Laurel Y/N/O/Comments: N 2731 NextHop Y/N/O/Comments: N Future Release of GateD NGC may 2732 support event numbers. 2734 3.35 Finite State Machine / Section 8.2.2 2736 2.35.181 ConnectRetryTimer 2738 Functionality/Description: Sufficiently large to allow TCP 2739 initialization 2741 RFC2119: SHOULD 2743 Alcatel Y/N/O/Comments: Y 2744 Cisco Y/N/O/Comments: Y 2745 Laurel Y/N/O/Comments: Y 2746 NextHop Y/N/O/Comments: Y 2748 2.35.182 2nd connection tracking 2750 Functionality/Description: In response to a TCP connection 2751 succeeds [Event 16 or Event 17], the 2nd connection SHALL be 2752 tracked until it sends an OPEN message 2754 RFC2119: SHALL 2756 Alcatel Y/N/O/Comments: Y 2757 Cisco Y/N/O/Comments: Y 2758 Laurel Y/N/O/Comments: Y 2759 NextHop Y/N/O/Comments: Y 2761 3.36 UPDATE Message Handling / Section 9 2763 2.36.183 UPDATE Message Handling 2765 Functionality/Description: Does your implementation handle 2766 UPDATE messages in a manner compatible to the description in 2767 this section? 2769 RFC2119: N/A 2771 Alcatel Y/N/O/Comments: Y 2772 Cisco Y/N/O/Comments: Y 2773 Laurel Y/N/O/Comments: Y 2775 ^L 2776 NextHop Y/N/O/Comments: Y 2778 2.36.184 WITHDRAWN ROUTES 2780 Functionality/Description: Any previously advertised routes 2781 whose destinations are contained in this field SHALL be removed 2782 from the Adj-RIB-In 2784 RFC2119: SHALL 2786 Alcatel Y/N/O/Comments: Y 2787 Cisco Y/N/O/Comments: Y 2788 Laurel Y/N/O/Comments: Y 2789 NextHop Y/N/O/Comments: Y 2791 2.36.185 WITHDRAWN ROUTES 2793 Functionality/Description: The BGP speaker SHALL run its 2794 Decision Process since the previously advertised route is no 2795 longer available for use 2797 RFC2119: SHALL 2799 Alcatel Y/N/O/Comments: Y 2800 Cisco Y/N/O/Comments: Y 2801 Laurel Y/N/O/Comments: Y 2802 NextHop Y/N/O/Comments: Y 2804 3.36.186 Implicit withdraw 2806 Functionality/Description: If an UPDATE message contains a 2807 feasible route, and the NLRI of the new route is identical to 2808 the one of a route currently stored in the Adj-RIB-In, then the 2809 new route SHALL replace the older route 2811 RFC2119: SHALL 2813 Alcatel Y/N/O/Comments: Y 2814 Cisco Y/N/O/Comments: Y 2815 Laurel Y/N/O/Comments: Y 2816 NextHop Y/N/O/Comments: Y 2818 2.36.187 Other feasible routes 2820 Functionality/Description: If an UPDATE message contains a 2822 ^L 2823 feasible route, and the NLRI of the new route is not identical 2824 to the one of any route currently stored in the Adj-RIB-In, then 2825 the new route SHALL be placed in the Adj-RIB-In 2827 RFC2119: SHALL 2829 Alcatel Y/N/O/Comments: Y 2830 Cisco Y/N/O/Comments: Y 2831 Laurel Y/N/O/Comments: Y 2832 NextHop Y/N/O/Comments: Y 2834 2.36.188 Adj-RIB-In Update 2836 Functionality/Description: Once a BGP speaker updates the 2837 Adj-RIB-In, it SHALL run its Decision Process 2839 RFC2119: SHALL 2841 Alcatel Y/N/O/Comments: Y 2842 Cisco Y/N/O/Comments: Y 2843 Laurel Y/N/O/Comments: Y 2844 NextHop Y/N/O/Comments: Y 2846 3.37 Decision Process / Section 9.1 2848 2.37.189 Decision Process 2850 Functionality/Description: Is your implementation compatible 2851 with the description in this section? 2853 RFC2119: N/A 2855 Alcatel Y/N/O/Comments: Y 2856 Cisco Y/N/O/Comments: Y 2857 Laurel Y/N/O/Comments: Y 2858 NextHop Y/N/O/Comments: Y 2860 2.37.190 Degree of Preference 2862 Functionality/Description: SHALL NOT use as its inputs any of 2863 the following: the existence of other routes, the non-existence 2864 of other routes, or the path attributes of other routes 2866 RFC2119: SHALL NOT 2868 Alcatel Y/N/O/Comments: Y 2870 ^L 2871 Cisco Y/N/O/Comments: Y 2872 Laurel Y/N/O/Comments: Y 2873 NextHop Y/N/O/Comments: Y 2875 3.38 Phase 1: Calculation of Degree of Preference / Section 9.1.1 2877 2.38.191 Ineligible degree of preference 2879 Functionality/Description: The route MAY NOT serve as an input 2880 to the next phase of route selection 2882 RFC2119: MAY NOT 2884 Alcatel Y/N/O/Comments: Y 2885 Cisco Y/N/O/Comments: Y 2886 Laurel Y/N/O/Comments: Y 2887 NextHop Y/N/O/Comments: Y 2889 2.38.192 Eligible degree of preference 2891 Functionality/Description: Used as the LOCAL_PREF value in any 2892 IBGP readvertisement 2894 RFC2119: MUST 2896 Alcatel Y/N/O/Comments: Y 2897 Cisco Y/N/O/Comments: Y 2898 Laurel Y/N/O/Comments: Y 2899 NextHop Y/N/O/Comments: Y 2901 3.39 Phase 2: Route Selection / Section 9.1.2 2903 2.39.193 Unresolvable NEXT_HOP 2905 Functionality/Description: If the NEXT_HOP attribute of a BGP 2906 route depicts an address that is not resolvable, or it would 2907 become unresolvable if the route was installed in the routing 2908 table the BGP route MUST be excluded 2910 RFC2119: MUST 2912 Alcatel Y/N/O/Comments: Y 2913 Cisco Y/N/O/Comments: Y 2914 Laurel Y/N/O/Comments: Y 2915 NextHop Y/N/O/Comments: Y 2917 ^L 2919 2.39.194 Routes installed in LOC-RIB 2921 Functionality/Description: The route in the Adj-RIBs-In 2922 identified as the best (see section 9.1.2) is installed in the 2923 Loc-RIB, replacing any route to the same destination that is 2924 currently being held in the Loc-RIB 2926 RFC2119: SHALL 2928 Alcatel Y/N/O/Comments: Y 2929 Cisco Y/N/O/Comments: Y 2930 Laurel Y/N/O/Comments: Y 2931 NextHop Y/N/O/Comments: Y 2933 2.39.195 Immediate next-hop address 2935 Functionality/Description: MUST be determined from the NEXT_HOP 2936 attribute of the selected route (see Section 5.1.3) 2938 RFC2119: MUST 2940 Alcatel Y/N/O/Comments: Y 2941 Cisco Y/N/O/Comments: Y 2942 Laurel Y/N/O/Comments: Y 2943 NextHop Y/N/O/Comments: Y 2945 2.39.196 Phase 2: Route Selection 2947 Functionality/Description: Performed again if either the 2948 immediate next hop or the IGP cost to the NEXT_HOP changes 2950 RFC2119: MUST 2952 Alcatel Y/N/O/Comments: Y 2953 Cisco Y/N/O/Comments: Y 2954 Laurel Y/N/O/Comments: Y 2955 NextHop Y/N/O/Comments: Y 2957 2.39.197 Immediate next-hop address 2959 Functionality/Description: Used for packet forwarding 2961 RFC2119: MUST 2963 Alcatel Y/N/O/Comments: Y 2965 ^L 2966 Cisco Y/N/O/Comments: Y 2967 Laurel Y/N/O/Comments: Y 2968 NextHop Y/N/O/Comments: Y 2970 2.39.198 Unresolvable routes 2972 Functionality/Description: Removed from the Loc-RIB and the 2973 routing table 2975 RFC2119: SHALL 2977 Alcatel Y/N/O/Comments: Y 2978 Cisco Y/N/O/Comments: Y 2979 Laurel Y/N/O/Comments: Y 2980 NextHop Y/N/O/Comments: Y 2982 2.39.199 Unresolvable routes 2984 Functionality/Description: Kept in the corresponding Adj-RIBs-In 2986 RFC2119: SHOULD 2988 Alcatel Y/N/O/Comments: Y 2989 Cisco Y/N/O/Comments: Y 2990 Laurel Y/N/O/Comments: Y 2991 NextHop Y/N/O/Comments: Y 2993 3.40 Route Resolvability Condition / Section 9.1.2.1 2995 2.40.200 Unresolvable routes 2997 Functionality/Description: Excluded from the Phase 2 decision 2999 RFC2119: SHOULD 3001 Alcatel Y/N/O/Comments: Y 3002 Cisco Y/N/O/Comments: Y 3003 Laurel Y/N/O/Comments: Y 3004 NextHop Y/N/O/Comments: Y 3006 2.40.201 Multiple Matching Routes 3008 Functionality/Description: Only the longest matching route 3009 SHOULD be considered 3011 ^L 3012 RFC2119: SHOULD 3014 Alcatel Y/N/O/Comments: Y 3015 Cisco Y/N/O/Comments: Y 3016 Laurel Y/N/O/Comments: Y 3017 NextHop Y/N/O/Comments: Y 3019 2.40.202 Mutual Recursion 3021 Functionality/Description: If a route fails the resolvability 3022 check because of mutual recursion, an error message SHOULD be 3023 logged 3025 RFC2119: SHOULD 3027 Alcatel Y/N/O/Comments: Y 3028 Cisco Y/N/O/Comments: O We have checks that disallow mutual 3029 recursion, so this won't happen. 3030 Laurel Y/N/O/Comments: Y 3031 NextHop Y/N/O/Comments: Y 3033 3.41 Breaking Ties (Phase 2) / Section 9.1.2.2 3035 2.41.203 Tie-breaking criteria 3037 Functionality/Description: Applied in the order specified 3039 RFC2119: MUST 3041 Alcatel Y/N/O/Comments: Y 3042 Cisco Y/N/O/Comments: Y 3043 Laurel Y/N/O/Comments: Y 3044 NextHop Y/N/O/Comments: Y 3046 2.41.204 Algorithm used 3048 Functionality/Description: BGP implementations MAY use any 3049 algorithm which produces the same results asthose described here 3051 RFC2119: MAY 3053 Alcatel Y/N/O/Comments: Y 3054 Cisco Y/N/O/Comments: Y 3055 Laurel Y/N/O/Comments: Y 3056 NextHop Y/N/O/Comments: Y 3058 ^L 3060 2.41.205 MULTI_EXIT_DISC removal 3062 Functionality/Description: If done before re-advertising a route 3063 into IBGP, then comparison based on the received EBGP 3064 MULTI_EXIT_DISC attribute MAY still be performed 3066 RFC2119: MAY 3068 Alcatel Y/N/O/Comments: Y 3069 Cisco Y/N/O/Comments: Y 3070 Laurel Y/N/O/Comments: Y 3071 NextHop Y/N/O/Comments: Y 3073 2.41.206 MULTI_EXIT_DISC removal 3075 Functionality/Description: The optional comparison on 3076 MULTI_EXIT_DISC if performed at all MUST be performed only among 3077 EBGP learned routes 3079 RFC2119: MUST 3081 Alcatel Y/N/O/Comments: Y 3082 Cisco Y/N/O/Comments: Y 3083 Laurel Y/N/O/Comments: Y 3084 NextHop Y/N/O/Comments: Y 3086 2.41.207 MULTI_EXIT_DISC comparison 3088 Functionality/Description: Performed for IBGP learned routes 3090 RFC2119: MUST 3092 Alcatel Y/N/O/Comments: Y 3093 Cisco Y/N/O/Comments: Y 3094 Laurel Y/N/O/Comments: Y 3095 NextHop Y/N/O/Comments: Y 3097 3.42 Phase 3: Route Dissemination / Section 9.1.3 3099 2.42.208 Policy for processing routes from the Loc-RIB into Adj-RIBs- 3100 Out 3102 Functionality/Description: Exclude a route in the Loc-RIB from 3103 being installed in a particular Adj-RIB-Out 3105 ^L 3106 RFC2119: MAY 3108 Alcatel Y/N/O/Comments: Y 3109 Cisco Y/N/O/Comments: Y 3110 Laurel Y/N/O/Comments: Y 3111 NextHop Y/N/O/Comments: Y 3113 2.42.209 Adj-Rib-Out Route Installation 3115 Functionality/Description: Not unless the destination and 3116 NEXT_HOP described by this route may be forwarded appropriately 3117 by the Routing Table 3119 RFC2119: SHALL NOT 3121 Alcatel Y/N/O/Comments: Y 3122 Cisco Y/N/O/Comments: Y 3123 Laurel Y/N/O/Comments: Y 3124 NextHop Y/N/O/Comments: Y 3126 2.42.210 Withdraw routes 3128 Functionality/Description: If a route in Loc-RIB is excluded 3129 from a particular Adj-RIB-Out the previously advertised route in 3130 that Adj-RIB-Out MUST be withdrawn from service by means of an 3131 UPDATE message (see 9.2) 3133 RFC2119: MUST 3135 Alcatel Y/N/O/Comments: Y 3136 Cisco Y/N/O/Comments: Y 3137 Laurel Y/N/O/Comments: Y 3138 NextHop Y/N/O/Comments: Y 3140 3.43 Overlapping Routes / Section 9.1.4 3142 2.43.211 Overlapping Routes 3144 Functionality/Description: Consider both routes based on the 3145 configured acceptance policy 3147 RFC2119: MUST 3149 Alcatel Y/N/O/Comments: Y 3150 Cisco Y/N/O/Comments: Y 3151 Laurel Y/N/O/Comments: Y 3153 ^L 3154 NextHop Y/N/O/Comments: Y 3156 2.43.212 Accepted Overlapping Routes 3158 Functionality/Description: The Decision Process MUST either 3159 install both routes or... 3161 RFC2119: MUST 3163 Alcatel Y/N/O/Comments: Y 3164 Cisco Y/N/O/Comments: Y 3165 Laurel Y/N/O/Comments: Y 3166 NextHop Y/N/O/Comments: Y 3168 2.43.213 Accepted Overlapping Routes 3170 Functionality/Description: Aggregate the two routes and install 3171 the aggregated route, provided that both routes have the same 3172 value of the NEXT_HOP attribute 3174 RFC2119: MUST 3176 Alcatel Y/N/O/Comments: Y 3177 Cisco Y/N/O/Comments: N We install both in Local RIB. 3178 Laurel Y/N/O/Comments: N no automatic aggregation 3179 NextHop Y/N/O/Comments: N no automatic aggregation 3181 2.43.214 Aggregation 3183 Functionality/Description: Either include all ASs used to form 3184 the aggreagate in an AS_SET or add the ATOMIC_AGGREGATE 3185 attribute to the route 3187 RFC2119: SHOULD 3189 Alcatel Y/N/O/Comments: Y 3190 Cisco Y/N/O/Comments: Y 3191 Laurel Y/N/O/Comments: Y 3192 NextHop Y/N/O/Comments: Y 3194 2.43.215 De-aggregation 3196 Functionality/Description: Routes SHOULD NOT be de-aggregated 3198 RFC2119: SHOULD NOT 3200 ^L 3201 Alcatel Y/N/O/Comments: Y 3202 Cisco Y/N/O/Comments: Y 3203 Laurel Y/N/O/Comments: Y 3204 NextHop Y/N/O/Comments: Y 3206 2.43.216 Route with the ATOMIC_AGGREGATE attribute 3208 Functionality/Description: Not de-aggregated 3210 RFC2119: MUST NOT 3212 Alcatel Y/N/O/Comments: Y 3213 Cisco Y/N/O/Comments: Y 3214 Laurel Y/N/O/Comments: Y 3215 NextHop Y/N/O/Comments: Y 3217 3.44 Update-Send Process / Section 9.2 3219 2.44.217 UPDATE message received from an internal peer 3221 Functionality/Description: Not re-distribute the routing 3222 information to other internal peers, unless the speaker acts as 3223 a BGP Route Reflector [RFC2796] 3225 RFC2119: SHALL NOT 3227 Alcatel Y/N/O/Comments: Y 3228 Cisco Y/N/O/Comments: Y 3229 Laurel Y/N/O/Comments: Y 3230 NextHop Y/N/O/Comments: Y 3232 2.44.218 No replacement route 3234 Functionality/Description: All newly installed routes and all 3235 newly unfeasible routes for which there is no replacement route 3236 SHALL be advertised to its peers by means of an UPDATE message 3238 RFC2119: SHALL 3240 Alcatel Y/N/O/Comments: Y 3241 Cisco Y/N/O/Comments: Y 3242 Laurel Y/N/O/Comments: Y 3243 NextHop Y/N/O/Comments: Y 3245 ^L 3247 2.44.219 Previously Advertised Routes 3249 Functionality/Description: A BGP speaker SHOULD NOT advertise a 3250 given feasible BGP route if it would produce an UPDATE message 3251 containing the same BGP route as was previously advertised 3253 RFC2119: SHOULD NOT 3255 Alcatel Y/N/O/Comments: Y 3256 Cisco Y/N/O/Comments: Y 3257 Laurel Y/N/O/Comments: Y 3258 NextHop Y/N/O/Comments: Y 3260 2.44.220 Unfeasible routes 3262 Functionality/Description: Removed from the Loc-RIB 3264 RFC2119: SHALL 3266 Alcatel Y/N/O/Comments: Y 3267 Cisco Y/N/O/Comments: Y 3268 Laurel Y/N/O/Comments: Y 3269 NextHop Y/N/O/Comments: Y 3271 2.44.221 Changes to reachable destinations 3273 Functionality/Description: Changes to the reachable destinations 3274 within its own autonomous system SHALL also be advertised in an 3275 UPDATE message 3277 RFC2119: SHALL 3279 Alcatel Y/N/O/Comments: Y 3280 Cisco Y/N/O/Comments: Y 3281 Laurel Y/N/O/Comments: Y 3282 NextHop Y/N/O/Comments: Y 3284 2.44.222 A single route doesn't fit into the UPDATE message 3286 Functionality/Description: Don't advertise 3288 RFC2119: MUST 3290 Alcatel Y/N/O/Comments: Y 3291 Cisco Y/N/O/Comments: Y 3292 Laurel Y/N/O/Comments: Y 3294 ^L 3295 NextHop Y/N/O/Comments: Y 3297 2.44.223 A single route doesn't fit into the UPDATE message 3299 Functionality/Description: Log an error local 3301 RFC2119: MAY 3303 Alcatel Y/N/O/Comments: Y 3304 Cisco Y/N/O/Comments: N 3305 Laurel Y/N/O/Comments: Y 3306 NextHop Y/N/O/Comments: Y 3308 3.45 Frequency of Route Advertisement / Section 9.2.1.1 3310 2.45.224 MinRouteAdvertisementIntervalTimer 3312 Functionality/Description: Minimum separation between two UPDATE 3313 messages sent by a BGP speaker to a peer that advertise feasible 3314 routes and/or withdrawal of unfeasible routes to some common set 3315 of destinations 3317 RFC2119: MUST 3319 Alcatel Y/N/O/Comments: Y 3320 Cisco Y/N/O/Comments: Y 3321 Laurel Y/N/O/Comments: Y 3322 NextHop Y/N/O/Comments: Y 3324 2.45.225 Fast Convergence 3326 Functionality/Description: MinRouteAdvertisementIntervalTimer 3327 used for internal peers SHOULD be shorter than the 3328 MinRouteAdvertisementIntervalTimer used for external peers, or 3330 RFC2119: SHOULD 3332 Alcatel Y/N/O/Comments: O Configurable on per peer basis. 3333 Cisco Y/N/O/Comments: Y 3334 Laurel Y/N/O/Comments: N they are same for ebgp and ibgp 3335 NextHop Y/N/O/Comments: Y Configuration option allows to set 3336 the time per peer. 3338 2.45.226 Fast Convergence 3340 ^L 3341 Functionality/Description: The procedure describes in this 3342 section SHOULD NOT apply for routes sent to internal peers 3344 RFC2119: SHOULD NOT 3346 Alcatel Y/N/O/Comments: O Operator has to ensure that through 3347 configuration. 3348 Cisco Y/N/O/Comments: Y 3349 Laurel Y/N/O/Comments: N 3350 NextHop Y/N/O/Comments: Y Default setting is off for BGP 3351 peers. 3353 2.45.227 MinRouteAdvertisementIntervalTimer 3355 Functionality/Description: The last route selected SHALL be 3356 advertised at the end of MinRouteAdvertisementIntervalTimer 3358 RFC2119: SHALL 3360 Alcatel Y/N/O/Comments: Y 3361 Cisco Y/N/O/Comments: Y 3362 Laurel Y/N/O/Comments: Y 3363 NextHop Y/N/O/Comments: Y 3365 3.46 Aggregating Routing Information / Section 9.2.2.2 3367 2.46.228 MULTI_EXIT_DISC 3369 Functionality/Description: Routes that have different 3370 MULTI_EXIT_DISC attribute SHALL NOT be aggregated 3372 RFC2119: SHALL NOT 3374 Alcatel Y/N/O/Comments: N 3375 Cisco Y/N/O/Comments: N 3376 Laurel Y/N/O/Comments: N 3377 NextHop Y/N/O/Comments: Y 3379 2.46.229 AS_SET as the First Element 3381 Functionality/Description: If the aggregated route has an AS_SET 3382 as the first element in its AS_PATH attribute, then the router 3383 that originates the route SHOULD NOT advertise the 3384 MULTI_EXIT_DISC attribute with this route 3386 ^L 3387 RFC2119: SHOULD NOT 3389 Alcatel Y/N/O/Comments: Y 3390 Cisco Y/N/O/Comments: Y 3391 Laurel Y/N/O/Comments: Y 3392 NextHop Y/N/O/Comments: Y 3394 2.46.230 NEXT_HOP 3396 Functionality/Description: When aggregating routes that have 3397 different NEXT_HOP attribute, the NEXT_HOP attribute of the 3398 aggregated route SHALL identify an interface on the BGP speaker 3399 that performs the aggregation 3401 RFC2119: SHALL 3403 Alcatel Y/N/O/Comments: Y 3404 Cisco Y/N/O/Comments: Y 3405 Laurel Y/N/O/Comments: Y 3406 NextHop Y/N/O/Comments: Y 3408 2.46.231 ORIGIN INCOMPLETE 3410 Functionality/Description: Used if at least one route among 3411 routes that are aggregated has ORIGIN with the value INCOMPLETE 3413 RFC2119: MUST 3415 Alcatel Y/N/O/Comments: Y 3416 Cisco Y/N/O/Comments: Y 3417 Laurel Y/N/O/Comments: Y 3418 NextHop Y/N/O/Comments: Y 3420 2.46.232 ORIGIN EGP 3422 Functionality/Description: Used if at least one route among 3423 routes that are aggregated has ORIGIN with the value EGP 3425 RFC2119: MUST 3427 Alcatel Y/N/O/Comments: Y 3428 Cisco Y/N/O/Comments: Y 3429 Laurel Y/N/O/Comments: Y 3430 NextHop Y/N/O/Comments: Y 3432 ^L 3434 2.46.233 Routes to be aggregated have different AS_PATH attributes 3436 Functionality/Description: The aggregated AS_PATH attribute 3437 SHALL satisfy all of the following conditions: ... 3439 RFC2119: SHALL 3441 Alcatel Y/N/O/Comments: Y 3442 Cisco Y/N/O/Comments: N 3443 Laurel Y/N/O/Comments: Y 3444 NextHop Y/N/O/Comments: Y 3446 2.46.234 Routes to be aggregated have different AS_PATH attributes 3448 Functionality/Description: All tuples of type AS_SEQUENCE in the 3449 aggregated AS_PATH SHALL appear in all of the AS_PATH in the 3450 initial set of routes to be aggregated 3452 RFC2119: SHALL 3454 Alcatel Y/N/O/Comments: Y 3455 Cisco Y/N/O/Comments: Y 3456 Laurel Y/N/O/Comments: Y 3457 NextHop Y/N/O/Comments: Y 3459 2.46.235 Routes to be aggregated have different AS_PATH attributes 3461 Functionality/Description: All tuples of type AS_SET in the 3462 aggregated AS_PATH SHALL appear in at least one of the AS_PATH 3463 in the initial set 3465 RFC2119: SHALL 3467 Alcatel Y/N/O/Comments: Y 3468 Cisco Y/N/O/Comments: Y 3469 Laurel Y/N/O/Comments: Y 3470 NextHop Y/N/O/Comments: Y 3472 2.46.236 Routes to be aggregated have different AS_PATH attributes 3474 Functionality/Description: For any tuple X of type AS_SEQUENCE 3475 in the aggregated AS_PATH which precedes tuple Y in the 3476 aggregated AS_PATH, X precedes Y in each AS_PATH in the initial 3477 set which contains Y, regardless of the type of Y 3479 RFC2119: N/A 3481 ^L 3482 Alcatel Y/N/O/Comments: Y 3483 Cisco Y/N/O/Comments: N 3484 Laurel Y/N/O/Comments: Y 3485 NextHop Y/N/O/Comments: Y 3487 2.46.237 Routes to be aggregated have different AS_PATH attributes 3489 Functionality/Description: No tuple of type AS_SET with the same 3490 value SHALL appear more than once in the aggregated AS_PATH 3492 RFC2119: SHALL 3494 Alcatel Y/N/O/Comments: Y 3495 Cisco Y/N/O/Comments: Y 3496 Laurel Y/N/O/Comments: Y 3497 NextHop Y/N/O/Comments: Y 3499 2.46.238 Routes to be aggregated have different AS_PATH attributes 3501 Functionality/Description: Multiple tuples of type AS_SEQUENCE 3502 with the same value may appear in the aggregated AS_PATH only 3503 when adjacent to another tuple of the same type and value 3505 RFC2119: N/A 3507 Alcatel Y/N/O/Comments: Y 3508 Cisco Y/N/O/Comments: N 3509 Laurel Y/N/O/Comments: N 3510 NextHop Y/N/O/Comments: Y 3512 2.46.239 AS_PATH Aggregation Algorithm 3514 Functionality/Description: Able to perform the (minimum) 3515 algorithm described in 9.2.2.2. 3517 RFC2119: SHALL 3519 Alcatel Y/N/O/Comments: Y 3520 Cisco Y/N/O/Comments: N We don't do merging. 3521 Laurel Y/N/O/Comments: Y 3522 NextHop Y/N/O/Comments: Y 3524 2.46.240 ATOMIC_AGGREGATE 3526 Functionality/Description: The aggregated route SHALL have this 3528 ^L 3529 attribute if at least one of the routes to be aggregated has it 3531 RFC2119: SHALL 3533 Alcatel Y/N/O/Comments: Y 3534 Cisco Y/N/O/Comments: Y 3535 Laurel Y/N/O/Comments: Y 3536 NextHop Y/N/O/Comments: Y 3538 2.46.241 AGGREGATOR 3540 Functionality/Description: Attribute from routes to be 3541 aggregated MUST NOT be included in aggregated route 3543 RFC2119: MUST NOT 3545 Alcatel Y/N/O/Comments: Y 3546 Cisco Y/N/O/Comments: Y 3547 Laurel Y/N/O/Comments: Y 3548 NextHop Y/N/O/Comments: Y 3550 2.46.242 AGGREGATOR 3552 Functionality/Description: Attach a new one when aggregating 3553 (see Section 5.1.7) 3555 RFC2119: MAY 3557 Alcatel Y/N/O/Comments: Y 3558 Cisco Y/N/O/Comments: Y 3559 Laurel Y/N/O/Comments: Y 3560 NextHop Y/N/O/Comments: Y 3562 3.47 Route Selection Criteria / Section 9.3 3564 2.47.243 Unstable routes 3566 Functionality/Description: Avoid using them 3568 RFC2119: SHOULD 3570 Alcatel Y/N/O/Comments: Y 3571 Cisco Y/N/O/Comments: Y 3572 Laurel Y/N/O/Comments: Y 3573 NextHop Y/N/O/Comments: Y 3575 ^L 3577 2.47.244 Route changes 3579 Functionality/Description: SHOULD NOT make rapid spontaneous 3580 changes to the choice of route 3582 RFC2119: SHOULD NOT 3584 Alcatel Y/N/O/Comments: Y 3585 Cisco Y/N/O/Comments: Y 3586 Laurel Y/N/O/Comments: Y 3587 NextHop Y/N/O/Comments: Y 3589 3.48 Originating BGP routes / Section 9.4 3591 2.48.245 Non-BGP acquired routes 3593 Functionality/Description: Distributed to other BGP speakers 3594 within the local AS as part of the update process 3595 (see Section 9.2) 3597 RFC2119: MAY 3599 Alcatel Y/N/O/Comments: Y 3600 Cisco Y/N/O/Comments: Y 3601 Laurel Y/N/O/Comments: Y 3602 NextHop Y/N/O/Comments: Y 3604 2.48.246 Non-BGP acquired routes 3606 Functionality/Description: Distribution controlled via 3607 configuration 3609 RFC2119: SHOULD 3611 Alcatel Y/N/O/Comments: Y 3612 Cisco Y/N/O/Comments: Y 3613 Laurel Y/N/O/Comments: Y 3614 NextHop Y/N/O/Comments: Y 3616 3.49 BGP Timers / Section 10 3618 2.49.247 Optional Timers 3620 Functionality/Description: Two optional timers MAY be supported: 3621 DelayOpenTimer, IdleHoldTimer by BGP 3623 ^L 3624 RFC2119: MAY 3626 Alcatel Y/N/O/Comments: N 3627 Cisco Y/N/O/Comments: O We support DelayOpenTimer but not 3628 IdleHoldTimer 3629 Laurel Y/N/O/Comments: Y support IdleHoldTimer but not the 3630 DelayOpenTimer 3631 NextHop Y/N/O/Comments: Y 3633 2.49.248 Hold Time 3635 Functionality/Description: Configurable on a per peer basis 3637 RFC2119: MUST 3639 Alcatel Y/N/O/Comments: Y 3640 Cisco Y/N/O/Comments: Y 3641 Laurel Y/N/O/Comments: Y 3642 NextHop Y/N/O/Comments: Y 3644 2.49.249 Timers 3646 Functionality/Description: Allow the other timers to be 3647 configurable 3649 RFC2119: MAY 3651 Alcatel Y/N/O/Comments: Y 3652 Cisco Y/N/O/Comments: Y 3653 Laurel Y/N/O/Comments: Y 3654 NextHop Y/N/O/Comments: Y 3656 2.49.250 Jitter 3658 Functionality/Description: Applied to the timers associated with 3659 MinASOriginationInterval, KeepAlive, 3660 MinRouteAdvertisementInterval, and ConnectRetry 3662 RFC2119: SHOULD 3664 Alcatel Y/N/O/Comments: Y 3665 Cisco Y/N/O/Comments: O We only apply to ConnectRetry. 3666 Laurel Y/N/O/Comments: Y 3667 NextHop Y/N/O/Comments: Y 3669 ^L 3671 2.49.251 Jitter 3673 Functionality/Description: Apply the same jitter to each of 3674 these quantities regardless of the destinations to which the 3675 updates are being sent; that is, jitter need not be configured 3676 on a "per peer" basis 3678 RFC2119: MAY 3680 Alcatel Y/N/O/Comments: Y 3681 Cisco Y/N/O/Comments: Y We apply same only for connectretry. 3682 Laurel Y/N/O/Comments: Y 3683 NextHop Y/N/O/Comments: Y 3685 2.49.252 Default amount of jitter 3687 Functionality/Description: Determined by multiplying the base 3688 value of the appropriate timer by a random factor which is 3689 uniformly distributed in the range from 0.75 to 1.0 3691 RFC2119: SHALL 3693 Alcatel Y/N/O/Comments: Y Range is 0.9 to 1.1 3694 Cisco Y/N/O/Comments: Y 3695 Laurel Y/N/O/Comments: Y 3696 NextHop Y/N/O/Comments: Y 3698 2.49.253 Default amount of jitter 3700 Functionality/Description: New random value picked each time the 3701 timer is set 3703 RFC2119: SHOULD 3705 Alcatel Y/N/O/Comments: Y 3706 Cisco Y/N/O/Comments: Y 3707 Laurel Y/N/O/Comments: Y 3708 NextHop Y/N/O/Comments: Y 3710 2.49.254 Jitter Random Value Range 3712 Functionality/Description: Configurable 3714 RFC2119: MAY 3716 Alcatel Y/N/O/Comments: N 3717 Cisco Y/N/O/Comments: N 3718 Laurel Y/N/O/Comments: Y 3720 ^L 3721 NextHop Y/N/O/Comments: N 3723 3.50 TCP options that may be used with BGP / Appendix E 3725 2.50.255 TCP PUSH function supported 3727 Functionality/Description: Each BGP message SHOULD be 3728 transmitted with PUSH flag set 3730 RFC2119: SHOULD 3732 Alcatel Y/N/O/Comments: Y 3733 Cisco Y/N/O/Comments: Y 3734 Laurel Y/N/O/Comments: Y 3735 NextHop Y/N/O/Comments: O Depends on the TCP stack support. 3736 GateD 10, NGC can run over 3737 multiple stacks. 3739 2.50.256 DSCP Field Support 3741 Functionality/Description: TCP connections opened with bits 0-2 3742 of the DSCP field set to 110 (binary) 3744 RFC2119: SHOULD 3746 Alcatel Y/N/O/Comments: Y 3747 Cisco Y/N/O/Comments: Y 3748 Laurel Y/N/O/Comments: Y 3749 NextHop Y/N/O/Comments: O Depends on the TCP stack support. 3750 GateD 10, NGC can run over 3751 multiple stacks. 3753 3.51 Reducing route flapping / Appendix F.2 3755 2.51.257 Avoid excessive route flapping 3757 Functionality/Description: A BGP speaker which needs to withdraw 3758 a destination and send an update about a more specific or less 3759 specific route SHOULD combine them into the same UPDATE message 3761 RFC2119: SHOULD 3763 Alcatel Y/N/O/Comments: Y 3764 Cisco Y/N/O/Comments: N 3765 Laurel Y/N/O/Comments: N 3766 NextHop Y/N/O/Comments: N 3768 ^L 3770 3.52 Complex AS_PATH aggregation / Appendix F.6 3772 2.52.258 Multiple instances in AS_PATH 3774 Functionality/Description: The last instance (rightmost 3775 occurrence) of that AS number is kept 3777 RFC2119: SHOULD 3779 Alcatel Y/N/O/Comments: N We use algorithm in 9.2.2.2 3780 Cisco Y/N/O/Comments: N 3781 Laurel Y/N/O/Comments: N 3782 NextHop Y/N/O/Comments: N 3784 3.53 Security Considerations 3786 2.53.259 Authentication Mechanism 3788 Functionality/Description: RFC2385 3790 RFC2119: MUST 3792 Alcatel Y/N/O/Comments: Y 3793 Cisco Y/N/O/Comments: Y 3794 Laurel Y/N/O/Comments: Y 3795 NextHop Y/N/O/Comments: Y 3797 4. Additional BGP implementations Information 3799 Three implementations responded to a call (5/20/04-6/2/04) for 3800 information on those implementations that had a BGP implementation, 3801 but did not complete the full survey. The responses for the call for 3802 additional information are below. 3804 4.1 Avici 3806 If you have an implementation of BGP and you did not send in an 3807 implementation report (answering the 259 questions), could you send 3808 me the answer the following questions: 3810 1) BGP product 3811 Contributor (your name):Curtis Villamizar [curtis@fictitious.org] 3812 Company: Avici 3813 name of product: IPriori (TM) 3814 minor version: No interoperability problems with any version. 3816 ^L 3817 Current deployed versions are 5.x and 6.0.x. 3818 Version 6.1 and beyond are tested against the 3819 latest BGP draft soon to replace rfc1771. 3821 2) What other implementations you interoperate with. 3823 Cisco: IOS 12.0(22) 3824 Juniper: JUNOS (version not given) 3826 3) Do you inter-operate with: 3828 1) Alcatel BGP (release) - not tested 3829 2) cisco BGP IOS 12.0(27)s - not tested 3830 tested with IOS 12.0(22); BGP is the same 3832 3) laurel BGP (specify release) - not tested 3833 4) NextHop GateD- not tested 3835 4) Did the length of the survey for BGP cause you to not 3836 submit the BGP implementation report? 3838 yes 3840 4.2 Data Connection Ltd. 3842 If you have an implementation of BGP and you did not send in an 3843 implementation report (answering the 259 questions), could you send 3844 me the answer the following questions: 3846 1) BGP product 3847 Contributor (your name): Mike Dell 3848 Company: Data Connection Ltd. 3849 name of product: DC-BGP 3850 version and minor of software: v1.1 3851 release date: April 2003 3853 2) What other implementations you interoperate with. 3855 Cisco (12.0(26)S) 3856 Alcatal (7770 0BX) 3857 Agilent (Router Tester) 3858 Ixia (1600T) 3859 Netplane (Powercode) 3860 Nortel (Shasta 5000 BSN) 3861 Redback (SmartEdge 800) 3862 Riverstone (RS8000) 3863 Spirent (AX4000) 3865 ^L 3866 IP Infusion (ZebOs) 3867 Nokia (IP400) 3868 Juniper (M5) 3870 3) Do you inter-operate with 3872 1) Alcatel BGP (release) YES 3873 2) cisco BGP IOS 12.0(27)s 3874 Unknown, but we do inter-operate with v12.0(26)s 3875 3) laurel BGP (specify release) Unknown 3876 4) NextHop GateD YES 3878 4) Did the length of the survey for BGP 3879 cause you to not submit the BGP 3880 implementation report? 3882 YES 3884 4.3 Nokia BGP 3886 If you have an implementation of BGP and you did not send in an 3887 implementation report (answering the 259 questions), could you send 3888 me the answer the following questions: 3890 1) BGP product 3892 Contributor (your name):Rahul Bahadur 3893 (rahul.bahadur@nokia.com) 3894 Company: Nokia 3895 Name of product: IP Security Platforms 3896 Version and minor of software IPSO 3.8 Build031 3897 Release date May 24, 2004 3899 2) What other implementations you interoperate with. 3901 Cisco: IOS 12.3(1) 3902 Extreme: Extremeware Version 6.1.7 (Build 9) 3903 Foundry: SW Version 07.5.05iT53 3904 Juniper: JUNOS 5.3R1.2 3905 Nortel: BayRS 15.4.0.1 3906 GNU Zebra: zebra-0.92a 3908 3) Do you inter-operate with 3910 1) Alcatel BGP (release) - not tested 3911 2) cisco BGP IOS 12.0(27)s - yes 3912 3) laurel BGP (specify release) - not tested 3913 4) NextHop GateD- not tested 3915 ^L 3917 4) Did the length of the survey for BGP 3918 cause you to not submit the BGP implementation report? 3920 Yes - lack of resources to help with task. 3922 Security Considerations 3924 This document does not address any security issues. 3926 Normative References 3928 [BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway Protocol 4 3929 (BGP-4)", draft-ietf-idr-bgp4-24.txt, June 2004 3931 [RFC1771] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 3932 (BGP-4)", RFC1771, March 1995 3934 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3935 Requirement Levels", BCP 14, March 1997 3937 [RFC2385] A. Heffernan, "Protection of BGP Session via a TCP MD5 3938 Signature", RFC2385, August 1998 3940 [RFC2796] Bates, T., Chandra, R., Chen, E., "BGP Route Reflection - 3941 an Alternative to Full Mesh IBGP", RFC 2796, April 2000 3943 [RFC2918] Chen, E., "Route Refresh Capability for BGP-4", RFC2918, 3944 September 2000 3946 [RFC3065] Traina, P., McPherson, D., Scudder, J., "Autonomous 3947 Confederations for BGP", RFC 3065, February 2001 3949 [RFC3667] Bradner, S., "IETF Rights in Contributions", BCP 78, 3950 February 2004 3952 [RFC3668] Bradner, S. "Intellectual Property Rights in IETF 3953 Technology", BCP 79, February 2004 3955 ^L 3957 Acknowledgments 3959 Alcatel Responses provided by: 3960 Contact Name: Devendra Raut 3961 Contact Email: Devendra.raut@Alcatel.com 3963 Cisco Systems Responses provided by: 3964 Contact Name: Himanshu Shah, Ruchi Kapoor 3965 Contact e-mail Address: hhshah@cisco.com, ruchi@cisco.com 3967 Laurel Responses provided by: 3968 Contact Name: Manish Vora 3969 Contact e-mail Address: vora@laurelnetworks.com 3971 NextHop Responses provided by: 3972 Contact Name: Susan Hares 3973 Contact e-mail Address: skh@nexthop.com 3974 Additional Help: Matt Richardson, Shane Wright. 3976 Authors' Addresses 3978 Susan Hares 3979 NextHop Technologies 3980 825 Victors Way, Suite 100 3981 Phone: 734.222.1610 3982 Email: skh@nexthop.com 3984 Alvaro Retana 3985 Cisco Systems, Inc. 3986 7025 Kit Creek Rd. 3987 Research Triangle Park, NC 27709 3988 Phone: 919 392 2061 3989 e-mail: aretana@cisco.com 3991 Intellectual Property Statement 3993 The IETF takes no position regarding the validity or scope of any 3994 Intellectual Property Rights or other rights that might be claimed 3995 to pertain to the implementation or use of the technology 3996 described in this document or the extent to which any license 3997 under such rights might or might not be available; nor does it 3998 represent that it has made any independent effort to identify any 3999 such rights. Information on the procedures with respect to rights 4000 in RFC documents can be found in BCP 78 and BCP 79. 4002 ^L 4003 Copies of IPR disclosures made to the IETF Secretariat and any 4004 assurances of licenses to be made available, or the result of an 4005 attempt made to obtain a general license or permission for the use 4006 of such proprietary rights by implementers or users of this 4007 specification can be obtained from the IETF on-line IPR repository 4008 at http://www.ietf.org/ipr. 4010 The IETF invites any interested party to bring to its attention 4011 any copyrights, patents or patent applications, or other 4012 proprietary rights that may cover technology that may be required 4013 to implement this standard. Please address the information to the 4014 IETF at ietf-ipr@ietf.org. 4016 Disclaimer of Validity 4018 This document and the information contained herein are provided on 4019 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 4020 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 4021 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 4022 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 4023 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 4024 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4026 Copyright Statement 4028 Copyright (C) The Internet Society (2004). This document is subject 4029 to the rights, licenses and restrictions contained in BCP 78, and 4030 except as set forth therein, the authors retain all their rights. 4032 ^L