UpdatedPROPOSED STANDARDIETF stream

RFC 3830: MIKEY: Multimedia Internet KEYing

Still current, but amended. Parts of this document are changed or extended by RFC 4738, RFC 6309. Read both.

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
Updated by:
RFC 4738, RFC 6309

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.

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?

canonical URL: /rfc/3830-mikey-multimedia-internet-keying