Mobile IPv6 Bootstrapping in Split Scenario
RFC 5026, “Mobile IPv6 Bootstrapping in Split Scenario”, is a Proposed Standard document published in October 2007 by G. Giaretta, J. Kempf, V. Devarapalli. It has since been updated by RFC 8553. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5026 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5025 Presence Authorization Rules
- RFC 5027 Security Preconditions for Session Description Protocol Media Streams
- RFC 5024 ODETTE File Transfer Protocol 2.0
- RFC 5028 A Telephone Number Mapping Service Registration for Instant Messaging Services
- RFC 5023 The Atom Publishing Protocol
- RFC 5029 Definition of an IS-IS Link Attribute Sub-TLV
- RFC 5022 Media Server Control Markup Language and Protocol
- RFC 5030 Mobile IPv4 RADIUS Requirements