RFC 3830: MIKEY: Multimedia Internet KEYing
In plain English — editorial summary, not part of the RFC
This document describes a key management scheme that can be used for real-time applications (both for peer-to-peer communication and group communication). In particular, its use to support the Secure Real-time Transport Protocol is described in detail. Security protocols for real-time multimedia applications have started to appear. This has brought forward the need for a key management solution to support these protocols. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3830
- Published
- August 2004
- Authors
- J. Arkko; E. Carrara; F. Lindholm; M. Naslund; K. Norrman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 66
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4567Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)Current
July 2006
- RFC 4442Bootstrapping Timed Efficient Stream Loss-Tolerant Authentication (TESLA)Current
March 2006
- RFC 4650HMAC-Authenticated Diffie-Hellman for Multimedia Internet KEYing (MIKEY)Current
September 2006
- RFC 5027Security Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
October 2007
- RFC 6043MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY)Updated
March 2011
- RFC 8269The ARIA Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)Current
October 2017
- RFC 3820Internet X.509 Public Key Infrastructure (PKI) Proxy Certificate ProfileCurrent
June 2004
- RFC 3850Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate HandlingObsoleted
July 2004
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?