[webrtc-encoded-transform] Questioning the value of the ability to change SFrame transform on the fly (#298)

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

== Questioning the value of the ability to change SFrame transform on the fly ==
With SFrame transform, we have a very limited set of possible transforms. The only part in which they can differ is in their key setting and their "type" configuration. Key setting is handled by AddKey on the receive side, so the only possible use case for changing a receiver transform is to fail receiving packets that were marked with old keys - this can also be handled with RemoveKey.

I fail to concieve of an use case where replacing or removing the recieve SFrame transform will be useful.
The only case where I can see changing the send Sframe transform would be useful is changing from type "per-packet" to "per-frame" or vice versa.

Is that use case worth the complexity of permitting replacing of the SFrame transform?


Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/298 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 17 February 2026 17:13:03 UTC