Releasing Resources in Mobile IP
draft-subbarao-mobileip-resource-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rajesh Bhalla | ||
| Last updated | 2001-02-26 | ||
| 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
Currently, in Mobile IP when an MN moves from one FA to another FA/CoA, relevant resources at the previous FA are consumed until its visitor entry for the MN expires. The Resource Release Message and Resource Management Extension described in this draft will facilitate the release of these valuable resources at the previous FA as the MN moves to a new location. The HA notifies the previous FA of any changes in the CoA for an MN, thereby allowing the FA to release its resources.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)