On the applicability of various MIKEY modes and extensions
draft-fries-msec-mikey-applicability-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Steffen Fries , Dragan Ignjatic | ||
| Last updated | 2006-11-29 (Latest revision 2006-02-28) | ||
| Replaced by | RFC 5197 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-msec-mikey-applicability | |
| 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
Multimedia Internet Keying - MIKEY - is a key management scheme that can be used for real-time applications. In particular, it has been defined focusing on the support of the Secure Real-time Transport Protocol. MIKEY itself defines four key distribution schemes. Moreover, it is defined to allow extensions of the protocol. As MIKEY becomes more and more accepted, extensions to the base protocol arose, especially in terms of additional key distribution schemes, but also in terms of payload enhancements. This document provides an overview about MIKEY in general as well as the existing extensions in MIKEY, which have been defined or are in the process of definition.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)