draft-ietf-idr-bgp-issues-00.txt   draft-ietf-idr-bgp-issues-01.txt 
Internet Engineering Task Force A. Lange Internet Engineering Task Force A. Lange
INTERNET DRAFT Cable & Wireless INTERNET DRAFT Cable & Wireless
May 2003 June 2003
Expires November 2003 Expires December 2003
Issues in Revising BGP-4 Issues in Revising BGP-4
<draft-ietf-idr-bgp-issues-00.txt> <draft-ietf-idr-bgp-issues-01.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 Internet-
Drafts. Drafts.
skipping to change at page 2, line 35 skipping to change at page 2, line 35
Protocol............................................... 27 Protocol............................................... 27
2.20 Wording fix in Section 4.3............................. 28 2.20 Wording fix in Section 4.3............................. 28
2.21 Authentication Text Update............................. 28 2.21 Authentication Text Update............................. 28
2.22 Scope of Path Attribute Field.......................... 29 2.22 Scope of Path Attribute Field.......................... 29
2.23 Withdrawn and Updated routes in the same UPDATE message 29 2.23 Withdrawn and Updated routes in the same UPDATE message 29
2.24 Addition or Deletion of Path Attributes................ 31 2.24 Addition or Deletion of Path Attributes................ 31
2.25 NEXT_HOP Semantics..................................... 32 2.25 NEXT_HOP Semantics..................................... 32
2.26 Attributes with Multiple Prefixes...................... 32 2.26 Attributes with Multiple Prefixes...................... 32
2.27 Allow All Non-Destructive Messages to Refresh Hold 2.27 Allow All Non-Destructive Messages to Refresh Hold
Timer.................................................. 33 Timer.................................................. 33
2.28 BGP Identifier as Variable Quantity.................... 2.28 BGP Identifier as Variable Quantity.................... 34
2.29 State Why Unresolveable Routes Should Be Kept in 2.29 State Why Unresolveable Routes Should Be Kept in
Adj-RIB-In............................................. Adj-RIB-In............................................. 34
2.30 Mention Other Message Types............................ 2.30 Mention Other Message Types............................ 35
2.31 Add References to Additional Options................... 2.31 Add References to Additional Options................... 36
2.32 Clarify EGP Reference.................................. 2.32 Clarify EGP Reference.................................. 36
2.32.1 EGP ORIGIN Clarification............................. 2.32.1 EGP ORIGIN Clarification............................. 37
2.32.2 BGP Destination-based Forwarding Paradigm............ 2.32.2 BGP Destination-based Forwarding Paradigm............ 41
2.33 Add "Optional Non-Transitive" to the MED Section....... 2.33 Add "Optional Non-Transitive" to the MED Section....... 45
2.34 Timer & Counter Definition............................. 2.34 Timer & Counter Definition............................. 45
2.35 Fix Typo............................................... 2.35 Fix Typo............................................... 46
2.36 Add Adj-RIB-In, Adj-RIB-Out and Loc-RIB to the Glossary 2.36 Add Adj-RIB-In, Adj-RIB-Out and Loc-RIB to the Glossary 46
2.37 Combine "Unfeasible Routes" and "Withdrawn Routes"..... 2.37 Combine "Unfeasible Routes" and "Withdrawn Routes"..... 46
2.38 Clarify Outbound Route Text............................ 2.38 Clarify Outbound Route Text............................ 48
2.39 Redundant Sentence Fragments........................... 2.39 Redundant Sentence Fragments........................... 49
2.40 Section 9.2.1.1 - Per Peer vs. Per Router 2.40 Section 9.2.1.1 - Per Peer vs. Per Router
MinRouteAdvertisementInterval.......................... MinRouteAdvertisementInterval.......................... 50
2.41 Mention FSM Internal Timers............................ 50
2.41 Mention FSM Internal Timers............................ 2.42 Delete the FSM Section................................. 51
2.42 Delete the FSM Section................................. 2.43 Clarify the NOTIFICATION Section....................... 51
2.43 Clarify the NOTIFICATION Section....................... 2.44 Section 6.2: OPEN message error handling............... 52
2.44 Section 6.2: OPEN message error handling............... 2.45 Consistent References to BGP Peers/Connections/Sessions 54
2.45 Consistent References to BGP Peers/Connections/Sessions 2.46 FSM Connection Collision Detection..................... 55
2.46 FSM Connection Collision Detection..................... 2.47 FSM - Add Explicit State Change Wording................ 57
2.47 FSM - Add Explicit State Change Wording................ 2.48 Explicitly Define Processing of Incoming Connections... 57
2.48 Explicitly Define Processing of Incoming Connections.. 2.49 Explicitly Define Event Generation..................... 61
2.49 Explicitly Define Event Generation...................... 2.50 FSM Timers............................................. 62
2.50 FSM Timers............................................. 2.51 FSM ConnectRetryCnt.................................... 62
2.51 FSM ConnectRetryCnt.................................... 2.52 Section 3: Keeping routes in Adj-RIB-In................ 63
2.52 Section 3: Keeping routes in Adj-RIB-In................ 2.53 Section 4.3 - Routes v. Destinations - Advertise....... 64
2.53 Section 4.3 - Routes v. Destinations - Advertise....... 2.54 Section 4.3 - Routes v. Destinations - Withdraw........ 65
2.54 Section 4.3 - Routes v. Destinations - Withdraw........ 2.55 Section 4.3 - Description of AS_PATH length............ 67
2.55 Section 4.3 - Description of AS_PATH length............ 2.56 Section 6 - BGP Error Handling......................... 68
2.56 Section 6 - BGP Error Handling......................... 2.57 Section 6.2 - Hold timer as Zero....................... 70
2.57 Section 6.2 - Hold timer as Zero....................... 2.58 Deprecation of ATOMIC_AGGREGATE........................ 71
2.58 Deprecation of ATOMIC_AGGREGATE........................ 2.59 Section 4.3 - Move text................................ 79
2.59 Section 4.3 - Move text................................ 2.60 Section 4.3 - Path Attributes.......................... 80
2.60 Section 4.3 - Path Attributes.......................... 2.61 Next Hop for Redistributed Routes...................... 81
2.61 Next Hop for Redistributed Routes......................
2.62 Deprecate BGP Authentication Optional Parameter from 2.62 Deprecate BGP Authentication Optional Parameter from
RFC1771................................................ RFC1771................................................ 83
2.63 Clarify MED Removal Text............................... 2.63 Clarify MED Removal Text............................... 87
2.64 MED for Originated Routes.............................. 2.64 MED for Originated Routes.............................. 93
2.65 Rules for Aggregating with MED and NEXT_HOP............ 2.65 Rules for Aggregating with MED and NEXT_HOP............ 93
2.66 Complex AS Path Aggregating............................ 2.66 Complex AS Path Aggregating............................ 94
2.67 Counting AS_SET/AS_CONFED_*............................ 2.67 Counting AS_SET/AS_CONFED_*............................ 96
2.68 Outbound Loop Detection................................ 2.68 Outbound Loop Detection................................ 97
2.69 Appendix A - Other Documents........................... 2.69 Appendix A - Other Documents........................... 99
3.1 Reference to RFC 1772................................... 3. The Issues from -18 to -19............................... 99
3.2 MUST/SHOULD Capitalization.............................. 3.1 Reference to RFC 1772................................... 99
3.3 Fix Update Error Subcode 7 -- accidently removed........ 3.2 MUST/SHOULD Capitalization.............................. 99
3.4 Section 5.1.4 - Editorial Comment........................ 3.3 Fix Update Error Subcode 7 -- accidently removed........ 100
3.5 Section 9.1 - Change "all peers" to "peers"............. 3.4 Section 5.1.4 - Editorial Comment....................... 101
3.6 AS Loop Detection & Implicit Withdraws.................. 3.5 Section 9.1 - Change "all peers" to "peers"............. 101
3.7 Standardize FSM Timer Descriptions...................... 3.6 AS Loop Detection & Implicit Withdraws.................. 101
3.8 FSM MIB enumerations.................................... 3.7 Standardize FSM Timer Descriptions...................... 102
3.9 Make "delete routes" language consistent................ 3.8 FSM MIB enumerations.................................... 103
3.10 Correct OpenSent and OpenConfirm delete wording........ 3.9 Make "delete routes" language consistent................ 104
3.11 Incorrect next state when the delay open timer expires. 3.10 Correct OpenSent and OpenConfirm delete wording........ 104
3.12 Entering OpenConfirm / Adding "Stop OpenDelay" action.. 3.11 Incorrect next state when the delay open timer expires. 105
3.13 FSM Missing Next States................................ 3.12 Entering OpenConfirm / Adding "Stop OpenDelay" action.. 105
3.13 FSM Missing Next States................................ 111
3.13.1 FSM Missing Next States - Event 15 or 16 3.13.1 FSM Missing Next States - Event 15 or 16
(Connect State)...................................... (Connect State)...................................... 111
3.13.2 FSM Missing Next States - Event 14 (Connect State)... 3.13.2 FSM Missing Next States - Event 14 (Connect State)... 113
3.13.3 FSM Missing Next States - Event 15 or 16 3.13.3 FSM Missing Next States - Event 15 or 16
(Active State)....................................... (Active State)....................................... 115
3.13.4 FSM Missing Next States - Event 13-17 3.13.4 FSM Missing Next States - Event 13-17
(TCP Connection)..................................... (TCP Connection)..................................... 116
3.13.5 FSM Missing Next States - Event 17 (Connect State)... 3.13.5 FSM Missing Next States - Event 17 (Connect State)... 118
3.13.6 FSM Missing Next States - Event 18 (Open Confirm).... 3.13.6 FSM Missing Next States - Event 18 (Open Confirm).... 121
3.14 FSM - Peer Oscillation Damping......................... 3.14 FSM - Peer Oscillation Damping......................... 124
3.15 FSM - Consistent FSM Event Names....................... 3.15 FSM - Consistent FSM Event Names....................... 124
3.16 Many Editorial Comments................................ 3.16 Many Editorial Comments................................ 127
3.17 Section 3, Page 8, Paragraph 3 - Obsolete?............. 3.17 Section 3, Page 8, Paragraph 3 - Obsolete?............. 132
3.18 MED Removal Text....................................... 3.18 MED Removal Text....................................... 135
3.19 Security Considerations................................ 3.19 Security Considerations................................ 138
3.20 Peer Oscillation Damping............................... 3.20 Peer Oscillation Damping............................... 138
3.21 Session Attributes - IdleHold Timer.................... 3.21 Session Attributes - IdleHold Timer.................... 139
3.22 Specify New Attributes (Accept Connections/Peer 3.22 Specify New Attributes (Accept Connections/Peer
Oscillation Damping)................................... Oscillation Damping)................................... 141
3.23 Event1/Event2 Clean Up................................. 3.23 Event1/Event2 Clean Up................................. 142
3.24 Events 3, 5, 6 & 7 Give Examples....................... 3.24 Events 3, 5, 6 & 7 Give Examples....................... 142
3.25 Event 4 & 5 Session Initiation Text.................... 3.25 Event 4 & 5 Session Initiation Text.................... 144
3.26 Event 4 & 5 - bgp_stop_flap option..................... 3.26 Event 4 & 5 - bgp_stop_flap option..................... 145
3.27 Event 5 Clarification.................................. 3.27 Event 5 Clarification.................................. 147
3.28 Timer Events Definition - Make Consistent.............. 3.28 Timer Events Definition - Make Consistent.............. 148
3.29 Event 8 - Clean Up..................................... 3.29 Event 8 - Clean Up..................................... 148
3.30 Hold Timer - Split?.................................... 3.30 Hold Timer - Split?.................................... 149
3.31 OpenDelay Timer Definition............................. 3.31 OpenDelay Timer Definition............................. 149
3.32 Definition of TCP Connection Accept (Event 13)......... 3.32 Definition of TCP Connection Accept (Event 13)......... 149
3.33 Event 13 & 14 - Valid Addresses & Ports................ 3.33 Event 13 & 14 - Valid Addresses & Ports................ 150
3.34 Event 17 - TCP Connection Fails to TCP Connection 3.34 Event 17 - TCP Connection Fails to TCP Connection
Termination............................................ Termination............................................ 151
3.35 Making Definition Style Consistent..................... 3.35 Making Definition Style Consistent..................... 151
3.36 Event 19 - Definition Cleanup.......................... 3.36 Event 19 - Definition Cleanup.......................... 154
3.37 Event 22 - Cleanup..................................... 3.37 Event 22 - Cleanup..................................... 155
3.38 FSM Description - ConnectRetry Count................... 3.38 FSM Description - ConnectRetry Count................... 156
3.39 Handling Event 7 (Auto Stop to Idle State processing).. 3.39 Handling Event 7 (Auto Stop to Idle State processing).. 157
3.40 Clearing the Connection Retry Timer.................... 3.40 Clearing the Connection Retry Timer.................... 157
3.41 Handling of Event 14 in the Connect State.............. 3.41 Handling of Event 14 in the Connect State.............. 159
3.42 Handling events 20, 21 in the Connect State and Active 3.42 Handling events 20, 21 in the Connect State and Active
State.................................................. State.................................................. 160
3.43 Handling the default events in the Connect state....... 3.43 Handling the default events in the Connect state....... 163
3.44 Handling Event 23 in Connect and OpenSent.............. 3.44 Handling Event 23 in Connect and OpenSent.............. 165
3.45 Event 17 in the Connect state.......................... 3.45 Event 17 in the Connect state.......................... 167
3.46 Handling of Event 17 in Active state................... 3.46 Handling of Event 17 in Active state................... 170
3.47 Handling of Event 19 in Active state................... 3.47 Handling of Event 19 in Active state................... 170
3.48 Handling of Event 2 in Active state.................... 3.48 Handling of Event 2 in Active state.................... 171
3.49 Default Event handling in Active state................. 3.49 Default Event handling in Active state................. 173
3.50 Clearing Hold timer in OpenSent, OpenConfirm and 3.50 Clearing Hold timer in OpenSent, OpenConfirm and
Established State...................................... Established State...................................... 173
3.51 Clearing Keepalive timer in OpenConfirm and Established 3.51 Clearing Keepalive timer in OpenConfirm and Established
State.................................................. State.................................................. 174
3.52 Handling Event 18 in the OpenSent state (Keepalive 3.52 Handling Event 18 in the OpenSent state (Keepalive
Timer)................................................. Timer)................................................. 174
3.53 Established State MIB.................................. 3.53 Established State MIB.................................. 177
3.54 State impact of not supporting Optional Events......... 3.54 State impact of not supporting Optional Events......... 177
3.55 New DelayOpen State.................................... 3.55 New DelayOpen State.................................... 178
3.56 Clarify what is covered in the base document........... 3.56 Clarify what is covered in the base document........... 178
4. References............................................... 179
5. Author's Address......................................... 180
Specification of Requirements Specification of Requirements
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 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
1. Introduction 1. Introduction
This document records the issues discussed and the consensus reached This document records the issues discussed and the consensus reached
skipping to change at page 99, line 16 skipping to change at page 99, line 28
2.69 Appendix A - Other Documents 2.69 Appendix A - Other Documents
Over the course of this discussion, a number of issues have been Over the course of this discussion, a number of issues have been
raised that the group though would be better dealt with in other raised that the group though would be better dealt with in other
documents. These additional documents, and their concomitant issues documents. These additional documents, and their concomitant issues
will be more fully addressed when the WG turns its focus to them. will be more fully addressed when the WG turns its focus to them.
These projects are: These projects are:
1) Update RFC 1772: Application of the Border Gateway Protocol in the 1) Update RFC 1772: Application of the Border Gateway Protocol in the
Internet. This will probably entail a complete rewrite. 2) Update Internet. This will probably entail a complete rewrite.
Route Reflector (2796) and Confederation (3065) RFC's regarding their
impact on route selection. 3) Write a new document covering BGP 2) Update Route Reflector (2796) and Confederation (3065) RFC's
Multipath. regarding their impact on route selection.
2. The Issues from -18 to -19.
3) Write a new document covering BGP Multipath.
3. The Issues from -18 to -19.
This section lists the issues discussed on the list from November This section lists the issues discussed on the list from November
2002 to late February 2003. 2002 to late February 2003.
3.1 Reference to RFC 1772 3.1 Reference to RFC 1772
Status: Consensus Status: Consensus
Change: No Change: No
Summary: Proposed changing RFC 1772 reference, since that document Summary: Proposed changing RFC 1772 reference, since that document
should be updated. should be updated.
skipping to change at page 138, line 42 skipping to change at page 139, line 8
available. available.
After some discussion the plan is to advance draft-ietf-idr-bgp- After some discussion the plan is to advance draft-ietf-idr-bgp-
vuln-00.txt as Informational along with the base BGP specification. vuln-00.txt as Informational along with the base BGP specification.
This draft will serve as the security analysis section of the base This draft will serve as the security analysis section of the base
spec. spec.
This is discussed in the "revised Security Considerations section" This is discussed in the "revised Security Considerations section"
thread. thread.
2.20 Peer Oscillation Damping 3.20 Peer Oscillation Damping
Status: Consensus Status: Consensus
Change: No Change: No
Summary: Keep the Peer Oscillation Damping reference in the Summary: Keep the Peer Oscillation Damping reference in the
specification. specification.
Discussion: Discussion:
This began when Siva proposed: This began when Siva proposed:
skipping to change at page 142, line 17 skipping to change at page 142, line 31
9) accept connections from un-configured peers 9) accept connections from un-configured peers
5) BGP stop_peer_flap flag 5) BGP stop_peer_flap flag
We are at consensus on this. We are at consensus on this.
This was discussed in the "Response to FSM input - Comments 1-10" This was discussed in the "Response to FSM input - Comments 1-10"
thread: Comment #3. This was also discussed in the "BGP Draft 19 - thread: Comment #3. This was also discussed in the "BGP Draft 19 -
Close open items 22" thread. Close open items 22" thread.
2.23 Event1/Event2 Clean Up 3.23 Event1/Event2 Clean Up
Status: Consensus Status: Consensus
Change: Yes Change: Yes
Summary: Use "Local system administrator" in both sections. Summary: Use "Local system administrator" in both sections.
Discussion: Discussion:
Siva proposed that we clean up the text for these Events by selecting Siva proposed that we clean up the text for these Events by selecting
either "Administrator" or "Local system" but not both. either "Administrator" or "Local system" but not both.
Sue proposed text using "Local system administrator" that was agreed Sue proposed text using "Local system administrator" that was agreed
on. on.
This was discussed in the "Response to FSM input - Comments 1-10" This was discussed in the "Response to FSM input - Comments 1-10"
thread: Comment #4. thread: Comment #4.
2.24 Events 3, 5, 6 & 7 Give Examples 3.24 Events 3, 5, 6 & 7 Give Examples
Status: Consensus Status: Consensus
Change: No Change: No
Summary: Leave the examples out. Summary: Leave the examples out.
Discussion: Discussion:
This began with Siva proposing we add examples for these event This began with Siva proposing we add examples for these event
states. Sue believes this is largely out-of-scope, but did agree to states. Sue believes this is largely out-of-scope, but did agree to
move the example of "automatic stop" to the event description move the example of "automatic stop" to the event description
skipping to change at page 180, line 4 skipping to change at page 180, line 24
This document specifies the base behavior of the BGP protocol. This document specifies the base behavior of the BGP protocol.
This behavior can and is modified by extension specifications. This behavior can and is modified by extension specifications.
When the protocol is extended the new behavior is fully documented When the protocol is extended the new behavior is fully documented
in the extension specifications. in the extension specifications.
This was discussed in the "Next-Hop in IPv6 only environments" This was discussed in the "Next-Hop in IPv6 only environments"
thread. thread.
4. References 4. References
[RFC1771] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", [RFC1771] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)",
RFC 1771, March 1995. RFC 1771, March 1995.
[BGP4Draft] Rekhter, Y., Lo, T., Hares, S., "A Border Gateway [BGP4Draft] Rekhter, Y., Lo, T., Hares, S., "A Border Gateway
Protocol 4 (BGP-4)", draft-ietf-idr-bgp4-20.txt. Protocol 4 (BGP-4)", work-in-progress, draft-ietf-idr-bgp4-20.txt.
5. Author's Address: 5. Author's Address:
Andrew Lange Andrew Lange
Cable & Wireless Cable & Wireless
1215 Borregas Ave. 1215 Borregas Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
andrewl@cw.net andrewl@cw.net
 End of changes. 

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