W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2022

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

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Mon, 3 Jan 2022 23:21:43 +0000
To: "public-webrtc@W3.org" <public-webrtc@w3.org>
Message-ID: <DM6PR00MB07302C34B0D1996FD70212E6EC499@DM6PR00MB0730.namprd00.prod.outlook.com>
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:

A preview of the specification with PR 125 merged is available here:

Slides relating to the PR from the December Virtual Interim are available here (starts at slide 17):

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)
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...
Received on Monday, 3 January 2022 23:22:01 UTC

This archive was generated by hypermail 2.4.0 : Monday, 3 January 2022 23:22:04 UTC