- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Nov 2021 08:11:52 +0000
- To: public-webrtc-logs@w3.org
Going for a summary..... - getCapabilities() has troublesome aspects. One of these is fingerprinting; another one is its synchronous aspect. - the amount of new fingerprint surface exposed by SVC modes is limited - the interaction between setParameters and MediaCapabilities (if any) is not specified, implemented or tested. So it's not clear if this is a clean replacement (now, or in the near future). My current preference is to take three actions: - Follow up on the issue of getCapabilities, suggesting that it can be replaced with MediaCapabilities API, and that it should be deprecated and eventually removed once the specification of MediaCapabilities API is good enough - Ask MediaCapabilities specification authors to add a clear description of how codec settings vetted through MediaCapabilities can be used in the preference-setting calls of the WebRTC API - Ship SVC as-is, including the getCapabilities extension Would that be an acceptable course of action? -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-svc/issues/49#issuecomment-964879351 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 November 2021 08:11:55 UTC