RFC 8643: An Opportunistic Approach for Secure Real-time Transport Protocol (OSRTP)
In plain English — editorial summary, not part of the RFC
Opportunistic Secure Real-time Transport Protocol (OSRTP) is an implementation of the Opportunistic Security mechanism, as defined in RFC 7435, applied to the Real-time Transport Protocol (RTP). OSRTP allows encrypted media to be used in environments where support for encryption is not known in advance and is not required. OSRTP does not require Session Description Protocol (SDP) extensions or features and is fully backwards compatible with existing implementations using encrypted and authenticated media and implementations that do not encrypt or authenticate media packets. OSRTP is not specific to any key management technique for Secure RTP (SRTP). OSRTP is a transitional approach useful for migrating existing deployments of real-time communications to a fully encrypted and authenticated state.
Document record
- Document ID
- RFC8643
- Published
- August 2019
- Authors
- A. Johnston; B. Aboba; A. Hutton; R. Jesske; T. Stach
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8723Double Encryption Procedures for the Secure Real-Time Transport Protocol (SRTP)Current
April 2020
- RFC 8870Encrypted Key Transport for DTLS and Secure RTPCurrent
January 2021
- RFC 8291Message Encryption for Web PushCurrent
November 2017
- RFC 9185DTLS Tunnel between a Media Distributor and Key Distributor to Facilitate Key ExchangeCurrent
April 2022
- RFC 5027Security Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
October 2007
- RFC 4568Session Description Protocol (SDP) Security Descriptions for Media StreamsCurrent
July 2006
- RFC 8548Cryptographic Protection of TCP Streams (tcpcrypt)Current
May 2019
- RFC 8547TCP-ENO: Encryption Negotiation OptionCurrent
May 2019
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?