Route Optimization hint option
draft-shima-mip6-rohints-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Keiichi Shima | ||
| Last updated | 2003-10-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
This memo describes the distribution mechanism of route optimization hints, which can be used by a mobile node to determine when the node should initiate the route optimization procedure when communicating with correspondent nodes. Usually, a mobile node will perform RO procedure to any correspondent node as described in Mobile IPv6 specification [1]. However, in some cases, it is better not to perform RO. A typical example is a firewalled network. This memo also describes a configuration of a firewall which makes mobile nodes possible to move between an intranet and the Internet by using RO hints.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)