RFC 5266: Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE)

Enterprise users require mobility and secure connectivity when they roam and connect to the services offered in the enterprise. Secure connectivity is…

Read RFC 5266 on the RFC Editor

Outgoing relationships (12 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 4301: Security Architecture for the Internet Protocol
Normative reference — RFC 4306: Internet Key Exchange (IKEv2) Protocol
Normative reference — RFC 3344: IP Mobility Support for IPv4
Normative reference — RFC 4555: IKEv2 Mobility and Multihoming Protocol (MOBIKE)
Normative reference — RFC 5265: Mobile IPv4 Traversal across IPsec-Based VPN Gateways
Informative reference — RFC 2409: The Internet Key Exchange (IKE)
Informative reference — RFC 3948: UDP Encapsulation of IPsec ESP Packets
Informative reference — RFC 3947: Negotiation of NAT-Traversal in the IKE
Informative reference — RFC 3024: Reverse Tunneling for Mobile IP, revised
Informative reference — RFC 3519: Mobile IP Traversal of Network Address Translation (NAT) Devices
Informative reference — RFC 4093: Problem Statement: Mobile IPv4 Traversal of Virtual Private Network (VPN) Gateways

Incoming relationships (2 related RFCs)

Informatively referenced by — RFC 6071: IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap
Informatively referenced by — RFC 5454: Dual-Stack Mobile IPv4