A new Request for Comments is now available in online RFC libraries.
RFC 4555
Title: IKEv2 Mobility and Multihoming Protocol
(MOBIKE)
Author: P. Eronen
Status: Standards Track
Date: June 2006
Mailbox: pasi.eronen@nokia.com
Pages: 33
Characters: 78698
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mobike-protocol-08.txt
URL: http://www.rfc-editor.org/rfc/rfc4555.txt
This document describes the MOBIKE protocol, a mobility and
multihoming extension to Internet Key Exchange (IKEv2). MOBIKE
allows the IP addresses associated with IKEv2 and tunnel mode IPsec
Security Associations to change. A mobile Virtual Private Network
(VPN) client could use MOBIKE to keep the connection with the VPN
gateway active while moving from one address to another. Similarly,
a multihomed host could use MOBIKE to move the traffic to a different
interface if, for instance, the one currently being used stops
working. [STANDARDS TRACK]
This document is a product of the IKEv2 Mobility and Multihoming
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of the
Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol. Distribution of this memo is
unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
