IPsec mobility and multihoming requirements : Problem statement
draft-mglt-ipsec-mm-requirements-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Daniel Migault | ||
Last updated | 2009-09-24 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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:
Abstract
Currently IPsec mobility is the purpose of MOBIKE [RFC4555] which is the IKEv2 multihoming and mobility extension. More specifically, MOBIKE mobility support provides the ability to change the outer IP address of a tunnel mode Security Association. On the other hand MOBIKE multihoming support provides the ability of a peer to inform its correspondent that alternate IP addresses may be used if the current IP address does not work any more. This draft presents requirements to extend mobility and multihoming facilities. This includes the use of simultaneous IP addresses as well as other IPsec mode like transport mode.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)