- From: Richard Barnes via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Sep 2021 19:16:59 +0000
- To: public-webrtc-logs@w3.org
I feel like I might be missing some nuance here, but I think I disagree with @aboba here. MLS doesn't have anything to say about how media is encrypted. It just provides keys that are applied by some media encryption scheme such as SFrame. That said, I'll grant that there are some interesting API questions about how exactly we should do the integration. Since MLS is useful outside of WebRTC, it seems not unlikely that the instantiation of MLS will be in some WebMLS thing that stands alone from WebRTC. So you'll get a WebMLS context/group that can provide keys, and the question is how you attach that thing to the WebRTC context: Do you attach it to an SFrameTransform so that it provides keys to that transform? Do you attach it to something higher-level like a PeerConnection so that it can provide keys to whatever E2E security thing plugs into that? ISTM that the former would be cleaner, but it does seem like there are a few options. -- GitHub Notification of comment by bifurcation Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/114#issuecomment-911982372 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 September 2021 19:17:01 UTC