- From: Roman Shpount via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 May 2020 07:05:07 +0000
- To: public-webrtc-logs@w3.org
Another way of dealing with this would be to only resolve FQDN candidates if some sort of DNS obfuscation mechanism, such as DNS-over-HTTPS or forwarding to a well known DNS server over TURN is used. FQDN candidates should be ignored otherwise (they are not actually used in practice for anything except .local). If anyone thought through FQDN candidate use cases, they would have added FQDN address support to TURN allocate requests. -- GitHub Notification of comment by rshpount Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2533#issuecomment-634470925 using your GitHub account
Received on Wednesday, 27 May 2020 07:05:09 UTC