Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming
RFC 5266, “Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming”, is a Best Current Practice document published in June 2008 by V. Devarapalli, P. Eronen. The canonical text is published by the RFC Editor.
Abstract
Enterprise users require mobility and secure connectivity when they roam and connect to the services offered in the enterprise. Secure connectivity is required when the user connects to the enterprise from an untrusted network. Mobility is beneficial when the user moves, either inside or outside the enterprise network, and acquires a new IP address. This document describes a solution using Mobile IPv4 (MIPv4) and mobility extensions to IKEv2 (MOBIKE) to provide secure connectivity and mobility. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
The canonical text of RFC 5266 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5265 Mobile IPv4 Traversal across IPsec-Based VPN Gateways
- RFC 5267 Contexts for IMAP4
- RFC 5264 Publication of Partial Presence Information
- RFC 5268 Mobile IPv6 Fast Handovers
- RFC 5263 Session Initiation Protocol Extension for Partial Notification of Presence Information
- RFC 5269 Distributing a Symmetric Fast Mobile IPv6 Handover Key Using SEcure Neighbor Discovery
- RFC 5262 Presence Information Data Format Extension for Partial Presence
- RFC 5270 Mobile IPv6 Fast Handovers over IEEE 802.16e Networks