- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Oct 2018 17:18:15 +0000
- To: public-webrtc-logs@w3.org
> MDNS might be used to expose non default route candidates for some of these cases. When I initially filed [Webkit bug 174500](https://bugs.webkit.org/show_bug.cgi?id=174500), I was really excited about the mDNS approach being used to resolve it. I was probably one of the very first to cheer this on and hoped that mDNS would be used for the exact purpose you are mentioning - hiding non-default route candidates for applications that don't have consent. But so far, it went in the opposite direction. And while using mDNS to hide non-default route candidates would likely improve the situation, I'm convinced that we will see *consent* vs. *no consent* diverge further. Thus, the only resolution I see is that we need to allow non-`getUserMedia` use cases to obtain user consent to prevent further discrimination and having this reproach bubbling up every time new *consent*-bound things are being discussed. -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2012#issuecomment-432338835 using your GitHub account
Received on Tuesday, 23 October 2018 17:18:17 UTC