Call for Consensus (CfC) on PR 125 (WebRTC Encoded Transform API): "Add API to request key frames"

This is a Call for Consensus (CfC) on Pull Request 125 ("Add API to request key frames") to WebRTC Encoded Transform.  The PR is available for inspection here:
https://github.com/w3c/webrtc-encoded-transform/pull/125

A preview of the specification with PR 125 merged is available here:
https://pr-preview.s3.amazonaws.com/youennf/webrtc-insertable-streams/pull/125.html

Slides relating to the PR from the December Virtual Interim are available here (starts at slide 17):
https://docs.google.com/presentation/d/1jNC69sD-ZeSS7NNHIGcVkOdiZP8m265u6TycEX4G0vw/edit#slide=id.g107baf01ed4_0_97

The CfC will last until Monday January 17, 2022 at midnight Pacific Time.  Please respond with one of the following:


  *   I support merging PR 125.
  *   I object to merging PR 125, due to reasons included in my comments on the PR (https://github.com/w3c/webrtc-encoded-transform/pull/125)
[https://opengraph.githubassets.com/8e6152c856ac9fb6116819b6d5d17d4ed1d2756d7c1524fd1c0a7ae0b1fc38ba/w3c/webrtc-encoded-transform/pull/125]<https://github.com/w3c/webrtc-encoded-transform/pull/125>
Add API to request key frames by youennf  Pull Request #125  w3c/webrtc-encoded-transform<https://github.com/w3c/webrtc-encoded-transform/pull/125>
This includes 3 different APIs: An API to generate a key frame from a RTCRtpScriptTransformer on sender side A corresponding API in RTCRtpSender. This API shares the same algorithm as the first on...
github.com

Received on Monday, 3 January 2022 23:22:01 UTC