Inter-Domain Routing (idr)
|Area||Routing Area (rtg)|
|More info||IDR Wiki|
|Jabber chat||Room address||xmpp://email@example.com|
Charter for 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
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.
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
- 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
- Specify Link Bandwidth Extended Community for use in unequal cost
- 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
- 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.
|Apr 2016||Progress base BGP specification (RFC 4271) as Full Standard|
Solicit work items for scalability improvements
Submit Yang BGP Modules to IESG as Proposed Standard
|Feb 2016||Submit ASpath ORF draft to IESG as a Proposed Standard|
|Jan 2016||Revise WG charter|
|Dec 2015||Submit Dynamic Capability for BGP-4 to IESG as a Proposed Standard|
|Nov 2015||Submit Multisession BGP to IESG as a Proposed Standard|
|Nov 2015||Submit MIB v2 for BGP-4 to IESG as a Proposed Standard|
|Jun 2015||Submit BGP Link Bandwidth Extended Community to IESG as a Proposed Standard|
Submit Advertisement of Multiple Paths in BGP to IESG as a Proposed Standard
|Mar 2015||Submit ASpath ORF to IESG as a Proposed Standard|
Submit Error Handling for Optional Transitive BGP Attributes to IESG as a Proposed Standard
|Done||Submit The Accumulated IGP Metric Attribute for BGP to IESG as a Proposed Standard|
|Done||Submit Revisions to the BGP 'Minimum Route Advertisement Interval' to IESG as a Proposed Standard|
|Done||Submit BGP Support for Four-octet AS Number Space (revised version) to IESG as a Proposed Standard|
|Done||Submit AS-wide Unique BGP Identifier for BGP-4 to IESG as a Proposed Standard|
|Done||Prefix and ASpath ORF draft to IESG as a Proposed Standard|
|Done||Submit Outbound Route Filter, Prefix and ASpath ORF draft to IESG as a Proposed Standard|
|Done||Submit 4-byte AS ID to IESG as a Proposed Standard|
|Done||Submit Subcodes for BGP Cease Notification Message to IESG as a Proposed Standard|
|Done||Submit revised text on Multi-Protocol BGP (rfc2858bis) 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 BGP4 document to IESG as a Draft Standard|
|Done||Submit BGP4 MIB to IESG as a Proposed Standard|
|Done||Submit BGP Security Vulnerabilities Analysis to IESG as an Informational|
|Done||Submit to BGP Capability Advertisement to the IESG|