Richards, Thanks for the explanation. The third paragraph of the Intro section says: The Secure Real-Time Protocol (SRTP) is already widely used for HBH encryption [RFC3711]. The SRTP "double encryption" scheme defines a way to do E2E encryption in SRTP [RFC8723]. Unfortunately, this scheme has poor efficiency and high complexity, and its entanglement with RTP makes it unworkable in several realistic SFU scenarios. Is Secure Frame intended for fixing the poor efficiency and high complexity of SRTP? The SRTP used for HBH requires the SFU to perform the decryption, correct?
Can Secure Frame use the SRTP? Thank you, Linda From: Richard Barnes <rlb@xxxxxx> Hi Linda, Secure Frames are *not* decrypted by the SFU. The outer HBH encryption is decrypted by the SFU, but the point of the E2E encryption is that the SFU does not have the keys. The document does not claim to save on SFU processing. For a switching SFU, the processing should be roughly the same with or without SFrame. --Richard On Sat, Mar 30, 2024 at 9:23 AM Linda Dunbar via Datatracker <noreply@xxxxxxxx> wrote:
|
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call