Re: Call for Consensus (CfC): Transition of "WebRTC Priority Control API" to Candidate Recommendation

I support transitioning "WebRTC Priority Control API" to CR.


On Thu, Feb 4, 2021 at 5:16 PM Bernard Aboba <Bernard.Aboba@microsoft.com>
wrote:

> This is a Call for Consensus (CfC) on transition of "WebRTC Priority Control API" to Candidate Recommendation (CR).
>
> The specification is here: WebRTC Priority Control API (w3c.github.io) <https://w3c.github.io/webrtc-priority/>
>
> The GitHub repo is here: Issues · w3c/webrtc-priority (github.com) <https://github.com/w3c/webrtc-priority/issues/>
>
> The CfC will last for two weeks and will end on Thursday, February 18, 2021.
>
> In response, please state one of the following:
>
>   *   I support transitioning "WebRTC Priority Control API" to CR.
>
>   *   I object to transitioning "WebRTC Priority Control API" to CR, due to issues filed in open bug <#number>.
>
> Bernard Aboba
>
> For the Chairs
>
> WebRTC Priority Control API - GitHub Pages
> <https://w3c.github.io/webrtc-priority/>
> Conformance. Conformance requirements are expressed with a combination of
> descriptive assertions and RFC 2119 terminology. The key words “MUST”,
> “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
> “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
> document are to be interpreted as described in RFC 2119.
> w3c.github.io
>
>
>