2.5.5 Inter-Domain Routing (idr)

NOTE: This charter is a snapshot of the 49th IETF Meeting in San Diego, California. It may now be out-of-date. Last Modified: 11-Oct-00

Chair(s):

Susan Hares <skh@merit.edu>
Y Rekhter <yakov@cisco.com>

Routing Area Director(s):

David Oran <oran@cisco.com>
Rob Coltun <rcoltun@redback.com>

Routing Area Advisor:

Rob Coltun <rcoltun@redback.com>

Mailing Lists:

General Discussion:idr@merit.edu
To Subscribe: idr-request@merit.edu
Archive: ftp://ftp.merit.edu/mail.archives/idr

Description of Working Group:

The main list for this working group is bgp@ans.net, but there is also an IDRP-specific mailing list:

- List: idrp@merit.edu

- To Subscribe: idrp-request@merit.edu

- Archive: merit.edu:/pub/archive/idrp

The Inter-Domain Routing Working Group is chartered to standardize and promote the Border Gateway Protocol Version 4 (BGP-4) and ISO Inter-Domain Routing Protocol (IDRP) as scalable inter-autonomous system routing protocols 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 (IPv4). IDRP is seen as a protocol that will support IPv4 as well as the next generation of IP (IPv6).

The working group will plan a smooth transition between BGP-4 and IDRP.

Documents:

1) BGP-4 (standards track)

This document contains the specification of the BGP protocol that enables it to be used as a protocol for exchange of ``inter-autonomous system information'' among routers to support forwarding of IPv4 packets across multiple autonomous systems.

2) BGP-4 MIB (standards track)

This document contains the MIB definitions for BGP-4.

3) IDRP for IPv4/IPv6 (standards track)

This document contains the appropriate adaptations of the IDRP protocol definition that enables it to be used as a protocol for exchange of ``inter-autonomous system information'' among routers to support forwarding of IPv4 or IPv6 packets across multiple autonomous systems.

4) IDRP MIB (standards track)

This document contains the MIB definitions for IDRP.

5) BGP/IDRP -- OSPF Interactions (standards track)

This document will specify the interactions between BGP/IDRP and OSPF. This document will be based on a combination of the BGP - OSPF interactions, and IDRP - IS-IS interaction documents.

6) BGP/IDRP Usage (standards track)

Most of BGP/IDRP Usage document will reference the CIDR (supernetting) RFCs and related Internet-Drafts. IDRP Usage will contain a sample policy configuration language and examples on how to use IDRP in the Internet today.

7) BGP-4 to IDRP v6 Transition (standards track)

This document will provide information on how to transition between BGP-4 and IDRP v6 networks.

Goals and Milestones:

Jun 96

  

Update IDRP for IPv4/IPv6 Internet-Draft.

Jun 96

  

Submit IDRP for IPV4/IPv6 Internet-Draft to IESG for consideration as a Proposed Standard.

Apr 97

  

Update IDRP for IPv4/IPv6 MIB Internet-Draft.

Apr 97

  

Submit BGP-4 MIB to IESG for consideration as a Draft Standard.

Apr 97

  

Submit Internet-Draft on BGP-4 to IDRPv6 transition.

Jun 97

  

Submit IDRP for IPv4/IPv6 MIB Internet-Draft to IESG for consideration as a Proposed Standard.

Internet-Drafts:

Request For Comments:

RFC

Status

Title

RFC1267

H

A Border Gateway Protocol 3 (BGP-3)

RFC1269

PS

Definitions of Managed Objects for the Border Gateway Protocol (Version 3)

RFC1266

 

Experience with the BGP Protocol

RFC1265

 

BGP Protocol Analysis

RFC1397

PS

Default Route Advertisement In BGP2 And BGP3 Versions Of The Border Gateway Protocol

RFC1403

PS

BGP OSPF Interaction

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

RFC1774

 

BGP-4 Protocol Analysis

RFC1773

 

Experience with the BGP-4 protocol

RFC1771

DS

A Border Gateway Protocol 4 (BGP-4)

RFC1863

E

A BGP/IDRP Route Server alternative to a full mesh routing

RFC1930

 

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

RFC1998

 

An Application of the BGP Community Attribute in Multi-home Routing

RFC1997

PS

BGP Communities Attribute

RFC2270

 

Using a Dedicated AS for Sites Homed to a Single Provider

RFC2385

PS

Protection of BGP Sessions via the TCP MD5 Signature Option

RFC2439

PS

BGP Route Flap Damping

RFC2519

 

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

S

Capabilities Advertisement with BGP-4

RFC2858

PS

Multiprotocol Extensions for BGP-4

RFC2918

PS

Route Refresh Capability for BGP-4

Current Meeting Report

None received.

Slides

None received.