Summary of CfC on PR 125 (WebRTC Encoded Transform API): "Add API to request key frames"

The Call for Consensus (CfC) on PR 125 has concluded.  The announcement is here:
Call for Consensus (CfC) on PR 125 (WebRTC Encoded Transform API): "Add API to request key frames" from Bernard Aboba on 2022-01-03 (public-webrtc@w3.org from January 2022)<https://lists.w3.org/Archives/Public/public-webrtc/2022Jan/0002.html>

Two responses were received:

Bernard: Re: Call for Consensus (CfC) on PR 125 (WebRTC Encoded Transform API): "Add API to request key frames" from Bernard Aboba on 2022-01-03 (public-webrtc@w3.org from January 2022)<https://lists.w3.org/Archives/Public/public-webrtc/2022Jan/0003.html>

Youenn: Re: REMINDER: Call for Consensus (CfC) on PR 125 (WebRTC Encoded Transform API): "Add API to request key frames" from Youenn Fablet on 2022-01-18 (public-webrtc@w3.org from January 2022)<https://lists.w3.org/Archives/Public/public-webrtc/2022Jan/0051.html>

The responses were positive with respect to merging PR 125.  However, concerns were raised about synchronization:

  *   PR 125<https://github.com/w3c/webrtc-encoded-transform/pull/125> differs from PR 37<https://github.com/w3c/webrtc-extensions/pull/37>  in that a timestamp is not returned. The timestamp indicates which keyframe is the result of the request, which is useful for ScriptTransform.
  *   For SFrameTransform, Issue 127<https://github.com/w3c/webrtc-encoded-transform/issues/127> was raised relating to synchronization of Keyframe generation and key update.

The issues were discussed at the WEBRTC WG Virtual Interim on January 18, 2022.