Configuring IDRP Confederations
draft-ietf-idr-rdc-config-01
| Document | Type | Expired Internet-Draft (idr WG) | |
|---|---|---|---|
| Last updated | 1996-10-28 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-idr-rdc-config-01.txt
https://www.ietf.org/archive/id/draft-ietf-idr-rdc-config-01.txt
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
Ramesh Govindan (govindan@isi.edu)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)