Private IP Encapsulation within IP (PIPE)
draft-petri-mobileip-pipe-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Bernhard H. Petri | ||
| Last updated | 2000-01-20 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
RFC 2003 specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram. This is a means to alter the normal IP routing for datagrams, by delivering them to an intermediate destination that would otherwise not be selected by the (network part of the) IP Destination Address field in the original IP header. This draft allows to extend this encapsulation mechanism also for private IP addresses.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)