<div><div><div dir="auto">Hi all, </div></div></div><div><div dir="auto"><br></div><div dir="auto">I am wrong on a couple of things:</div><div dir="auto"><br></div><div dir="auto">1. Vote is not tomorrow they will discuss the motion. So statement is not for tomorrow </div><div dir="auto"><br></div><div dir="auto">2. We could also vote on individual recs but it is preferable to vote on package. </div><div dir="auto"><br></div><div dir="auto">We shal continue the discussion anyway before voting happens. </div><div><br><div class="gmail_quote"><div dir="ltr">On Wed, Feb 13, 2019 at 8:13 PM farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" target="_blank">farzaneh.badii@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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_-9217307311565993511m_7247658879316290393gmail-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_-9217307311565993511m_7247658879316290393gmail-Apple-interchange-newline"></div><div class="gmail_default"><span id="m_-9217307311565993511m_7247658879316290393gmail-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">https://docs.google.com/document/d/1M8M0kaQSdQD3CC1HmpSTwMIKcufCT0ekVu7yHgx_f5w/edit?usp=sharing</a></span></font><br></p></span><br class="m_-9217307311565993511m_7247658879316290393gmail-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></div></div><div dir="ltr"><div dir="ltr"><div dir="ltr"><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_-9217307311565993511m_7247658879316290393gmail-m_-4778997151346405233gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div></div></div></div>
</blockquote></div></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>