RFC 4640: Problem Statement for bootstrapping Mobile IPv6 (MIPv6)

A mobile node needs at least the following information: a home address, a home agent address, and a security association with home agent to register with the…

Read RFC 4640 on the RFC Editor

Outgoing relationships (8 related RFCs)

Informative reference — RFC 3748: Extensible Authentication Protocol (EAP)
Informative reference — RFC 3775: Mobility Support in IPv6
Informative reference — RFC 3753: Mobility Related Terminology
Informative reference — RFC 3041: Privacy Extensions for Stateless Address Autoconfiguration in IPv6
Informative reference — RFC 3776: Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents
Informative reference — RFC 2794: Mobile IP Network Access Identifier Extension for IPv4
Informative reference — RFC 4283: Mobile Node Identifier Option for Mobile IPv6 (MIPv6)
Informative reference — RFC 4285: Authentication Protocol for Mobile IPv6

Incoming relationships (6 related RFCs)

Normatively referenced by — RFC 5637: Authentication, Authorization, and Accounting (AAA) Goals for Mobile IPv6
Informatively referenced by — RFC 5447: Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction
Informatively referenced by — RFC 7429: Distributed Mobility Management: Current Practices and Gap Analysis
Informatively referenced by — RFC 5778: Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction
Informatively referenced by — RFC 6611: Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario
Informatively referenced by — RFC 6610: DHCP Options for Home Information Discovery in Mobile IPv6 (MIPv6)