Inter-Domain Routing (idr) Internet Drafts

Outbound Route Filtering Capability for BGP-4

draft-ietf-idr-route-filter-17.txt

Date: 23/06/2008

Authors: Enke Chen, Yakov Rekhter

Working Group: Inter-Domain Routing (idr)

Formats: txt

This document defines a BGP-based mechanism that allows a BGP speaker to send to its BGP peer a set of Outbound Route Filters (ORFs) that the peer would use to constrain/filter its outbound routing updates to the speaker.

Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4),Second Version

draft-ietf-idr-bgp4-mibv2-07.txt

Date: 22/06/2008

Authors: Jeffrey Haas

Working Group: Inter-Domain Routing (idr)

Formats: xml txt

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular it defines objects for managing the Border Gateway Protocol, Version 4.

AS-wide Unique BGP Identifier for BGP-4

draft-ietf-idr-bgp-identifier-09.txt

Date: 13/05/2008

Authors: Enke Chen, Jenny Yuan

Working Group: Inter-Domain Routing (idr)

Formats: txt

To accommodate situations where the current requirements for the BGP Identifier are not met, this document relaxes the definition of the BGP Identifier to be a 4-octet unsigned, non-zero integer, and relaxes the "uniqueness" requirement so that only AS-wide uniqueness of the BGP Identifiers is required. These revisions to the base BGP specification do not introduce any backward compatibility issue.

Address Prefix Based Outbound Route Filter for BGP-4

draft-ietf-idr-bgp-prefix-orf-05.txt

Date: 23/06/2008

Authors: Enke Chen, Srihari Sangli

Working Group: Inter-Domain Routing (idr)

Formats: txt

This document defines a new Outbound Router Filter (ORF) type for BGP, termed "Address Prefix Outbound Route Filter", that can be used to perform address prefix based route filtering. This ORF-type supports prefix length or range based matching, wild-card based address prefix matching, as well as the exact address prefix matching for address families.

Dissemination of flow specification rules

draft-ietf-idr-flow-spec-01.txt

Date: 02/04/2008

Authors: Pedro Roque Marques, Nischal Sheth, Robert Raszuk, Barry Greene, Danny McPherson

Working Group: Inter-Domain Routing (idr)

Formats: txt

This document defines a new BGP NLRI encoding format that can be used to distribute traffic flow specifications. This allows the routing system to propagate information regarding more-specific components of the traffic aggregate defined by an IP destination prefix. Additionally it defines two applications of that encoding format. One that can be used to automate inter-domain coordination of traffic filtering, such as what is required in order to mitigate (distributed) denial of service attacks. And a second application to traffic filtering in the context of a BGP/MPLS VPN service. The information is carried via the Border Gateway Protocol (BGP), thereby reusing protocol algorithms, operational experience and administrative processes such as inter-provider peering agreements.

Capabilities Advertisement with BGP-4

draft-ietf-idr-rfc3392bis-00.txt

Date: 22/05/2008

Authors: John Scudder, Ravi Chandra

Working Group: Inter-Domain Routing (idr)

Formats: txt

This document defines an Optional Parameter, called Capabilities, that is expected to facilitate the introduction of new capabilities in the Border Gateway Protocol (BGP) by providing graceful capability advertisement without requiring that BGP peering be terminated. This document obsoletes RFC 3392.

Inter-Domain Routing (idr)

Last Modified: 2008-04-23

Additional information is available at tools.ietf.org/wg/idr

Chair(s):

Susan Hares <skh@nexthop.com>

Yakov Rekhter <yakov@juniper.net>

Routing Area Director(s):

Ross Callon <rcallon@juniper.net>

David Ward <dward@cisco.com>

Routing Area Advisor:

David Ward <dward@cisco.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
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:

Outbound Route Filtering Capability for BGP-4 (24338 bytes)
Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4), Second Version (158778 bytes)
AS-wide Unique BGP Identifier for BGP-4 (9197 bytes)
Address Prefix Based Outbound Route Filter for BGP-4 (11036 bytes)
Dissemination of flow specification rules (39100 bytes)
Capabilities Advertisement with BGP-4 (12932 bytes)

Request For Comments:

IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

Return to working group directory.

Return to IETF home page.