Pip Overview and Examples
draft-tsuchiya-pip-overview-01
| Document | Type |
Expired Internet-Draft
(pip WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Paul Francis | ||
| Last updated | 1992-06-28 (Latest revision 2002-06-25) | ||
| 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
Pip is an internet protocol that scales efficiently encodes policy. It facilitates many advanced features, such as mobility and multiple defaults routing, and has a well-bounded routing table lookup, and is therefore fast. Pip is proposed as an alternative to the two 'medium term' proposals that emerged from the Road (Routing and Addressing) group to deal with the dual IP problems of scaling and address depletion.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)