<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<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:"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;}
@font-face
{font-family:"Helvetica Neue";
panose-1:2 0 5 3 0 0 0 2 0 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 2 6 3 5 4 5 2 3 4;}
@font-face
{font-family:"Helvetica Neue Light";
panose-1:2 0 4 3 0 0 0 2 0 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Helvetica Neue";}
.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;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue"">Kurt and ePDP Team –
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><br>
RrSG members have discussed this recommendation, and agree with the draft language:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span style="font-size:12.0pt">During Phase 1 of its work, the EPDP Team documented the data processing activities and responsible parties associated with gTLD registration data.<b>
</b>The EPDP Team, accordingly, recommends the inclusion of the data processing activities and responsible parties, outlined below, to be confirmed and documented in the relevant data processing agreements, noting, however, this Recommendation may be affected
by the finalization of the necessary agreements (described elsewhere in this report) that would confirm and define the roles and responsibilities.<o:p></o:p></span></i></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue"">Additionally, we’d like to append the following sentence to the end of this Recommendation:<o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:12.0pt;font-family:"Helvetica Neue"">“To ensure compliance with GDPR and other data protection regulations, these agreements must be in place prior to the enforcement of ePDP policy recommendations."<o:p></o:p></span></i></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue"">This is consistent with statements made at our F2F in Toronto.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><br>
Thanks—<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><br>
J.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica Neue Light"">-------------<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-family:"Helvetica Neue Light";color:#00B050">James Bladel<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-family:"Helvetica Neue Light"">GoDaddy</span><span style="font-size:12.0pt;font-family:"Helvetica Neue Light""><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Gnso-epdp-team <gnso-epdp-team-bounces@icann.org> on behalf of Kurt Pritz <kurt@kjpritz.com><br>
<b>Date: </b>Wednesday, January 23, 2019 at 21:18<br>
<b>To: </b>EPDP <gnso-epdp-team@icann.org><br>
<b>Subject: </b>[Gnso-epdp-team] Recommendation 14 - Responsible Parties: email discussion<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">Hi Everyone:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">With the goal of progressing (even more) issues via email, the leadership team has considered the discussion during the most recent planary conference
call and suggests the following language to capture the agreement in principle that was developed on Recommendation 14 (Responsible Parties).</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">Based on the discussion of the EPDP meeting on 22 Jan 2019, the amendment below is proposed for EPDP Team consideration.</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:10.5pt">Initial Report Language</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">The EPDP Team recommends that the policy includes the following data processing activities as well as responsible parties: <See Initial Report Language>.</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:10.5pt">Plenary Discussion on this Issue</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">It was stated that the EPDP Team documented the data processing activities and responsible parties associated with gTLD registration data based upon
data analysis and facts available at the time of the Phase I discussion.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">The EPDP Team acknowledged that, given the iterative nature between the development of GDPR-compliant agreements and the specification of data processing
activities & responsible parties, whatever Recommendation is made at this time is likely to be affected by the completion of the necessary agreements, i.e., that contract development work would confirm and define the roles and responsibilities.</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:10.5pt">Proposed Updated Language: </span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">During Phase 1 of its work, the EPDP Team documented the data processing activities and responsible parties associated with gTLD registration data.<b>
</b>The EPDP Team, accordingly, recommends the inclusion of the data processing activities and responsible parties, outlined below, to be confirmed and documented in the relevant data processing agreements, noting, however, this Recommendation may be affected
by the finalization of the necessary agreements (described elsewhere in this report) that would confirm and define the roles and responsibilities.</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:10.5pt">Action</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">Please indicate on the mailing list whether you have any concerns about these modifications and/or what other aspects of this recommendation should
be discussed. If there are additional questions for ICANN Compliance that would serve to inform the deliberations on this recommendation, please share these also.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">Deadline: Monday, 28 January, additional email discussion might follow depending on responses.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt">Kurt</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt"> </span><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>