Re: [webrtc-pc] simple webrtc connection and manual signaling (QR, JSON, Carrier pigeon) - consent time out prevents connection (#2945)

The issue is that both sides need to perform their ICE checks around the same time. However each side will start their ICE processing when given the first candidate, so if signaling is slower than 10-15 seconds, this is hard to coordinate.

With some NATs, having only the initiator start ICE processing might work (answerer will use triggered checks). But if the NAT requires a pinhole to be created first, that won't fly.

Don't think the DTLS direction will have much effect as the key issue is at the ICE layer, I think.




-- 
GitHub Notification of comment by juberti
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2945#issuecomment-1965876503 using your GitHub account


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

Received on Tuesday, 27 February 2024 06:33:25 UTC