Re: Call for Consensus (CfC): Moving degradationPreference from WebRTC-PC to the Content-Hints Specification

I support moving degradationPreference to content-hints

On Thu, Oct 24, 2019 at 11:24 PM Bernard Aboba <Bernard.Aboba@microsoft.com>
wrote:

> This is a Call for Consensus (CfC) to move degradationPrefence
> <https://rawgit.com/w3c/webrtc-pc/master/webrtc.html#dom-rtcrtpsendparameters-degradationpreference>
> from the WebRTC-PC specification to Content-Hints
> <https://w3c.github.io/mst-content-hint/>.
>
> Please respond to this CfC by November 2, 2019.
>
> Explanation
>
> During TPAC 2019, we discussed the disposition of "features at risk".
> Unfortunately, we neglected to include degradationPreference
> <https://rawgit.com/w3c/webrtc-pc/master/webrtc.html#dom-rtcrtpsendparameters-degradationpreference>
> on the list of "at risk" features. While multiple implementations allow
> degradationPreference
> <https://rawgit.com/w3c/webrtc-pc/master/webrtc.html#dom-rtcrtpsendparameters-degradationpreference>
> to be set and retrieved, setting values does not currently have an
> observable effect.  Therefore, despite test passes, degradationPreference
> <https://rawgit.com/w3c/webrtc-pc/master/webrtc.html#dom-rtcrtpsendparameters-degradationpreference>
> represents a "feature at risk".
>
> Why move degradationPreference
> <https://rawgit.com/w3c/webrtc-pc/master/webrtc.html#dom-rtcrtpsendparameters-degradationpreference>
> to Content-Hints <https://w3c.github.io/mst-content-hint/>?
>
> At TPAC, we discussed feedback on the Content-Hints specification
> <https://w3c.github.io/mst-content-hint/> which suggested that the
> specification should include normative language defining the effect of
> setting various values.  PR 31
> <https://github.com/w3c/mst-content-hint/pull/31> is currently under
> development to address this; since it refers to the behavior specified
> for values of degradationPreference , it appears that content-hints and
> degradationPreference are related.
>