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

I also support moving degradationPreference to content-hints.
________________________________
From: Florent Castelli <orphis@google.com>
Sent: Friday, October 25, 2019 9:34 AM
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Cc: Youenn Fablet <youenn@apple.com>; Bernard Aboba <Bernard.Aboba@microsoft.com>; public-webrtc@w3.org <public-webrtc@w3.org>
Subject: [EXTERNAL] Re: Call for Consensus (CfC): Moving degradationPreference from WebRTC-PC to the Content-Hints Specification

I support moving degradationPreference to content-hints.

On Fri, Oct 25, 2019 at 3:12 PM Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com<mailto:stefan.lk.hakansson@ericsson.com>> wrote:

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



From: <youenn@apple.com<mailto:youenn@apple.com>> on behalf of Youenn Fablet <youenn@apple.com<mailto:youenn@apple.com>>
Date: Friday, 25 October 2019 at 14:48
To: Bernard Aboba <Bernard.Aboba@microsoft.com<mailto:Bernard.Aboba@microsoft.com>>
Cc: "public-webrtc@w3.org<mailto:public-webrtc@w3.org>" <public-webrtc@w3.org<mailto: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<mailto:public-webrtc@w3.org>" <public-webrtc@w3.org<mailto: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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwebrtc-pc%2Fmaster%2Fwebrtc.html%23dom-rtcrtpsendparameters-degradationpreference&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc29a2be15bd040a3532008d75969323f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637076180698144671&sdata=XeApS7B3FWI2MEt6lnCw4H1psvdNQCy9iwDJ1z41NZg%3D&reserved=0> from the WebRTC-PC specification to Content-Hints<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3Dac1aa3b7-f0906843-ac1ae32c-86cd58c48020-b0df4dca5bcc3110%26q%3D1%26e%3D53d226db-a485-4071-a088-4fd7fde00b1e%26u%3Dhttps%253A%252F%252Fw3c.github.io%252Fmst-content-hint%252F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc29a2be15bd040a3532008d75969323f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637076180698144671&sdata=R8x3qGlxk91nogzZQAvdG6buyx%2BASR9R7B5NkszRYgs%3D&reserved=0>.



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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwebrtc-pc%2Fmaster%2Fwebrtc.html%23dom-rtcrtpsendparameters-degradationpreference&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc29a2be15bd040a3532008d75969323f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637076180698154661&sdata=crg8t8x%2BAhDDgze9RIxr%2F7YY92u8G%2FuujFcTtm%2FYaWc%3D&reserved=0> on the list of "at risk" features. While multiple implementations allow degradationPreference<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwebrtc-pc%2Fmaster%2Fwebrtc.html%23dom-rtcrtpsendparameters-degradationpreference&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc29a2be15bd040a3532008d75969323f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637076180698154661&sdata=crg8t8x%2BAhDDgze9RIxr%2F7YY92u8G%2FuujFcTtm%2FYaWc%3D&reserved=0> to be set and retrieved, setting values does not currently have an observable effect.  Therefore, despite test passes, degradationPreference<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwebrtc-pc%2Fmaster%2Fwebrtc.html%23dom-rtcrtpsendparameters-degradationpreference&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc29a2be15bd040a3532008d75969323f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637076180698164655&sdata=DS98WvcahE6TIOJ9SHz70jGUlgYrHB08SpqV79c10Wg%3D&reserved=0> represents a "feature at risk".



Why move degradationPreference<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwebrtc-pc%2Fmaster%2Fwebrtc.html%23dom-rtcrtpsendparameters-degradationpreference&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc29a2be15bd040a3532008d75969323f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637076180698164655&sdata=DS98WvcahE6TIOJ9SHz70jGUlgYrHB08SpqV79c10Wg%3D&reserved=0> to Content-Hints<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3Dc3f089ea-9f7a421e-c3f0c971-86cd58c48020-fa907f7d241a4607%26q%3D1%26e%3D53d226db-a485-4071-a088-4fd7fde00b1e%26u%3Dhttps%253A%252F%252Fw3c.github.io%252Fmst-content-hint%252F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc29a2be15bd040a3532008d75969323f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637076180698174649&sdata=m1chyQklihQWpInbmSyDEHjuJsxR%2BToKcUMOiYTOSDY%3D&reserved=0>?



At TPAC, we discussed feedback on the Content-Hints specification<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3D7e79c7b7-22f30c43-7e79872c-86cd58c48020-c78dd3ba419ac33f%26q%3D1%26e%3D53d226db-a485-4071-a088-4fd7fde00b1e%26u%3Dhttps%253A%252F%252Fw3c.github.io%252Fmst-content-hint%252F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc29a2be15bd040a3532008d75969323f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637076180698174649&sdata=%2FO3g0CLTbq46tm46eo%2FhDIG9xmA%2BYR%2B%2BdBdS5lupu%2BM%3D&reserved=0> which suggested that the specification should include normative language defining the effect of setting various values.  PR 31<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3D859aad0e-d91066fa-859aed95-86cd58c48020-c29fa61bfd357010%26q%3D1%26e%3D53d226db-a485-4071-a088-4fd7fde00b1e%26u%3Dhttps%253A%252F%252Fgithub.com%252Fw3c%252Fmst-content-hint%252Fpull%252F31&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc29a2be15bd040a3532008d75969323f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637076180698184645&sdata=V6b3uTlPVjsyvojxHxt0ynif4snlBMpydmt%2FZRkFVcw%3D&reserved=0> 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.