Extensions for Selective Updates in Inter Domain Routing
draft-ietf-idr-rifs-00
| Document | Type |
Expired Internet-Draft
(idr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kannan Varadhan , Curtis Villamizar , Yakov Rekhter | ||
| Last updated | 2024-08-23 (Latest revision 1995-02-16) | ||
| 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
Under certain circumstances[4, 5] it is desirable for an entity that participates in inter-domain routing (either via BGP or IDRP) to specify the routing information it wishes to receive from its peer. This document proposes a mechanism that provides this functionality. Unless stated otherwise, for the rest of the document we do not distinguish between a BGP and an IDRP speaker.
Authors
Kannan Varadhan
Curtis Villamizar
Yakov Rekhter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)