Route management of mobile entity with an ipv6 home address roaming into the ipv4 network
draft-wan-mip6-nemo-routing-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Changsheng Wan | ||
| Last updated | 2006-06-14 | ||
| 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
The current Mobile IPv6 and NEMO specification supports only IPv6. As an extension, the DSMip6 protocol [v4traversal]defines how the dual-stack mobile node roams in the ipv4 network. The dsmip6 protocol assumes that both home agent and mobile node supports mipv4 and mipv6 protocol. It also assumes that both the home agent and mobile node have a configured ipv4 address. These assumptions do work during many scenarios. However, as the ipv4 address is a scarce resource in many counrties, some mobile nodes may not be able to get configured ipv4 home addresses from their home agents. In this scenario, a temporary ipv4 home address is more useful. This document will focuse on this scenario.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)