Configuring IDRP Confederations
draft-ietf-idr-rdc-config-01
| Document | Type |
Expired Internet-Draft
(idr WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Ramesh Govindan | ||
| Last updated | 2024-08-23 (Latest revision 1996-10-28) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In the Inter-Domain Routing Protocol (IDRP), all border routers (border intermediate systems (BISs) in ISO terminology) of a routing domain confederation (RDC) must be configured with the identity of all RDCs that overlap or enclose that RDC. This draft describes some minor modifications to IDRP specification that removes this requirement.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)