[webrtc-encoded-transform] SFrameTransform needs more key management than "set" (#259)

bifurcation has just created a new issue for https://github.com/w3c/webrtc-encoded-transform:

== SFrameTransform needs more key management than "set" ==
Right now, the way SFrameTransform is provided with keys via the `setEncryptionKey` method, which replaces the key used for encryption.  In applications where keys are rotated (e.g., on join/leave), this one method is insufficient.

The typical lifecycle is as follows:

* A next key is distributed for a given sender.
* Receivers add the next key for receiving (**in addition to** the current key).
* Once a sufficient fraction of receivers have added the key, the sender begins using the next key to send.
* Once the sender starts using the next key, the receivers can delete the current key.

So we probably need an idea that SFrameTransform has multiple keys active at once (when receiving) and more of an "add / remove" semantic than a "set" semantic.

Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/259 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 13:33:09 UTC