Requirements for a Handover Information Service
draft-faccin-mih-infoserv-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Stefano Faccin | ||
| Last updated | 2006-03-08 | ||
| 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
Handover Information Services may be used to assist handovers between one network to another network or within a network, based on stored network knowledge. Information Services can be used to provide essential network related information e.g. topology and channel information which may allow a moving host to select an appropriate link-layer connection to make, amongst available networks, whether using the same technology or heterogeneous technologies. This document is an effort to describe use cases and transport requirements for handover information services, when they are transported over IP networks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)