datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE)
draft-ietf-mip4-mobike-connectivity-03

RFC
Document Stream: IETF
Last updated: 2007-03-05
Replaces: draft-devarapalli-mip4-mobike-connectivity
Intended RFC status: Best Current Practice
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 5266
IANA Action State: No IC 
Responsible AD: Jari Arkko
IESG Note: RFC 5266
BCP 0136
Send notices to: mip4-chairs@tools.ietf.org,vijay.devarapalli@azairenet.com,pasi.eronen@nokia.com

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-mip4-mobike-connectivity.

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.

Authors:
Pasi Eronen <pasi.eronen@nokia.com>
Vijay Devarapalli <vijay.devarapalli@azairenet.com>

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