metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9335: Completely Encrypting RTP Header Extensions and Contributing Sources

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9335
Published
January 2023
Authors
J. Uberti; C. Jennings; S. Murillo
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
21
Also known as
—
Updates:
RFC 3711

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/9335-completely-encrypting-rtp-header-extensions-and-contributing-sources