%% You should probably cite rfc9605 instead of this I-D. @techreport{ietf-sframe-enc-09, number = {draft-ietf-sframe-enc-09}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-sframe-enc/09/}, author = {Emad Omara and Justin Uberti and Sergio Garcia Murillo and Richard Barnes and Youenn Fablet}, title = {{Secure Frame (SFrame)}}, pagetotal = 74, year = 2024, month = apr, day = 4, abstract = {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. The proposed 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.}, }