- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 May 2020 12:54:06 +0000
- To: public-webrtc-logs@w3.org
Suggested fix: Add to the "in parallel" steps on https://w3c.github.io/webrtc-pc/#dom-peerconnection-addicecandidate: "If the candidate is disallowed by policy, reject the promise with a newly created InvalidAccessError" For canddiates present in a remote description, rejecting a description based on a single bad candidate seems excessive. I suggest adding to https://w3c.github.io/webrtc-pc/#set-description, as step 4 under "apply as JSEP with these restrictions": "Any candidates in the remote description that are disallowed by policy MUST be ignored, and MUST be removed from the SDP before it is set as PendingRemoteDescription." -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2534#issuecomment-634006039 using your GitHub account
Received on Tuesday, 26 May 2020 12:54:07 UTC