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

I do too (I think I already said so…).

From: <youenn@apple.com> on behalf of Youenn Fablet <youenn@apple.com>
Date: Friday, 25 October 2019 at 14:48
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: Call for Consensus (CfC): Moving degradationPreference from WebRTC-PC to the Content-Hints Specification
Resent from: "public-webrtc@w3.org" <public-webrtc@w3.org>
Resent date: Friday, 25 October 2019 at 14:45

+1 as well.


On 25 Oct 2019, at 13:56, Henrik Boström <hbos@google.com<mailto:hbos@google.com>> wrote:

I support moving degradationPreference to content-hints

On Thu, Oct 24, 2019 at 11:24 PM Bernard Aboba <Bernard.Aboba@microsoft.com<mailto: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://protect2.fireeye.com/v1/url?k=ac1aa3b7-f0906843-ac1ae32c-86cd58c48020-b0df4dca5bcc3110&q=1&e=53d226db-a485-4071-a088-4fd7fde00b1e&u=https%3A%2F%2Fw3c.github.io%2Fmst-content-hint%2F>.

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://protect2.fireeye.com/v1/url?k=c3f089ea-9f7a421e-c3f0c971-86cd58c48020-fa907f7d241a4607&q=1&e=53d226db-a485-4071-a088-4fd7fde00b1e&u=https%3A%2F%2Fw3c.github.io%2Fmst-content-hint%2F>?

At TPAC, we discussed feedback on the Content-Hints specification<https://protect2.fireeye.com/v1/url?k=7e79c7b7-22f30c43-7e79872c-86cd58c48020-c78dd3ba419ac33f&q=1&e=53d226db-a485-4071-a088-4fd7fde00b1e&u=https%3A%2F%2Fw3c.github.io%2Fmst-content-hint%2F> which suggested that the specification should include normative language defining the effect of setting various values.  PR 31<https://protect2.fireeye.com/v1/url?k=859aad0e-d91066fa-859aed95-86cd58c48020-c29fa61bfd357010&q=1&e=53d226db-a485-4071-a088-4fd7fde00b1e&u=https%3A%2F%2Fgithub.com%2Fw3c%2Fmst-content-hint%2Fpull%2F31> 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.