RFC 9335: Completely Encrypting RTP Header Extensions and Contributing Sources

While the Secure Real-time Transport Protocol (SRTP) provides confidentiality for the contents of a media packet, a significant amount of metadata is left…

Read RFC 9335 on the RFC Editor

Outgoing relationships (13 related RFCs)

Updates, Normative reference — RFC 3711: The Secure Real-time Transport Protocol (SRTP)
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3550: RTP: A Transport Protocol for Real-Time Applications
Normative reference — RFC 3264: An Offer/Answer Model with Session Description Protocol (SDP)
Normative reference — RFC 8859: A Framework for Session Description Protocol (SDP) Attributes When Multiplexing
Normative reference — RFC 8866: SDP: Session Description Protocol
Normative reference — RFC 8285: A General Mechanism for RTP Header Extensions
Normative reference — RFC 9143: Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
Informative reference — RFC 6904: Encryption of Header Extensions in the Secure Real-time Transport Protocol (SRTP)
Informative reference — RFC 6464: A Real-time Transport Protocol (RTP) Header Extension for Client-to-Mixer Audio Level Indication
Informative reference — RFC 6465: A Real-time Transport Protocol (RTP) Header Extension for Mixer-to-Client Audio Level Indication
Informative reference — RFC 7714: AES-GCM Authenticated Encryption in the Secure Real-time Transport Protocol (SRTP)

Incoming relationships (1 related RFC)

Informatively referenced by — RFC 9626: Video Frame Marking RTP Header Extension