Ruminations on Route Leaking
draft-almquist-leak-01
| Document | Type |
Expired Internet-Draft
(rreq WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Philip Almquist | ||
| 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
This memo discusses how routers can 'leak' routing information learned from one routing domain into another routing domain. Although this memo is not an official product of the Router Requirements working group, it is being published as an Internet Draft because it is required reading for those who wish to actively participate in the Router Requirements sessions during the IETF meeting in Atlanta.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)