<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><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;}
@font-face
{font-family:"Calibri Light";
panose-1:2 15 3 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 2 6 3 5 4 5 2 3 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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri Light",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
.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><!--[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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'>Hi Alan,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Calibri Light",sans-serif;color:black;background:white'>Thank you for your response. To be clear, ICANN is not able to share personal data even with an NDA, as ICANN does not have consent to share data in that manner. The redactions would be applied so that personal data is masked in part, but there would be sufficient information remaining in order to identify where changes occurred. </span><span style='font-family:"Calibri Light",sans-serif'><o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'>We will work to find the right resources who may be able to answer your questions about ARS record selections, etc. <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'>Kind regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'>--<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'>Negar<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri Light",sans-serif'><o:p> </o:p></span></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'>Alan Greenberg <alan.greenberg@mcgill.ca><br><b>Date: </b>Tuesday, September 25, 2018 at 11:30 AM<br><b>To: </b>Negar Farzinnia <negar.farzinnia@icann.org>, Susan Kawaguchi <susankpolicy@gmail.com><br><b>Cc: </b>RDS-WHOIS2-Leadership <rds-whois2-rt-leadership_staff@icann.org><br><b>Subject: </b>[Ext] Re: [RDS-WHOIS2-RT-Leadership_Staff] Compliance meeting - LA - 27 September 2018<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>Sorry for not getting back quicker.<br><br>It is hard to agree to that without knowing what will be redacted and how it relates to the "changes". My preference is to sign a non-disclosure agreement and not have to worry about that. I don't know if Susan can agree to that.<br><br>Lastly, I wanted to reiterate that we would also like to talk to someone from the WHOIS Accuracy Reporting System (ARS) group. e would like some additional clarity on how registrations are selected and the timing of the process.<br><br>Alan<br><br>At 21/09/2018 12:33 PM, Negar Farzinnia wrote:<br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>Dear Alan, Susan, and Stephanie,<br> <br>In light of the upcoming face-to-face Compliance meeting in Los Angeles, on 27 September 2018, we wanted to confer with you on how we can go about helping to answer your questions. We’d like to discuss with you a proposal to share with you a number of ARS tickets that were closed as a result of a change in the WHOIS data. We propose to not require a non-disclosure agreement, and to redact the tickets only minimally as necessary to protect any registrant personal data which is now masked in the public WHOIS since the Temporary Specification went into place. If that sounds acceptable then we will have a number of tickets redacted and ready for your review.<br> <br>Please let us know if you think this proposal is in line with the kind of information you were hoping to get better clarity on during the face-to-face discussion. Since the manual review and redacting will be somewhat time consuming, we’d request that you <u>please provide your feedback by Monday, 24 September 2018</u>. <br> <br>Kind regards,<br> <br>-- <br> <br>Negar Farzinnia<br>Director, MSSI Technical Reviews & Review Implementation<br>MSSI | Multistakeholder Strategy and Strategic Initiatives<br><a href="mailto:negar.farzinnia@icann.org">negar.farzinnia@icann.org</a> | (310) 578-8977<br> <br>ICANN | Internet Corporation for Assigned Names and Numbers<br>12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094<br> <br> <br> <br><b>From: </b>RDS-WHOIS2-RT-Leadership_Staff <rds-whois2-rt-leadership_staff-bounces@icann.org> on behalf of Alan Greenberg <alan.greenberg@mcgill.ca><br><b>Date: </b>Thursday, August 23, 2018 at 2:28 PM<br><b>To: </b>RDS-WHOIS2-Leadership <rds-whois2-rt-leadership_staff@icann.org><br><b>Subject: </b>[RDS-WHOIS2-RT-Leadership_Staff] Compliance meeting - LA - 27 September 2018<br> <br>After discussing it with Susan, we want to keep the meeting as <br>scheduled. We will work with Compliance and SMEs until then to refine <br>what we are looking for in this or other compliance areas.<br> <br>If we defer the meeting, instead of a few hundred dollars it will be <br>a few thousand, possible more depending on who we need to bring with <br>us (in this case, Susan and I will both already be there).<br> <br>Please inform Constituency Travel that the RDS-WHOIS2 Review Team <br>budget will cover one additional day hotel and per diem for me and <br>whatever incidental costs Susan may incur.<br> <br>Also, please find out what hotel the EPDP will be using to see if it <br>makes sense to stay there or move to the Doubletree.<br> <br>Alan<br> <br>_______________________________________________<br>RDS-WHOIS2-RT-Leadership_Staff mailing list<br><a href="mailto:RDS-WHOIS2-RT-Leadership_Staff@icann.org">RDS-WHOIS2-RT-Leadership_Staff@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt-leadership_staff">https://mm.icann.org/mailman/listinfo/rds-whois2-rt-leadership_staff</a> <br> <o:p></o:p></p></blockquote></div></body></html>