The Multi-Level Path Vector Routing Scheme
draft-ietf-pip-vector-00
| Document | Type |
Expired Internet-Draft
(pip WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Paul Francis , Dr. Bala Rajagopalan | ||
| Last updated | 1993-04-08 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | thumper.bellcore.com%3A~/pub/tsuchiya/pip-archive | ||
| 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 document describes protocols that are part of the Multi-Level Path Vector (MLPV) routing scheme being developed for use in PIP internets. MLPV is a hierarchical routing scheme. It allows an arbitrary number of levels in the topological hierarchy and arbitrary interconnections within and across levels. Conceptually, the execution of MLPV in a PIP router consists of running multiple, independent instances of a path vector routing algorithm, one for each level of the hierarchy that routes are being computed. This document describes the MLPV topological model and specifies the basic path vector routing schemes used at various levels of the hierarchy.
Authors
Paul Francis
Dr. Bala Rajagopalan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)