Re: [webrtc-encoded-transform] generateKeyFrame algorithm makes wrong assumptions about number of encoders (#145)

The spec uses an abstract representation which does not have to match how UA are implemented.
I am opened to readability/clarification changes, but I prefer being specific about the behaviour, for instance:
- If sender is not sending, reject with NotFoundError.
- If rid is not matching any negotiated rid, reject with NotFoundError.
- If rid is not specified, use the first rid negotiated rid value.
- If there is an ongoing request for the provided rid, do nothing.

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/145#issuecomment-1234200209 using your GitHub account


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

Received on Thursday, 1 September 2022 12:17:17 UTC