Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network

O. Henrik Levkowetz, Pat R. Calhoun, James Kempf, Gary Kenward, Hamid Syed, Jukka Manner, Madjid Nakhjiri, Govind Krishnamurthi, Rajeev Koodli, Kulwinder S. Atwal, Michael Thomas, Mat Horan, Phillip Neumiller

Research output: Working paperDiscussion paperScientific


In IP access networks that support host mobility, the routing paths between the host and the network may change frequently and rapidly. In some cases, the host may establish certain context transfer candidate services on subnets that are left behind when the host moves. Examples of such services are Authentication, Authorization, and Accounting (AAA), header compression, and Quality of Service (QoS). In order for the host to obtain those services on the new subnet, the host must explicitly re-establish the service by performing the necessary signaling flows from scratch. In some cases, this process would considerably slow the process of establishing the mobile host on the new subnet. An alternative is to transfer information on the existing state associated with these services, or context, to the new subnet, a process called "context transfer". This document discusses the desirability of context transfer for facilitating seamless IP mobility.
Original languageEnglish
PublisherInternet Society
Number of pages14
Publication statusPublished - 2002
MoE publication typeD4 Published development or research report or study

Publication series

NameRequest for Comments
ISSN (Electronic)2070-1721

Fingerprint Dive into the research topics of 'Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network'. Together they form a unique fingerprint.

Cite this