General Requirements for a Context Transfer
draft-ietf-seamoby-ct-reqs-05

Document Type Expired Internet-Draft (seamoby WG)
Last updated 2015-10-14 (latest revision 2002-10-07)
Stream IETF
Intended RFC status Informational
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Allison Mankin
IESG note The WG decided to withdraw the document at IETF 57.
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-seamoby-ct-reqs-05.txt

Abstract

The success of time sensitive services like VoIP telephony, video, etc., in a mobile environment depends heavily on the ability to minimize the impact of the traffic redirection during a change of packet forwarding path. In the process of establishing the new forwarding path, the nodes along the new path must be prepared to provide similar forwarding treatment to the IP packets. The transfer of context information may be advantageous in minimizing the impact of host mobility on IP services. This document captures the set of requirements for a context transfer framework and the requirements for a generic context transfer protocol to carry the context between the context transfer peers.

Authors

Gary Kenward (gkenward@nortelnetworks.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)