RFC 8723: Double Encryption Procedures for the Secure Real-Time Transport Protocol (SRTP)
In plain English — editorial summary, not part of the RFC
In some conferencing scenarios, it is desirable for an intermediary to be able to manipulate some parameters in Real-time Transport Protocol (RTP) packets, while still providing strong end-to-end security guarantees. This document defines a cryptographic transform for the Secure Real-time Transport Protocol (SRTP) that uses two separate but related cryptographic operations to provide hop-by-hop and end-to-end security guarantees. Both the end-to-end and hop-by-hop cryptographic algorithms can utilize an authenticated encryption with associated data (AEAD) algorithm or take advantage of future SRTP transforms with different properties.
Document record
- Document ID
- RFC8723
- Published
- April 2020
- Authors
- C. Jennings; P. Jones; R. Barnes; A.B. Roach
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8870Encrypted Key Transport for DTLS and Secure RTPCurrent
January 2021
- RFC 9185DTLS Tunnel between a Media Distributor and Key Distributor to Facilitate Key ExchangeCurrent
April 2022
- RFC 8643An Opportunistic Approach for Secure Real-time Transport Protocol (OSRTP)Current
August 2019
- RFC 8871A Solution Framework for Private Media in Privacy-Enhanced RTP Conferencing (PERC)Current
January 2021
- RFC 8843Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Obsoleted
January 2021
- RFC 8845Framework for Telepresence Multi-StreamsCurrent
January 2021
- RFC 8858Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)Current
January 2021
- RFC 8862Best Practices for Securing RTP Media Signaled with SIPCurrent
January 2021
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?