<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi all,<div>Thanks for making this suggestion. It does seem to raise questions and I am afraid I also have some. </div><div><br></div><div>The reference to <br><blockquote type="cite"><div dir="ltr"><div class="WordSection1"><p class="MsoNormal"><span style="color: rgb(255, 0, 0);"><br></span></p><p class="MsoNormal"><span style="color: rgb(255, 0, 0);">obligations applicable to regulated entities.</span></p><p class="MsoNormal"><span style="color: rgb(255, 0, 0);"> </span></p></div></div></blockquote><div><br></div>Including the footnote is very broad and maybe too unspecific to be a permissible purpose. We have been advised before that enumerations with „including“, „such as“ etc don’t work. In addition to that the NIS Directive is not a regulation as GDPR so that national implementation varies quite significantly and we might not offer clarity with the example, but confusion. </div><div><br></div><div>Best,</div><div>Thomas</div><div><div dir="ltr"><div><span style="font-size: 13pt;">========</span></div><div>PS - <span style="background-color: rgba(255, 255, 255, 0);">Sent from my cell. Please excuse typos and brevity.</span></div></div><div dir="ltr"><br><blockquote type="cite">Am 27.07.2020 um 17:54 schrieb Crossman, Matthew via Gnso-epdp-team <gnso-epdp-team@icann.org>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
{mso-style-priority:99;
mso-style-link:"Footnote Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
span.MsoFootnoteReference
{mso-style-priority:99;
vertical-align:super;}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.FootnoteTextChar
{mso-style-name:"Footnote Text Char";
mso-style-priority:99;
mso-style-link:"Footnote Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
/* Page Definitions */
@page
{mso-endnote-separator:url("cid:header.htm\@01D663F3.7A920140") es;
mso-endnote-continuation-separator:url("cid:header.htm\@01D663F3.7A920140") ecs;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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">Hi team,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As an update, Margie, Brian, and I worked on a compromise for the Rec 7 language on Requestor Purposes. We agreed on the following edit to 7.1(a):<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>7.1(a)<o:p></o:p></u></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Requestors MUST submit data disclosure requests for specific purposes such as but not limited to: but not limited to: (i) criminal law enforcement, national or public security, (ii) non law enforcement investigations and civil claims, including,
intellectual property infringement and UDRP and URS claims, <span style="color:red">
(iii) consumer protection, abuse prevention, and network security, and (iv) obligations applicable to regulated entities.</span><a style="mso-footnote-id:ftn1" href="#_ftn1" name="_ftnref1" title=""><span class="MsoFootnoteReference"><span style="font-size:10.0pt;color:red">[1]</span></span></a><span style="font-size:10.0pt;color:red">
</span>Requestors MAY also submit data verification requests on the basis of Registered Name Holder (RNH) consent that has been obtained by the Requestor (and is at the sole responsibility of that Requestor), for example to validate the RNH’s claim of ownership
of a domain name registration, or contract with the Requestor.<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">(Footnote below)<o:p></o:p></p>
<p class="MsoNormal"><span class="MsoFootnoteReference"><span style="font-size:10.0pt;color:red">1
</span></span><span style="font-size:10.0pt;color:red"> </span><span style="color:red">For example, the EU Directive on security of network and information systems (known as the NIS Directive) imposes specific obligations on Digital Service Providers and Operators
of Essential Services.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:red"><o:p> </o:p></span></p>
<p class="MsoNormal">With these changes this is no longer a CLW item for the RySG. Let us know if this new language causes any concern for other groups.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<br>
Matt<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;color:black">Matthew Crossman</span></b><span style="font-size:10.0pt;color:#FF9900">
</span><span style="font-size:10.0pt;color:#44546A">| </span><b><span style="font-size:10.0pt;color:#F79646">Amazon</span></b><span style="font-size:10.0pt;color:#FF9900">
<br>
</span><span style="font-size:10.0pt">Corporate Counsel gTLD Registry, IP<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">P: </span><span style="font-size:10.0pt">206-266-1103
</span><span style="font-size:10.0pt">| C: 530-574-2956<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Email: <a href="mailto:mmcross@amazon.com">
<span style="color:#0563C1">mmcross@amazon.com</span></a> <o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div style="mso-element:footnote-list"><br clear="all">
<hr align="left" size="1" width="33%">
<div style="mso-element:footnote" id="ftn1">
<p class="MsoFootnoteText"><a style="mso-footnote-id:ftn1" href="#_ftnref1" name="_ftn1" title=""><span class="MsoFootnoteReference">[1]</span></a> This approach is very similar to the business model ARSI had previously discussed with the Author Central Pro
teams for the .AUTHOR TLD.<o:p></o:p></p>
</div>
</div>
<span>_______________________________________________</span><br><span>Gnso-epdp-team mailing list</span><br><span>Gnso-epdp-team@icann.org</span><br><span>https://mm.icann.org/mailman/listinfo/gnso-epdp-team</span><br><span>_______________________________________________</span><br><span>By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</span></div></blockquote></div></body></html>