Key Management Mobility Capability (K) flag in Mobile IPv6 BU/BA messages.
draft-sdecugis-mextkbitissues-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Sebastien Decugis | ||
| Last updated | 2007-12-21 | ||
| 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
Mobile IPv6 specification (RFC 3775) introduces a flag called "Key Management Mobility Capability (K)" to use during the home registration procedure (BU/BA exchange.) This document describes the sequences of events that occur when this flag is not used by the implementation. It also highlights the requirements that this flag puts on the interface between the MIPv6 entity and the IKE entity.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)