<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks Kristina for the proposal to allow alternates to access
the AC Room. It greatly helps to follow more easily the exchanges
and thus be up to date information in the case where the alternate
must replace a member. I was able to resume the history of the
last exchanges and am therefore ready to follow the meeting later.</p>
<p>Have a nice day</p>
<p>Arnaud<br>
</p>
<div class="moz-cite-prefix">Le 16/08/2018 à 05:35, 'Rosette,
Kristina' via ePDP team a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:c91e7ce1597342c995fecd08db01beb7@EX13D08UWB001.ant.amazon.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:554238801;
mso-list-template-ids:-599633828;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">FYI.
Not sure of the timing of Kurt’s response so recommend that
any comments/proposed changes be provided to Alan, Marc and
Arnaud tomorrow. (Arnaud is acting as Member on my behalf
until Monday.)<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">K<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
Gnso-epdp-team [<a class="moz-txt-link-freetext" href="mailto:gnso-epdp-team-bounces@icann.org">mailto:gnso-epdp-team-bounces@icann.org</a>]
<b>On Behalf Of </b>Kurt Pritz<br>
<b>Sent:</b> Wednesday, August 15, 2018 5:14 PM<br>
<b>To:</b> GNSO EPDP <a class="moz-txt-link-rfc2396E" href="mailto:gnso-epdp-team@icann.org"><gnso-epdp-team@icann.org></a><br>
<b>Subject:</b> [Gnso-epdp-team] Fwd: Coordination
between ICANN org and EPDP<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Everyone: <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Yesterday, I received the email below
from Göran Marby. I wanted those of you who are interested
to see and have the ability to comment on my draft reply,
which is immediately below Göran’s letter.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The reply will be from me so I might not
include all comments - not necessarily because I disagree
with the substance but it might be because of tone, timing
or level of detail. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On the other hand, I’d be foolish not to
consult with you as many of you have been involved with
ICANN efforts at correspondence and issue resolution. If you
have input, I will read and consider it carefully.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am not sure I want to make this a topic
of discussion in tomorrow’s meeting as finishing the triage
is more important. I see the letter as more of an invitation
to start a dialogue where we can integrate efforts, rather
than pursue separate objectives. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Kurt<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Begin forwarded message:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><b><span
style="font-family:"Helvetica",sans-serif">From:
</span>
</b><span
style="font-family:"Helvetica",sans-serif">Goran
Marby <<a href="mailto:goran.marby@icann.org"
moz-do-not-send="true">goran.marby@icann.org</a>></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-family:"Helvetica",sans-serif">Subject:
Coordination between ICANN org and EPDP</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-family:"Helvetica",sans-serif">Date:
</span>
</b><span
style="font-family:"Helvetica",sans-serif">August
14, 2018 at 8:17:13 AM PDT</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-family:"Helvetica",sans-serif">To:
</span>
</b><span
style="font-family:"Helvetica",sans-serif">"<a
href="mailto:rafik.dammak@gmail.com"
moz-do-not-send="true">rafik.dammak@gmail.com</a>"
<<a href="mailto:rafik.dammak@gmail.com"
moz-do-not-send="true">rafik.dammak@gmail.com</a>>,
"<a href="mailto:kurt@kjpritz.com"
moz-do-not-send="true">kurt@kjpritz.com</a>" <<a
href="mailto:kurt@kjpritz.com"
moz-do-not-send="true">kurt@kjpritz.com</a>></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-family:"Helvetica",sans-serif">Cc:
</span>
</b><span
style="font-family:"Helvetica",sans-serif">David
Olive <<a href="mailto:david.olive@icann.org"
moz-do-not-send="true">david.olive@icann.org</a>>,
Theresa Swinehart <<a
href="mailto:theresa.swinehart@icann.org"
moz-do-not-send="true">theresa.swinehart@icann.org</a>>,
John Jeffrey <<a
href="mailto:john.jeffrey@icann.org"
moz-do-not-send="true">john.jeffrey@icann.org</a>>,
"Akram Atallah" <<a
href="mailto:akram.atallah@icann.org"
moz-do-not-send="true">akram.atallah@icann.org</a>>,
Chris Disspain <<a
href="mailto:chris.disspain@board.icann.org"
moz-do-not-send="true">chris.disspain@board.icann.org</a>>,
"<a href="mailto:leon.sanchez@board.icann.org"
moz-do-not-send="true">leon.sanchez@board.icann.org</a>"
<<a href="mailto:leon.sanchez@board.icann.org"
moz-do-not-send="true">leon.sanchez@board.icann.org</a>>,
Cassia Oliveira <<a
href="mailto:cassia.oliveira@icann.org"
moz-do-not-send="true">cassia.oliveira@icann.org</a>></span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Kurt,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri",sans-serif"> </span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Today,
ICANN org held a call to provide community leaders
with updates regarding various GDPR activities.
The slides and recording of the call are available
at<span class="apple-converted-space"> </span><a
href="https://www.icann.org/resources/pages/data-protection-meetings-2017-12-08-en"
moz-do-not-send="true"><span
style="color:#0B4CB4">https://www.icann.org/resources/pages/data-protection-meetings-2017-12-08-en</span></a>.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">On
the call, a few community leaders reinforced the
value of coordination between ICANN org and the
EPDP Working Group, particularly around access
model. To this end, please share with us any
thoughts you might have regarding a process by
which (1) ICANN org can share guidance we receive
from the DPAs and European Data Protection Board
with the EPDP Working Group; and (2) How the EPDP
Working Group will provide input regarding access
to ICANN org to use in our interactions with DPAs
and European Data Protection Board to obtain legal
guidance that will help guide the Working Group in
its work. As you know, we post all information we
receive through our blogs and engage with
stakeholders, also through communications we post
whether through correspondence or comments via<span
class="apple-converted-space"> </span><a
href="mailto:gdpr@icann.org"
moz-do-not-send="true"><span
style="color:#0B4CB4">gdpr@icann.org</span></a>.
I look forward to hearing your thoughts on how we
can continue to strengthen our work together
toward the common goal of having an access model
that is guided by the law and supported by the
community.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif">Best
regards,</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif"> </span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif">Göran
Marby</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif">President
& CEO ICANN</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif">+1(310)
578 8690</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif"> </span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif"> </span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif">Cássia
Oliveira</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif">Sr.
Manager, Office of the President & CEO </span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif"><a
href="mailto:cassia.oliveira@icann.org"
moz-do-not-send="true">cassia.oliveira@icann.org</a></span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif">+1(310)
578 8656</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Dear Goran: <br>
<br>
I have repeated some your email below so that there is a
clear connection between your questions and my responses.<br>
<br>
<span style="color:#0433FF">Today, ICANN org held a call to
provide community leaders with updates regarding various
GDPR activities. The slides and recording of the call are
available at <a
href="https://www.icann.org/resources/pages/data-protection-meetings-2017-12-08-en"
moz-do-not-send="true">https://www.icann.org/resources/pages/data-protection-meetings-2017-12-08-en</a>.<br>
<br>
On the call, a few community leaders reinforced the value
of coordination between ICANN org and the EPDP Working
Group, particularly around access model. To this end,
please share with us any thoughts you might have regarding
a process by which:<br>
<br>
1) ICANN org can share guidance we receive from the
DPAs and European Data Protection Board with the
EPDP Working Group.</span><br>
<br>
a. Through its many recent actions: engaging with the
ICANN community, governments, the EDPB, and others, it is
apparent that ICANN is the midst of executing a plan to
obtain certainty around the various GDPR provisions. It
would be instructive for the EPDP Team if ICANN were to
share its plan (or elements of it) so that the team can
anticipate the receipt (and timing) of new information. It
would also indicate where there is likely no additional
information, i.e., where the team would be left to draw
conclusions based on the information that is already
available. This information would likely cut down on the
number of questions the ICANN Org receives from the team. <br>
<br>
We understand that the plan must have a degree of
informality and be flexible, with each step based upon the
information received in the step before it. However, where
available, it would be instructive to know the planned-for
objectives, expected learnings, a set of ultimate questions
to be answered, planned inquiries, targets and so on.<br>
<br>
b. While ICANN has published each communication, the
findings or results of those communications have not been
organized in anyway of which we know. For example, observers
of the back-and-forth between the ICANN Org and the EDPB
have offered conclusions that can be drawn from these
documents. However, no one has organized those conclusions
in a way that might become a rule set or set of guidelines
for those reviewing the Temporary Specification or creating
an access model.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
Coincidentally, in today’s EPDP meeting such a request was
made: for disclosure of all the communications with the EDPB
and DPAs, the staff commentary to those communications, and
some organization of same.<br>
<br>
c. We also wish to hear of developments related to GDPR
in other industries, if available, such as:<o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
what data processing protocols have been adopted<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
what data processing protocols have been tested in courts<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
what other privacy regimes are in works in other
jurisdictions<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
what data is available regarding:<o:p></o:p></li>
</ol>
<ol start="4" type="1">
<ol start="1" type="1">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level2 lfo1">
the effects of GDPR on malfeasance detection, avoidance<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level2 lfo1">
other positive or negative effects of GDPR<o:p></o:p></li>
</ol>
</ol>
<p class="MsoNormal"><br>
<span style="color:#0433FF">2) How the EPDP Working
Group will provide input regarding access to ICANN org to
use in our interactions with DPAs and European Data
Protection Board to obtain legal guidance that will help
guide the Working Group in its work. As you know, we post
all information we receive through our blogs and engage
with stakeholders, also through communications we post
whether through correspondence or comments via <a
href="mailto:gdpr@icann.org" moz-do-not-send="true">gdpr@icann.org</a>.</span><br>
<br>
a. The EPDP team’s third set of deliverables is to
provide an, “Initial Report and a Final Report regarding the
EPDP Team’s recommendations … for a System for Accredited
Access to Non-Public Registration Data.” Work on this could
begin as early as the completion and publication of the
Initial Report on the Temporary Specification. (The Team
stays in close contact with the GNSO Council leadership in
pursuit of the deliverables to ensure the spirit and letter
of the EPDP Charter is followed.)<br>
<br>
b. While our current answer to this question is not yet
finely honed, it is likely that, from time to time, the EPDP
Team will have question regarding the constraints
/ opportunities imposed by the GDPR. These questions might
take the form of a proposed access model (or elements of an
access model). The EPDP Team will forward those to
ICANN, which, in turn, can test them against its own
knowledge base, with DPAs, with the EDPB, or elsewhere.<br>
<br>
c. As ICANN is a data controller involved in the
collection, use and disclosure of the same data that is the
subject matter of this Team’s work, it is expected that
ICANN will work with the team on the successor to the
Temporary Specification and an access model.<br>
<br>
I hope you find this response helpful. The team is keen to
continue an active correspondence with ICANN in order to
flesh out the framework provided by GDPR with detailed
clarifications, implementation guidance and cases from
other, similarly situated industries that have faced many of
these same issues.<br>
<br>
We also plan to remain in close communication with ICANN
leaders on this topic, through the ICANN-provided liaisons
to the EPDP Team.<br>
<br>
Sincerely,<o:p></o:p></p>
</div>
</div>
-- <br>
You received this message because you are subscribed to the Google
Groups "ePDP team" group.<br>
To unsubscribe from this group and stop receiving emails from it,
send an email to <a
href="mailto:epdp-team+unsubscribe@googlegroups.com"
moz-do-not-send="true">epdp-team+unsubscribe@googlegroups.com</a>.<br>
To post to this group, send email to <a
href="mailto:epdp-team@googlegroups.com" moz-do-not-send="true">epdp-team@googlegroups.com</a>.<br>
To view this discussion on the web visit <a
href="https://groups.google.com/d/msgid/epdp-team/c91e7ce1597342c995fecd08db01beb7%40EX13D08UWB001.ant.amazon.com?utm_medium=email&utm_source=footer"
moz-do-not-send="true">https://groups.google.com/d/msgid/epdp-team/c91e7ce1597342c995fecd08db01beb7%40EX13D08UWB001.ant.amazon.com</a>.<br>
For more options, visit <a
href="https://groups.google.com/d/optout" moz-do-not-send="true">https://groups.google.com/d/optout</a>.<br>
</blockquote>
<br>
<div class="moz-signature"><br>
</div>
</body>
</html>