Completely Encrypting RTP Header Extensions and Contributing Sources, January 2023
- File formats:
- Also available: XML file for editing
- PROPOSED STANDARD
- RFC 3711
- J. Uberti
- avtcore (art)
Discuss this RFC: Send questions or comments to the mailing list [email protected]
While the Secure Real-time Transport Protocol (SRTP) provides confidentiality for the contents of a media packet, a significant amount of metadata is left unprotected, including RTP header extensions and contributing sources (CSRCs). However, this data can be moderately sensitive in many applications. While there have been previous attempts to protect this data, they have had limited deployment, due to complexity as well as technical limitations.
This document updates RFC 3711, the SRTP specification, and defines Cryptex as a new mechanism that completely encrypts header extensions and CSRCs and uses simpler Session Description Protocol (SDP) signaling with the goal of facilitating deployment.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.