W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2020

[webrtc-pc] Describe what happens with administratively prohibited candidates (#2531)

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Thu, 14 May 2020 14:15:06 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-618267290-1589465705-sysbot+gh@w3.org> 
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc:

== Describe what happens with administratively prohibited candidates ==
If a TCP candidate is connecting to a port on the Do-not-connect list (from Fetch), something should happen to the candidate, and a connection attempt should not be made.

It seems OK to do what Chrome currently does, and just ignore the candidate - it does not show up in stats, in remote-description or in GetRemoteCandidates.


Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2531 using your GitHub account
Received on Thursday, 14 May 2020 14:15:08 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 14 May 2020 14:15:08 UTC