RFC 5764: Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)
In plain English — editorial summary, not part of the RFC
This document describes a Datagram Transport Layer Security (DTLS) extension to establish keys for Secure RTP (SRTP) and Secure RTP Control Protocol (SRTCP) flows. DTLS keying happens on the media path, independent of any out-of-band signalling channel present. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5764
- Published
- May 2010
- Authors
- D. McGrew; E. Rescorla
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 26
- 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 5763Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)Updated
May 2010
- RFC 5761Multiplexing RTP Data and Control Packets on a Single PortUpdated
April 2010
- RFC 5767User-Agent-Driven Privacy Mechanism for SIPCurrent
April 2010
- RFC 5768Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)Current
April 2010
- RFC 5760RTP Control Protocol (RTCP) Extensions for Single-Source Multicast Sessions with Unicast FeedbackUpdated
February 2010
- RFC 5774Considerations for Civic Addresses in the Presence Information Data Format Location Object (PIDF-LO): Guidelines and IANA Registry DefinitionCurrent
March 2010
- RFC 5725Post-Repair Loss RLE Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)Current
February 2010
- RFC 5808Requirements for a Location-by-Reference MechanismCurrent
May 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?