Intercepting Location Updates
draft-lmk-mobileip-intercepting-update-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | C.J. Lee , Glenn Morrow , Fayaz Kadri | ||
| Last updated | 2000-11-30 | ||
| 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 base Mobile IP allows a host to transparently send datagrams to mobile nodes as it would to any other nodes. Datagrams addressed to the mobile are always routed via the Home Agent in the home network. However, as the mobile node moves away from its home network, it may no longer be topologically close to its home agent. Route optimization [MIP-OPTIM] has been proposed to allow a host to send packets to the mobile as a mobile node (MN) moves, without having to route the packets via the home agent each time. The mobile provides its current address to a host (or correspondent node, CN) that it is communicating with as it moves. The host updates the cache of the mobile location with this new address and tunnels datagrams (addressed to the mobile) to the current address of the mobile. However not all correspondent nodes are capable of tunneling IP datagrams as required by the route optimization mechanisms described in [MIP-OPTIM]. More importantly, disclosing the current location (or COA) of the mobile node to correspondent nodes is not always desirable, nor is the overhead of encapsulating datagram to the MN ideal.
Authors
C.J. Lee
Glenn Morrow
Fayaz Kadri
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)