Extension to RFC 3775 for Alerting the Mobile Node to Home Agent Unavailability
draft-kempf-mip6-ha-alert-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | James Kempf | ||
| Last updated | 2005-02-09 | ||
| 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
RFC 3775 contains no way for a home agent to notify a mobile node that the home agent will shortly become unavailable, and suggest possible substitutes. A mobile node can suddenly find itself without mobility service. This document describes a simple protocol to inform the mobile node when its home agent is about to become unavailable and whether the mobile node should re-run bootstrapping to find a new home agent.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)