RFC 5764: Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc5764.html

Published

2010-05-01

Updated

unknown

Accessed

2026-09-23

HTTP status

200

License

IETF Trust Legal Provisions (BCP 78); no-redistribution; short excerpts and locators only

Source notes citing this source

• DTLS-SRTP derives the SRTP master key and salt for each direction from the DTLS handshake using the TLS exporter label 'EXTRACTOR-dtls_srtp', so no keys appear in SDP. in context
• In DTLS-SRTP, DTLS is used only to establish keys. Once use_srtp is negotiated, RTP and RTCP are protected solely by SRTP and never sent as DTLS application data. in context
• RFC 5764 defines the DTLS-SRTP protection profiles SRTP_AES128_CM_HMAC_SHA1_80, SRTP_AES128_CM_HMAC_SHA1_32, SRTP_NULL_HMAC_SHA1_80 and SRTP_NULL_HMAC_SHA1_32, which are negotiated in the DTLS use_srtp extension. in context
• RFC 5764 leaves the choice of DTLS client and DTLS server to an out-of-band mechanism such as SDP. in context
• As published in 2010, RFC 5764 demultiplexed packets on a shared port by first byte: 0-1 STUN, 20-63 DTLS and 128-191 RTP/RTCP. in context

Cite this source record

APA

WarmTransfer. (2010, May 1). RFC 5764: Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP). WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-5764-dtls-srtp

BibTeX

@misc{warmtransfer-rfc-5764-dtls-srtp,
  title  = {RFC 5764: Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)},
  author = {{WarmTransfer}},
  year   = {2010},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-5764-dtls-srtp},
  note   = {IETF / RFC Editor, accessed 2026-09-23}
}