- From: Mészáros Mihály via GitHub <sysbot+gh@w3.org>
- Date: Sun, 16 May 2021 20:28:48 +0000
- To: public-webrtc-logs@w3.org
AFAIU TURN or relaying may could add some benefit still here too in some edge case. (I don't knwo maybe it is not so edge.) Think about such a use case where the local ISP of the user has limited (crowded, bad quality) commodity uplink network (capacity limitation to International directions), but very good connection to local Internet exchange. If TURN servers are sitting very close to these Internet Exchanges(IX) and your TURN servers has good reliable connection, then TURN still could add some help to the user's media traffic to reach the reliable internet "highway" faster, and so it may gives for them lower latency, or better reliability, (or both) etc.. Somehow it adds an alternative route through the local IX. And we saw from the presentation on Kranky Geek this year, that ISPs (even more the smallest ISPs) routing is not always based on low latency but much more on the cost of the commodity traffic. (demo was about an edge case where multihop SFU routed traffic was ~1s faster then direct connection) So in such use case the direct connection from the client to server is not always the fastest path, and using a relay (TURN or SFU) still make sense. -- GitHub Notification of comment by misi Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2651#issuecomment-841873150 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 16 May 2021 20:28:51 UTC