- From: youennf via GitHub <noreply@w3.org>
- Date: Tue, 17 Jun 2025 18:59:38 +0000
- To: public-webrtc-logs@w3.org
The principle is the following: 1. On sender side, setting the encryption key means using it from now on, the old key can be forgotten. This is really a set semantics. 2. On receiver side, setting the encryption key means making it available as SFrame key material. It will be used when keyID matches. So it is really an add semantics. There is no remove now as the transform can potentially forget the past key that was used. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/259#issuecomment-2981512261 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 June 2025 18:59:39 UTC