Some Thoughts on Multi-Domain Routing
draft-callon-routing-00
Document | Type |
Expired Internet-Draft
(rreq WG)
Expired & archived
|
|
---|---|---|---|
Author | Ross Callon | ||
Last updated | 1991-07-25 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | WG state | 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
Frequently a router may have multiple sources of information about paths through the network. For example, a router may be simultaneously learning routes from multiple routing domains, and may have static routes configured by the network manager. This paper resents a proposal for control of interactions between multiple routing protocols, including choice of routes when multiple IP routing protocols are being used simultaneously, as well as exchange of routes between routing protocols.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)