Inter-Domain Routing (idr) -------------------------- Charter Last Modified: 2011-12-09 Current Status: Active Working Group Chair(s): Susan Hares John Scudder Routing Area Director(s): Stewart Bryant Adrian Farrel Routing Area Advisor: Stewart Bryant 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, develop, and support the Border Gateway Protocol Version 4 (BGP-4) [RFC 4271] capable of supporting policy based routing for TCP/IP internets. The main objective of the working group is to support the use of BGP-4 by IP version 4 and IP version 6 networks. The working group will also continue to work on improving the robustness and scalability of BGP. IDR will review extensions made to BGP in other working groups at least at WG document adoption and during working group last calls. The IDR working group will also provide advice and guidance on BGP to other working groups as requested. Work Items: The IDR working group will work on correctness, robustness and scalability of the BGP protocol, as well as clarity and accuracy of the BGP document set. The group will also work on extensions beyond these areas when specifically added to the charter. The current additional work items are: - Relax the definition of BGP identifiers to only require AS-wide uniqueness. This change must be made in a backward compatible way. - Specify a means to non-disruptively introduce new BGP Capabilities to an existing BGP session. - Upgrade of the base BGP specification to Full Standard - Define AS_PATH based Outbound Route Filtering. - MIB v2 for BGP-4 - Augment the BGP multiprotocol extensions to support the use of multiple concurrent sessions between a given pair of BGP speakers. Each session is used to transport routes related by some session- based attribute such as AFI/SAFI. This will provide an alternative to the MP-BGP approach of multiplexing all routes onto a single connection. - Support for four-octet AS Numbers in BGP. - Revisions to the BGP 'Minimum Route Advertisement Interval' deprecating the previously recommended values and allowing for withdrawals to be exempted from the MRAI. - Advertisement of multiple paths for the same address prefix without the new paths implicitly replacing any previous ones. Each path is identified by a path identifier in addition to the address prefix. - Revised error handling rules for optional transitive BGP attributes so that a BGP speaker is no longer required to reset the session over which a malformed attribute is received. Provide guidelines for authors of documents that define new optional transitive attributes, and re-assess procedures for existing optional transitive attributes - Specify Link Bandwidth Extended Community for use in unequal cost load balancing. - The definition of an "Accumulated IGP Metric" attribute for BGP to report the sum of the metric of each link along the path. This attribute is for use in a restricted environment where: - all ASes are subject to the administrative control - some form of tunneling is used to deliver a packet to its next BGP hop - where the path for a route leads outside the AS to which the BGP speaker adding the attribute belongs. - Advertisement of the best external route in BGP to assist with resolution of the next hop in the chosen data plane. 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 Done Prefix and ASpath ORF draft to IESG as a Proposed Standard Mar 2010 Solicit work items for scalability improvements Aug 2010 Submit AS-wide Unique BGP Identifier for BGP-4 to IESG as a Proposed Standard Aug 2010 Submit Dynamic Capability for BGP-4 to IESG as a Proposed Standard Aug 2010 Submit ASpath ORF draft to IESG as a Proposed Standard Aug 2010 Submit MIB v2 for BGP-4 to IESG as a Proposed Standard Nov 2010 Submit BGP Support for Four-octet AS Number Space (revised version) to IESG as a Proposed Standard Nov 2010 Submit Revisions to the BGP 'Minimum Route Advertisement Interval' to IESG as a Proposed Standard Nov 2010 Submit Advertisement of Multiple Paths in BGP to IESG as a Proposed Standard Nov 2010 Submit BGP Link Bandwidth Extended Community to IESG as a Proposed Standard Nov 2010 Submit Advertisement of the best external route in BGP to IESG as a Proposed Standard Dec 2010 Submit Multisession BGP to IESG as a Proposed Standard Dec 2010 Submit Error Handling for Optional Transitive BGP Attributes to IESG as a Proposed Standard Dec 2010 Submit ASpath ORF to IESG as a Proposed Standard Dec 2010 Revise WG charter Mar 2011 Submit The Accumulated IGP Metric Attribute for BGP to IESG as a Proposed Standard Mar 2011 Progress base BGP specification (RFC 4271) as Full Standard Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Aug 2001 Dec 2011 Dynamic Capability for BGP-4 Dec 2008 Sep 2011 Revisions to the BGP 'Minimum Route Advertisement Interval' Dec 2008 Sep 2011 Advertisement of Multiple Paths in BGP Apr 2009 Oct 2011 BGP Link Bandwidth Extended Community May 2009 Dec 2011 The Accumulated IGP Metric Attribute for BGP May 2009 Jan 2012 Advertisement of the best external route in BGP Aug 2009 Aug 2011 BGP Bestpath Selection Criteria Enhancement Oct 2010 Feb 2012 Subcodes for BGP Finite State Machine Error Dec 2010 Nov 2011 Best Practices for Advertisement of Multiple Paths in IBGP Feb 2011 Dec 2011 Assigned BGP extended communities Jun 2011 Sep 2011 BGP Optimal Route Reflection (BGP-ORR) Jun 2011 Oct 2011 Dissemination of Flow Specification Rules for IPv6 Jun 2011 Dec 2011 Enhanced Route Refresh Capability for BGP-4 Jun 2011 Jan 2012 Extended Message support for BGP Jul 2011 Oct 2011 IPv6 Extensions for Route Target Distribution Nov 2011 Dec 2011 Revised Error Handling for BGP UPDATE Messages Nov 2011 Nov 2011 BGP Custom Decision Process Nov 2011 Jan 2012 Codification of AS 0 processing. Jan 2012 Dec 2011 Notification Message support for BGP Graceful Restart Jan 2012 Dec 2011 Accelerated Routing Convergence for BGP Graceful Restart Jan 2012 Jan 2012 Automatic Route Target Filtering for legacy PEs Jan 2012 Jan 2012 Carrying next-hop cost information in BGP Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC1105 E Jun 1989 Border Gateway Protocol BGP RFC1164 H Jun 1990 Application of the Border Gateway Protocol in the Internet RFC1163 H Jun 1990 A Border Gateway Protocol (BGP) 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 RFC1656 I Jul 1994 BGP-4 Protocol Document Roadmap and Implementation Experience RFC1657 DS Jul 1994 Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 RFC1655 PS Jul 1994 Application of the Border Gateway Protocol in the Internet RFC1654 PS Jul 1994 A Border Gateway Protocol 4 (BGP-4) 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 RFC4486 PS Apr 2006 Subcodes for BGP Cease Notification Message RFC4456 DS Apr 2006 BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) 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 RFC5292 PS Aug 2008 Address-Prefix-Based Outbound Route Filter for BGP-4 RFC5291Standard Aug 2008 Outbound Route Filtering Capability for BGP-4 RFC5396 PS Dec 2008 Textual Representation of Autonomous System (AS) Numbers RFC5398 I Dec 2008 Autonomous System (AS) Number Reservation for Documentation Use RFC5492 DS Feb 2009 Capabilities Advertisement with BGP-4 RFC5575 PS Aug 2009 Dissemination of Flow Specification Rules RFC6286 PS Jun 2011 Autonomous-System-Wide Unique BGP Identifier for BGP-4 RFC6472BCP Dec 2011 Recommendation for Not Using AS_SET and AS_CONFED_SET in BGP