- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Sep 2021 11:22:01 +0000
- To: public-webrtc-logs@w3.org
Treating all remote candidates as adminstratively prohibited (ie not causing a connection attempt) would indeed prevent RTCPeerConnection from making a connection to a remote site. As outlined in https://w3c.github.io/webrtc-pc/#dfn-administratively-prohibited, it would not give any signal to the user on why the connection failed. It does not prevent usage of an RTCPeerConnection for strictly local purposes, like trying to gather local interface information, but since that's not the goal of CSP checks, I think that's OK. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/81#issuecomment-911557530 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 September 2021 11:22:03 UTC