- From: Tim Panton via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Jan 2023 11:09:07 +0000
- To: public-webrtc-logs@w3.org
I'd like to see numbers on the delay caused by IPV6 collection because : a) I expect almost all IPV6 host addresses are collected quickly (no stun rtt needed) b) Any delay is avoidable by using trickle ice. c) I'd expect the IPV4 TURN TLS candidate to arrive last - so you'll have to wait for that anyway - (this is the works-everywhere fallback candidate) I do agree that it is sometimes useful to filter the received candidates to those that are likely to succeed - but that really is best done at the receiving end. -- GitHub Notification of comment by steely-glint Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/138#issuecomment-1378586493 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 January 2023 11:09:08 UTC