Mobile IPv6 Bootstrapping in Split Scenario

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 28
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]
Publication Date: 2007-10-01
Status Note: Proposed Standard
DOI: 10.17487/RFC5026
Link: https://doi.org/10.17487/RFC5026
Author(s): Gerardo Giaretta
James Kempf
Vijay Devarapalli
Keyword(s): MIPv6, Bootstrapping

Latest version of IETF RFC 5026

Document Versions — IETF RFC 5026

▶ IETF RFC 5026 (2007-10-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Amended by:

IETF RFC 8553 [Active*]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 2136 [Active*]
IETF RFC 2782 [Active*]
IETF RFC 3775 [Superseded*]
IETF RFC 4306 [Superseded*]
IETF RFC 4877 [Active*]

Bibliographic Reference(s)

Giaretta, G., "AAA Goals for Mobile IPv6" , Work in Progress, September 2006. EXTERNAL
Chowdhury, K., "RADIUS Mobile IPv6 Support" , Work in Progress, March 2007. EXTERNAL
Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the Integrated Scenario", Work in Progress, June 2007. EXTERNAL
Jang, H., "DHCP Option for Home Information Discovery in MIPv6", Work in Progress, June 2007. EXTERNAL
Bournelle, J., "Diameter Mobile IPv6: HA <-> HAAA Support" , Work in Progress, May 2007. EXTERNAL
IETF RFC 2845 [Superseded*]
IETF RFC 2930 [Active*]
IETF RFC 3280 [Superseded*]
RFC3646 — 3 EXTERNAL
IETF RFC 3753 [Active*]
IETF RFC 3972 [Active*]
IETF RFC 4033 [Active*]
IETF RFC 4210 [Superseded*]
RFC4640 — 7 EXTERNAL
IETF RFC 4861 [Active*]
IETF RFC 4941 [Superseded*]
IETF RFC 4945 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5026.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 5026, Mobile IPv6 Bootstrapping in Split Scenario. Available at https://doi.org/10.17487/RFC5026

Snippet:

IETF RFC 5026, Mobile IPv6 Bootstrapping in Split Scenario. Available at https://doi.org/10.17487/RFC5026

HTML (ISO 690 compliant)

Preview:

IETF RFC 5026, Mobile IPv6 Bootstrapping in Split Scenario. Available at https://doi.org/10.17487/RFC5026

Snippet:

<span class="citation"><cite>IETF RFC 5026</cite>, Mobile IPv6 Bootstrapping in Split Scenario. Available at <a href="https://doi.org/10.17487/RFC5026" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5026</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 5026, Mobile IPv6 Bootstrapping in Split Scenario
doi: 10.17487/RFC5026
url: https://doi.org/10.17487/RFC5026

Snippet:

<li>
<cite id="bib-rfc5026">IETF RFC 5026</cite>, Mobile IPv6 Bootstrapping in Split Scenario
<span class="doi">10.17487/RFC5026</span>
</li>

Referenced By

IETF RFC 5555 [Active*]
IETF RFC 6071 [Active*]
IETF RFC 6275 [Active*]
IETF RFC 8553 [Active*]