RFC 9605 on Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media
rfc-editor@rfc-editor.org Tue, 27 August 2024 22:46 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA6ADC14F603; Tue, 27 Aug 2024 15:46:01 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 3EE7B7FA6E; Tue, 27 Aug 2024 15:46:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9605 on Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240827224601.3EE7B7FA6E@rfcpa.rfc-editor.org>
Date: Tue, 27 Aug 2024 15:46:01 -0700
Message-ID-Hash: B5DO3PLCCIKJEEGDDHVZXXS5R7TMOOZW
X-Message-ID-Hash: B5DO3PLCCIKJEEGDDHVZXXS5R7TMOOZW
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sframe@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/lRQIUUkf3ZFa2TY-s4PJUcDXvQo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries. RFC 9605 Title: Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media Author: E. Omara, J. Uberti, S. G. Murillo, R. Barnes, Ed., Y. Fablet Status: Standards Track Stream: IETF Date: August 2024 Mailbox: eomara@apple.com, justin@fixie.ai, sergio.garcia.murillo@cosmosoftware.io, rlb@ipv.sx, youenn@apple.com Pages: 68 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sframe-enc-09.txt URL: https://www.rfc-editor.org/info/rfc9605 DOI: 10.17487/RFC9605 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. This document is a product of the Secure Media Frames Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC