Time Efficient context Transfer (TEXT)
draft-nakhjiri-seamoby-text-ct-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Madjid Nakhjiri | ||
| Last updated | 2003-03-04 | ||
| 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 document presents a context transfer proposal that allows completion of context transfer outside timing critical message sequence for handover. The context transfer process is initiated at a moment of MN’s choice (in regard to layer 2 and 3 handover and MN’s traffic) and is completed without a disruption in the flow of MN’s real time traffic. This proposal is in line with the current fast handover framework within Mobile IP WG [3]. Although this document provides a specific recommendation, the framework proposed here, along with multiple alternatives that are mentioned, provides a great amount of flexibility in detailed design of context transfer. A minimum reliability mechanism for ensuring quality of transferred context is added to provide context updates that cannot be achieved by any transport protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)