RFC 5026: Mobile IPv6 Bootstrapping in Split Scenario
In plain English — editorial summary, not part of the RFC
A Mobile IPv6 node requires a Home Agent address, a home address, and IPsec security associations with its Home Agent before it can start utilizing Mobile IPv6 service. RFC 3775 requires that some or all of these are statically configured. This document defines how a Mobile IPv6 node can bootstrap this information from non-topological information and security credentials pre-configured on the Mobile Node. The solution defined in this document solves the split scenario described in the Mobile IPv6 bootstrapping problem statement in RFC 4640. The split scenario refers to the case where the Mobile Node's mobility service is authorized by a different service provider than basic network access. The solution described in this document is also generically applicable to any bootstrapping case, since other scenarios are more specific realizations of the split scenario. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5026
- Published
- October 2007
- Authors
- G. Giaretta; J. Kempf; V. Devarapalli
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 28
- Also known as
- —
- Updated by:
- RFC 8553
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5094Mobile IPv6 Vendor Specific OptionCurrent
December 2007
- RFC 5096Mobile IPv6 Experimental MessagesCurrent
December 2007
- RFC 4877Mobile IPv6 Operation with IKEv2 and the Revised IPsec ArchitectureCurrent
April 2007
- RFC 4285Authentication Protocol for Mobile IPv6Current
January 2006
- RFC 5846Binding Revocation for IPv6 MobilityCurrent
June 2010
- RFC 5030Mobile IPv4 RADIUS RequirementsCurrent
October 2007
- RFC 5011Automated Updates of DNS Security (DNSSEC) Trust AnchorsCurrent
September 2007
- RFC 5010The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags SuboptionCurrent
September 2007
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?