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

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 14
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.
Publication Date: 2002-09-01
Status Note: Informational
DOI: 10.17487/RFC3374
Link: https://doi.org/10.17487/RFC3374
Author(s): James Kempf
Keyword(s): AAA, QoS, Quality Of Service, Header Compression

Latest version of IETF RFC 3374

Document Versions — IETF RFC 3374

▶ IETF RFC 3374 (2002-09-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

IEEE.STD802.11F.2001 — 9 EXTERNAL
3GPP TR 25.936 V4.0.0, "Handovers for Real Time Services from PS Domain," 3GPP, March 2001. EXTERNAL
Aboba, B. and M. Moore, "A Model for Context Transfer in IEEE 802", Work in Progress. EXTERNAL
Perkins, C., and P. Calhoun, "AAA Registration Keys for Mobile IP", Work in Progress. EXTERNAL
Johnson, D. and C. Perkins, "Mobility Support in IPv6" , Work in Progress. EXTERNAL
IEEE Std. P802.1X/D11, "Standard for Port based Network Access Control", March 2001. EXTERNAL
IETF RFC 1661 [Active*]
IETF RFC 2284 [Superseded*]
IETF RFC 2401 [Superseded*]
IETF RFC 3095 [Active*]
IETF RFC 3220 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC3374.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 3374, Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network. Available at https://doi.org/10.17487/RFC3374

Snippet:

IETF RFC 3374, Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network. Available at https://doi.org/10.17487/RFC3374

HTML (ISO 690 compliant)

Preview:

IETF RFC 3374, Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network. Available at https://doi.org/10.17487/RFC3374

Snippet:

<span class="citation"><cite>IETF RFC 3374</cite>, Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network. Available at <a href="https://doi.org/10.17487/RFC3374" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3374</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 3374, Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network
doi: 10.17487/RFC3374
url: https://doi.org/10.17487/RFC3374

Snippet:

<li>
<cite id="bib-rfc3374">IETF RFC 3374</cite>, Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network
<span class="doi">10.17487/RFC3374</span>
</li>

Referenced By

IETF RFC 3481 [Active*]
IETF RFC 3753 [Active*]
IETF RFC 4067 [Active*]