RFC 5265: Mobile IPv4 Traversal across IPsec-Based VPN Gateways

This document outlines a solution for the Mobile IPv4 (MIPv4) and IPsec coexistence problem for enterprise users. The solution consists of an applicability…

Read RFC 5265 on the RFC Editor

Outgoing relationships (14 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 4301: Security Architecture for the Internet Protocol
Normative reference — RFC 4303: IP Encapsulating Security Payload (ESP)
Normative reference — RFC 3344: IP Mobility Support for IPv4
Normative reference — RFC 3948: UDP Encapsulation of IPsec ESP Packets
Normative reference — RFC 3947: Negotiation of NAT-Traversal in the IKE
Normative reference — RFC 3519: Mobile IP Traversal of Network Address Translation (NAT) Devices
Informative reference — RFC 4282: The Network Access Identifier
Informative reference — RFC 2002: IP Mobility Support
Informative reference — RFC 4555: IKEv2 Mobility and Multihoming Protocol (MOBIKE)
Informative reference — RFC 3776: Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents
Informative reference — RFC 3456: Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode
Informative reference — RFC 4093: Problem Statement: Mobile IPv4 Traversal of Virtual Private Network (VPN) Gateways

Incoming relationships (3 related RFCs)

Normatively referenced by — RFC 5266: Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE)
Informatively referenced by — RFC 6071: IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap
Informatively referenced by — RFC 5454: Dual-Stack Mobile IPv4