Skip to main content

Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Vijay Devarapalli , Pasi Eronen
Last updated 2008-12-01 (Latest revision 2005-10-20)
Replaced by draft-ietf-mip4-mobike-connectivity
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mip4-mobike-connectivity
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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 and mobility extensions to IKEv2 (MOBIKE) to provide secure connectivity and mobility.


Vijay Devarapalli
Pasi Eronen

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)