Skip to main content

Completely Encrypting RTP Header Extensions and Contributing Sources
RFC 9335

Revision differences

Document history

Date By Action
2023-01-25
(System)
Received changes through RFC Editor sync (created alias RFC 9335, changed abstract to 'While the Secure Real-time Transport Protocol (SRTP) provides confidentiality for the …
Received changes through RFC Editor sync (created alias RFC 9335, changed abstract to '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.', changed pages to 21, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-01-25, changed IESG state to RFC Published, created updates relation between draft-ietf-avtcore-cryptex and RFC 3711)
2023-01-25
(System) RFC published