<div dir="ltr"><div dir="ltr"><div><br></div><div><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 10pt;line-height:13.5pt"><span lang="EN-US" style="color:rgb(34,34,34);letter-spacing:0.25pt;font-family:"Arial","sans-serif";font-size:7pt">DeDear Kurt,</span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 0pt;line-height:13.5pt"><span lang="EN-US" style="color:rgb(34,34,34);letter-spacing:0.25pt;font-family:"Arial","sans-serif";font-size:7pt">Subject
to further refinement of the text by other Team member, I found the language
you proposed a way forward to fix the problem and ready to finalize the report</span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 0pt;line-height:13.5pt"><span style="color:rgb(34,34,34);letter-spacing:0.25pt;font-family:"Arial","sans-serif";font-size:7pt">regards</span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:13.5pt"><span style="color:rgb(34,34,34);letter-spacing:0.25pt;font-family:"Arial","sans-serif";font-size:7pt">kavouss </span></p><font color="#000000" face="Times New Roman" size="3">
</font></div><div><br></div></div></div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Thu, Jan 24, 2019 at 4:18 AM Kurt Pritz <<a href="mailto:kurt@kjpritz.com">kurt@kjpritz.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div style="-ms-word-wrap: break-word;"><div style="-ms-word-wrap: break-word;">
<p class="MsoNormal"><span style="font-size:14px">Hi Everyone:</span></p><p class="MsoNormal"><span style="font-size:14px">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></p><p class="MsoNormal"><span style="font-size:14px">Based on the discussion of
the EPDP meeting on 22 Jan 2019, the amendment below is proposed for EPDP Team
consideration.</span></p><div><span style="font-size:14px"><br></span></div><p class="MsoNormal"><b><span style="font-size:14px">Initial Report Language</span></b></p><p class="MsoNormal"><span style="font-size:14px">The EPDP
Team recommends that the policy includes the following data processing activities
as well as responsible parties: <See Initial Report Language>.</span></p><div><span style="font-size:14px"><br></span></div><p class="MsoNormal"><b><span style="font-size:14px">Plenary Discussion on this Issue</span></b></p><p class="MsoNormal"><span style="font-size:14px">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></p><p class="MsoNormal"><span style="font-size:14px">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></p><div><span style="font-size:14px"><br></span></div><p class="MsoNormal"><span style="font-size:14px"><b><span>Proposed Updated Language:</span></b><b><span> </span></b></span></p><p class="MsoNormal"><span style="font-size:14px">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></p><div><span style="font-size:14px"><br></span></div><p class="MsoNormal"><b><span style="font-size:14px">Action</span></b></p><p class="MsoNormal"><span style="font-size:14px">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></p><p class="MsoNormal"><span style="font-size:14px">Deadline: Monday, 28 January,
additional email discussion might follow depending on responses.</span></p><p class="MsoNormal"><span style="font-size:14px"><br></span></p><p class="MsoNormal"><span style="font-size:14px">Best regards,</span></p><p class="MsoNormal"><span style="font-size:14px"><span>Kurt</span><span style="font-family:-webkit-standard,serif"><u></u><u></u></span></span></p><div><span style="font-size:14px"> </span><br class="gmail-m_-4936684769274848370webkit-block-placeholder"></div>
</div></div>_______________________________________________<br>
Gnso-epdp-team mailing list<br>
<a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></blockquote></div>