Connecting Mobile IPv6 Nodes Across IPv4 Clouds Back
To IPv6 Domains With Mobile IPv4
draft-liu-mobileip-mipv6tomipv4-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ching-Gung Liu | ||
| Last updated | 2002-05-22 | ||
| 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 document specifies a mechanism for Mobile IPv6 nodes of IPv6 Site to continue utilizing Mobile IPv6 services when they roam into IPv4 domains. The mechanism is based on Mobile IPv6 and Mobile IPv4 glued together by IPv4 encapsulation for delivering IPv6 packets between the Mobile IPv6 nodes and their Mobile IPv6 home agents. To support the mechanism specified in this draft, the Mobile IPv6 nodes MUST be Mobile IPv4 capable and MUST NOT utilize Mobile IPv6 route optimization when in IPv4 domain, and some of the border routers of the site MUST be capable to act as Mobile IPv4 home agent(s). The IPv6 site does not need to run 6to4 protocol, however.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)