Mobile IPv6 Neighborhood Routing for Fast Handoff
draft-yegin-mobileip-nrouting-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alper E. Yegin , Mohan Parthasarathy | ||
| Last updated | 2000-11-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
The Mobile IP working group is currently examining proposals to assist in minimizing the latency and packet loss due to handoffs when a Mobile IPv6 node moves from one point of attachment to another. One of the desires to reduce this latency and packet loss is a result of the strict requirements of real-time network services. This proposal specifies a solution whereby the mobile node sends a binding update with multiple care-of-addresses which match the current link and other links that the mobile node may possibly visit next. After receiving such a binding update, the correspondent nodes and home agent use a new routing header extension to route the packet that will be received by the mobile node at one of the possible care-of-addresses. Thus, the correspondent nodes and home agent can still communicate with the mobile node despite not knowing its exact location while the mobile node moves across links. The proposal presents no new networking entities and the resulting architecture describes a natural extension to the Mobile IPv6 protocol.
Authors
Alper E. Yegin
Mohan Parthasarathy
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)