The EIPIP Protocol: a Pip engine with an EIP shell
draft-ietf-pip-eip-shell-00
| Document | Type |
Expired Internet-Draft
(pip WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Paul Francis , Dr. Zheng Wang | ||
| Last updated | 1992-11-03 | ||
| 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
In this memo, we present an internet protocol called 'EIPIP'. EIPIP is basically a protocol with a Pip engine and an EIP shell; it has the full capacity of Pip and all the desirable properties of EIP. We discuss the modifications required to the current Internet systems, the support for old IP hosts, deployment plan and implementation experience.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)