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

Re: [webrtc-stats] Is exposing a remote peer IP address through RTCIceCandidateStats.address a privacy issue

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Wed, 10 Oct 2018 00:06:24 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-428393930-1539129983-sysbot+gh@w3.org>
Is there value in exposing those IP addresses in WebRTC stats. From what I heard in https://github.com/w3c/webrtc-stats/issues/374, value might be low (but maybe I am wrong...).

Knowing the value, we should weight it against potential countermeasures.

As to whether a peer wants to disclose its addresses, this is done by providing or not its candidates to the other peer. I do not think we should tie this to mdns, this applies to regular host candidates as well.
IIANM, by definition, prflx means that the STUN sender has not disclosed its IP address.

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/375#issuecomment-428393930 using your GitHub account
Received on Wednesday, 10 October 2018 00:06:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:07 UTC