- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Aug 2021 08:30:24 +0000
- To: public-webrtc-logs@w3.org
> So there's still a case to be made for doing the key derivation within the browser, inside one API context or another. In addition to the above security concerns, it's more ergonomic. If we had some sort of API where you connect an MLS context and an SFrame context, we could put the key derivation logic in one of those contexts. Agreed. Going with key derivation in JS is okay but it would be preferable to support a more direct setup. This could be done by extending the current SFrameTransform API, or on a yet to be defined MLS API to handle native SFrame keys. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/114#issuecomment-897449390 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 August 2021 08:30:25 UTC