RFC 4567: Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)
In plain English — editorial summary, not part of the RFC
This document defines general extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as specified by a key management protocol, in order to secure the media. These extensions are presented as a framework, to be used by one or more key management protocols. As such, their use is meaningful only when complemented by an appropriate key management protocol. General guidelines are also given on how the framework should be used together with SIP and RTSP. The usage with the Multimedia Internet KEYing (MIKEY) key management protocol is also defined. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4567
- Published
- July 2006
- Authors
- J. Arkko; F. Lindholm; M. Naslund; K. Norrman; E. Carrara
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3830MIKEY: Multimedia Internet KEYingUpdated
August 2004
- RFC 5027Security Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
October 2007
- RFC 4650HMAC-Authenticated Diffie-Hellman for Multimedia Internet KEYing (MIKEY)Current
September 2006
- RFC 4442Bootstrapping Timed Efficient Stream Loss-Tolerant Authentication (TESLA)Current
March 2006
- RFC 4738MIKEY-RSA-R: An Additional Mode of Key Distribution in Multimedia Internet KEYing (MIKEY)Current
November 2006
- RFC 6043MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY)Updated
March 2011
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 8269The ARIA Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)Current
October 2017
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?