[gnso-rds-pdp-wg] ICANN Meetings/Conversations with Data Protection and Privacy Commissioners

[allison nixon]

Can someone clearly and plainly explain why social media exposure is
permissible but whois is not, given that both have privacy settings that
can be invoked

there is no logical consistency for why social media is fine as-is but
whois must be locked down. This only makes sense logically if the privacy
controls youall offer to your customers are broken and do not legally
qualify as obtaining consent. so please explain

On Tue, Sep 26, 2017 at 12:13 PM, Dotzero <dotzero at gmail.com> wrote:

> You are raising a different discussion/issue Andrew. A discussion of what
> the working group thinks is appropriate is a different discussion vs
> assertions as to the legal requirements from various jurisdictions as to
> what we are obliged to do.
>
> I keep on hearing law invoked and therefore asked what precedent there is
> specific to whois and CBDF. It's a straight forward question and with the
> various privacy and legal experts on the list, one that should be easily
> answered if there are precedents specific to whois out there. Volker threw
> up a laundry list of references that don't really apply to the question I
> asked.
>
> Michael Hammer
>
> On Tue, Sep 26, 2017 at 11:12 AM, Andrew Sullivan <ajs at anvilwalrusden.com>
> wrote:
>
>> On Tue, Sep 26, 2017 at 10:59:15AM -0400, Dotzero wrote:
>> > predecessor regulations have been around for quite some time and if the
>> > whois privacy issues we have been debating are truly a significant
>> problem
>> > to the extent that some represent them to be, I would expect that there
>> > would have been at least some sort of precedents specific to whois.
>>
>> I think that, regardless of any legal cases, the current whois leaks
>> way too much information.  ICANN has an enormous bureaucracy around
>> "whois accuracy" partly (but only partly) because ordinary people
>> don't want to pay extra to keep their home telephone numbers off from
>> being wide open on the Internet, so they lie about it.  There is _no
>> reason_ that we are still using an ancient protocol that was designed
>> for a completely different network environment.
>>
>> The IAB recommends, in RFC 6973, that protocols do something about
>> data minimization (see section 6.1).  The evidence we have is that
>> greater exposure of data provides a vector for attacks we haven't even
>> thought about.  Therefore, we should not expose data to everyone
>> unless we are sure that it is necessary (and some of this data _is_
>> necessary to expose to everyone); and we should be able to track who
>> got the data if we're exposing data that is not published to everyone.
>>
>> I don't think any of this should be news, and I think it is really
>> strange that we seem still to be discussing whether it is something we
>> need to embrace.
>>
>> Best regards,
>>
>> A
>>
>>
>> --
>> Andrew Sullivan
>> ajs at anvilwalrusden.com
>> _______________________________________________
>> gnso-rds-pdp-wg mailing list
>> gnso-rds-pdp-wg at icann.org
>> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
>>
>
>
> _______________________________________________
> gnso-rds-pdp-wg mailing list
> gnso-rds-pdp-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
>



-- 
_________________________________
Note to self: Pillage BEFORE burning.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20170926/ceec67c9/attachment.html>