<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I fully agree with your first sentence. For this reason,
specificity of the actual purposes is required instead of the
blanket statement proposed up to now. <br>
</p>
<p>Ultimately, any ICANN purpose must be specifically defined by the
questions of what is collected for what specific purpose for and
with whom it may be shared. <br>
</p>
<p>Say we take escrow as a purpose, which is likely univerally
agreed as a valid ICANN purpose:</p>
<p>ICANN will collect registration data to: protect the ownership of
a data subject in his registered domain names in case of a
registry or registrar failure or de-accreditation. For this
purpose, the data may be shared with escrow service providers
x,y,z (and potentially others) as well as other contracted parties
who may be assigned to take over the management of the affected
domain name registrations. <br>
</p>
<p>The language is not perfect, but I hope this illustrates the
level of specificity I am seeking here. If ICANN has purposes (and
I think we agree that it does), we need to specify these purposes
by saying what, how and why.</p>
<p>Best,</p>
<p>Volker</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 05.03.2020 um 11:21 schrieb Hadia
Abdelsalam Mokhtar EL miniawi:<br>
</div>
<blockquote type="cite"
cite="mid:fba25e4564c3484b86dab99a22ac5474@ntra-mbx1.TRA.GOV.EG">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{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.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:570234873;
mso-list-template-ids:-1285096850;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We
need not forget that data subjects need to know with whom
their data might be shared and for what purposes. To this
end purpose 2 is important as it establishes one core
purpose for processing the data related to ICANN's mission
and stated in its bylaws. Also in the EC letter to Joran in
May 2019 under purposes of processing and access model, the
EC say "For this reason we would recommend revising the
formulation of purpose two by excluding the second part of
the purpose "through enabling responses to lawful data
disclosure requests" and maintaining a broader purpose "
Contribute to the maintenance of the security, stability and
resiliency of the Domain Name System in accordance with
ICANN's mission" <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">This
was the recommendation of the EC to us in May 2019, the
question now is why don't we want to follow this
recommendation? Maintaining the SSR of the internet is
ICANN's core mission and is indeed a purpose for which data
might be processed why don't we want to be clear about this.<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">Hadia<o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
Gnso-epdp-team [<a class="moz-txt-link-freetext" href="mailto:gnso-epdp-team-bounces@icann.org">mailto:gnso-epdp-team-bounces@icann.org</a>]
<b>On Behalf Of </b>Alan Greenberg<br>
<b>Sent:</b> Thursday, March 05, 2020 2:18 AM<br>
<b>To:</b> Margie Milam; brian.kingATmarkmonitor.com;
<a class="moz-txt-link-abbreviated" href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-epdp-team] Purpose 2<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have to agree with Margie. These are all
important things and we cannot be left at some later date
being told that we cannot do this because it was never
mentioned to registrants.<br>
<br>
I could live with a much more general statement, but we have
been told by the CPH that they need something less vague to
put in their policies to registrants.<br>
<br>
Although I do not believe there is any merit in pursuing it, I
will restate that SOME 3rd party requests are in fact in
support of ICANN's mission (those that directly protect the
SSR of the DNS) and I believe that the statement that we were
conflating 3rd-party purposes with our own was partially in
error.<br>
<br>
Alan<br>
<br>
At 04/03/2020 05:50 PM, Margie Milam wrote:<br>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">We support Brian’s proposed Purpose 2
below, and note that without it – theere are many gaps,
including:
<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
Operationalizing and implementing new policies and contract
provisions (RDAP, transfers, TM Clearinghouse, etc.)
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
Conducting research using the contacts <o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
Coordinating cyber-attack responses such as Conficker &
other cyber attacks <o:p>
</o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
Publishing Accuracy Reporting System (ARS) reports <o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
Conducting testing of new registrar/registries to ensure
that the WHOIS systems work in the manner required by the
contract
<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
Implementing & testing escrow deposits with 3<sup>rd</sup>
party escrow providers
<o:p></o:p></li>
</ul>
<p class="MsoNormal"> <br>
All the best,<br>
<br>
Margie, Mark & Steve<br>
On behalf of the BC<br>
<br>
<b> <br>
Margie Milam<br>
</b>IP Enforcement & DNS Policy Lead | Facebook Legal<br>
NOTICE: This email (including any attachments) may contain
information that is private, confidential, or protected by
attorney-client or other privilege. Unless you are the
intended recipient, you may not use, copy, or retransmit the
email or its contents.<br>
<br>
<br>
<br>
<b>From: </b>Gnso-epdp-team
<a class="moz-txt-link-rfc2396E" href="mailto:gnso-epdp-team-bounces@icann.org"><gnso-epdp-team-bounces@icann.org></a> on behalf of "King,
Brian via Gnso-epdp-team" <a class="moz-txt-link-rfc2396E" href="mailto:gnso-epdp-team@icann.org"><gnso-epdp-team@icann.org></a><br>
<b>Reply-To: </b>"brian.kingATmarkmonitor.com"
<a class="moz-txt-link-rfc2396E" href="mailto:brian.king@markmonitor.com"><brian.king@markmonitor.com></a><br>
<b>Date: </b>Wednesday, March 4, 2020 at 10:12 AM<br>
<b>To: </b><a class="moz-txt-link-rfc2396E" href="mailto:gnso-epdp-team@icann.org">"gnso-epdp-team@icann.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:gnso-epdp-team@icann.org"><gnso-epdp-team@icann.org></a><br>
<b>Subject: </b>[Gnso-epdp-team] Purpose 2<br>
<br>
Hi all, <br>
<br>
Following last week’s conversation about some EPDP
members’ desire to have a bit more specificity in Purpose 2
(the irony of which is not lost on the IPC ), I propose the
below:
<br>
<br>
Contributing to the maintenance of the security, stability,
and resiliency of the Domain Name System in accordance with
ICANN’s mission, specifically “maintenance of and access
to accurate and up-to-date information concerning registered
names and name servers.†(ICANN Bylaws, Annex G-1; ICANN
Bylaws, Annex G-2)<br>
<br>
<b>Brian J. King </b><br>
Director of Internet Policy and Industry Affairs<br>
<br>
T +1 443 761 3726<a
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.markmonitor.com&d=DwMGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=_4XWSt8rUHZPiRG6CoP4Fnk_CCk4p550lffeMi3E1z8&m=Q65Or6H39_7X6LJk1SN78sszy_Hne8qlISmI8kN7Wh8&s=72C7v9XA12IEQxdYxgz5IDlXPMnrRUz4uW6aDcYmwcU&e="
moz-do-not-send="true">
<br>
markmonitor.com</a><u><br>
</u> <br>
<b>MarkMonitor<br>
</b>Protecting companies and consumers in a digital world<br>
<br>
_______________________________________________<br>
Gnso-epdp-team mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-epdp-team@icann.org">Gnso-epdp-team@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a><br>
_______________________________________________<br>
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
(<a href="https://www.icann.org/privacy/policy"
moz-do-not-send="true"> https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a
href="https://www.icann.org/privacy/tos"
moz-do-not-send="true"> https://www.icann.org/privacy/tos</a>).
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.<o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-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>
_______________________________________________
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 (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). 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.</pre>
</blockquote>
<div class="moz-signature">-- <br>
Volker A. Greimann<br>
General Counsel and Policy Manager<br>
<strong style="border-bottom: 3px solid #5C46B5">KEY-SYSTEMS GMBH</strong><br>
<br>
T: +49 6894 9396901<br>
M: +49 6894 9396851<br>
F: +49 6894 9396851<br>
W: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a><br>
<br>
Key-Systems GmbH is a company registered at the local court of
Saarbruecken, Germany with the registration no. HR B 18835<br>
CEO: Alexander Siffrin<br>
<br>
Part of the CentralNic Group PLC (LON: CNIC) a company registered
in England and Wales with company number 8576358.</div>
</body>
</html>