draft-ietf-idr-bgp-implementation-00.txt   draft-ietf-idr-bgp-implementation-01.txt 
Interdomain Working Group Interdomain Working Group
Internet Draft S. Hares Internet Draft S. Hares
Document: draft-ietf-idr-bgp-implementation-00.txt NextHop Document: draft-ietf-idr-bgp-implementation-01.txt NextHop
A. Retana A. Retana
Cisco Cisco
Expires: August 2004 February 2004 Expires: August 2004 July 2004
BGP 4 Implementation Report BGP 4 Implementation Report
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, we certify that any applicable
all provisions of Section 10 of RFC2026 [1]. patent or other IPR claims of which we are aware have been
disclosed, or will be disclosed, and any of which we become aware
will be disclosed, in accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as
Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six
and may be updated, replaced, or obsoleted by other documents at any months and may be updated, replaced, or obsoleted by other
time. It is inappropriate to use Internet-Drafts as reference documents at any time. It is inappropriate to use Internet-Drafts
material or to cite them other than as "work in progress." as reference material or to cite them other than as "work in
progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt .
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. This document may not be modified, and derivative works of it may
not be created, except to publish it as an RFC and to translate it
into languages other than English.
Abstract Abstract
This document provides a survey of the BGP-4 implementation draft- This document provides a survey of the BGP-4 implementation draft-
ietf-idr-bgp4-23.txt. After a brief summary, each response is ietf-idr-bgp4-24.txt. After a brief summary, each response is
listed. The editor makes no claim as to the accuracy of the listed. The editor makes no claim as to the accuracy of the
information provided. information provided.
Conventions used in this document Conventions used in this document
^L
draft-ietf-idr-bgp-implementation-01 July 2004
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [2]. document are to be interpreted as described in RFC-2119 [1].
TABLE of CONTENTS TABLE of CONTENTS
1. Summary........................................................3 1. Introduction...................................................3
1.1 General....................................................3 2. Results of Survey..............................................4
1.2 Full Survey result summary.................................4 2.1 Differences................................................5
1.3 Differences................................................4 2.2 Implementations and interoperability.......................6
1.4 Implementations and interoperability.......................5 2.3 BGP Implementation Identification..........................7
1.5 BGP Implementation Identification..........................5 3. BGP4 Implementation Report.....................................7
2. BGP4 Implementation Report.....................................6 2.0 Summary of Operation / Section 3...........................7
2.0 Summary of Operation / Section 3...........................6 3.1 Routes: Advertisement and Storage / Section 3.1............8
2.1 Routes: Advertisement and Storage / Section 3.1............6 3.2 Routing Information Bases / Section 3.2....................9
2.2 Routing Information Bases / Section 3.2....................7 3.3 Message Formats / Section 4................................9
2.3 Message Formats / Section 4................................8 3.4 Message Header Format / Section 4.1........................9
2.4 Message Header Format / Section 4.1........................8 3.5 OPEN Message / Section 4.2................................11
2.5 OPEN Message / Section 4.2.................................9 3.6 UPDATE Message Format / Section 4.3.......................11
2.6 UPDATE Message Format / Section 4.3.......................10 3.7 KEEPALIVE Message Format / Section 4.4....................15
2.7 KEEPALIVE Message Format / Section 4.4....................13 3.8 NOTIFICATION Message Format / Section 4.5.................15
2.8 NOTIFICATION Message Format / Section 4.5.................14 3.9 Path Attributes /Section 5................................16
2.9 Path Attributes /Section 5................................14 3.10 ORIGIN / Section 5.1.1...................................19
2.10 ORIGIN / Section 5.1.1...................................18 3.11 AS_PATH / Section 5.1.2..................................20
2.11 AS_PATH / Section 5.1.2..................................18 3.12 NEXT_HOP / Section 5.1.3.................................21
2.12 NEXT_HOP / Section 5.1.3.................................19 3.13 MULTI_EXIT_DISC / Section 5.1.4..........................24
2.13 MULTI_EXIT_DISC / Section 5.1.4..........................23 3.14 LOCAL_PREF / Section 5.1.5...............................26
2.14 LOCAL_PREF / Section 5.1.5...............................25 3.15 ATOMIC_AGGREGATE / Section 5.1.6.........................28
2.15 ATOMIC_AGGREGATE / Section 5.1.6.........................26 3.16 AGGREGATOR / Section 5.1.7...............................29
2.16 AGGREGATOR / Section 5.1.7...............................27 3.17 BGP Error Handling / Section 6...........................30
2.17 BGP Error Handling / Section 6...........................28 3.18 Message Header Error Handling / Section 6.1..............30
2.18 Message Header Error Handling / Section 6.1..............29 3.19 OPEN message error handling / Section 6.2................32
2.19 OPEN message error handling / Section 6.2................30 3.20 UPDATE message error handling / Section 6.3..............35
2.20 UPDATE message error handling / Section 6.3..............33 3.21 NOTIFICATION message error handling / Section 6.4........44
2.21 NOTIFICATION message error handling / Section 6.4........42 3.22 Hold Timer Expired error handling / Section 6.5..........44
2.22 Hold Timer Expired error handling / Section 6.5..........43 3.23 Finite State Machine error handling / Section 6.6........45
2.23 Finite State Machine error handling / Section 6.6........43 3.24 Cease / Section 6.7......................................45
2.24 Cease / Section 6.7......................................43 3.25 BGP connection collision detection / Section 6.8.........46
2.25 BGP connection collision detection / Section 6.8.........45 3.26 BGP Version Negotiation / Section 7......................47
2.26 BGP Version Negotiation / Section 7......................46 3.27 BGP Finite State machine (FSM) / Section 8...............48
2.27 BGP Finite State machine (FSM) / Section 8...............46 3.28 Administrative Events / Section 8.1.2....................48
2.28 Administrative Events / Section 8.1.2....................47 3.29 Timer Events / Section 8.1.3.............................53
2.29 Timer Events / Section 8.1.3.............................52 3.30 TCP Connection based Events / Section 8.1.4..............55
2.30 TCP Connection based Events / Section 8.1.4..............53 3.31 BGP Messages based Events / Seciton 8.1.5................56
2.31 BGP Messages based Events / Seciton 8.1.5................54 3.32 FSM Definition / Section 8.2.1...........................57
2.32 FSM Definition / Section 8.2.1...........................56 3.33 FSM and collision detection / Section 8.2.1.2............58
2.33 FSM and collision detection / Section 8.2.1.2............56 3.34 FSM Event numbers / Section 8.2.1.4......................58
2.34 FSM Event numbers / Section 8.2.1.4......................57 3.35 Finite State Machine / Section 8.2.2.....................59
2.35 Finite State Machine / Section 8.2.2.....................57
2.36 UPDATE Message Handling / Section 9......................58
2.37 Decision Process / Section 9.1...........................59
2.38 Phase 1: Calculation of Degree of Preference / Section 9.1.1
..............................................................60
2.39 Phase 2: Route Selection / Section 9.1.2.................61
2.40 Route Resolvability Condition / Section 9.1.2.1..........63
2.41 Breaking Ties (Phase 2) / Section 9.1.2.2................63
2.42 Phase 3: Route Dissemination / Section 9.1.3.............65
2.43 Overlapping Routes / Section 9.1.4.......................66
2.44 Update-Send Process / Section 9.2........................67
2.45 Frequency of Route Advertisement / Section 9.2.1.1.......69
2.46 Aggregating Routing Information / Section 9.2.2.2........71
2.47 Route Selection Criteria / Section 9.3...................75
2.48 Originating BGP routes / Section 9.4.....................75
2.49 BGP Timers / Section 10..................................76
2.50 TCP options that may be used with BGP / Appendix E.......78
2.51 Reducing route flapping / Appendix F.2...................79
2.52 Complex AS_PATH aggregation / Appendix F.6...............79
2.53 Security Considerations..................................79
Security Considerations..........................................80
References.......................................................80
Acknowledgments..................................................80
Author's Addresses...............................................81
1. Summary ^L
draft-ietf-idr-bgp-implementation-01 July 2004
1.1 General 3.36 UPDATE Message Handling / Section 9......................59
3.37 Decision Process / Section 9.1...........................61
3.38 Phase 1: Calculation of Degree of Preference / Section 9.1.1
..............................................................62
3.39 Phase 2: Route Selection / Section 9.1.2.................62
3.40 Route Resolvability Condition / Section 9.1.2.1..........64
3.41 Breaking Ties (Phase 2) / Section 9.1.2.2................65
3.42 Phase 3: Route Dissemination / Section 9.1.3.............66
3.43 Overlapping Routes / Section 9.1.4.......................67
3.44 Update-Send Process / Section 9.2........................69
3.45 Frequency of Route Advertisement / Section 9.2.1.1.......71
3.46 Aggregating Routing Information / Section 9.2.2.2........72
3.47 Route Selection Criteria / Section 9.3...................76
3.48 Originating BGP routes / Section 9.4.....................77
3.49 BGP Timers / Section 10..................................77
3.50 TCP options that may be used with BGP / Appendix E.......80
3.51 Reducing route flapping / Appendix F.2...................80
3.52 Complex AS_PATH aggregation / Appendix F.6...............81
3.53 Security Considerations..................................81
4. Additional BGP implementations Information....................81
4.1 Avici.....................................................81
4.2 Data Connection Ltd.......................................82
4.3 Nokia BGP.................................................83
Security Considerations..........................................84
Normative References.............................................84
Acknowledgments..................................................85
Authors' Addresses...............................................85
Copyright Statement..............................................86
This draft of BGP-4 attempts to bring BGP standard as described in 1. Introduction
RFC 1771 in alignment with the deployments of the BGP-4 protocols.
The changes with RFC 1771 are listed in the appendix A of[BGP4]. This revision of the BGP-4 standard [BGP4] updates the BGP standard
BGP-4 as deployed in the Internet encompasses both this base [RFC1771] to be in alignment with the deployments of the BGP-4
specification and additional specifications such as TCP MD5 protocols. BGP-4 as deployed in the Internet encompasses both this
base specification and additional specifications such as TCP MD5
[RFC2385], BGP Route Reflectors [RFC 2796], BGP Confederations [RFC2385], BGP Route Reflectors [RFC 2796], BGP Confederations
[RFC3065], and BGP Route Refresh [RFC 2918]. [RFC3065], and BGP Route Refresh [RFC 2918].
BGP as a widely deployed cornerstone of Internet technology BGP as a widely deployed cornerstone of Internet technology
continues to add additional functionality as the needs within the continues to add additional functionality as the needs within the
Internet require. This survey had 259 detailed questions on the Internet requires. This survey has 259 detailed questions on the
compliances with the standard. 3 implementers (Cisco, Laurel, compliance with the revised standard. 4 implementers (Alcatel,
NextHop) sent in implementation reports. Sections X - Y provides Cisco, Laurel, NextHop) sent in implementation reports. Section 2
the compilation of those results. provides a compilation of those results.
X implementers who responded below indicating inter-operability with Section 1.3 provides the quick survey results on inter-operability.
other implementations. Of these X implementations, Y also indicated Section 1.4 provides an inter-operability of the 4 implementations.
the length of the survey was as problem. The editor recommends that
other methods, such as enlisting existing testing vendors be
employed to gather more implementation report.
Section Z provides the quick survey results on inter-operability. ^L
draft-ietf-idr-bgp-implementation-01 July 2004
1.2 Full Survey result summary Due to the large number of BGP implementations and the small number
of responses, the editors took an informal survey to determine if
the length of survey was an issue. Three implementers responded,
and all indicated the length of the survey was the issue. Section 3
gives this informal survey results.
The editors have compiled the submitted survey results and the
informal survey results. We do not guarantee the accuracy of the
responses.
2. Results of Survey
Significant Differences Significant Differences
All 259 survey points had two "y" or "y" and "O" except the For every item listed (259 questions), the respondents indicated
following: whether their implementation supports the Functionality/Description
or not (Y/N) indicated by the RFC2199 [RFC2119] language. Of the 259
questions in the survey, had two implementations giving an
affirmative response(two "y" or "y" and "O") except the following:
MUST - Question 214 a) Must - Linked questions 212/213, regarding section 9.1.4
Question 214 about aggregation of routes. section 9.1.4 had a "N" The linking of the questions lead to question 213 having three
response from 3 implementers indicating that they install both vendors (Cisco, Laurel, and NextHop) give a "no" as the second
routes, and 1 yes. half of a question due to the format of the survey question.
(See the next section for details).
SHALL NOT - Question 228, regarding section 9.2.2.2 b) SHALL NOT - Question 228, regarding section 9.2.2.2
Three vendors (Alcatel, Cisco, Laurel), answered "N" to shall not Three vendors (Alcatel, Cisco, Laurel), answered "N" to shall
(meaning they did). One vendor (NextHop) indicate "y" matching not (meaning they did). One vendor (NextHop) indicated "O"
the specification. matching the specification.
text: Routes that have different MULTI_EXIT_DISC attribute SHALL Text: Routes that have different MULTI_EXIT_DISC attribute
NOT be aggregated. SHALL NOT be aggregated.
SHOULD - 2 in appendix F (questions 257, 258) c) SHOULD - 2 in appendix F (questions 257, 258)
Three vendors said no, one vendor said yes to question 257. All Three vendors said no, one vendor said yes to question 257.
four vendors indicated no to question 258. (Please note that All four vendors indicated no to question 258. (Please note
Appendix F is an optional text section) that Appendix F is text section for optional support.
Text: section F.2 - A BGP speaker which needs to withdraw a Text: Section F.2 - A BGP speaker which needs to withdraw a
destination and send an update about a more specific or less destination and send an update about a more specific or
specific route SHOULD combine them into the same UPDATE message.
^L
draft-ietf-idr-bgp-implementation-01 July 2004
less specific route SHOULD combine them into the same
UPDATE message.
Text: Section F.6: The last instance (rightmost occurrence) of Text: Section F.6: The last instance (rightmost occurrence) of
that AS number is kept. that AS number is kept.
1.3 Differences d) MAY - 1 in section 8.1.2.4, 1 in Section 10 (question 254)
Section 8: 3 "No", 1 yes
Text: "The Event numbers (1-28) utilized in this state machine
description aid in specifying the behavior of the BGP
state machine. Implementations MAY use these numbers to
provide network management information. The exact form of
a FSM or the FSM events are specific to each
implementation."
Editors note: Section 8.1.2.4 was written to allow existing
implementations to transition to the new event
numbering. It was expected over time (3 years)
that the FSM event numbering would be updated to
the new numbering.
Section 10: 3 "no"
Three vendors answered "no" configurable jitter time values.
One vendor indicated a configurable jitter timer value.
Text: A given BGP speaker MAY apply the same jitter to each of
these quantities regardless of the destinations to
which the updates are being sent; that is, jitter need
not be configured on a "per peer" basis.
Question: Is the jitter range configurable?
2.1 Differences
The following section provides a list of sections where all answers The following section provides a list of sections where all answers
were not "yes". This section is provided to allow the reader a short were not "yes". This section is provided to allow the reader a short
cut to the interesting points. cut to the interesting points.
Differences are found in Subsections: Differences are found in Subsections:
^L
draft-ietf-idr-bgp-implementation-01 July 2004
MUST MUST
8, 97, 106, 107, 111, 122, 125, 138, 141, 213, 232 97, 106, 107, 111, 122, 125, 138, 141, 213
SHALL SHALL
233, 239 233, 239
SHALL NOT SHALL NOT
228 228
SHOULD SHOULD
42, 117, 132, 146, 152, 155, 156, 157, 158, 159, 160, 161, 163, 42, 117, 132, 146, 152, 155, 156, 157, 158, 159, 160, 161, 163,
164, 165, 169, 170, 171, 173, 174, 175, 202, 225, 250, 255, 256 164, 165, 169, 170, 171, 173, 174, 175, 202, 225, 250, 255, 256
SHOULD NOT SHOULD NOT
226 226
MAY MAY
94, 121, 180, 223, 247, 254 67, 94, 121, 143, 180, 223, 247, 254
Other Other
238 236, 238
1.4 Implementations and interoperability Linked Questions
Short informal summary of implementers reporting implementations and 212/213
inter-operability
[This section will be added later but will have the format below ] Question 213 about the aggregation of routes had 3 "N" and 1
"Y". Questions 212 and 213 are grouped together.
Question 212 states:
"The decision process MUST either install both routes" or
Question 213:
"Aggregate the two routes and install the aggregated route,
provided that both routes have the same value of the
NEXT_HOP attribute"
The four respondents that said "Y" to question 212, said "N" to
questions 213. Given the context of the question, the "N" to
question 213 is appropriate.
2.2 Implementations and interoperability
Alcatel Cisco Laurel NextHop Alcatel Cisco Laurel NextHop
Alcatel Alcatel Y Y
Cisco Cisco Y
Laurel Laurel Y Y
NextHop NextHop Y Y
1.5 BGP Implementation Identification ^L
draft-ietf-idr-bgp-implementation-01 July 2004
1.5.0 Alcatel 2.3 BGP Implementation Identification
1.5.1 Cisco 1.6.0 Alcatel
Implementation Name/Version:
Alcatel 7750 BGP Implementation Release 1.3
Date: July 2003
Contact Name: Devendra Raut
Contact Email: Devendra.raut@Alcatel.com
1.6.1 Cisco
Implementation Name/Version: Cisco BGP Implementation, 12.0(27)S Implementation Name/Version: Cisco BGP Implementation, 12.0(27)S
Contact Name: Alvaro Retana
Date: 11/26/2003 Date: 11/26/2003
1.5.2 Laurel 1.6.2 Laurel
Implementation Name/Version: Laurel Networks 3.0
Contact Name: Manish Vora
Contact Email: vora@laurelnetworks.com
Date: 2/1/2004
1.5.3 NextHop Technologies 1.6.3 NextHop Technologies
Implementation Name/Version: Gated NGC 2.0, 2.2 Implementation Name/Version: Gated NGC 2.0, 2.2
Date: January 2004 Date: January 2004
2. BGP4 Implementation Report 3. BGP4 Implementation Report
For every item listed, the respondents indicated whether their For every item listed, the respondents indicated whether their
implementation supports the Functionality/Description or not (Y/N) implementation supports the Functionality/Description or not (Y/N)
according to the RFC2119 [3] language indicated. Any respondent according to the RFC2119 [2] language indicated. Any respondent
comments are included. If appropriate, the respondents indicated comments are included. If appropriate, the respondents indicated
with O the fact that the support is neither Y/N (an alternate with O the fact that the support is neither Y/N (an alternate
behavior, for example). Refer to the appropriate sections in the behavior, for example). Refer to the appropriate sections in [BGP4]
latest BGP-4 ID [4] for additional details. for additional details.
2.0 Summary of Operation / Section 3 2.0 Summary of Operation / Section 3
2.0.1 Base Behavior 2.0.1 Base Behavior
Functionality/Description: Is your implementation compatible with Functionality/Description: Is your implementation compatible with
the base behavior described in this section? the base behavior described in this section?
RFC2119: N/A RFC2119: N/A
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.0.2 Local Policy Changes 2.0.2 Local Policy Changes
Functionality/Description: To allow local policy changes to have Functionality/Description: To allow local policy changes to have
the correct effect without resetting any BGP connections, a BGP the correct effect without resetting any BGP connections, a BGP
speaker SHOULD either (a) retain the current version of the speaker SHOULD either (a) retain the current version of the
skipping to change at page 6, line 45 skipping to change at page 8, line 29
the connection, or (b) make use of the Route Refresh extension the connection, or (b) make use of the Route Refresh extension
[RFC2918] [RFC2918]
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.1 Routes: Advertisement and Storage / Section 3.1 3.1 Routes: Advertisement and Storage / Section 3.1
2.1.3 Withdraw routes from service 2.1.3 Withdraw routes from service
Functionality/Description: Does your implementation support the Functionality/Description: Does your implementation support the
three methods described in this section? three methods described in this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 7, line 26 skipping to change at page 9, line 5
Functionality/Description: Added to or modified before Functionality/Description: Added to or modified before
advertising the route advertising the route
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.2 Routing Information Bases / Section 3.2 ^L
draft-ietf-idr-bgp-implementation-01 July 2004
3.2 Routing Information Bases / Section 3.2
2.2.5 Routing Information Bases 2.2.5 Routing Information Bases
Functionality/Description: Is your implementation compatible Functionality/Description: Is your implementation compatible
with the RIB structure described in this section? with the RIB structure described in this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 8, line 7 skipping to change at page 9, line 35
Loc-RIB MUST be resolvable via the local BGP speaker's Routing Loc-RIB MUST be resolvable via the local BGP speaker's Routing
Table Table
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.3 Message Formats / Section 4 3.3 Message Formats / Section 4
2.3.7 Message Size 2.3.7 Message Size
Functionality/Description: Does your implementation support the Functionality/Description: Does your implementation support the
message sizes described in this section? message sizes described in this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.4 Message Header Format / Section 4.1 3.4 Message Header Format / Section 4.1
2.4.8 Marker 2.4.8 Marker
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Functionality/Description: MUST be set to all ones Functionality/Description: MUST be set to all ones
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.4.9 Length 2.4.9 Length
skipping to change at page 9, line 26 skipping to change at page 11, line 5
message is allowed, so the Length field MUST have the smallest message is allowed, so the Length field MUST have the smallest
value required given the rest of the message value required given the rest of the message
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.5 OPEN Message / Section 4.2 ^L
draft-ietf-idr-bgp-implementation-01 July 2004
3.5 OPEN Message / Section 4.2
2.5.12 Hold Timer Calculation 2.5.12 Hold Timer Calculation
Functionality/Description: Use the smaller of its configured Functionality/Description: Use the smaller of its configured
Hold Time and the Hold Time received in the OPEN message Hold Time and the Hold Time received in the OPEN message
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 10, line 17 skipping to change at page 11, line 45
Functionality/Description: Based on the Hold Time Functionality/Description: Based on the Hold Time
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Sends notification. Cisco Y/N/O/Comments: Y Sends notification.
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.6 UPDATE Message Format / Section 4.3 3.6 UPDATE Message Format / Section 4.3
2.6.15 UPDATE 2.6.15 UPDATE
Functionality/Description: Simultaneously advertise a feasible Functionality/Description: Simultaneously advertise a feasible
route and withdraw multiple unfeasible routes from service route and withdraw multiple unfeasible routes from service
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: O We have capability to process this Cisco Y/N/O/Comments: O We have capability to process this
functionality on receiving end but functionality on receiving end but
we don't send feasible & unfeasible we don't send feasible & unfeasible
simultaneously. simultaneously.
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 11, line 25 skipping to change at page 13, line 5
Functionality/Description: Lower-order four bits set to zero Functionality/Description: Lower-order four bits set to zero
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.6.19 Attribute Flags octet receiving 2.6.19 Attribute Flags octet receiving
Functionality/Description: Lower-order four bits ignored Functionality/Description: Lower-order four bits ignored
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 12, line 24 skipping to change at page 14, line 4
2.6.22 AGGREGATOR IP Address 2.6.22 AGGREGATOR IP Address
Functionality/Description: Same address as the one used for the Functionality/Description: Same address as the one used for the
BGP Identifier of the speaker BGP Identifier of the speaker
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Default behavior. Can be configured Alcatel Y/N/O/Comments: Y Default behavior. Can be configured
different from BGP ID. different from BGP ID.
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.6.23 UPDATE messages that include the same address prefix in the 2.6.23 UPDATE messages that include the same address prefix in the
WITHDRAWN ROUTES and Network Layer Reachability Information fields WITHDRAWN ROUTES and Network Layer Reachability Information fields
Functionality/Description: UPDATE messages SHOULD NOT include Functionality/Description: UPDATE messages SHOULD NOT include
that information that information
skipping to change at page 13, line 24 skipping to change at page 15, line 5
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Withdrawn routes are processed Alcatel Y/N/O/Comments: Y Withdrawn routes are processed
before NLRI fields. Hence we get the before NLRI fields. Hence we get the
desired behavior. desired behavior.
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.7 KEEPALIVE Message Format / Section 4.4 ^L
draft-ietf-idr-bgp-implementation-01 July 2004
3.7 KEEPALIVE Message Format / Section 4.4
2.7.26 Maximum KEEPALIVE frequency 2.7.26 Maximum KEEPALIVE frequency
Functionality/Description: Not greater than one second Functionality/Description: Not greater than one second
RFC2119: MUST NOT RFC2119: MUST NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
skipping to change at page 14, line 15 skipping to change at page 15, line 44
Functionality/Description: No KEEPALIVEs sent Functionality/Description: No KEEPALIVEs sent
RFC2119: MUST NOT RFC2119: MUST NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.8 NOTIFICATION Message Format / Section 4.5 3.8 NOTIFICATION Message Format / Section 4.5
2.8.29 NOTIFICATION Message 2.8.29 NOTIFICATION Message
Functionality/Description: Does your implementation support the Functionality/Description: Does your implementation support the
NOTIFICATION Message as described in this section? NOTIFICATION Message as described in this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.9 Path Attributes /Section 5 3.9 Path Attributes /Section 5
2.9.30 Path attributes 2.9.30 Path attributes
Functionality/Description: Does your implementation support the Functionality/Description: Does your implementation support the
path attributes as described in this section? path attributes as described in this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 15, line 24 skipping to change at page 17, line 5
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.9.33/34 Discretionary Attributes 2.9.33/34 Discretionary Attributes
Functionality/Description: Sent in a particular UPDATE message Functionality/Description: Sent in a particular UPDATE message
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: MAY or MAY NOT RFC2119: MAY or MAY NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.9.35 Well-known attributes 2.9.35 Well-known attributes
Functionality/Description: Passed along (after proper updating, Functionality/Description: Passed along (after proper updating,
skipping to change at page 16, line 23 skipping to change at page 18, line 4
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.9.38 Partial Bit for unrecognized transitive optional attributes 2.9.38 Partial Bit for unrecognized transitive optional attributes
Functionality/Description: Set to 1 if the attribute is accepted Functionality/Description: Set to 1 if the attribute is accepted
^L
draft-ietf-idr-bgp-implementation-01 July 2004
and passed to other BGP speakers and passed to other BGP speakers
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.9.39 Unrecognized non-transitive optional attributes 2.9.39 Unrecognized non-transitive optional attributes
skipping to change at page 17, line 24 skipping to change at page 19, line 5
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.9.42 Path Attributes 2.9.42 Path Attributes
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Functionality/Description: Ordered in ascending order of Functionality/Description: Ordered in ascending order of
attribute type attribute type
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: O All attributes are ordered in Cisco Y/N/O/Comments: O All attributes are ordered in
ascending order except Extended ascending order except Extended
Community, which is type 16 but we Community, which is type 16 but we
send it out after community send it out after community
skipping to change at page 18, line 16 skipping to change at page 19, line 45
Functionality/Description: Present in all exchanges if NLRI are Functionality/Description: Present in all exchanges if NLRI are
contained in the UPDATE message contained in the UPDATE message
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.10 ORIGIN / Section 5.1.1 3.10 ORIGIN / Section 5.1.1
2.10.45 ORIGIN 2.10.45 ORIGIN
Functionality/Description: Value SHOULD NOT be changed by any Functionality/Description: Value SHOULD NOT be changed by any
speaker, except the originator speaker, except the originator
RFC2119: SHOULD NOT RFC2119: SHOULD NOT
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.11 AS_PATH / Section 5.1.2 3.11 AS_PATH / Section 5.1.2
2.11.46 AS_PATH 2.11.46 AS_PATH
Functionality/Description: Not modified when advertising a route Functionality/Description: Not modified when advertising a route
to an internal peer to an internal peer
RFC2119: SHALL NOT RFC2119: SHALL NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 19, line 26 skipping to change at page 21, line 5
more than one instance of its own AS number in the AS_PATH more than one instance of its own AS number in the AS_PATH
attribute attribute
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.12 NEXT_HOP / Section 5.1.3 ^L
draft-ietf-idr-bgp-implementation-01 July 2004
3.12 NEXT_HOP / Section 5.1.3
2.12.49 NEXT_HOP 2.12.49 NEXT_HOP
Functionality/Description: Used as the next hop to the Functionality/Description: Used as the next hop to the
destinations listed in the UPDATE message destinations listed in the UPDATE message
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 20, line 25 skipping to change at page 22, line 5
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.12.52 NEXT_HOP 2.12.52 NEXT_HOP
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Functionality/Description: If the route is directly connected to Functionality/Description: If the route is directly connected to
the speaker, or the interface address of the router through the speaker, or the interface address of the router through
which the announced network is reachable for the speaker is the which the announced network is reachable for the speaker is the
internal peer's address, then the BGP speaker SHOULD use for the internal peer's address, then the BGP speaker SHOULD use for the
NEXT_HOP attribute its own IP address (the address of the NEXT_HOP attribute its own IP address (the address of the
interface that is used to reach the peer) interface that is used to reach the peer)
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
skipping to change at page 21, line 24 skipping to change at page 23, line 4
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.12.55 NEXT_HOP Propagation 2.12.55 NEXT_HOP Propagation
Functionality/Description: The speaker MAY be configured to Functionality/Description: The speaker MAY be configured to
propagate the NEXT_HOP attribute. In this case when advertising propagate the NEXT_HOP attribute. In this case when advertising
^L
draft-ietf-idr-bgp-implementation-01 July 2004
a route that the speaker learned from one of its peers, the a route that the speaker learned from one of its peers, the
NEXT_HOP attribute of the advertised route is exactly the same NEXT_HOP attribute of the advertised route is exactly the same
as the NEXT_HOP attribute of the learned route (the speaker just as the NEXT_HOP attribute of the learned route (the speaker just
doesn't modify the NEXT_HOP attribute) doesn't modify the NEXT_HOP attribute)
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: O Alcatel Y/N/O/Comments: O
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
skipping to change at page 22, line 25 skipping to change at page 24, line 4
2.12.58 NEXT_HOP 2.12.58 NEXT_HOP
Functionality/Description: A BGP speaker SHALL NOT install a Functionality/Description: A BGP speaker SHALL NOT install a
route with itself as the next hop route with itself as the next hop
RFC2119: SHALL NOT RFC2119: SHALL NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.12.59 NEXT_HOP 2.12.59 NEXT_HOP
Functionality/Description: Used to determine the actual outbound Functionality/Description: Used to determine the actual outbound
interface and immediate next-hop address that SHOULD be used to interface and immediate next-hop address that SHOULD be used to
forward transit packets to the associated destinations forward transit packets to the associated destinations
RFC2119: SHOULD RFC2119: SHOULD
skipping to change at page 23, line 21 skipping to change at page 24, line 50
next-hop address, this address SHOULD be used as the immediate next-hop address, this address SHOULD be used as the immediate
next-hop address for packet forwarding next-hop address for packet forwarding
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.13 MULTI_EXIT_DISC / Section 5.1.4 3.13 MULTI_EXIT_DISC / Section 5.1.4
2.13.62 Preferred metric 2.13.62 Preferred metric
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Functionality/Description: Lowest value Functionality/Description: Lowest value
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.13.63 MULTI_EXIT_DISC 2.13.63 MULTI_EXIT_DISC
skipping to change at page 24, line 26 skipping to change at page 26, line 5
Functionality/Description: Local configuration mechanism to Functionality/Description: Local configuration mechanism to
remove the attribute from a route remove the attribute from a route
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.13.66 Remove MULTI_EXIT_DISC 2.13.66 Remove MULTI_EXIT_DISC
Functionality/Description: Done prior to determining the degree Functionality/Description: Done prior to determining the degree
of preference of the route and performing route selection of preference of the route and performing route selection
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
skipping to change at page 25, line 16 skipping to change at page 26, line 45
Functionality/Description: Done prior to determining the degree Functionality/Description: Done prior to determining the degree
of preference of the route and performing route selection of preference of the route and performing route selection
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.14 LOCAL_PREF / Section 5.1.5 3.14 LOCAL_PREF / Section 5.1.5
2.14.69 LOCAL_PREF 2.14.69 LOCAL_PREF
Functionality/Description: Included in all UPDATE messages that Functionality/Description: Included in all UPDATE messages that
a given BGP speaker sends to the other internal peers a given BGP speaker sends to the other internal peers
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.14.70 Degree of Preference 2.14.70 Degree of Preference
Functionality/Description: Calculated for each external route Functionality/Description: Calculated for each external route
skipping to change at page 26, line 24 skipping to change at page 28, line 5
to external peers, except for the case of BGP Confederations to external peers, except for the case of BGP Confederations
[RFC3065] [RFC3065]
RFC2119: MUST NOT RFC2119: MUST NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.14.73 LOCAL_PREF 2.14.73 LOCAL_PREF
Functionality/Description: Ignored if received from an external Functionality/Description: Ignored if received from an external
peer, peer, except for the case of BGP Confederations [RFC3065]
except for the case of BGP Confederations [RFC3065]
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.15 ATOMIC_AGGREGATE / Section 5.1.6 3.15 ATOMIC_AGGREGATE / Section 5.1.6
2.15.74 ATOMIC_AGGREGATE 2.15.74 ATOMIC_AGGREGATE
Functionality/Description: Included if an aggregate excludes at Functionality/Description: Included if an aggregate excludes at
least some of the AS numbers present in the AS_PATH of the least some of the AS numbers present in the AS_PATH of the
routes that are aggregated as a result of dropping the AS_SET routes that are aggregated as a result of dropping the AS_SET
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
skipping to change at page 27, line 25 skipping to change at page 29, line 5
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.15.76 Received ATOMIC_AGGREGATE 2.15.76 Received ATOMIC_AGGREGATE
Functionality/Description: BGP speaker MUST NOT make any NLRI of Functionality/Description: BGP speaker MUST NOT make any NLRI of
that route more specific (as defined in 9.1.4) that route more specific (as defined in 9.1.4)
RFC2119: MUST NOT RFC2119: MUST NOT
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.16 AGGREGATOR / Section 5.1.7 3.16 AGGREGATOR / Section 5.1.7
2.16.77 AGGREGATOR 2.16.77 AGGREGATOR
Functionality/Description: Included in updates which are formed Functionality/Description: Included in updates which are formed
by aggregation (see Section 9.2.2.2) by aggregation (see Section 9.2.2.2)
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 28, line 26 skipping to change at page 30, line 5
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Default behavior. Can be configured Alcatel Y/N/O/Comments: Y Default behavior. Can be configured
different from BGP ID. different from BGP ID.
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.16.80 AGGREGATOR IP Address 2.16.80 AGGREGATOR IP Address
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Functionality/Description: The same as the BGP Identifier of the Functionality/Description: The same as the BGP Identifier of the
speaker speaker
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.17 BGP Error Handling / Section 6 3.17 BGP Error Handling / Section 6
2.17.81 Error Handling 2.17.81 Error Handling
Functionality/Description: Is your implementation compatible Functionality/Description: Is your implementation compatible
with the error handling procedures described in this section? with the error handling procedures described in this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 29, line 15 skipping to change at page 30, line 43
Functionality/Description: Zero, if it is not specified Functionality/Description: Zero, if it is not specified
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.18 Message Header Error Handling / Section 6.1 3.18 Message Header Error Handling / Section 6.1
2.18.83 Message Header Errors 2.18.83 Message Header Errors
Functionality/Description: Indicated by sending the NOTIFICATION Functionality/Description: Indicated by sending the NOTIFICATION
message with Error Code Message Header Error message with Error Code Message Header Error
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.18.84 Synchronization Error 2.18.84 Synchronization Error
Functionality/Description: Error Subcode MUST be set to Functionality/Description: Error Subcode MUST be set to
Connection Not Synchronized Connection Not Synchronized
RFC2119: MUST RFC2119: MUST
skipping to change at page 30, line 26 skipping to change at page 32, line 5
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.18.87 Type Field 2.18.87 Type Field
Functionality/Description: If the Type field of the message Functionality/Description: If the Type field of the message
header is not recognized, then the Error Subcode MUST be set to header is not recognized, then the Error Subcode MUST be set to
Bad Message Type Bad Message Type
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.18.88 Bad Message Type 2.18.88 Bad Message Type
Functionality/Description: The Data field MUST contain the Functionality/Description: The Data field MUST contain the
erroneous Type field erroneous Type field
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.19 OPEN message error handling / Section 6.2 3.19 OPEN message error handling / Section 6.2
2.19.89 OPEN Message Errors 2.19.89 OPEN Message Errors
Functionality/Description: Indicated by sending the NOTIFICATION Functionality/Description: Indicated by sending the NOTIFICATION
message with Error Code OPEN Message Error message with Error Code OPEN Message Error
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 31, line 26 skipping to change at page 33, line 5
Functionality/Description: The Error Subcode MUST be set to Functionality/Description: The Error Subcode MUST be set to
Unsupported Version Number Unsupported Version Number
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.19.91 Unnacceptable Autonomous System Field 2.19.91 Unnacceptable Autonomous System Field
Functionality/Description: The Error Subcode MUST be set to Bad Functionality/Description: The Error Subcode MUST be set to Bad
Peer AS Peer AS
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
skipping to change at page 32, line 17 skipping to change at page 33, line 45
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.19.94 Hold Time Rejection 2.19.94 Hold Time Rejection
Functionality/Description: Any proposed Hold Time Functionality/Description: An implementation may reject any
proposed Hold Time
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: N Laurel Y/N/O/Comments: N
^L
draft-ietf-idr-bgp-implementation-01 July 2004
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.19.95 Hold Time 2.19.95 Hold Time
Functionality/Description: If accepted, then the negotiated Functionality/Description: If accepted, then the negotiated
value MUST be used value MUST be used
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
skipping to change at page 33, line 23 skipping to change at page 35, line 5
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.19.98 Recognized but Malformed Optional Parameters 2.19.98 Recognized but Malformed Optional Parameters
Functionality/Description: The Error Subcode MUST be set to 0 Functionality/Description: The Error Subcode MUST be set to 0
(Unspecific) (Unspecific)
RFC2119: MUST RFC2119: MUST
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20 UPDATE message error handling / Section 6.3 3.20 UPDATE message error handling / Section 6.3
2.20.99 UPDATE Message Errors 2.20.99 UPDATE Message Errors
Functionality/Description: Indicated by sending the Functionality/Description: Indicated by sending the
NOTIFICATION message with Error Code UPDATE Message Error NOTIFICATION message with Error Code UPDATE Message Error
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 34, line 24 skipping to change at page 36, line 5
Attribute Flags that conflict with the Attribute Type Code, then Attribute Flags that conflict with the Attribute Type Code, then
the Error Subcode MUST be set to Attribute Flags Error the Error Subcode MUST be set to Attribute Flags Error
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.20.102 Conflicting Flags 2.20.102 Conflicting Flags
Functionality/Description: The Data field MUST contain the Functionality/Description: The Data field MUST contain the
erroneous attribute erroneous attribute
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
skipping to change at page 35, line 25 skipping to change at page 37, line 4
2.20.105 Missing Mandatory Well-Known Attributes 2.20.105 Missing Mandatory Well-Known Attributes
Functionality/Description: The Error Subcode MUST be set to Functionality/Description: The Error Subcode MUST be set to
Missing Well-known Attribute Missing Well-known Attribute
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20.106 Missing Mandatory Well-Known Attributes 2.20.106 Missing Mandatory Well-Known Attributes
Functionality/Description: The Data field MUST contain the Functionality/Description: The Data field MUST contain the
Attribute Type Code of the missing well-known attribute Attribute Type Code of the missing well-known attribute
RFC2119: MUST RFC2119: MUST
skipping to change at page 36, line 25 skipping to change at page 38, line 5
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20.109 Undefined ORIGIN 2.20.109 Undefined ORIGIN
Functionality/Description: The Error Sub-code MUST be set to Functionality/Description: The Error Sub-code MUST be set to
Invalid Origin Attribute Invalid Origin Attribute
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20.110 Undefined ORIGIN 2.20.110 Undefined ORIGIN
Functionality/Description: The Data field MUST contain the Functionality/Description: The Data field MUST contain the
skipping to change at page 37, line 24 skipping to change at page 39, line 4
2.20.112 Syntactically Incorrect NEXT_HOP 2.20.112 Syntactically Incorrect NEXT_HOP
Functionality/Description: The Data field MUST contain the Functionality/Description: The Data field MUST contain the
incorrect attribute incorrect attribute
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20.113 NEXT_HOP Semantic Correctness 2.20.113 NEXT_HOP Semantic Correctness
Functionality/Description: NEXT_HOP is checked for semantic Functionality/Description: NEXT_HOP is checked for semantic
correctness against the criteria in this section correctness against the criteria in this section
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
skipping to change at page 38, line 24 skipping to change at page 40, line 5
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20.116 Semantically incorrect NEXT_HOP 2.20.116 Semantically incorrect NEXT_HOP
Functionality/Description: Error logged Functionality/Description: Error logged
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20.117 Semantically incorrect NEXT_HOP 2.20.117 Semantically incorrect NEXT_HOP
Functionality/Description: Route Ignored Functionality/Description: Route Ignored
skipping to change at page 39, line 25 skipping to change at page 41, line 5
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20.120 Syntactically Incorrect AS_PATH 2.20.120 Syntactically Incorrect AS_PATH
Functionality/Description: The Error Subcode MUST be set to Functionality/Description: The Error Subcode MUST be set to
Malformed AS_PATH Malformed AS_PATH
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20.121 First Neighbor in AS_PATH check 2.20.121 First Neighbor in AS_PATH check
Functionality/Description: If the UPDATE message is received Functionality/Description: If the UPDATE message is received
skipping to change at page 40, line 25 skipping to change at page 42, line 5
Functionality/Description: Value MUST be checked if the Functionality/Description: Value MUST be checked if the
attribute is recognized attribute is recognized
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.20.124 Optional Attribute Error 2.20.124 Optional Attribute Error
Functionality/Description: The attribute MUST be discarded Functionality/Description: The attribute MUST be discarded
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 41, line 26 skipping to change at page 43, line 5
Functionality/Description: The Data field MUST contain the Functionality/Description: The Data field MUST contain the
attribute attribute
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.20.127 Duplicate Attributes 2.20.127 Duplicate Attributes
Functionality/Description: If any attribute appears more than Functionality/Description: If any attribute appears more than
once in the UPDATE message, then the Error Subcode MUST be set once in the UPDATE message, then the Error Subcode MUST be set
to Malformed Attribute List to Malformed Attribute List
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 42, line 23 skipping to change at page 44, line 4
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20.130 Semantically Incorrect NLRI Field 2.20.130 Semantically Incorrect NLRI Field
Functionality/Description: The prefix SHOULD be ignored Functionality/Description: The prefix SHOULD be ignored
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.20.131 UPDATE with no NLRI 2.20.131 UPDATE with no NLRI
Functionality/Description: An UPDATE message that contains Functionality/Description: An UPDATE message that contains
correct path attributes, but no NLRI, SHALL be treated as a correct path attributes, but no NLRI, SHALL be treated as a
valid UPDATE message valid UPDATE message
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.21 NOTIFICATION message error handling / Section 6.4 3.21 NOTIFICATION message error handling / Section 6.4
2.21.132 Error in NOTIFICATION message 2.21.132 Error in NOTIFICATION message
Functionality/Description: Noticed, logged locally, and brought Functionality/Description: Noticed, logged locally, and brought
to the attention of the administration of the peer to the attention of the administration of the peer
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.22 Hold Timer Expired error handling / Section 6.5 3.22 Hold Timer Expired error handling / Section 6.5
2.22.133 Hold Timer Expired 2.22.133 Hold Timer Expired
Functionality/Description: Is your implementation compatible Functionality/Description: Is your implementation compatible
with the error handling procedures described in this section? with the error handling procedures described in this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.23 Finite State Machine error handling / Section 6.6 ^L
draft-ietf-idr-bgp-implementation-01 July 2004
3.23 Finite State Machine error handling / Section 6.6
2.23.134 Finite State Machine Errors 2.23.134 Finite State Machine Errors
Functionality/Description: Is your implementation compatible Functionality/Description: Is your implementation compatible
with the error handling procedures described in this section? with the error handling procedures described in this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.24 Cease / Section 6.7 3.24 Cease / Section 6.7
2.24.135 Cease NOTIFICATION 2.24.135 Cease NOTIFICATION
Functionality/Description: Used in absence of any fatal errors Functionality/Description: Used in absence of any fatal errors
if a BGP peer chooses at any given time to close its BGP if a BGP peer chooses at any given time to close its BGP
connection connection
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
skipping to change at page 44, line 24 skipping to change at page 46, line 5
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.24.137 Upper bound on the number of address prefixes the speaker is 2.24.137 Upper bound on the number of address prefixes the speaker is
willing to accept from a neighbor willing to accept from a neighbor
Functionality/Description: Support by local configuration Functionality/Description: Support by local configuration
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.24.138 Upper bound on the number of address prefixes the speaker is 2.24.138 Upper bound on the number of address prefixes the speaker is
willing to accept from a neighbor willing to accept from a neighbor
skipping to change at page 45, line 15 skipping to change at page 46, line 45
Functionality/Description: Log locally Functionality/Description: Log locally
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.25 BGP connection collision detection / Section 6.8 3.25 BGP connection collision detection / Section 6.8
2.25.140 Connection Collision 2.25.140 Connection Collision
Functionality/Description: One of the connections MUST be closed Functionality/Description: One of the connections MUST be closed
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.25.141 Receipt of an OPEN message 2.25.141 Receipt of an OPEN message
Functionality/Description: The local system MUST examine all of Functionality/Description: The local system MUST examine all of
its connections that are in the OpenConfirm state its connections that are in the OpenConfirm state
RFC2119: MUST RFC2119: MUST
skipping to change at page 46, line 4 skipping to change at page 47, line 34
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.25.142 Receipt of an OPEN message 2.25.142 Receipt of an OPEN message
Functionality/Description: Examine connections in an OpenSent Functionality/Description: Examine connections in an OpenSent
state if it knows the BGP Identifier of the peer by means state if it knows the BGP Identifier of the peer by means
outside of the protocol outside of the protocol
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.26 BGP Version Negotiation / Section 7 3.26 BGP Version Negotiation / Section 7
2.26.143 Version Negotiation 2.26.143 Version Negotiation
Functionality/Description: Multiple attempts to open a BGP Functionality/Description: Multiple attempts to open a BGP
connection, starting with the highest version number each connection, starting with the highest version number each
supports supports
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: N Supports only version 4 Alcatel Y/N/O/Comments: N Supports only version 4
Cisco Y/N/O/Comments: O We resolve it through config. If Cisco Y/N/O/Comments: O We resolve it through config. If
Config is for version 3, and we get Config is for version 3, and we get
version 4, OPEN will always fail. version 4, OPEN will always fail.
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Similarly, if configed (default) is Similarly, if configed (default) is
version 4 and peers configured is 3, version 4 and peers configured is 3,
we don't try to negotiate version 3 we don't try to negotiate version 3
unless we have configured it. unless we have configured it.
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: N Supports only version 4.
2.26.144 Future versions of BGP 2.26.144 Future versions of BGP
Functionality/Description: MUST retain the format of the OPEN Functionality/Description: MUST retain the format of the OPEN
and NOTIFICATION messages and NOTIFICATION messages
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.27 BGP Finite State machine (FSM) / Section 8 3.27 BGP Finite State machine (FSM) / Section 8
2.27.145 FSM 2.27.145 FSM
Functionality/Description: Is your implementation compatible Functionality/Description: Is your implementation compatible
with the conceptual FSM described in this section? with the conceptual FSM described in this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.28 Administrative Events / Section 8.1.2 3.28 Administrative Events / Section 8.1.2
2.28.146 Optional Session Attribute Settings 2.28.146 Optional Session Attribute Settings
Functionality/Description: Each event has an indication of what Functionality/Description: Each event has an indication of what
optional session attributes SHOULD be set at each stage optional session attributes SHOULD be set at each stage
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: O Its rather vague. We have an option Cisco Y/N/O/Comments: O Its rather vague. We have an option
Of manually starting or stopping Of manually starting or stopping
sessions but not an option for all sessions but not an option for all
^L
draft-ietf-idr-bgp-implementation-01 July 2004
optional session attributes that are optional session attributes that are
listed in draft. listed in draft.
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y The following optional attributes NextHop Y/N/O/Comments: Y The following optional attributes
are implied in this implementation: are implied in this implementation:
1) Automatic start, 2) Automatic 1) Automatic start, 2) Automatic
Stop, 3) Stop, 3)
2.28.147 Event1: ManualStart 2.28.147 Event1: ManualStart
skipping to change at page 48, line 23 skipping to change at page 50, line 5
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.28.150 Event3: AutomaticStart 2.28.150 Event3: AutomaticStart
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Functionality/Description: DampPeerOscillations SHOULD be set to Functionality/Description: DampPeerOscillations SHOULD be set to
FALSE FALSE
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Don't support DampPeerOscillations Cisco Y/N/O/Comments: Y Don't support DampPeerOscillations
attribute, so it is always FALSE. attribute, so it is always FALSE.
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 49, line 23 skipping to change at page 51, line 5
NextHop Y/N/O/Comments: O We don't support DampPeerOscilation NextHop Y/N/O/Comments: O We don't support DampPeerOscilation
attribute with a setting of off, and attribute with a setting of off, and
hence Event 4. Future version will hence Event 4. Future version will
support Event 4 support Event 4
2.28.153 Event5: AutomaticStart_with_PassiveTcpEstablishment 2.28.153 Event5: AutomaticStart_with_PassiveTcpEstablishment
Functionality/Description: The AllowAutomaticStart attribute Functionality/Description: The AllowAutomaticStart attribute
SHOULD be set to TRUE SHOULD be set to TRUE
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.28.154 Event5: AutomaticStart_with_PassiveTcpEstablishment 2.28.154 Event5: AutomaticStart_with_PassiveTcpEstablishment
Functionality/Description: The PassiveTcpEstablishment attribute Functionality/Description: The PassiveTcpEstablishment attribute
skipping to change at page 50, line 24 skipping to change at page 52, line 4
Functionality/Description: The AllowAutomaticStart attribute Functionality/Description: The AllowAutomaticStart attribute
SHOULD be set to TRUE SHOULD be set to TRUE
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: N Alcatel Y/N/O/Comments: N
Cisco Y/N/O/Comments: O Don't support DampPeerOscillations Cisco Y/N/O/Comments: O Don't support DampPeerOscillations
attribute. attribute.
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.28.157 Event6: AutomaticStart_with_DampPeerOscillations 2.28.157 Event6: AutomaticStart_with_DampPeerOscillations
Functionality/Description: The DampPeerOscillations attribute Functionality/Description: The DampPeerOscillations attribute
SHOULD be set to TRUE SHOULD be set to TRUE
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: N Alcatel Y/N/O/Comments: N
skipping to change at page 51, line 23 skipping to change at page 53, line 5
Alcatel Y/N/O/Comments: N Alcatel Y/N/O/Comments: N
Cisco Y/N/O/Comments: O Don't support DampPeerOscillations Cisco Y/N/O/Comments: O Don't support DampPeerOscillations
attribute and hence Event7 attribute and hence Event7
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.28.160 Event 7: 2.28.160 Event 7:
AutomaticStart_with_DampPeerOscillations_and_PassiveTcpEstablishment AutomaticStart_with_DampPeerOscillations_and_PassiveTcpEstablishment
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Functionality/Description: The DampPeerOscillations attribute Functionality/Description: The DampPeerOscillations attribute
SHOULD be set to TRUE SHOULD be set to TRUE
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: N Alcatel Y/N/O/Comments: N
Cisco Y/N/O/Comments: O Don't support DampPeerOscillations Cisco Y/N/O/Comments: O Don't support DampPeerOscillations
attribute and hence Event7 attribute and hence Event7
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 52, line 14 skipping to change at page 53, line 45
Functionality/Description: The AllowAutomaticStop attribute Functionality/Description: The AllowAutomaticStop attribute
SHOULD be TRUE SHOULD be TRUE
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: N Alcatel Y/N/O/Comments: N
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.29 Timer Events / Section 8.1.3 3.29 Timer Events / Section 8.1.3
2.29.163 Event12: DelayOpenTimer_Expires 2.29.163 Event12: DelayOpenTimer_Expires
Functionality/Description: DelayOpen attribute SHOULD be set to Functionality/Description: DelayOpen attribute SHOULD be set to
TRUE TRUE
RFC2119: SHOULD RFC2119: SHOULD
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Alcatel Y/N/O/Comments: N Alcatel Y/N/O/Comments: N
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: n/a Laurel Y/N/O/Comments: n/a
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.29.164 Event12: DelayOpenTimer_Expires 2.29.164 Event12: DelayOpenTimer_Expires
Functionality/Description: DelayOpenTime attribute SHOULD be Functionality/Description: DelayOpenTime attribute SHOULD be
supported supported
skipping to change at page 53, line 24 skipping to change at page 55, line 5
Cisco Y/N/O/Comments: O Don't support DampPeerOscillations Cisco Y/N/O/Comments: O Don't support DampPeerOscillations
attribute and hence Event13 attribute and hence Event13
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.29.167 Event13: IdleHoldTimer_Expires 2.29.167 Event13: IdleHoldTimer_Expires
Functionality/Description: IdleHoldTimer SHOULD have just Functionality/Description: IdleHoldTimer SHOULD have just
expired expired
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: N Alcatel Y/N/O/Comments: N
Cisco Y/N/O/Comments: O Don't support DampPeerOscillations Cisco Y/N/O/Comments: O Don't support DampPeerOscillations
attribute and hence Event13 attribute and hence Event13
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.30 TCP Connection based Events / Section 8.1.4 3.30 TCP Connection based Events / Section 8.1.4
2.30.168 Event14: TcpConnection_Valid 2.30.168 Event14: TcpConnection_Valid
Functionality/Description: BGP's destination port SHOULD be port Functionality/Description: BGP's destination port SHOULD be port
179 179
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 54, line 24 skipping to change at page 56, line 5
Future versions will have additional Future versions will have additional
hooks. hooks.
2.30.170 Event15: Tcp_CR_Invalid 2.30.170 Event15: Tcp_CR_Invalid
Functionality/Description: BGP destination port number SHOULD be Functionality/Description: BGP destination port number SHOULD be
179 179
RFC2119: SHOULD RFC2119: SHOULD
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: O GateD NGC 2.0 provides hooks for NextHop Y/N/O/Comments: O GateD NGC 2.0 provides hooks for
the TCP state tracking, but use of the TCP state tracking, but use of
this option depends OS support. this option depends OS support.
Future versions will have additional Future versions will have additional
hooks. hooks.
2.31 BGP Messages based Events / Seciton 8.1.5 3.31 BGP Messages based Events / Seciton 8.1.5
2.31.171 Event19: BGPOpen 2.31.171 Event19: BGPOpen
Functionality/Description: The DelayOpen optional attribute Functionality/Description: The DelayOpen optional attribute
SHOULD be set to FALSE SHOULD be set to FALSE
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 55, line 25 skipping to change at page 57, line 5
Functionality/Description: The DelayOpen attribute SHOULD be set Functionality/Description: The DelayOpen attribute SHOULD be set
to TRUE to TRUE
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: N Not applicable Alcatel Y/N/O/Comments: N Not applicable
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: n/a Laurel Y/N/O/Comments: n/a
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.31.174 Event20: BGPOpen with DelayOpenTimer running 2.31.174 Event20: BGPOpen with DelayOpenTimer running
Functionality/Description: The DelayOpenTimer SHOULD be running Functionality/Description: The DelayOpenTimer SHOULD be running
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: N Alcatel Y/N/O/Comments: N
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: n/a Laurel Y/N/O/Comments: n/a
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 56, line 8 skipping to change at page 57, line 37
Alcatel Y/N/O/Comments: Y Collision detection event is logged. Alcatel Y/N/O/Comments: Y Collision detection event is logged.
Cisco Y/N/O/Comments: O We always detect collision before we Cisco Y/N/O/Comments: O We always detect collision before we
go to established state. go to established state.
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: O GateD NGC 2.0 does not support NextHop Y/N/O/Comments: O GateD NGC 2.0 does not support
Collision Detection in Established Collision Detection in Established
state. This option attribute is state. This option attribute is
always set to FALSE. always set to FALSE.
2.32 FSM Definition / Section 8.2.1 3.32 FSM Definition / Section 8.2.1
2.32.176 FSM 2.32.176 FSM
Functionality/Description: Separate FSM for each configured peer Functionality/Description: Separate FSM for each configured peer
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.32.177 TCP Port 179 2.32.177 TCP Port 179
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Functionality/Description: A BGP implementation MUST connect to Functionality/Description: A BGP implementation MUST connect to
and listen on TCP port 179 for incoming connections in addition and listen on TCP port 179 for incoming connections in addition
to trying to connect to peers to trying to connect to peers
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 56, line 45 skipping to change at page 58, line 30
Functionality/Description: A state machine MUST be instantiated Functionality/Description: A state machine MUST be instantiated
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.33 FSM and collision detection / Section 8.2.1.2 3.33 FSM and collision detection / Section 8.2.1.2
2.33.179 Connection Collision 2.33.179 Connection Collision
Functionality/Description: The corresponding FSM for the Functionality/Description: The corresponding FSM for the
connection that is closed SHOULD be disposed of connection that is closed SHOULD be disposed of
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 57, line 14 skipping to change at page 58, line 44
Functionality/Description: The corresponding FSM for the Functionality/Description: The corresponding FSM for the
connection that is closed SHOULD be disposed of connection that is closed SHOULD be disposed of
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.34 FSM Event numbers / Section 8.2.1.4 3.34 FSM Event numbers / Section 8.2.1.4
2.34.180 Event Numbers 2.34.180 Event Numbers
Functionality/Description: Used to provide network management Functionality/Description: Used to provide network management
information information
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Not visible to operator. Alcatel Y/N/O/Comments: Y Not visible to operator.
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
Laurel Y/N/O/Comments: N Laurel Y/N/O/Comments: N
NextHop Y/N/O/Comments: N Future Release of GateD NGC may NextHop Y/N/O/Comments: N Future Release of GateD NGC may
support event numbers. support event numbers.
2.35 Finite State Machine / Section 8.2.2 3.35 Finite State Machine / Section 8.2.2
2.35.181 ConnectRetryTimer 2.35.181 ConnectRetryTimer
Functionality/Description: Sufficiently large to allow TCP Functionality/Description: Sufficiently large to allow TCP
initialization initialization
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 58, line 4 skipping to change at page 59, line 32
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.35.182 2nd connection tracking 2.35.182 2nd connection tracking
Functionality/Description: In response to a TCP connection Functionality/Description: In response to a TCP connection
succeeds [Event 16 or Event 17], the 2nd connection SHALL be succeeds [Event 16 or Event 17], the 2nd connection SHALL be
tracked until it sends an OPEN message tracked until it sends an OPEN message
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.36 UPDATE Message Handling / Section 9 3.36 UPDATE Message Handling / Section 9
2.36.183 UPDATE Message Handling 2.36.183 UPDATE Message Handling
Functionality/Description: Does your implementation handle Functionality/Description: Does your implementation handle
UPDATE messages in a manner compatible to the description in UPDATE messages in a manner compatible to the description in
this section? this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.36.184 WITHDRAWN ROUTES 2.36.184 WITHDRAWN ROUTES
Functionality/Description: Any previously advertised routes Functionality/Description: Any previously advertised routes
whose destinations are contained in this field SHALL be removed whose destinations are contained in this field SHALL be removed
from the Adj-RIB-In from the Adj-RIB-In
RFC2119: SHALL RFC2119: SHALL
skipping to change at page 59, line 23 skipping to change at page 61, line 4
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.36.187 Other feasible routes 2.36.187 Other feasible routes
Functionality/Description: If an UPDATE message contains a Functionality/Description: If an UPDATE message contains a
^L
draft-ietf-idr-bgp-implementation-01 July 2004
feasible route, and the NLRI of the new route is not identical feasible route, and the NLRI of the new route is not identical
to the one of any route currently stored in the Adj-RIB-In, then to the one of any route currently stored in the Adj-RIB-In, then
the new route SHALL be placed in the Adj-RIB-In the new route SHALL be placed in the Adj-RIB-In
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 59, line 46 skipping to change at page 61, line 31
Functionality/Description: Once a BGP speaker updates the Functionality/Description: Once a BGP speaker updates the
Adj-RIB-In, it SHALL run its Decision Process Adj-RIB-In, it SHALL run its Decision Process
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.37 Decision Process / Section 9.1 3.37 Decision Process / Section 9.1
2.37.189 Decision Process 2.37.189 Decision Process
Functionality/Description: Is your implementation compatible Functionality/Description: Is your implementation compatible
with the description in this section? with the description in this section?
RFC2119: N/A RFC2119: N/A
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
skipping to change at page 60, line 23 skipping to change at page 62, line 4
2.37.190 Degree of Preference 2.37.190 Degree of Preference
Functionality/Description: SHALL NOT use as its inputs any of Functionality/Description: SHALL NOT use as its inputs any of
the following: the existence of other routes, the non-existence the following: the existence of other routes, the non-existence
of other routes, or the path attributes of other routes of other routes, or the path attributes of other routes
RFC2119: SHALL NOT RFC2119: SHALL NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.38 Phase 1: Calculation of Degree of Preference / Section 9.1.1 3.38 Phase 1: Calculation of Degree of Preference / Section 9.1.1
2.38.191 Ineligible degree of preference 2.38.191 Ineligible degree of preference
Functionality/Description: The route MAY NOT serve as an input Functionality/Description: The route MAY NOT serve as an input
to the next phase of route selection to the next phase of route selection
RFC2119: MAY NOT RFC2119: MAY NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 61, line 8 skipping to change at page 62, line 38
Functionality/Description: Used as the LOCAL_PREF value in any Functionality/Description: Used as the LOCAL_PREF value in any
IBGP readvertisement IBGP readvertisement
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.39 Phase 2: Route Selection / Section 9.1.2 3.39 Phase 2: Route Selection / Section 9.1.2
2.39.193 Unresolvable NEXT_HOP 2.39.193 Unresolvable NEXT_HOP
Functionality/Description: If the NEXT_HOP attribute of a BGP Functionality/Description: If the NEXT_HOP attribute of a BGP
route depicts an address that is not resolvable, or it would route depicts an address that is not resolvable, or it would
become unresolvable if the route was installed in the routing become unresolvable if the route was installed in the routing
table the BGP route MUST be excluded table the BGP route MUST be excluded
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.39.194 Routes installed in LOC-RIB 2.39.194 Routes installed in LOC-RIB
Functionality/Description: The route in the Adj-RIBs-In Functionality/Description: The route in the Adj-RIBs-In
identified as the best (see section 9.1.2) is installed in the identified as the best (see section 9.1.2) is installed in the
Loc-RIB, replacing any route to the same destination that is Loc-RIB, replacing any route to the same destination that is
currently being held in the Loc-RIB currently being held in the Loc-RIB
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
skipping to change at page 62, line 23 skipping to change at page 64, line 4
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.39.197 Immediate next-hop address 2.39.197 Immediate next-hop address
Functionality/Description: Used for packet forwarding Functionality/Description: Used for packet forwarding
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.39.198 Unresolvable routes 2.39.198 Unresolvable routes
Functionality/Description: Removed from the Loc-RIB and the Functionality/Description: Removed from the Loc-RIB and the
routing table routing table
RFC2119: SHALL RFC2119: SHALL
skipping to change at page 63, line 5 skipping to change at page 64, line 35
Functionality/Description: Kept in the corresponding Adj-RIBs-In Functionality/Description: Kept in the corresponding Adj-RIBs-In
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.40 Route Resolvability Condition / Section 9.1.2.1 3.40 Route Resolvability Condition / Section 9.1.2.1
2.40.200 Unresolvable routes 2.40.200 Unresolvable routes
Functionality/Description: Excluded from the Phase 2 decision Functionality/Description: Excluded from the Phase 2 decision
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.40.201 Multiple Matching Routes 2.40.201 Multiple Matching Routes
Functionality/Description: Only the longest matching route Functionality/Description: Only the longest matching route
SHOULD be considered SHOULD be considered
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.40.202 Mutual Recursion 2.40.202 Mutual Recursion
Functionality/Description: If a route fails the resolvability Functionality/Description: If a route fails the resolvability
skipping to change at page 63, line 44 skipping to change at page 65, line 29
logged logged
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: O We have checks that disallow mutual Cisco Y/N/O/Comments: O We have checks that disallow mutual
recursion, so this won't happen. recursion, so this won't happen.
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.41 Breaking Ties (Phase 2) / Section 9.1.2.2 3.41 Breaking Ties (Phase 2) / Section 9.1.2.2
2.41.203 Tie-breaking criteria 2.41.203 Tie-breaking criteria
Functionality/Description: Applied in the order specified Functionality/Description: Applied in the order specified
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.41.204 Algorithm used 2.41.204 Algorithm used
Functionality/Description: BGP implementations MAY use any Functionality/Description: BGP implementations MAY use any
skipping to change at page 64, line 23 skipping to change at page 66, line 5
Functionality/Description: BGP implementations MAY use any Functionality/Description: BGP implementations MAY use any
algorithm which produces the same results asthose described here algorithm which produces the same results asthose described here
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.41.205 MULTI_EXIT_DISC removal 2.41.205 MULTI_EXIT_DISC removal
Functionality/Description: If done before re-advertising a route Functionality/Description: If done before re-advertising a route
into IBGP, then comparison based on the received EBGP into IBGP, then comparison based on the received EBGP
MULTI_EXIT_DISC attribute MAY still be performed MULTI_EXIT_DISC attribute MAY still be performed
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 65, line 15 skipping to change at page 66, line 45
Functionality/Description: Performed for IBGP learned routes Functionality/Description: Performed for IBGP learned routes
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.42 Phase 3: Route Dissemination / Section 9.1.3 3.42 Phase 3: Route Dissemination / Section 9.1.3
2.42.208 Policy for processing routes from the Loc-RIB into Adj-RIBs- 2.42.208 Policy for processing routes from the Loc-RIB into Adj-RIBs-
Out Out
Functionality/Description: Exclude a route in the Loc-RIB from Functionality/Description: Exclude a route in the Loc-RIB from
being installed in a particular Adj-RIB-Out being installed in a particular Adj-RIB-Out
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.42.209 Adj-Rib-Out Route Installation 2.42.209 Adj-Rib-Out Route Installation
Functionality/Description: Not unless the destination and Functionality/Description: Not unless the destination and
skipping to change at page 66, line 4 skipping to change at page 67, line 34
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.42.210 Withdraw routes 2.42.210 Withdraw routes
Functionality/Description: If a route in Loc-RIB is excluded Functionality/Description: If a route in Loc-RIB is excluded
from a particular Adj-RIB-Out the previously advertised route in from a particular Adj-RIB-Out the previously advertised route in
that Adj-RIB-Out MUST be withdrawn from service by means of an that Adj-RIB-Out MUST be withdrawn from service by means of an
UPDATE message (see 9.2) UPDATE message (see 9.2)
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.43 Overlapping Routes / Section 9.1.4 3.43 Overlapping Routes / Section 9.1.4
2.43.211 Overlapping Routes 2.43.211 Overlapping Routes
Functionality/Description: Consider both routes based on the Functionality/Description: Consider both routes based on the
configured acceptance policy configured acceptance policy
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.43.212 Accepted Overlapping Routes 2.43.212 Accepted Overlapping Routes
Functionality/Description: The Decision Process MUST either Functionality/Description: The Decision Process MUST either
install both routes or... install both routes or...
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
skipping to change at page 67, line 23 skipping to change at page 69, line 5
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.43.215 De-aggregation 2.43.215 De-aggregation
Functionality/Description: Routes SHOULD NOT be de-aggregated Functionality/Description: Routes SHOULD NOT be de-aggregated
RFC2119: SHOULD NOT RFC2119: SHOULD NOT
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.43.216 Route with the ATOMIC_AGGREGATE attribute 2.43.216 Route with the ATOMIC_AGGREGATE attribute
Functionality/Description: Not de-aggregated Functionality/Description: Not de-aggregated
RFC2119: MUST NOT RFC2119: MUST NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.44 Update-Send Process / Section 9.2 3.44 Update-Send Process / Section 9.2
2.44.217 UPDATE message received from an internal peer 2.44.217 UPDATE message received from an internal peer
Functionality/Description: Not re-distribute the routing Functionality/Description: Not re-distribute the routing
information to other internal peers, unless the speaker acts as information to other internal peers, unless the speaker acts as
a BGP Route Reflector [RFC2796] a BGP Route Reflector [RFC2796]
RFC2119: SHALL NOT RFC2119: SHALL NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.44.218 No replacement route 2.44.218 No replacement route
Functionality/Description: All newly installed routes and all Functionality/Description: All newly installed routes and all
newly unfeasible routes for which there is no replacement route newly unfeasible routes for which there is no replacement route
SHALL be advertised to its peers by means of an UPDATE message SHALL be advertised to its peers by means of an UPDATE message
skipping to change at page 68, line 22 skipping to change at page 70, line 5
newly unfeasible routes for which there is no replacement route newly unfeasible routes for which there is no replacement route
SHALL be advertised to its peers by means of an UPDATE message SHALL be advertised to its peers by means of an UPDATE message
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.44.219 Previously Advertised Routes 2.44.219 Previously Advertised Routes
Functionality/Description: A BGP speaker SHOULD NOT advertise a Functionality/Description: A BGP speaker SHOULD NOT advertise a
given feasible BGP route if it would produce an UPDATE message given feasible BGP route if it would produce an UPDATE message
containing the same BGP route as was previously advertised containing the same BGP route as was previously advertised
RFC2119: SHOULD NOT RFC2119: SHOULD NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 69, line 24 skipping to change at page 71, line 4
2.44.222 A single route doesn't fit into the UPDATE message 2.44.222 A single route doesn't fit into the UPDATE message
Functionality/Description: Don't advertise Functionality/Description: Don't advertise
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.44.223 A single route doesn't fit into the UPDATE message 2.44.223 A single route doesn't fit into the UPDATE message
Functionality/Description: Log an error local Functionality/Description: Log an error local
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.45 Frequency of Route Advertisement / Section 9.2.1.1 3.45 Frequency of Route Advertisement / Section 9.2.1.1
2.45.224 MinRouteAdvertisementIntervalTimer 2.45.224 MinRouteAdvertisementIntervalTimer
Functionality/Description: Minimum separation between two UPDATE Functionality/Description: Minimum separation between two UPDATE
messages sent by a BGP speaker to a peer that advertise feasible messages sent by a BGP speaker to a peer that advertise feasible
routes and/or withdrawal of unfeasible routes to some common set routes and/or withdrawal of unfeasible routes to some common set
of destinations of destinations
RFC2119: MUST RFC2119: MUST
skipping to change at page 70, line 23 skipping to change at page 72, line 5
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: O Configurable on per peer basis. Alcatel Y/N/O/Comments: O Configurable on per peer basis.
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: N they are same for ebgp and ibgp Laurel Y/N/O/Comments: N they are same for ebgp and ibgp
NextHop Y/N/O/Comments: Y Configuration option allows to set NextHop Y/N/O/Comments: Y Configuration option allows to set
the time per peer. the time per peer.
2.45.226 Fast Convergence 2.45.226 Fast Convergence
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Functionality/Description: The procedure describes in this Functionality/Description: The procedure describes in this
section SHOULD NOT apply for routes sent to internal peers section SHOULD NOT apply for routes sent to internal peers
RFC2119: SHOULD NOT RFC2119: SHOULD NOT
Alcatel Y/N/O/Comments: O Operator has to ensure that through Alcatel Y/N/O/Comments: O Operator has to ensure that through
configuration. configuration.
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: N Laurel Y/N/O/Comments: N
NextHop Y/N/O/Comments: Y Default setting is off for BGP NextHop Y/N/O/Comments: Y Default setting is off for BGP
skipping to change at page 71, line 5 skipping to change at page 72, line 32
Functionality/Description: The last route selected SHALL be Functionality/Description: The last route selected SHALL be
advertised at the end of MinRouteAdvertisementIntervalTimer advertised at the end of MinRouteAdvertisementIntervalTimer
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.46 Aggregating Routing Information / Section 9.2.2.2 3.46 Aggregating Routing Information / Section 9.2.2.2
2.46.228 MULTI_EXIT_DISC 2.46.228 MULTI_EXIT_DISC
Functionality/Description: Routes that have different Functionality/Description: Routes that have different
MULTI_EXIT_DISC attribute SHALL NOT be aggregated MULTI_EXIT_DISC attribute SHALL NOT be aggregated
RFC2119: SHALL NOT RFC2119: SHALL NOT
Alcatel Y/N/O/Comments: N Alcatel Y/N/O/Comments: N
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
Laurel Y/N/O/Comments: N Laurel Y/N/O/Comments: N
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.46.229 AS_SET as the First Element 2.46.229 AS_SET as the First Element
Functionality/Description: If the aggregated route has an AS_SET Functionality/Description: If the aggregated route has an AS_SET
as the first element in its AS_PATH attribute, then the router as the first element in its AS_PATH attribute, then the router
that originates the route SHOULD NOT advertise the that originates the route SHOULD NOT advertise the
MULTI_EXIT_DISC attribute with this route MULTI_EXIT_DISC attribute with this route
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: SHOULD NOT RFC2119: SHOULD NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.46.230 NEXT_HOP 2.46.230 NEXT_HOP
Functionality/Description: When aggregating routes that have Functionality/Description: When aggregating routes that have
skipping to change at page 72, line 21 skipping to change at page 73, line 51
2.46.232 ORIGIN EGP 2.46.232 ORIGIN EGP
Functionality/Description: Used if at least one route among Functionality/Description: Used if at least one route among
routes that are aggregated has ORIGIN with the value EGP routes that are aggregated has ORIGIN with the value EGP
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: N EGP is no longer a supported NextHop Y/N/O/Comments: Y
protocol
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.46.233 Routes to be aggregated have different AS_PATH attributes 2.46.233 Routes to be aggregated have different AS_PATH attributes
Functionality/Description: The aggregated AS_PATH attribute Functionality/Description: The aggregated AS_PATH attribute
SHALL satisfy all of the following conditions: ... SHALL satisfy all of the following conditions: ...
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
skipping to change at page 73, line 26 skipping to change at page 75, line 5
2.46.236 Routes to be aggregated have different AS_PATH attributes 2.46.236 Routes to be aggregated have different AS_PATH attributes
Functionality/Description: For any tuple X of type AS_SEQUENCE Functionality/Description: For any tuple X of type AS_SEQUENCE
in the aggregated AS_PATH which precedes tuple Y in the in the aggregated AS_PATH which precedes tuple Y in the
aggregated AS_PATH, X precedes Y in each AS_PATH in the initial aggregated AS_PATH, X precedes Y in each AS_PATH in the initial
set which contains Y, regardless of the type of Y set which contains Y, regardless of the type of Y
RFC2119: N/A RFC2119: N/A
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.46.237 Routes to be aggregated have different AS_PATH attributes 2.46.237 Routes to be aggregated have different AS_PATH attributes
Functionality/Description: No tuple of type AS_SET with the same Functionality/Description: No tuple of type AS_SET with the same
value SHALL appear more than once in the aggregated AS_PATH value SHALL appear more than once in the aggregated AS_PATH
skipping to change at page 74, line 24 skipping to change at page 76, line 4
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: N We don't do merging. Cisco Y/N/O/Comments: N We don't do merging.
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.46.240 ATOMIC_AGGREGATE 2.46.240 ATOMIC_AGGREGATE
Functionality/Description: The aggregated route SHALL have this Functionality/Description: The aggregated route SHALL have this
^L
draft-ietf-idr-bgp-implementation-01 July 2004
attribute if at least one of the routes to be aggregated has it attribute if at least one of the routes to be aggregated has it
RFC2119: SHALL RFC2119: SHALL
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.46.241 AGGREGATOR 2.46.241 AGGREGATOR
skipping to change at page 75, line 13 skipping to change at page 76, line 41
Functionality/Description: Attach a new one when aggregating Functionality/Description: Attach a new one when aggregating
(see Section 5.1.7) (see Section 5.1.7)
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.47 Route Selection Criteria / Section 9.3 3.47 Route Selection Criteria / Section 9.3
2.47.243 Unstable routes 2.47.243 Unstable routes
Functionality/Description: Avoid using them Functionality/Description: Avoid using them
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.47.244 Route changes 2.47.244 Route changes
Functionality/Description: SHOULD NOT make rapid spontaneous Functionality/Description: SHOULD NOT make rapid spontaneous
changes to the choice of route changes to the choice of route
RFC2119: SHOULD NOT RFC2119: SHOULD NOT
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.48 Originating BGP routes / Section 9.4 3.48 Originating BGP routes / Section 9.4
2.48.245 Non-BGP acquired routes 2.48.245 Non-BGP acquired routes
Functionality/Description: Distributed to other BGP speakers Functionality/Description: Distributed to other BGP speakers
within the local AS as part of the update process within the local AS as part of the update process
(see Section 9.2) (see Section 9.2)
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
skipping to change at page 76, line 19 skipping to change at page 77, line 47
Functionality/Description: Distribution controlled via Functionality/Description: Distribution controlled via
configuration configuration
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.49 BGP Timers / Section 10 3.49 BGP Timers / Section 10
2.49.247 Optional Timers 2.49.247 Optional Timers
Functionality/Description: Two optional timers MAY be supported: Functionality/Description: Two optional timers MAY be supported:
DelayOpenTimer, IdleHoldTimer by BGP DelayOpenTimer, IdleHoldTimer by BGP
^L
draft-ietf-idr-bgp-implementation-01 July 2004
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: N Alcatel Y/N/O/Comments: N
Cisco Y/N/O/Comments: O We support DelayOpenTimer but not Cisco Y/N/O/Comments: O We support DelayOpenTimer but not
IdleHoldTimer IdleHoldTimer
Laurel Y/N/O/Comments: Y support IdleHoldTimer but not the Laurel Y/N/O/Comments: Y support IdleHoldTimer but not the
DelayOpenTimer DelayOpenTimer
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.49.248 Hold Time 2.49.248 Hold Time
skipping to change at page 77, line 24 skipping to change at page 79, line 5
MinASOriginationInterval, KeepAlive, MinASOriginationInterval, KeepAlive,
MinRouteAdvertisementInterval, and ConnectRetry MinRouteAdvertisementInterval, and ConnectRetry
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: O We only apply to ConnectRetry. Cisco Y/N/O/Comments: O We only apply to ConnectRetry.
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
^L
draft-ietf-idr-bgp-implementation-01 July 2004
2.49.251 Jitter 2.49.251 Jitter
Functionality/Description: Apply the same jitter to each of Functionality/Description: Apply the same jitter to each of
these quantities regardless of the destinations to which the these quantities regardless of the destinations to which the
updates are being sent; that is, jitter need not be configured updates are being sent; that is, jitter need not be configured
on a "per peer" basis on a "per peer" basis
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
skipping to change at page 78, line 22 skipping to change at page 79, line 53
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
2.49.254 Jitter Random Value Range 2.49.254 Jitter Random Value Range
Functionality/Description: Configurable Functionality/Description: Configurable
RFC2119: MAY RFC2119: MAY
Alcatel Y/N/O/Comments: N Not configurable. Alcatel Y/N/O/Comments: N
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y
2.50 TCP options that may be used with BGP / Appendix E ^L
draft-ietf-idr-bgp-implementation-01 July 2004
NextHop Y/N/O/Comments: N
3.50 TCP options that may be used with BGP / Appendix E
2.50.255 TCP PUSH function supported 2.50.255 TCP PUSH function supported
Functionality/Description: Each BGP message SHOULD be Functionality/Description: Each BGP message SHOULD be
transmitted with PUSH flag set transmitted with PUSH flag set
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
skipping to change at page 79, line 4 skipping to change at page 80, line 32
NextHop Y/N/O/Comments: O Depends on the TCP stack support. NextHop Y/N/O/Comments: O Depends on the TCP stack support.
GateD 10, NGC can run over GateD 10, NGC can run over
multiple stacks. multiple stacks.
2.50.256 DSCP Field Support 2.50.256 DSCP Field Support
Functionality/Description: TCP connections opened with bits 0-2 Functionality/Description: TCP connections opened with bits 0-2
of the DSCP field set to 110 (binary) of the DSCP field set to 110 (binary)
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y Depends on the TCP stack support. NextHop Y/N/O/Comments: O Depends on the TCP stack support.
GateD 10, NGC can run over GateD 10, NGC can run over
multiple stacks. multiple stacks.
2.51 Reducing route flapping / Appendix F.2 3.51 Reducing route flapping / Appendix F.2
2.51.257 Avoid excessive route flapping 2.51.257 Avoid excessive route flapping
Functionality/Description: A BGP speaker which needs to withdraw Functionality/Description: A BGP speaker which needs to withdraw
a destination and send an update about a more specific or less a destination and send an update about a more specific or less
specific route SHOULD combine them into the same UPDATE message specific route SHOULD combine them into the same UPDATE message
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
Laurel Y/N/O/Comments: N Laurel Y/N/O/Comments: N
NextHop Y/N/O/Comments: N NextHop Y/N/O/Comments: N
2.52 Complex AS_PATH aggregation / Appendix F.6 ^L
draft-ietf-idr-bgp-implementation-01 July 2004
3.52 Complex AS_PATH aggregation / Appendix F.6
2.52.258 Multiple instances in AS_PATH 2.52.258 Multiple instances in AS_PATH
Functionality/Description: The last instance (rightmost Functionality/Description: The last instance (rightmost
occurrence) of that AS number is kept occurrence) of that AS number is kept
RFC2119: SHOULD RFC2119: SHOULD
Alcatel Y/N/O/Comments: N We use algorithm in 9.2.2.2 Alcatel Y/N/O/Comments: N We use algorithm in 9.2.2.2
Cisco Y/N/O/Comments: N Cisco Y/N/O/Comments: N
Laurel Y/N/O/Comments: N Laurel Y/N/O/Comments: N
NextHop Y/N/O/Comments: N NextHop Y/N/O/Comments: N
2.53 Security Considerations 3.53 Security Considerations
2.53.259 Authentication Mechanism 2.53.259 Authentication Mechanism
Functionality/Description: RFC2385 Functionality/Description: RFC2385
RFC2119: MUST RFC2119: MUST
Alcatel Y/N/O/Comments: Y Alcatel Y/N/O/Comments: Y
Cisco Y/N/O/Comments: Y Cisco Y/N/O/Comments: Y
Laurel Y/N/O/Comments: Y Laurel Y/N/O/Comments: Y
NextHop Y/N/O/Comments: Y NextHop Y/N/O/Comments: Y
4. Additional BGP implementations Information
Three implementations responded to a call (5/20/04-6/2/04) for
information on those implementations that had a BGP implementation,
but did not complete the full survey. The responses for the call for
additional information are below.
4.1 Avici
If you have an implementation of BGP and you did not send in an
implementation report (answering the 259 questions), could you send
me the answer the following questions:
1) BGP product
Contributor (your name):Curtis Villamizar [curtis@fictitious.org]
Company: Avici
name of product: IPriori (TM)
minor version: No interoperability problems with any version.
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Current deployed versions are 5.x and 6.0.x.
Version 6.1 and beyond are tested against the
latest BGP draft soon to replace rfc1771.
2) What other implementations you interoperate with.
Cisco: IOS 12.0(22)
Juniper: JUNOS (version not given)
3) Do you inter-operate with:
1) Alcatel BGP (release) - not tested
2) cisco BGP IOS 12.0(27)s - not tested
tested with IOS 12.0(22); BGP is the same
3) laurel BGP (specify release) - not tested
4) NextHop GateD- not tested
4) Did the length of the survey for BGP cause you to not
submit the BGP implementation report?
yes
4.2 Data Connection Ltd.
If you have an implementation of BGP and you did not send in an
implementation report (answering the 259 questions), could you send
me the answer the following questions:
1) BGP product
Contributor (your name): Mike Dell
Company: Data Connection Ltd.
name of product: DC-BGP
version and minor of software: v1.1
release date: April 2003
2) What other implementations you interoperate with.
Cisco (12.0(26)S)
Alcatal (7770 0BX)
Agilent (Router Tester)
Ixia (1600T)
Netplane (Powercode)
Nortel (Shasta 5000 BSN)
Redback (SmartEdge 800)
Riverstone (RS8000)
Spirent (AX4000)
^L
draft-ietf-idr-bgp-implementation-01 July 2004
IP Infusion (ZebOs)
Nokia (IP400)
Juniper (M5)
3) Do you inter-operate with
1) Alcatel BGP (release) YES
2) cisco BGP IOS 12.0(27)s
Unknown, but we do inter-operate with v12.0(26)s
3) laurel BGP (specify release) Unknown
4) NextHop GateD YES
4) Did the length of the survey for BGP
cause you to not submit the BGP
implementation report?
YES
4.3 Nokia BGP
If you have an implementation of BGP and you did not send in an
implementation report (answering the 259 questions), could you send
me the answer the following questions:
1) BGP product
Contributor (your name):Rahul Bahadur
(rahul.bahadur@nokia.com)
Company: Nokia
Name of product: IP Security Platforms
Version and minor of software IPSO 3.8 Build031
Release date May 24, 2004
2) What other implementations you interoperate with.
Cisco: IOS 12.3(1)
Extreme: Extremeware Version 6.1.7 (Build 9)
Foundry: SW Version 07.5.05iT53
Juniper: JUNOS 5.3R1.2
Nortel: BayRS 15.4.0.1
GNU Zebra: zebra-0.92a
3) Do you inter-operate with
1) Alcatel BGP (release) - not tested
2) cisco BGP IOS 12.0(27)s - yes
3) laurel BGP (specify release) - not tested
4) NextHop GateD- not tested
^L
draft-ietf-idr-bgp-implementation-01 July 2004
4) Did the length of the survey for BGP
cause you to not submit the BGP implementation report?
Yes - lack of resources to help with task.
Security Considerations Security Considerations
This document does not address any security issues. This document does not address any security issues.
References Normative References
1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP [BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway Protocol 4
9, RFC 2026, October 1996. (BGP-4)", draft-ietf-idr-bgp4-24.txt, June 2004
2 Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC1771] Rekhter, Y., Li, T., "A Border Gateway Protocol 4
Levels", BCP 14, RFC 2119, March 1997 (BGP-4)", RFC1771, March 1995
3 RFC 2119 reference here [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, March 1997
4 BGP ID reference [RFC2385] A. Heffernan, "Protection of BGP Session via a TCP MD5
Signature", RFC2385, August 1998
[RFC2796] Bates, T., Chandra, R., Chen, E., "BGP Route Reflection -
an Alternative to Full Mesh IBGP", RFC 2796, April 2000
[RFC2918] Chen, E., "Route Refresh Capability for BGP-4", RFC2918,
September 2000
[RFC3065] Traina, P., McPherson, D., Scudder, J., "Autonomous
Confederations for BGP", RFC 3065, February 2001
[RFC3667] Bradner, S., "IETF Rights in Contributions", BCP 78,
February 2004
[RFC3668] Bradner, S. "Intellectual Property Rights in IETF
Technology", BCP 79, February 2004
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Acknowledgments Acknowledgments
Alcatel Responses provided by: Alcatel Responses provided by:
Contact Name: Contact Name: Devendra Raut
Contact Email: Contact Email: Devendra.raut@Alcatel.com
Cisco Systems Responses provided by: Cisco Systems Responses provided by:
Contact Name: Himanshu Shah, Ruchi Kapoor Contact Name: Himanshu Shah, Ruchi Kapoor
Contact e-mail Address: hhshah@cisco.com, ruchi@cisco.com Contact e-mail Address: hhshah@cisco.com, ruchi@cisco.com
Laurel Responses provided by: Laurel Responses provided by:
Contact Name: Contact Name: Manish Vora
Contact e-mail Address: Contact e-mail Address: vora@laurelnetworks.com
NextHop Responses provided by: NextHop Responses provided by:
Contact Name: Susan Hares Contact Name: Susan Hares
Contact e-mail Address: skh@nexthop.com Contact e-mail Address: skh@nexthop.com
Additional Help: Matt Richardson, Shane Wright.
Author's Addresses Authors' Addresses
Susan Hares Susan Hares
NextHop Technologies NextHop Technologies
825 Victors Way, Suite 100 825 Victors Way, Suite 100
Phone: 734.222.1610 Phone: 734.222.1610
Email: skh@nexthop.com Email: skh@nexthop.com
Alvaro Retana Alvaro Retana
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd. 7025 Kit Creek Rd.
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
Phone: 919 392 2061 Phone: 919 392 2061
e-mail: aretana@cisco.com e-mail: aretana@cisco.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed
to pertain to the implementation or use of the technology
described in this document or the extent to which any license
under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any
such rights. Information on the procedures with respect to rights
in RFC documents can be found in BCP 78 and BCP 79.
^L
draft-ietf-idr-bgp-implementation-01 July 2004
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use
of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository
at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention
any copyrights, patents or patent applications, or other
proprietary rights that may cover technology that may be required
to implement this standard. Please address the information to the
IETF at ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
^L
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/