W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2018

Re: WebRTC NV Use Cases

From: Lennart Grahl <lennart.grahl@gmail.com>
Date: Tue, 22 May 2018 21:27:49 +0200
To: public-webrtc@w3.org
Message-ID: <12be336a-f273-4f65-0857-8da737dd65ac@gmail.com>
As a supplement to the "mandatory permission request" idea:

I think we should try to find a way how to resolve the issue with IPs 
leaking in WebRTC, optimally without impacting the ability to establish 
direct connections. Using mode 3 by default (which Apple's Safari 
already does) would significantly hamper the ability to establish a 
direct connection. Moreover, this would have a significantly negative 
impact on applications where high throughput is required. The permission 
request idea is a cheap way to fix this but probably not optimal either 
because permission requests are always annoying and others have raised 
concerns that the user may not be able to understand the permission request.
However, there may be another solution: Youenn Fablet has added a 
feature to Safari that allows the use of temporary host names created 
and resolved by using mDNS to hide the IPs (see 
https://bugs.webkit.org/show_bug.cgi?id=174500). I think this is a 
clever approach and we should discuss it. Maybe Youenn or other Safari 
folks can also share their experiences with it.

Cheers
Lennart


On 22.05.2018 20:54, Lennart Grahl wrote:
> [...]
> 
> ## High Throughput / High Performance
> 
> [...]
> 
> Ideas:
> [...]
> - API: A mandatory permission request for direct connections (mode 1) as 
> an alternative to gUM. Other non-A/V or A/V receive only use cases would 
> also benefit from that. This would also solve our problems with privacy 
> extensions that hate WebRTC for leaking IPs because we could possibly go 
> restrictive (srflx) by default.
> 
> [...]
Received on Tuesday, 22 May 2018 19:28:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:41 UTC