Re: Feature at risk: DegradationPreference

I agree with Stefan.  Content-Hints and degradationPreference are related so they belong together.
________________________________
From: Harald Alvestrand <harald@alvestrand.no>
Sent: Friday, October 18, 2019 12:05 AM
To: public-webrtc@w3.org <public-webrtc@w3.org>
Subject: Feature at risk: DegradationPreference

It seems that we missed one feature in our list of unimplemented
features: DegradationPreference -
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwebrtc-pc%2F%23dom-rtcrtpsendparameters-degradationpreference&amp;data=02%7C01%7CBernard.Aboba%40microsoft.com%7C50f4fe53a9b04e2f021f08d75399d472%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637069792484493198&amp;sdata=kcjuqT0ACbov61HNAVpYu8aW9YZ%2BmyYGMCProJ3W8Xo%3D&amp;reserved=0

No browser has currently implemented support for this beyond setting and
getting its value, according to the reports we have.

The chairs have discussed this issue, and the fact that the
functionality of degradationPreference is significantly overlapping with
what Content-Hint (https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fmst-content-hint%2F&amp;data=02%7C01%7CBernard.Aboba%40microsoft.com%7C50f4fe53a9b04e2f021f08d75399d472%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637069792484493198&amp;sdata=OQDohGnfhPnPDqopaD4ar6t6ls9nB%2FXGu1vXTU0M3YM%3D&amp;reserved=0) is intended
to achieve.

We thus suggest that we move the degradationPreference property to the
content-hint spec, so that both of these features can be considered on
their own, without becoming undocumented, and without blocking the
progress of WebRTC 1.0 to Proposed Recommendation.

Comments welcome.

Harald, for the chairs