MOBIKE eXtension (MOBIKE-X) for Transport Mobility and Multihomed IKE_SA
draft-mglt-ipsec-mm-mobikex-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Daniel Migault | ||
| Last updated | 2009-09-30 | ||
| 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
This draft provides a description of MOBIKE mobility and multihoming extension (MOBIKE-X). The extension is elaborated from the MOBIKE [RFC4555] protocol as well as mobility and multihoming requirements described in [I-D.mglt-ipsec-mm-requirements]. Extension concerns the Security Association facilities in a multihoming and mobile environment. More specifically this draft considers the use of multiple interfaces and the transport mode of IPsec. One of the goal of this draft was to make this extension compatible with MOBIKE [RFC4555]. We especially point out the differences from MOBIKE [RFC4555], as well as how its interacts with MOBIKE.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)