Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 8553

Authors:

G. Giaretta, Ed.
J. Kempf
V. Devarapalli, Ed.

Stream:

IETF

Source:

mip6 (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5026

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5026

Abstract

A Mobile IPv6 node requires a Home Agent address, a home address, andIPsec security associations with its Home Agent before it can startutilizing Mobile IPv6 service. RFC 3775 requires that some or all ofthese are statically configured. This document defines how a MobileIPv6 node can bootstrap this information from non-topologicalinformation and security credentials pre-configured on the MobileNode. The solution defined in this document solves the splitscenario described in the Mobile IPv6 bootstrapping problem statementin RFC 4640. The split scenario refers to the case where the MobileNode's mobility service is authorized by a different service providerthan basic network access. The solution described in this documentis also generically applicable to any bootstrapping case, since otherscenarios are more specific realizations of the split scenario. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.