Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media
RFC 9605
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2025-03-25
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2025-03-03
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2024-08-29
|
(System) | IANA registries were updated to include RFC9605 |
|
2024-08-27
|
(System) | Received changes through RFC Editor sync (created document RFC 9605, created became rfc relationship between draft-ietf-sframe-enc and RFC 9605, set title to 'Secure … Received changes through RFC Editor sync (created document RFC 9605, created became rfc relationship between draft-ietf-sframe-enc and RFC 9605, set title to 'Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media', set abstract to 'This document describes the Secure Frame (SFrame) end-to-end encryption and authentication mechanism for media frames in a multiparty conference call, in which central media servers (Selective Forwarding Units or SFUs) can access the media metadata needed to make forwarding decisions without having access to the actual media. This mechanism differs from the Secure Real-Time Protocol (SRTP) in that it is independent of RTP (thus compatible with non-RTP media transport) and can be applied to whole media frames in order to be more bandwidth efficient.', set pages to 68, set standardization level to Proposed Standard, added RFC published event at 2024-08-27) |
|
2024-08-27
|
(System) | RFC published |