<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font size="+1"><font face="Lucida Grande">precisely. Lack of
clarity about what is under ICANN control (through the policy)
and what is solely under Registrar/registry control is making
this messy.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie</font></font><br>
</p>
<div class="moz-cite-prefix">On 2019-02-14 10:00, farzaneh badii
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAN1qJvDnFAGGr4SJJXUJsbAa7m6L3CJSAvB2P_WU__ZEXkwu3w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>
<div dir="auto">Yeah but it didn’t have to be included in this
policy which has disclosure provisions. </div>
</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr">On Thu, Feb 14, 2019 at 9:59 AM Stephanie
Perrin <<a
href="mailto:stephanie.perrin@mail.utoronto.ca"
moz-do-not-send="true">stephanie.perrin@mail.utoronto.ca</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p><font size="+1"><font face="Lucida Grande">Basically
the contracted parties appear to be agreeing that
registries should be thin, unless the need for data
transfer has been proven. Some of those registries
have legitimate needs to verify some data. They
ought to, of course, do a review under the GDPR and
limit the personal data...but that is up to them as
controllers.</font></font></p>
</div>
<div>
<p><font size="+1"><font face="Lucida Grande">Stephanie</font></font><br>
</p>
<div class="m_-4374382719164850178moz-cite-prefix">On
2019-02-14 09:55, farzaneh badii wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-family:verdana,sans-serif">Hi Kathy </div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Yes sorry I
wanted the statement be brief. The additional data
elements are what new gtld registries ask for from
the registrants. For example .Lawyer might ask for a
bar (law not liquor) license. As the new
gtlds expand these additional data elements can be
hundreds of personal info such as driver's license,
identification cards etc. </div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">I am going to
elaborate on this statement and the recommendations
in the Google doc. </div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div>
<div dir="ltr"
class="m_-4374382719164850178gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div><font face="verdana, sans-serif">Farzaneh </font></div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Feb 14, 2019
at 9:45 AM Kathy Kleiman <a
class="m_-4374382719164850178moz-txt-link-rfc2396E"
href="mailto:kathy@dnrc.tech" target="_blank"
moz-do-not-send="true">
<kathy@dnrc.tech></a> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>H Farzaneh,</p>
<p>Tx to the amazing work of the NCSG EPDP team,
and for your posting below.<i> Question: can you
provide us with a bit more detail about the
"additional potentially personal and
sensitive data elements that are 'identified
by Registry Operator in its registration
policy'"? </i><i><br>
</i></p>
<p><i>What types of elements are being discussed?
</i><br>
</p>
<p>Best and tx, Kathy<br>
</p>
<div
class="m_-4374382719164850178gmail-m_1644384078556915552moz-cite-prefix">On
2/13/2019 8:13 PM, farzaneh badii wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default"
style="font-family:verdana,sans-serif">Dear
All,</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">The
Council is going to vote on the motion
to approve the recommendations of EPDP
tomorrow (Thursday). We are at the final
stages of our deliberations at EPDP and
it is almost done. </div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">The
council has to vote on this report
(attached) as a whole and cannot vote on
recommendations separately. This makes
our work a bit difficult because we do
not agree with all the recommendations.
One approach would be for NCSG
councilors to approve the report but
make a short statement for our own
record. </div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">I
have been discussing the concerns for a
couple of weeks on this list so there is
nothing new and I hope that we can
direct our councilors tomorrow to make
this statement if they can:</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><span
id="m_-4374382719164850178gmail-m_1644384078556915552gmail-docs-internal-guid-5967c891-7fff-89f9-cc99-9a22525484f2">
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:10pt"><span style="font-size:11pt;font-family:Verdana;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">NCSG
statement/ For GNSO Council Meeting, 14 February </span></p>
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:10pt"><span style="font-size:11pt;font-family:Verdana;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Despite
an unrealistic timeline, EPDP achieved its goal and delivered the final report. We are positive about the final report and our councilors have voted for its approval. But we are concerned with some aspects of the report and would like to record our concerns.</span></p>
<br>
<ul
style="margin-top:0pt;margin-bottom:0pt">
<li dir="ltr" style="list-style-type:disc;font-size:11pt;font-family:Verdana;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:10pt"><span style="font-size:11pt;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">The report has included
additional potentially personal and sensitive data elements that are “identified by Registry Operator in its registration policy." There was no justifiable reason to include these additional data elements in the report, nor was it justifiable to formulate
purposes that could relate to processing these additional elements. These additional data elements were not included in Temp Spec either. We are concerned about subjecting these additional data elements to this policy and warn the ICANN community and domain
name registrants that due to this addition even more sensitive and personal data might be disclosed to third parties on a global scale.
</span></p>
</li>
</ul>
<br>
<ul
style="margin-top:0pt;margin-bottom:0pt">
<li dir="ltr" style="list-style-type:disc;font-size:11pt;font-family:Verdana;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:10pt"><span style="font-size:11pt;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Data protection should
be provided for all domain name registrants globally regardless of their location. Discriminatory treatment of domain name registrants and providing some with less data protection is not justified, especially as we are moving towards disclosing domain name
registrants data to third parties "globally".</span></p>
</li>
<li dir="ltr" style="list-style-type:disc;font-size:11pt;font-family:Verdana;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:10pt"><span style="font-size:11pt;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"></span><span style="background-color:transparent;font-size:11pt;white-space:pre-wrap">We
believe "disclosure" of data to third parties is not an ICANN purpose for processing the data.
</span></p>
</li>
</ul>
<br>
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:10pt"><span style="font-size:11pt;font-family:Arial;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">We thank
the EPDP, its leadership and ICANN staff for achieving this milestone. We hope that with this policy by cultivating a privacy-respecting culture at ICANN, protecting the personal data of domain name registrants becomes a norm, and not remain an exception.
</span></p>
</span><br
class="m_-4374382719164850178gmail-m_1644384078556915552gmail-Apple-interchange-newline">
</div>
<div class="gmail_default"><span
id="m_-4374382719164850178gmail-m_1644384078556915552gmail-docs-internal-guid-26c035cb-7fff-4015-7d76-b4ae1e5f78a1">
<p dir="ltr"
style="font-family:verdana,sans-serif;line-height:1.38;margin-top:0pt;margin-bottom:10pt"><br>
</p>
<p
style="font-family:verdana,sans-serif;line-height:1.38;margin-top:0pt;margin-bottom:10pt">Link
to the statement: </p>
<p
style="font-family:verdana,sans-serif;line-height:1.38;margin-top:0pt;margin-bottom:10pt"><br>
</p>
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:10pt"><font
face="Verdana"><span style="font-size:14.6667px;white-space:pre-wrap"><a href="https://docs.google.com/document/d/1M8M0kaQSdQD3CC1HmpSTwMIKcufCT0ekVu7yHgx_f5w/edit?usp=sharing" target="_blank" moz-do-not-send="true">https://docs.google.com/document/d/1M8M0kaQSdQD3CC1HmpSTwMIKcufCT0ekVu7yHgx_f5w/edit?usp=sharing</a></span></font><br>
</p>
</span><br
class="m_-4374382719164850178gmail-m_1644384078556915552gmail-Apple-interchange-newline">
</div>
<div class="gmail_default">
<div class="gmail_default"><br>
</div>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Comments
are welcome (I think we have some
hours) but since Councilors are going
to read this statement out I give them
the liberty of changing the tone or
re-doing the statement.</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Best </div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div>
<div dir="ltr"
class="m_-4374382719164850178gmail-m_1644384078556915552gmail-m_-4778997151346405233gmail_signature">
<div dir="ltr">
<div><font face="verdana,
sans-serif">Farzaneh </font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<pre class="m_-4374382719164850178gmail-m_1644384078556915552moz-signature" cols="72">--
Kathy Kleiman
Visiting Scholar, Center for Information Technology, Princeton University
President (on leave), Domain Name Rights Coalition</pre>
<div
id="m_-4374382719164850178gmail-m_1644384078556915552DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid
rgb(211,212,222)">
<tbody>
<tr>
<td style="width:55px;padding-top:13px"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon"
target="_blank" moz-do-not-send="true"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
alt=""
style="width:46px;height:29px"
moz-do-not-send="true" width="46"
height="29"></a></td>
<td
style="width:470px;padding-top:12px;color:rgb(65,66,78);font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free.
<a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link"
style="color:rgb(68,83,234)"
target="_blank" moz-do-not-send="true">
www.avast.com</a> </td>
</tr>
</tbody>
</table>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div><font face="verdana, sans-serif">Farzaneh </font></div>
</div>
</div>
</blockquote>
</body>
</html>