Double Encryption Procedures for the Secure Real-Time Transport Protocol
RFC 8723, “Double Encryption Procedures for the Secure Real-Time Transport Protocol”, is a Proposed Standard document published in April 2020 by C. Jennings, P. Jones, R. Barnes, A.B. Roach. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8723 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8722 Defining the Role and Function of IETF Protocol Parameter Registry Operators
- RFC 8724 SCHC: Generic Framework for Static Context Header Compression and Fragmentation
- RFC 8721 Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents
- RFC 8725 JSON Web Token Best Current Practices
- RFC 8720 Principles for Operation of Internet Assigned Numbers Authority Registries
- RFC 8726 How Requests for IANA Action Will Be Handled on the Independent Stream
- RFC 8719 High-Level Guidance for the Meeting Policy of the IETF
- RFC 8727 JSON Binding of the Incident Object Description Exchange Format