RFC 4093: Problem Statement: Mobile IPv4 Traversal of Virtual Private Network (VPN) Gateways

Deploying Mobile-IP v4 in networks that are connected to the Internet through a Virtual Private Network (VPN) gateway presents some problems that do not…

Read RFC 4093 on the RFC Editor

Outgoing relationships (9 related RFCs)

Normative reference — RFC 3344: IP Mobility Support for IPv4
Informative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 1918: Address Allocation for Private Internets
Informative reference — RFC 2131: Dynamic Host Configuration Protocol
Informative reference — RFC 2401: Security Architecture for the Internet Protocol
Informative reference — RFC 2003: IP Encapsulation within IP
Informative reference — RFC 3715: IPsec-Network Address Translation (NAT) Compatibility Requirements
Informative reference — RFC 3947: Negotiation of NAT-Traversal in the IKE
Informative reference — RFC 3519: Mobile IP Traversal of Network Address Translation (NAT) Devices

Incoming relationships (3 related RFCs)

Informatively referenced by — RFC 6071: IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap
Informatively referenced by — RFC 5265: Mobile IPv4 Traversal across IPsec-Based VPN Gateways
Informatively referenced by — RFC 5266: Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE)