<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>This purpose description seems to be a significant case of
mission creep by including non-technical uses under the
commitment of section 1.2(a)(i), which should remain focussed on
the technical role of ICANN of maintaining a secure, stable and
resiliant DNS. <br>
</p>
<p>Adding in fraud or crime prevention expends the scope beyond that
contemplated in the bylaws and should be rejected.<br>
</p>
<p>The best definition of this purpose is included in the bylaws
under the scope of the <abbr title="Security – Security,
Stability and Resiliency (SSR)" class="">Security</abbr>, <abbr
title="Security, Stability and Resiliency" class="">Stability</abbr>,
and <abbr title="Security Stability & Resiliency (SSR)"
class="">Resiliency</abbr> Review as well as the Annexes G1 and
G2, none of which provide for such a broad interpretation of this
purpose.</p>
<p>This purpose is a technical function with some elements
regulating the behaviour of those parties that a delegated
elements of this technical functions, e.g. the contracted parties,
with regard to this technical function.</p>
<p>Best,</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 16.10.2018 um 23:28 schrieb Caitlin
Tubergen:<br>
</div>
<blockquote type="cite"
cite="mid:D9A3CE8D-41D8-464F-9AC9-6DCA5CFB5C3D@icann.org">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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;}
/* 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: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:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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>
<div class="WordSection1">
<p class="MsoNormal">Thanks, Benedict.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Given the proximity to ICANN63, we took the
liberty of sending this language to the full team so that we
can discuss in Barcelona.<o:p></o:p></p>
<p class="MsoNormal"><br>
Thanks again for taking the lead on this!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Marika, Berry and Caitlin<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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">Benedict Addis
<a class="moz-txt-link-rfc2396E" href="mailto:bee@theale.co.uk"><bee@theale.co.uk></a><br>
<b>Date: </b>Tuesday, October 16, 2018 at 6:21 AM<br>
<b>To: </b>Kurt Pritz <a class="moz-txt-link-rfc2396E" href="mailto:kurt@kjpritz.com"><kurt@kjpritz.com></a><br>
<b>Cc: </b>Stephanie Perrin
<a class="moz-txt-link-rfc2396E" href="mailto:stephanie.perrin@mail.utoronto.ca"><stephanie.perrin@mail.utoronto.ca></a>, Thomas Rickert
<a class="moz-txt-link-rfc2396E" href="mailto:epdp@gdpr.ninja"><epdp@gdpr.ninja></a>, Lindsay Hamilton-Reid
<a class="moz-txt-link-rfc2396E" href="mailto:lindsay.hamilton-reid@fasthosts.com"><lindsay.hamilton-reid@fasthosts.com></a>, Caitlin
Tubergen <a class="moz-txt-link-rfc2396E" href="mailto:caitlin.tubergen@icann.org"><caitlin.tubergen@icann.org></a>,
<a class="moz-txt-link-rfc2396E" href="mailto:gnso-epdp-lead@icann.org">"gnso-epdp-lead@icann.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:gnso-epdp-lead@icann.org"><gnso-epdp-lead@icann.org></a><br>
<b>Subject: </b>[Ext] Re: [GNSO-EPDP-Lead] Purpose B
Small Team<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Dear all, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On Kurt’s suggestion, I propose the
following Purpose B that relies directly on the language in
Recitals 47, 49 and 50.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">[ICANN requires that registration data is
processed for the purpose of...]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="color:black">maintaining
the security, stability and resiliency of the
Domain Name System. This will involve the
disclosure of existing registration data to
legitimate third parties, for the following
reasons only: 1) fraud prevention; 2) network and
information security; and 3) indicating possible
criminal acts, or threats to public security.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think that for ICANN, disclosure
will happen under 6(1)f. Third parties will require a
lawful basis of their own for their processing, governed
by a common set of standards that we’ll discuss when we
come to the access discussion.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thoughts?<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">B<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-epdp-team mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-epdp-team@icann.org">Gnso-epdp-team@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Volker A. Greimann
General Counsel and Policy Manager
KEY-SYSTEMS GMBH
T: +49 6894 9396901
F: +49 6894 9396851
W: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a>
Key-systems is a company registered in Germany with Registration No.: HR B 18835 - Saarbruecken: CEO: Alexander Siffrin
Registered Offices: Im Oberen Werk 1, DE-66386 St. Ingbert, Germany
Part of the CentralNic Group PLC (LON: CNIC) a company registered in England and Wales with company number 8576358.
Registered Offices: 35-39 Moorgate, London, EC2R 6AR. </pre>
</body>
</html>