An Opportunistic Approach for Secure Real-time Transport Protocol (OSRTP)
RFC 8643
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['srtp', 'opportunistic security', 'encryption', 'best effort', 'osrtp']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "T. Stach": changed name from "Thomas Stach" to "T. Stach", changed order from "4" to "5" |
|
2026-05-20
|
(System) | Changed author "R. Jesske": changed name from "Roland Jesske" to "R. Jesske", cleared country (was "Germany"), changed order from "3" to "4" |
|
2026-05-20
|
(System) | Changed author "A. Hutton": changed name from "Andrew Hutton" to "A. Hutton", cleared country (was "UK"), changed order from "2" to "3" |
|
2026-05-20
|
(System) | Changed author "B. Aboba": changed name from "Bernard Aboba" to "B. Aboba", cleared country (was "USA"), changed order from "1" to "2" |
|
2026-05-20
|
(System) | Changed author "A. Johnston": changed name from "Alan Johnston" to "A. Johnston", cleared country (was "USA"), changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2019-08-26
|
Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
|
2019-08-26
|
Gunter Van de Velde | Assignment of request for Last Call review by OPSDIR to Will LIU was marked no-response |
|
2019-08-09
|
(System) | Received changes through RFC Editor sync (created alias RFC 8643, changed abstract to 'Opportunistic Secure Real-time Transport Protocol (OSRTP) is an implementation of the … Received changes through RFC Editor sync (created alias RFC 8643, changed abstract to '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.', changed standardization level to Informational, changed state to RFC, added RFC published event at 2019-08-09, changed IESG state to RFC Published) |
|
2019-08-09
|
(System) | RFC published |