Fast Handoffs in Mobile IPv4
draft-elmalki-mobileip-fast-handoffs-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Karim El Malki , Srba Cvetkovic | ||
| Last updated | 2000-09-27 | ||
| 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 draft describes a method to achieve Fast Handoffs in Mobile IPv4. Fast Handoffs are required in Mobile IPv4 in order to limit the period of service disruption experienced by a wireless Mobile Node when moving between Foreign Agents. This requirement becomes even more important when supporting real-time services. Fast Handoffs involve anticipating the movement of MNs by sending multiple copies of the traffic to potential Mobile Node movement locations (i.e. FAs). Both a flat and a Hierarchical Mobile IPv4 model are considered. The Hierarchical MIPv4 model in Regional Tunnel Management [1] already offers improvements to Mobile IP handoffs by providing local Home Agent functionality. Some additions are made to the operation of this existing Hierarchical model to achieve Fast Handoffs and limit or avoid triangle routing within the hierarchical domain.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)