RFC 6043: MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY)
In plain English — editorial summary, not part of the RFC
The Multimedia Internet KEYing (MIKEY) specification describes a key management scheme for real-time applications. In this document, we note that the currently defined MIKEY modes are insufficient to address deployment scenarios built around a centralized key management service. Interest in such deployments is increasing. Therefore, a set of new MIKEY modes that work well in such scenarios are defined. The new modes use a trusted key management service and a ticket concept, similar to that in Kerberos. The new modes also support features used by many existing applications, where the exact identity of the other endpoint may not be known at the start of the communication session. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6043
- Published
- March 2011
- Authors
- J. Mattsson; T. Tian
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 58
- Also known as
- —
- Updated by:
- RFC 6309
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4738MIKEY-RSA-R: An Additional Mode of Key Distribution in Multimedia Internet KEYing (MIKEY)Current
November 2006
- RFC 5197On the Applicability of Various Multimedia Internet KEYing (MIKEY) Modes and ExtensionsCurrent
June 2008
- RFC 5027Security Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
October 2007
- RFC 7201Options for Securing RTP SessionsCurrent
April 2014
- RFC 4650HMAC-Authenticated Diffie-Hellman for Multimedia Internet KEYing (MIKEY)Current
September 2006
- RFC 8269The ARIA Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)Current
October 2017
- RFC 6188The Use of AES-192 and AES-256 in Secure RTPCurrent
March 2011
- RFC 5767User-Agent-Driven Privacy Mechanism for SIPCurrent
April 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?