Last Modified: 2003-02-04
The current tasks of the WG are limited to:
- Revise and clarify the base BGP4 document (RFC 1771). Note that RFC 1771 no longer documents existing practice and one goal of the update is document existing practice. Determine whether the document can be advanced as full Standard or needs to recycle at Proposed or Draft Standard.
- Submit updated base BGP4 MIB to accompany the revised base BGP4 document.
Once these tasks are finished (means WG consensus, WG Last Call, AD Review, IETF Last Call, and IESG approval for publication), work will progress on the following:
- Review and Evaluate Existing RFCs on AS Confederations and Route Reflection. If changes are needed, create and advance revisions.
- Review and evaluate Multiprotocol BGP (RFC 2858) for advancement as Draft Standard.
- Progress BGP Extended Communities along standards track.
- Extend BGP to support a 4-byte AS number, develop plan for transitioning to usage of 4-byte AS numbers. Advance support for a 4-byte AS numbers along standards track.
- Produce BGP MIB v2 that includes support for AS Confederations, Route Reflection, Communities, Multi-Protocol BGP, BGP Extended Communities, support for 4-byte AS numbers.
- Progress along the IETF standards track a BGP-based mechanism that allows a BGP speaker to send to its BGP peer a set of route filters that the peer would use to constrain/filter its outbound routing updates to the speaker. Currently defined in draft-ietf-idr-route-filter-03.txt.
- Progress along standards track an Outbound Router Filter (ORF) type for BGP, that can be used to perform aspath based route filtering. The ORF-type will support aspath based route filtering as well as regular expression based matching for address groups. Currently defined in draft-ietf-idr-aspath-orf-00.txt.
- Progress a BGP Graceful Restart mechanism along standards track.
- Progress Subcodes for BGP Cease Notification Message along standards track.
- Progress AS-wide Unique BGP Identifier for BGP-4 along standards track.
- Progress Dynamic Capability for BGP-4 along standards track.
Tasks for this working group are limited to those listed above; new items to be added to the charter must be approved by the IESG.
|Done||Submit to BGP Capability Advertisement to the IESG|
|JAN 03||Submit BGP4 document to IESG.|
|JAN 03||Submit updated base BGP4 MIB to IESG.|
|JAN 03||Submit BGP Security Vulnerabilities Analysis to IESG|
|MAR 03||Submit BGP Graceful Restart to IESG|
|MAR 03||Submit revised text on Multi-Protocol BGP (rfc2858bis) to IESG|
|MAR 03||Submit BGP MIB v2 to IESG|
|MAR 03||Submit Extended Communities draft to IESG.|
|MAY 03||Submit 4-byte AS ID to IESG|
|MAY 03||Submit Outbound Route Filter, Prefix and ASpath ORF draft to IESG|
|MAY 03||Submit Subcodes for BGP Cease Notification Message to IESG|
|MAY 03||Submit AS-wide Unique BGP Identifier for BGP-4 to IESG|
|MAY 03||Submit Dynamic Capability for BGP-4 to IESG|
|RFC1105||E||Border Gateway Protocol BGP|
|RFC1164||H||Application of the Border Gateway Protocol in the Internet|
|RFC1163||H||A Border Gateway Protocol (BGP)|
|RFC1267||H||A Border Gateway Protocol 3 (BGP-3)|
|RFC1268||H||Application of the Border Gateway Protocol in the Internet|
|RFC1269||PS||Definitions of Managed Objects for the Border Gateway Protocol (Version 3)|
|RFC1266||I||Experience with the BGP Protocol|
|RFC1265||I||BGP Protocol Analysis|
|RFC1364||PS||BGP OSPF Interaction|
|RFC1397||PS||Default Route Advertisement In BGP2 And BGP3 Versions Of The Border Gateway Protocol|
|RFC1403||PS||BGP OSPF Interaction|
|RFC1656||I||BGP-4 Protocol Document Roadmap and Implementation Experience|
|RFC1657||DS||Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2|
|RFC1654||PS||A Border Gateway Protocol 4 (BGP-4)|
|RFC1655||PS||Application of the Border Gateway Protocol in the Internet|
|RFC1745||PS||BGP4/IDRP for IP---OSPF Interaction|
|RFC1771||DS||A Border Gateway Protocol 4 (BGP-4)|
|RFC1773||I||Experience with the BGP-4 protocol|
|RFC1774||I||BGP-4 Protocol Analysis|
|RFC1863||E||A BGP/IDRP Route Server alternative to a full mesh routing|
|RFC1930||BCP||Guidelines for creation, selection, and registration of an Autonomous System (AS)|
|RFC1965||E||Autonomous System Confederations for BGP|
|RFC1966||E||BGP Route Reflection An alternative to full mesh IBGP|
|RFC1998||I||An Application of the BGP Community Attribute in Multi-home Routing|
|RFC1997||PS||BGP Communities Attribute|
|RFC2270||I||Using a Dedicated AS for Sites Homed to a Single Provider|
|RFC2283||PS||Multiprotocol Extensions for BGP-4|
|RFC2385||PS||Protection of BGP Sessions via the TCP MD5 Signature Option|
|RFC2439||PS||BGP Route Flap Damping|
|RFC2519||I||A Framework for Inter-Domain Route Aggregation|
|RFC2545||PS||Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing|
|RFC2796||PS||BGP Route Reflection An alternative to full mesh IBGP|
|RFC2842||Standard||Capabilities Advertisement with BGP-4|
|RFC2858||PS||Multiprotocol Extensions for BGP-4|
|RFC2918||PS||Route Refresh Capability for BGP-4|
|RFC3065||PS||Autonomous System Confederations for BGP|
|RFC3345||I||Border Gateway Protocol (BGP) Persistent Route Oscillation Condition|
|RFC3392||DS||Capabilities Advertisement with BGP-4|
Minutes of IDR working group at iETF 56 ========================================= reported by Susan Hares from notes by Andrew Lange and Susan hares approved minutes will be posted at www.ndzh.com/ietf/ietf-56/minutes.txt Wednesday, March 19 1530-1730 ============================= CHAIRS: Sue Hares (firstname.lastname@example.org) Yakov Rekhter (email@example.com) The following was the agenda for the IDR meeting on 3/19/2003. AGENDA: 1530-1545 Administrivia (Yakov Rekhter, Sue Hares) Agenda Bashing Minutes Blue Sheets WG Document Status 15:45-16:10 Flexible BGP Communities (Andrew Lange) http://www.ietf.org/internet-drafts/dr aft-lange-flexible-bgp-communities-00.txt 16:10-16:25 BGP Security Vulnerabilities Analysis (Sandy Murphy) http://www.ietf.org/internet-drafts/dr aft-murphy-bgp-vuln-02.txt =========== 1) Administrivia: WG document status: The Base BGP protocol specification is complete. The editor's thanks go to Andrew Lange. draft-ietf-idr-bgp4-19.txt has incorporated all the comments we have received. draft-ietf-idr-bgp4-20.txt includes a few more editorial changes. We have completed last call the document. The resulting document will be forwarded to IESG. This document goes with a package of documents that detail the BGP4: 1) draft-ietf-idr-bgp4-20.txt 2) draft-ietf-idr-bgp4-mib-10.txt (version 1 MIB) 3) BGP security analysis draft-murphy-bgp-vuln-02.txt which will be re-issued as draft-ietf-idr-bgp4-vuln-01.txt The draft-ietf-idr-bgp4-mib-10.txt will be issued lasted call on the mail list which ends on 3/24. The BGP security analysis document needs to be reviewed and comments sent ASAP. And a group of reports for the IESG: 1) BGP-4 Protocol Analysis (Dave Meyer, Keyur Patel) 2) Experience with the BGP-4 Protocol (Danny McPherson, Keyur Patel) 3) BGP implementation report (Alvaro Retano) Will be uploaded as idr documents. Please comment on these documents. B) 15:46 -16:10 Flexible BGP communities Andrew Lange gave a presentation on BGP communities in BGP Flexible Communities.ppt A discussion ensued afterward containing the following points: a) Should this specification supercede the base communities, the Extended communities or should this document only include communities not specified in these two drafts? Several people (Enke Chen, Yakov Rekhter) felt that it imposed a deployment burden if the draft superceded these two document. Additional discussion of this point b) Should this work continue. Several people felt this work was useful. Additional feedback was given to the author. Additional discussion will continue on the list. c) 16:10-16:25 BGP Security Vulnerabilities Analysis (Sandy Murphy) http://www.ietf.org/internet-drafts/dr aft-murphy-bgp-vuln-02.txt Sandy present the slides idr.vulnerabilities.ppt After the presentation, a discussion about the drat continued with the following points: a) The use of unconfigured peers in the base draft. b) The use of TTL as an alternative security mechanisms for unconfigured peers, c) Do we include failure scenarios where a BGP Speaker doesn't send info it was supposed to send. eg not sending a WITHDRAW d) We need to make sure the draft is clear that there are two types of attacks: 1) Spoofs/session interrupts/disruptive attacks. 2) Poison info attacks (sending malicious info) On Unconfigured peers (point a), the discussion centered around re-opening the issue of unconfigured peers. The majority of the working group did not want to re-open the issue. The general consensus was that an explanation for unconfigured peers be added to the experience draft. On item b, the use of TTL as a security issue, Yakov pointed out that the TTL document is not even a working group document. We are progressing BGP (in 3 documents base, mib, security document) on what is. Sandy Murphy pointed out that TTL doesn't work with EBGP multi-hop. Vijay agreed with Sandy, but indicated that TTL works for most cases. Sandy pointed out that security analysis are required to look security in all cases. The TTL document is new work and will not be discussed until the Routing ADs lift the hold on new work. On item c, the consensus was to leave this out because it contains no informaiton. There is no way to differentiate between a bug in an implementation and an attack for these "attacks of omission". On item d, Sandy Murphy indicated that it was included in the draft. Comments are welcomed to clarify the text.