Behavior of A Mobility Agent in Mobile IP in order to manage the flow
draft-ishi-mobileip-behavior-ma-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Koichi Ishibashi , Koji Shimizu , Shoichiro Seno | ||
| Last updated | 2001-10-02 | ||
| 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
Mobile IP [1] protocol allows a mobile node (MN) to move between different networks seamlessly. However, in certain cases, the latency involved in the handoff can be beyond the threshold required for the support of delay-sensitive or real-time services. In order to address the above problem, there have been many proposals related to extensions of Mobile IP handoffs in order to achieve efficient handoff procedures.
Authors
Koichi Ishibashi
Koji Shimizu
Shoichiro Seno
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)