Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network
RFC 3374, “Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network”, is an Informational document published in September 2002 by J. Kempf. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3374 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3373 Three-Way Handshake for Intermediate System to Intermediate System Point-to-Point Adjacencies
- RFC 3375 Generic Registry-Registrar Protocol Requirements
- RFC 3372 Session Initiation Protocol for Telephones : Context and Architectures
- RFC 3376 Internet Group Management Protocol, Version 3
- RFC 3371 Layer Two Tunneling Protocol "L2TP" Management Information Base
- RFC 3377 Lightweight Directory Access Protocol : Technical Specification
- RFC 3370 Cryptographic Message Syntax Algorithms
- RFC 3378 EtherIP: Tunneling Ethernet Frames in IP Datagrams