RFC 3374: Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network
In plain English — editorial summary, not part of the RFC
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 routing-related services on subnets that are left behind when the host moves. Examples of such services are AAA, header compression, and 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.
Document record
- Document ID
- RFC3374
- Published
- September 2002
- Authors
- J. Kempf
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3086Definition of Differentiated Services Per Domain Behaviors and Rules for their SpecificationCurrent
April 2001
- RFC 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 2000
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 2000
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 2005
- RFC 2215General Characterization Parameters for Integrated Service Network ElementsCurrent
September 1997
- RFC 2212Specification of Guaranteed Quality of ServiceCurrent
September 1997
- RFC 5559Pre-Congestion Notification (PCN) ArchitectureCurrent
June 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?