2.6.3 Inter-Domain Routing (idr)

NOTE: This charter is a snapshot of the 65th IETF Meeting in Dallas, TX USA. It may now be out-of-date.

Last Modified: 2006-01-25

Chair(s):

Susan Hares <skh@nexthop.com>
Yakov Rekhter <yakov@juniper.net>

Routing Area Director(s):

Bill Fenner <fenner@research.att.com>
Alex Zinin <zinin@psg.com>

Routing Area Advisor:

Bill Fenner <fenner@research.att.com>

Technical Advisor(s):

Randall Atkinson <rja@extremenetworks.com>
Sharon Chisholm <schishol@nortel.com>

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
Oct 2006  Submit BGP MIB v2 to IESG as a Proposed Standard
Oct 2006  Submit Outbound Route Filter, Prefix and ASpath ORF draft to IESG as a Proposed Standard
Oct 2006  Submit AS-wide Unique BGP Identifier for BGP-4 to IESG as a Proposed Standard
Oct 2006  Submit Dynamic Capability for BGP-4 to IESG as a Proposed Standard
Done  Submit 4-byte AS ID to IESG as a Proposed Standard

Internet-Drafts:

  • draft-ietf-idr-route-filter-13.txt
  • draft-ietf-idr-restart-10.txt
  • draft-ietf-idr-as4bytes-12.txt
  • draft-ietf-idr-aspath-orf-08.txt
  • draft-ietf-idr-dynamic-cap-08.txt
  • draft-ietf-idr-cease-subcode-07.txt
  • draft-ietf-idr-rfc2858bis-09.txt
  • draft-ietf-idr-bgp-identifier-06.txt
  • draft-ietf-idr-rfc3065bis-05.txt
  • draft-ietf-idr-rfc2796bis-02.txt
  • draft-ietf-idr-bgp-multisession-02.txt
  • draft-ietf-idr-avoid-transition-04.txt
  • draft-ietf-idr-bgp-prefix-orf-02.txt
  • draft-ietf-idr-as-hopcount-00.txt
  • draft-ietf-idr-as-pathlimit-01.txt

    Request For Comments:

    RFCStatusTitle
    RFC1105 E Border Gateway Protocol BGP
    RFC1163 H A Border Gateway Protocol (BGP)
    RFC1164 H Application of the Border Gateway Protocol in the Internet
    RFC1265 I BGP Protocol Analysis
    RFC1266 I Experience with the BGP Protocol
    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)
    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
    RFC1654 PS A Border Gateway Protocol 4 (BGP-4)
    RFC1655 PS Application of the Border Gateway Protocol in the Internet
    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
    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
    RFC1997 PS BGP Communities Attribute
    RFC1998 I An Application of the BGP Community Attribute in Multi-home Routing
    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
    RFC3562 I Security Requirements for Keys used with the TCP MD5 Signature Option
    RFC4223 I Reclassification of RFC 1863 to Historic
    RFC4271 Standard A Border Gateway Protocol 4 (BGP-4)
    RFC4272 I BGP Security Vulnerabilities Analysis
    RFC4273 Standard Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4)
    RFC4274 I BGP-4 Protocol Analysis
    RFC4275 I BGP-4 MIB Implementation Survey
    RFC4276 I BGP 4 Implementation Report
    RFC4277 I Experience with the BGP-4 Protocol
    RFC4360 Standard BGP Extended Communities Attribute

    Meeting Minutes


    Slides

    6PE implementation report
    Advertising ECMP Routes in BGP
    Advertising Multiple NextHop Routes in BGP
    Entire Routes Reflecting capability
    IDR WG Document Status Update