- From: docfaraday via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Dec 2021 17:31:19 +0000
- To: public-webrtc-logs@w3.org
> > Hmm. Just because we have received no candidates from the other end does not mean we're sunk. If the other side is able to get an ICE check to land on us, that gives us a peer reflexive candidate to work with, and ICE can then succeed. > > I can't follow tbh. In which case would the UA not emit **any** candidates (not even mDNS ones), then signal `end-of-candidates` but still be able to send connectivity checks? If there are no STUN/TURN servers configured, and the service (or browser) is configured to hide host candidates, and the browser is behind a NAT, we will end up in this exact situation. -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2698#issuecomment-985701181 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 December 2021 17:31:21 UTC