RFC 5026: Mobile IPv6 Bootstrapping in Split Scenario

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…

Read RFC 5026 on the RFC Editor

Incoming relationships (11 related RFCs)

Updated by, Informatively referenced by — RFC 8553: DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
Normatively referenced by — RFC 6275: Mobility Support in IPv6
Normatively referenced by — RFC 5555: Mobile IPv6 Support for Dual Stack Hosts and Routers
Normatively referenced by — RFC 5778: Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction
Normatively referenced by — RFC 6611: Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario
Normatively referenced by — RFC 5637: Authentication, Authorization, and Accounting (AAA) Goals for Mobile IPv6
Normatively referenced by — RFC 6612: Interactions between Proxy Mobile IPv6 (PMIPv6) and Mobile IPv6 (MIPv6): Scenarios and Related Issues
Informatively referenced by — RFC 5685: Redirect Mechanism for the Internet Key Exchange Protocol Version 2 (IKEv2)
Informatively referenced by — RFC 6071: IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap
Informatively referenced by — RFC 7429: Distributed Mobility Management: Current Practices and Gap Analysis
Informatively referenced by — RFC 6097: Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6