Virtual Internet Protocol version 2 (VIPv2)
draft-teraoka-mobileip-vip-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Fumio Teraoka | ||
| Last updated | 1995-12-12 | ||
| 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
This memo describes Virtual Internet Protocol version 2 (VIPv2), a protocol for mobility support in IPv4. The basic concept of VIP is separation of identifiers and addresses. TCP/UDP uses the identifier. The identifier is mapped to an address, and then the packet is routed in accordance with the address. End nodes as well as intermediate routers can have authentic mapping information for routing optimization and fault tolerance.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)