A new Request for Comments is now available in online RFC libraries.
RFC 9335
Title: Completely Encrypting RTP Header Extensions
and Contributing Sources
Author: J. Uberti,
C. Jennings,
S. Murillo
Status: Standards Track
Stream: IETF
Date: January 2023
Mailbox: [email protected],
[email protected],
[email protected]
Pages: 21
Updates: RFC 3711
I-D Tag: draft-ietf-avtcore-cryptex-08.txt
URL: https://www.rfc-editor.org/info/rfc9335
DOI: 10.17487/RFC9335
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.
This document is a product of the Audio/Video Transport Core Maintenance
Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
IETF-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-announce
