Re: [webrtc-extensions] Add a CSP check to RTCPeerConnection.constructor(). (#81)

Not sold on the idea:

- I'm not sure CSP is the right interface to modify in order to restrict WebRTC usage; my conversations with @mkwst back in 2018 indicated that there was some thought that CSP was already too complex and that better solutions were coming.
- I saw this idea brought up in 2018 and die for lack of a customer that really wanted it; I'm not sure we have a strong enough customer to get it implemented across browsers this round.

That said, I'm fine with the proposal technically - there are a number of usages of WebRTC that don't involve communication (attempts at inappropriate user tracking, mostly), and I'm not at all unhappy about blocking them rather than waiting until we can signal a "network failure" as a response to an attempt at communication.

So I won't block this at all, but I'm somewhat skeptical of it getting through the process and getting deployed.

-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/81#issuecomment-862633633 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 16 June 2021 19:01:36 UTC