Inter-Domain Routing (idr) -------------------------- Charter Last Modified: 2008-04-23 Current Status: Active Working Group Chair(s): Susan Hares Yakov Rekhter Routing Area Director(s): Ross Callon David Ward Routing Area Advisor: David Ward Technical Advisor(s): Randall Atkinson Sharon Chisholm Mailing Lists: General Discussion:idr@ietf.org To Subscribe: idr-request@ietf.org In Body: subscribe idr-post Archive: http://www.ietf.org/mail-archive/web/idr/index.html Description of Working Group: 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 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. Goals and Milestones: Done Submit to BGP Capability Advertisement to the IESG Done Submit BGP Security Vulnerabilities Analysis to IESG as an Informational Done Submit BGP4 MIB to IESG as a Proposed Standard Done Submit BGP4 document to IESG as a Draft Standard Done Submit Extended Communities draft to IESG as a Proposed Standard Done Submit BGP Graceful Restart to IESG as a Proposed Standard Done Submit revised text on Multi-Protocol BGP (rfc2858bis) to IESG as a Draft Standard Done Submit Subcodes for BGP Cease Notification Message to IESG as a Proposed Standard Done Submit 4-byte AS ID to IESG as a Proposed Standard Done Submit Outbound Route Filter, Prefix and ASpath ORF draft to IESG as a Proposed Standard Mar 2008 Submit AS-wide Unique BGP Identifier for BGP-4 to IESG as a Proposed Standard Mar 2008 Prefix and ASpath ORF draft to IESG as a Proposed Standard Mar 2008 Prefix and ASpath ORF draft to IESG as a Proposed Standard Mar 2008 Submit Dynamic Capability for BGP-4 to IESG as a Proposed Standard Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Sep 2000 Sep 2006 Outbound Route Filtering Capability for BGP-4 Feb 2002 May 2008 AS-wide Unique BGP Identifier for BGP-4 Aug 2004 Jul 2006 Address Prefix Based Outbound Route Filter for BGP-4 Aug 2007 Apr 2008 Dissemination of flow specification rules Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC1105 E Jun 1989 Border Gateway Protocol BGP RFC1163 H Jun 1990 A Border Gateway Protocol (BGP) RFC1164 H Jun 1990 Application of the Border Gateway Protocol in the Internet RFC1267 H Oct 1991 A Border Gateway Protocol 3 (BGP-3) RFC1268 H Oct 1991 Application of the Border Gateway Protocol in the Internet RFC1269 PS Oct 1991 Definitions of Managed Objects for the Border Gateway Protocol (Version 3) RFC1265 I Oct 1991 BGP Protocol Analysis RFC1266 I Oct 1991 Experience with the BGP Protocol RFC1364 PS Sep 1992 BGP OSPF Interaction RFC1397 PS Jan 1993 Default Route Advertisement In BGP2 And BGP3 Versions Of The Border Gateway Protocol RFC1403 PS Jan 1993 BGP OSPF Interaction RFC1657 DS Jul 1994 Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 RFC1656 I Jul 1994 BGP-4 Protocol Document Roadmap and Implementation Experience RFC1654 PS Jul 1994 A Border Gateway Protocol 4 (BGP-4) RFC1655 PS Jul 1994 Application of the Border Gateway Protocol in the Internet RFC1745 PS Dec 1994 BGP4/IDRP for IP---OSPF Interaction RFC1773 I Mar 1995 Experience with the BGP-4 protocol RFC1774 I Mar 1995 BGP-4 Protocol Analysis RFC1771 DS Mar 1995 A Border Gateway Protocol 4 (BGP-4) RFC1863 E Oct 1995 A BGP/IDRP Route Server alternative to a full mesh routing RFC1930BCP Apr 1996 Guidelines for creation, selection, and registration of an Autonomous System (AS) RFC1966 E Jun 1996 BGP Route Reflection An alternative to full mesh IBGP RFC1965 E Jun 1996 Autonomous System Confederations for BGP RFC1997 PS Aug 1996 BGP Communities Attribute RFC1998 I Aug 1996 An Application of the BGP Community Attribute in Multi-home Routing RFC2270 I Jan 1998 Using a Dedicated AS for Sites Homed to a Single Provider RFC2283 PS Feb 1998 Multiprotocol Extensions for BGP-4 RFC2385 PS Aug 1998 Protection of BGP Sessions via the TCP MD5 Signature Option RFC2439 PS Nov 1998 BGP Route Flap Damping RFC2519 I Feb 1999 A Framework for Inter-Domain Route Aggregation RFC2545 PS Mar 1999 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing RFC2796 PS Apr 2000 BGP Route Reflection An alternative to full mesh IBGP RFC2842Standard Jun 2000 Capabilities Advertisement with BGP-4 RFC2858 PS Jun 2000 Multiprotocol Extensions for BGP-4 RFC2918 PS Sep 2000 Route Refresh Capability for BGP-4 RFC3065 PS Feb 2001 Autonomous System Confederations for BGP RFC3345 I Aug 2002 Border Gateway Protocol (BGP) Persistent Route Oscillation Condition RFC3392 DS Nov 2002 Capabilities Advertisement with BGP-4 RFC3562 I Jul 2003 Security Requirements for Keys used with the TCP MD5 Signature Option RFC4223 I Oct 2005 Reclassification of RFC 1863 to Historic RFC4271Standard Jan 2006 A Border Gateway Protocol 4 (BGP-4) RFC4277 I Jan 2006 Experience with the BGP-4 Protocol RFC4276 I Jan 2006 BGP 4 Implementation Report RFC4275 I Jan 2006 BGP-4 MIB Implementation Survey RFC4274 I Jan 2006 BGP-4 Protocol Analysis RFC4273Standard Jan 2006 Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4) RFC4272 I Jan 2006 BGP Security Vulnerabilities Analysis RFC4360Standard Feb 2006 BGP Extended Communities Attribute RFC4456 DS Apr 2006 BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) RFC4486 PS Apr 2006 Subcodes for BGP Cease Notification Message RFC4724 PS Jan 2007 Graceful Restart Mechanism for BGP RFC4760 DS Jan 2007 Multiprotocol Extensions for BGP-4 RFC4798 PS Feb 2007 Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge Routers (6PE) RFC4893 PS May 2007 BGP Support for Four-octet AS Number Space RFC5065 DS Aug 2007 Autonomous System Confederations for BGP RFC5004 PS Sep 2007 Avoid BGP Best Path Transitions from One External to Another