Last Modifield: 05/30/2002
Ran Atkinson, the other Technical Advisors, has the task to advise on technical matters related to security work in this WG.
The Inter-Domain Routing Working Group is chartered to standardize and promote the Border Gateway Protocol Version 4 (BGP-4) [RFC 1771] capable of supporting policy based routing for TCP/IP internets. The objective is to promote the use of BGP-4 to support IP version 4 and IP version 6. The working group will continue to work on improving the scalability of BGP.
The current tasks of the WG include:
- 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.
- Advance RFC 2842, BGP Capability Advertisement, to Draft Standard.
- Review and Evaluate Existing RFCs on AS Confederations and Route Reflection. If changes are needed, create and advance revisions.
- Review RFC 2385 (Protection of BGP via TCP MD5 signature) to see if any changes need to be made based on current Internet practice or based on the changes to the current bgp draft. If changes are needed, create an revision. Issue the WG Last Call on advancing the document to Draft Standard.
- The existing BGP MIBs (RFC 1657) are not current with regards to BGP4. Produce a revised MIB that matches revised BGP4 document and move RFC 1657 to Historic.
- Produce MIBS for AS Confederations, Route Reflection, and Communities.
- Review and evaluate Multiprotocol BGP (RFC 2858) for advancement as Draft Standard, develop MIBs that support it.
- Complete work on an Extended Community Attribute. Develop MIB for BGP Extended Communities.
- Extend BGP to support a 4-byte AS number, develop plan for transitioning to usage of 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.
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.
| OCT 01 | Initial ID for MPBGP MIB | |
| NOV 01 | Submit to BGP Capability Advertisement to the IESG | |
| NOV 01 | Submit 4 BGP MIBs to IESG. | |
| DEC 01 | Submit Extended Communities draft to IESG. | |
| DEC 01 | Submit 4-byte AS ID to IESG. | |
| JAN 02 | Submit BGP4 document to IESG. | |
| JAN 02 | Initial Draft for RFC2858 (if needed) | |
| FEB 02 | BGP TCP MD5 signatures document to IESG. | |
| FEB 02 | Outbound Route Filter, Prefix and ASpath ORF draft to IESG. |
| RFC | Status | Title |
|---|---|---|
| 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) |
| RFC1265 | I | BGP Protocol Analysis |
| RFC1266 | I | Experience with the BGP Protocol |
| 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 |
| RFC1655 | PS | Application of the Border Gateway Protocol in the Internet |
| RFC1654 | PS | A Border Gateway Protocol 4 (BGP-4) |
| RFC1657 | DS | Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 |
| RFC1745 | PS | BGP4/IDRP for IP---OSPF Interaction |
| RFC1773 | I | Experience with the BGP-4 protocol |
| RFC1774 | I | BGP-4 Protocol Analysis |
| RFC1771 | DS | A Border Gateway Protocol 4 (BGP-4) |
| 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 |