<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<br>
<div dir="ltr"><br>
On May 31, 2019, at 00:30, jk <<a href="mailto:karklinsj@gmail.com">karklinsj@gmail.com</a>> <br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">May I also propose an experiment to you. Pls step in my shoes for a moment and try to reconcile different opinion of the team and come up with a compromise formulation.<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">Thing that I agree is that we don’t need to waste too much time on working definition. If after further reflections members will not be able to come to a consensual
compromise, I will park the document in the folder – Chair’s proposals.</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>
</blockquote>
<div><br>
</div>
<div>Janis </div>
<div>I understand your situation and appreciate your attempt to mediate a compromise working definition. I think we can agree at this point that we are not going to find that on the definition of access. Based on Amr’s more extensive analysis I believe we just
drop that one from the working definition. It doesn’t mean we drop the whole document. We just don’t agree on “access.”</div>
<div><br>
</div>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="WordSection1">
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></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"> Mueller, Milton L [<a href="mailto:milton@gatech.edu">mailto:milton@gatech.edu</a>]
<br>
<b>Sent:</b> Thursday, May 30, 2019 7:33 PM<br>
<b>To:</b> Janis Karklins <<a href="mailto:karklinsj@gmail.com">karklinsj@gmail.com</a>>;
<a href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a><br>
<b>Cc:</b> <a href="mailto:gnso-epdp-lead@icann.org">gnso-epdp-lead@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-epdp-team] Proposed working definitions of the frequently used terms during the EPDP Phase 2<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Hi, Janis,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">I am still having trouble with this: <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Times",serif;color:black">"The request of third parties for access to full set or subset of non-public gTLD domain name registration data through disclosure policy that is fully compliant with
GDPR and developed as a result of the EPDP."</span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Times",serif;color:black">This definition seems to be straining to get the word "access" into the definition even though the substance of the definition renders the word meaningless. Please do
the following experiment. Delete the words "<span style="background:white">access to full set or subset of</span>" from this definition. This is what you get: </span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Times",serif;color:black;background:white">"The request of third parties for non-public gTLD domain name registration data through disclosure policy that is fully compliant with GDPR and developed
as a result of the EPDP."</span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Times",serif;color:black;background:white">In other words, the definition works fine without the word access. </span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Times",serif;color:black;background:white">So let's be frank and realistic. We have a solid legal basis for talking about access for data subjects and none for access for third parties. Ergo, there
is no reason to include third party requests in the definition of "access" unless we are trying to leverage the definition to lead to a particular policy outcome. </span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Times",serif;color:black;background:white">I respectfully suggest, again, that we stop wasting time trying to impose idiosyncratic and politically motivated definitions on the process, and move
straight on to having the policy debate about what kind of disclosure processes and rights third parties are going to get. That, ultimately, is all that matters. The definitional stuff is just spinning our wheels with political spin and positioning. </span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Times",serif;color:black;background:white">--MM</span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org">gnso-epdp-team-bounces@icann.org</a>>
on behalf of Janis Karklins <<a href="mailto:karklinsj@gmail.com">karklinsj@gmail.com</a>><br>
<b>Sent:</b> Thursday, May 30, 2019 5:59 AM<br>
<b>To:</b> <a href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a><br>
<b>Cc:</b> <a href="mailto:gnso-epdp-lead@icann.org">gnso-epdp-lead@icann.org</a><br>
<b>Subject:</b> [Gnso-epdp-team] Proposed working definitions of the frequently used terms during the EPDP Phase 2</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Dear team members, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Pls see attached the Proposed working definitions of the frequently used terms during the EPDP Phase 2. It takes to account comments made by members and attempts to reconcile divergence of views on interpretation of some terms.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Pls consider this proposal with clear understanding that these are not legal definitions, but only explanatory texts for the use of EPDP Phase 2 only.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I hope you will find proposal as one you can live with. My wish is to endorse this understanding and move further with discussions on the outline of SSAD.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">JK<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<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:Times;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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;}
--></style>
</body>
</html>