<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23942">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=宋体>+1</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 9pt 宋体">----- Original Message ----- </DIV>
<DIV style="FONT: 9pt 宋体; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=alan.greenberg@mcgill.ca href="mailto:alan.greenberg@mcgill.ca">Alan
Greenberg</A> </DIV>
<DIV style="FONT: 9pt 宋体"><B>To:</B> <A title=carlton.samuels@gmail.com
href="mailto:carlton.samuels@gmail.com">Carlton Samuels</A> ; <A
title=bastiaan.goslings@ams-ix.net
href="mailto:bastiaan.goslings@ams-ix.net">Bastiaan Goslings</A> </DIV>
<DIV style="FONT: 9pt 宋体"><B>Cc:</B> <A title=ALAC@atlarge-lists.icann.org
href="mailto:ALAC@atlarge-lists.icann.org">ALAC Working List</A> </DIV>
<DIV style="FONT: 9pt 宋体"><B>Sent:</B> Wednesday, July 11, 2018 11:27 PM</DIV>
<DIV style="FONT: 9pt 宋体"><B>Subject:</B> Re: [ALAC] Draft Principles for
GDPR</DIV>
<DIV><BR></DIV>Carlton, I think that this is THE answer to the question of why
At-Large needs to participate in this process. There are likely to be few GNSO
participants that look at it from this perspective.<BR><BR>See my comment at
<A href="https://community.icann.org/x/_YlHBQ"
eudora="autourl">https://community.icann.org/x/_YlHBQ</A>.<BR><BR>Alan<BR><BR>At
11/07/2018 11:10 AM, Carlton Samuels wrote:<BR>
<BLOCKQUOTE class=cite cite="" type="cite">A good piece to introduce here.
So we not mis read this let me state how the end user interest is
inextricably conjoined with "third parties".<BR><BR>The first is the
protection of end users from predators and predatory practices enabled by
the DNS. The vast majority of end users would not know a WHOIS record even
it jumped up and bit them in the butt. We depend on others to help us, to be
on the line for our collective sake.<BR><BR>These surrogates, if you will,
include the reputation companies, the antivirus folks, the researchers and a
whole amalgam of third party interests. <BR><BR>When the end user gets a
green tick that says this is a safe website, it protects the end user. That
springs from the work of reputation companies. Accesd to WHOIS data is
vested in their formulaic response that keeps me from wandering,
mouth-breathing, into dangerous territory. <BR><BR>ICANN and the entire
chain of connections in the DNS infrastructure has a role, each from a
slightly different perspective. But reputation is not a sole interest as it
is for these guys. And the end user is a beneficiary of this interest, which
kicks in long way before the mainline DNS actors.<BR><BR>This is just one
example. But let us be clear. That end user interests are defended by
surrogates and so-called third parties is not an outlier. I would argue it
is the central case.<BR><BR>The ALAC may not argue for end user interests
absent an appreciation of the role in defending those interests by third
parties. That would be a failure to recognize the facts as they are...and an
egregious abdication of responsibilities.<BR><BR>-Carlton<BR><BR>On Wed, 11
Jul 2018, 7:51 am Bastiaan Goslings, <<A
href="mailto:bastiaan.goslings@ams-ix.net">
bastiaan.goslings@ams-ix.net</A>> wrote:<BR>
<DL>
<DD>I think I can agree with both Jonathan/Alan and Tijani on this. And as
a matter of principle I’d therefore suggest to follow what the EDPB says
on page 2 <A
href="https://www.icann.org/en/system/files/correspondence/jelinek-to-marby-05jul18-en.pdf">https://www.icann.org/en/system/files/correspondence/jelinek-to-marby-05jul18-en.pdf</A>
<BR><BR>
<DD>’The EDPB considers it essential that a clear distinction be
maintained between the different processing activities that take place in
the context of WHOIS and the respective purposes pursued by the various
stakeholders involved. (…) The EDPB therefore reiterates that ICANN should
taake care not to conflate its own purposes with the interests of third
parties, nor with the lawful grounds of processing which may be applicable
in a particular case’<BR><BR><BR><BR>
<DD>> On 11 Jul 2018, at 12:17, <A
href="mailto:h.raiche@internode.on.net">h.raiche@internode.on.net</A>
wrote:<BR>
<DD>> <BR>
<DD>> Hi Tijani<BR>
<DD>> <BR>
<DD>> I think we can both agree that it is about the public
interest. And while privacy is a big part of that, so are other
issues - a safe, stable DNS etc.<BR>
<DD>> <BR>
<DD>> I have asked that this discussion is on the wiki so that there is
a place for everyone to contribute - and I hope you will participate as
well.<BR>
<DD>> <BR>
<DD>> We need agreed principles for the people who will sit on the EpDP
- which means we need to hear from everyone - you included<BR>
<DD>> <BR>
<DD>> Holly<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> ----- Original Message -----<BR>
<DD>> From:<BR>
<DD>> "Tijani BEN JEMAA" <<A
href="mailto:tijani.benjemaa@benjemaa.com">
tijani.benjemaa@benjemaa.com</A>><BR>
<DD>> <BR>
<DD>> To:<BR>
<DD>> "Jonathan Zuck" <<A href="mailto:JZuck@innovatorsnetwork.org">
JZuck@innovatorsnetwork.org</A>><BR>
<DD>> Cc:<BR>
<DD>> "<A href="mailto:h.raiche@internodeon.net">
h.raiche@internodeon.net</A>" <<A
href="mailto:h.raiche@internode.on.net">
h.raiche@internode.on.net</A>>, "ALAC List" <<A
href="mailto:alac@atlarge-lists.icann.org">
alac@atlarge-lists.icann.org</A>>, "A t" <<A
href="mailto:staff@atlarge.icann.org">staff@atlarge.icann.org</A> ><BR>
<DD>> Sent:<BR>
<DD>> Wed, 11 Jul 2018 09:33:16 +0100<BR>
<DD>> Subject:<BR>
<DD>> Re: [ALAC] Draft Principles for GDPR<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Good morning everyone,<BR>
<DD>> <BR>
<DD>> I disagree with this statement Jonathan.<BR>
<DD>> The registrants represent the active part of the end-users. we
are responsible to defend their interest.<BR>
<DD>> I have heard such reflection, and it always lead to be more
aligned with the commercial interests. We need to be careful and be always
for the public interest, not for the political or commercial
interests.<BR>
<DD>> <BR>
<DD>>
-----------------------------------------------------------------------------<BR>
<DD>> Tijani BEN JEMAA<BR>
<DD>> Executive Director<BR>
<DD>> Mediterranean Federation of Internet Associations (FMAI)<BR>
<DD>> Phone: +216 98 330 114<BR>
<DD>> +216 52 385 114<BR>
<DD>>
-----------------------------------------------------------------------------<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Le 10 juil. 2018 Ã 22:27, Jonathan Zuck <<A
href="mailto:JZuck@innovatorsnetwork.org">
JZuck@innovatorsnetwork.org</A>> a écrit :<BR>
<DD>> <BR>
<DD>> Thanks Holly for getting this started. I guess what we’re
after are some basic principles on our perspective on the GDPR. The temp
spec is the temp spec so some of this will apply for sure, if we reach
some consensus on these but there are areas that are simply part of the
law over which we don’t have influence. A principle might be something
like<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> • The ALAC feels responsible to
reprresent the interests of non-registrants more so than registrants as
they represent the majority of users.<BR>
<DD>> <BR>
<DD>> I’m not saying we’ve agreed to that but that’s the kind of
filter we could send our reps in with?<BR>
<DD>> <BR>
<DD>> Jonathan<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> From: ALAC <<A
href="mailto:alac-bounces@atlarge-lists.icann.org">
alac-bounces@atlarge-lists.icann.org</A>> on behalf of "<A
href="mailto:h.raiche@internode.on.net"> h.raiche@internode.on.net</A>"
<h.raiche@internode.onnet><BR>
<DD>> Reply-To: "<A href="mailto:h.raiche@internode.on.net">
h.raiche@internode.on.net</A>" <<A
href="mailto:h.raiche@internode.on.net">
h.raiche@internode.on.net</A>><BR>
<DD>> Date: Tuesday, July 10, 2018 at 5:22 PM<BR>
<DD>> To: ALAC List <<A href="mailto:alac@atlarge-lists.icann.org">
alac@atlarge-lists.icann.org</A>>, A t <<A
href="mailto:staff@atlarge.icann.org">staff@atlarge.icann.org</A> ><BR>
<DD>> Subject: [ALAC] Draft Principles for GDPR<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Folks<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Since we all think principles are a good idea, I have set down
the basics from the Temporary Spec - very simplistic, but it's a
start. What we need now is discussion on the principles.<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Evin - I'm not sure if you have a new wiki page for discussion on
the temporary spec, but if not, would you create on.<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> And Olivier - the Temporary Spec necessarily will deal with
access - at the least, guiding principles, so whoever is on the EPDP will
have some guidance on our red lines on access.<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> So please everyone - comments<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Thanks<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Holly<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Temporary Specification for gTLD Registration Data<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Principles for requirements to replace the RAA/Registry
Requirements<BR>
<DD>> <BR>
<DD>> (within the context of compliance with the GDPR)<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Purpose of Collection of Data<BR>
<DD>> <BR>
<DD>> Quoting from the Temporary Spec – which is quoting from the
ICCANN Bylaws:<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> purpose is to coordinate the bottom-up, multistakeholder
development and implementation of policies “[f]or which uniform or
coordinated resolution is reasonably necessary to facilitate the openness,
interoperability, resilience, security and/or stability of the DNS
including, with respect to gTLD registrars and registriesâ€<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Purpose includes<BR>
<DD>> <BR>
<DD>> · ô°‚ resolution of disputes
regarding the registration of domain names (as opposed to the use of such
domain names, but including where such policies take into account use of
the domain names);<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> · ô°‚ maintenance of and access
to accurate and up-to-date information concerning registered names and
name servers;<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> · ô°‚ procedures to avoid
disruptions of domain name registrations due to suspension or termination
of operations by a registry operator or a registrar (e.g., escrow);
and<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> · ô°‚ the transfer of
registration data upon a change in registrar sponsoring one or more
registered names.<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> the Bylaws specifically obligate ICANN, in carrying out its
mandate, to “adequately address issues of competition, consumer
protection, security, stability and resiliency, malicious abuse issues,
sovereignty concerns, and rights protectionâ€<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Geographic Coverage of EPDP Outcome:<BR>
<DD>> <BR>
<DD>> · Apply globally or<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> · Apply only to European Economic Area (the
coverage of the GD<BR>
<DD>> R) and otherwise lesser requirements (existing RAA
requirements?)<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Data Collected<BR>
<DD>> <BR>
<DD>> · ‘Thick Whois†– bassed on the differing
uses of the data is listed in the purpose above – OR<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> · Some lesser amount of information<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Consent<BR>
<DD>> <BR>
<DD>> · Registrants must be told, at the time of
collection, what personal information is collected, why the collection
is necessary to achieve the purposes, who will have access and in
what circumstances access will be given to what information, and all
circumstances in which the data will be transferred (to Registry, Escrow)
and where heldThey must also be told their consent can be withdrawn at any
time (and consequences of withdrawal) and how to withdraw consent<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> Access to Data – Tiered access (largely what is in the Techniccal
Specification)<BR>
<DD>> <BR>
<DD>> · Applies to all Registrants – naturaal or
corporate persons<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> · Information generally publicly available<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> o Registrant name<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> o Anonymised email or other anonymous contact
means<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> · Access to other personal information –<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> o Only to accredited entities (not individuals)– >
<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> o Only in specific circumstances that warrant
access<BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> <BR>
<DD>> _______________________________________________<BR>
<DD>> ALAC mailing list<BR>
<DD>> <A
href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</A><BR>
<DD>> <A href="https://atlarge-lists.icann.org/mailman/listinfo/alac"
eudora="autourl">https://atlarge-lists.icann.org/mailman/listinfo/alac</A><BR>
<DD>> <BR>
<DD>> At-Large Online: <A
href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</A> <BR>
<DD>> ALAC Working Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</A>
<BR>
<DD>> <BR>
<DD>> _______________________________________________<BR>
<DD>> ALAC mailing list<BR>
<DD>> <A
href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</A><BR>
<DD>> <A href="https://atlarge-lists.icann.org/mailman/listinfo/alac"
eudora="autourl">https://atlarge-lists.icann.org/mailman/listinfo/alac</A><BR>
<DD>> <BR>
<DD>> At-Large Online: <A
href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</A> <BR>
<DD>> ALAC Working Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</A>
<BR><BR>
<DD>_______________________________________________<BR>
<DD>ALAC mailing list<BR>
<DD><A
href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</A><BR>
<DD><A href="https://atlarge-lists.icann.org/mailman/listinfo/alac"
eudora="autourl">https://atlarge-lists.icann.org/mailman/listinfo/alac</A><BR><BR>
<DD>At-Large Online: <A
href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</A> <BR>
<DD>ALAC Working Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</A>
<BR><BR></DD></DL>_______________________________________________<BR>ALAC
mailing list<BR>ALAC@atlarge-lists.icann.org<BR><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac"
eudora="autourl">https://atlarge-lists.icann.org/mailman/listinfo/alac</A><BR><BR>At-Large
Online: <A href="http://www.atlarge.icann.org/"
eudora="autourl">http://www.atlarge.icann.org</A><BR>ALAC Working Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC"
eudora="autourl">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</A>
)</BLOCKQUOTE>
<P>
<HR>
<P></P>_______________________________________________<BR>ALAC mailing
list<BR>ALAC@atlarge-lists.icann.org<BR>https://atlarge-lists.icann.org/mailman/listinfo/alac<BR><BR>At-Large
Online: http://www.atlarge.icann.org<BR>ALAC Working Wiki:
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</BLOCKQUOTE></BODY></HTML>