Mobile IP Traversal of Network Address Translation (NAT) Devices

Abstract

Mobile IP's datagram tunnelling is incompatible with Network Address

IP Mobility Support for IPv4, Revised

“…4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 T Foreign agent supports reverse tunneling as specified in [12]. U Mobility agent supports UDP Tunneling as specified in [27]. X Mobility agent supports Registration Revocation as specified in [28].…”

Dual-Stack Mobile IPv4

“…If the care-of address is a private address, then Mobile IP NAT Traversal as [RFC3519] MAY be used in combination with the extensions described in this specification. In that case, to transport IPv6 packets, the next header field of the Mobile Tunnel Data message header [RFC3519] MUST be set to the value for IPv6.…”

“…In that case, to transport IPv6 packets, the next header field of the Mobile Tunnel Data message header [RFC3519] MUST be set to the value for IPv6. Note that in that case, the encapsulation field of the UDP Tunnel Request Extension defined in [RFC3519] MUST be set to zero.…”

Mobile IPv6 Support for Dual Stack Hosts and Routers

“…In cases where this specification is used for NAT traversal, it is important to note that it has the same vulnerabilities associated with [RFC3519]. An attacker is able to hijack the mobile node's session with the home agent if it can modify the contents of the outer IPv4 header.…”