IP Address Encapsulation (IPAE): A Mechanism for Introducing a New IP
draft-crocker-ip-encaps-01

Document Type Expired Internet-Draft (individual)
Last updated 1992-11-11 (latest revision 2002-06-25)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-crocker-ip-encaps-01.txt

Abstract

The Internet seeks to increase the amount of IP address space that is available for hosts and to decrease the amount of table storage that is required by routers. Ultimately, the current IP (IP version 4) and any replacement are inherently incompatible and movement to the new version requires very substantial change to the IP installed base. This specification describes an approach which retains as much software, operations and training as possible, and minimizes overall operational disruption by allowing subsets of the Internet to carry the new-format Internet datagrams inside old-style IPv4 datagrams, using a technique called 'IP Address Encapsulation' (IPAE). This permits incremental and asynchronous introduction and makes transition entirely optional for portions of the Internet infrastructure. It further permits early reduction to routing table size.

Authors

Dave Crocker (dcrocker@brandenburg.com)
Bob Hinden (bob.hinden@nokia.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)