- From: Dominique Hazael-Massieux <notifications@github.com>
- Date: Thu, 31 Mar 2016 08:51:13 -0700
- To: w3ctag/spec-reviews <spec-reviews@noreply.github.com>
Received on Thursday, 31 March 2016 15:51:49 UTC
The [RTCWeb IP Handling draft](https://tools.ietf.org/html/draft-ietf-rtcweb-ip-handling-01) describe the strategies that browsers are invited to adopt to avoid revealing sensitive IP addresses. Essentially: * by default, only "safe" IP addresses get exposed; this includes so called "private" IP addresses (e.g. `192.168.0.1`) since in practice they don't reveal much, but not hidden-by-VPN IP addresses * once camera/mic access has been granted, more IP addresses get exposed to find more network efficient paths * browsers should provide a mechanism to never reveal any other IP address than the public one --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/spec-reviews/issues/14#issuecomment-203995268
Received on Thursday, 31 March 2016 15:51:49 UTC