Issues of the Key Management Mobility Capability (K) flag in Mobile IPv6.
draft-sdecugis-mext-kbit-issues-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Sebastien Decugis | ||
| Last updated | 2008-01-16 | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-sdecugis-mext-kbit-issues-00.txt
https://www.ietf.org/archive/id/draft-sdecugis-mext-kbit-issues-00.txt
Abstract
Mobile IPv6 specification (RFC 3775) introduces a flag called "Key Management Mobility Capability (K)" that is used during home registration procedure. This document describes the behavior of implementations when the capability is supported or not. The purpose of this description is to highlight the expected behavior of implementations at the end of home registration process with regards to the exchanged (K) flag value.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)