RFC 5764

RFC 5764
Title	RFC 5764
Type	Technical Standard
Status	Published
Year	2010
Authors	Christopher A. Wood, Jonathan Rosenberg, Henning Schulzrinne
Pages	61

RFC 5764

RFC 5764 specifies mappings and considerations for using Secure Real-time Transport Protocol (SRTP) with Datagram Transport Layer Security (DTLS) to protect media streams in interactive multimedia. The document updates earlier work on multimedia security by defining negotiation mechanisms, packet formats, and procedures that integrate with existing signaling protocols and transport systems. It addresses compatibility with deployed systems and situates its recommendations among standards maintained by the Internet Engineering Task Force and other standards bodies.

Introduction

RFC 5764 defines a method for key negotiation and media protection that binds Datagram Transport Layer Security to Secure Real-time Transport Protocol for use in interactive applications such as telephony and conferencing. The specification complements work in the Internet Engineering Task Force by aligning with profiles developed by the Session Initiation Protocol community and implementers in projects related to WebRTC, SIP, and multimedia frameworks. It positions itself relative to contemporaneous efforts at 3GPP, ITU-T, and industry forums that address secure media transport.

Background and Motivation

The need for RFC 5764 arose from interoperability challenges among implementations of SRTP, DTLS, and signaling protocols developed by groups such as IETF MMUSIC, IETF AVTCORE, and IETF SIPPING. Prior approaches, including centralized key management schemes promoted by MIKEY and call-control based keying used in SIP extensions, revealed limitations when applied to peer-to-peer scenarios envisaged by WebRTC and client-server architectures favored by IMS. The document responds to operational requirements in deployments by carriers like AT&T, vendors such as Cisco Systems, and browser projects including Mozilla and Google Chrome, which required a robust, standardized mechanism for negotiating cryptographic parameters for media.

Protocol Overview

RFC 5764 specifies binding DTLS handshake results to SRTP cryptographic contexts by deriving SRTP keys from DTLS exported keying material, and by defining RTP and RTCP demultiplexing rules for packets transported over UDP. The protocol integrates with session description formats used by IETF SDP and signaling via SIP or proprietary protocols used by companies like Skype Technologies and projects like Jitsi. It prescribes state machines influenced by the Transport Layer Security family and aligns with cipher suite choices associated with AES and HMAC algorithms documented by entities such as NIST and the IETF CFRG. Packet format considerations reference extensions and interworking constraints familiar to implementers who follow specifications from IETF RFC 3550, RFC 3711, and other multimedia transport standards.

Security Considerations

Security analysis in RFC 5764 emphasizes authentication, integrity, and confidentiality properties afforded by combining DTLS and SRTP, while warning about potential downgrade attacks, replay issues, and the need for correct certificate validation chains as used by X.509 and trust infrastructures in environments like Let's Encrypt and enterprise PKI deployments. The document addresses threats analyzed in forums such as IETF SAAG and considers mitigation strategies recommended by bodies including ENISA and OWASP for secure deployment. It also outlines operational cautions relevant to law, regulation and compliance frameworks like GDPR and standards-driven audits carried out by organizations including ISO and NIST.

Implementation and Deployment

Implementers for RFC 5764 include open-source projects and commercial vendors across the telecommunications and browser ecosystems; examples encompass contributions from Google, Mozilla Foundation, Linphone, and Asterisk. Deployment experience reported by operators such as Verizon and platform providers like Microsoft informed guidance on NAT traversal, interaction with traversal techniques standardized by IETF STUN and TURN, and considerations for middleboxes exemplified by legacy equipment from vendors like Ericsson and Nokia. The specification describes interoperation testing practices used in interoperability events organized by IETF Interop, industry consortia like ETSI, and collaborative testbeds operated by research institutions such as MIT and Stanford University.

Interoperability and Impact

RFC 5764 has influenced the development of secure media in consumer and enterprise products, contributing to interoperable media protection in WebRTC deployments, telephony platforms from Avaya and Genesys, and conferencing services provided by Zoom Video Communications and Cisco Webex. Its guidance has been incorporated into follow-on IETF work items and profiles adopted by standardization bodies including 3GPP and ITU-T, and has shaped best practices published by alliances like the IETF RTCWEB community. The document's emphasis on DTLS-based keying facilitated broader adoption of end-to-end encryption models in real-time communications and remains a reference point for implementers, researchers at institutions such as University of California, Berkeley and Carnegie Mellon University, and vendors pursuing interoperable, secure multimedia solutions.

Category:Internet standards