Skip to main content

Completely Encrypting RTP Header Extensions and Contributing Sources
RFC 9335

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: The IESG <>,,,,,,
Subject: Protocol Action: 'Completely Encrypting RTP Header Extensions and Contributing Sources' to Proposed Standard (draft-ietf-avtcore-cryptex-08.txt)

The IESG has approved the following document:
- 'Completely Encrypting RTP Header Extensions and Contributing Sources'
  (draft-ietf-avtcore-cryptex-08.txt) as Proposed Standard

This document is the product of the Audio/Video Transport Core Maintenance
Working Group.

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

A URL of this Internet Draft is:

Ballot Text

Technical Summary

   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). 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 defines Cryptex as a new mechanism that completely
   encrypts header extensions and CSRCs and uses simpler signaling with
   the goal of facilitating deployment.

Working Group Summary

   Working group handling was uncontroversial once the document was adopted.
   In general, the discussions converged rapidly and there were no 
   long-standing disagreements.

Document Quality

   By IETF 111 (draft -02), test vectors and two implementations
   (libsrtp and jitsi-srtp) existed.

   There appear to be no concerns about document quality.


   Bernard Aboba is the Document Shepherd.
   Murray Kucherawy is the responsible Area Director.

RFC Editor Note