<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
I will reply. Alan<br>
<br>
At 25/09/2018 10:57 AM, Jean-Baptiste Deroulez wrote:<br>
<blockquote type="cite" class="cite" cite="">Dear Alan, Dear Susan,<br>
<br>
Following up on Negar’s email below, can you please confirm whether the suggested proposal described below is in line with the kind of information you were hoping to get better clarity on this Thursday?<br>
<br>
Many thanks in advance for your confirmation,<br>
<br>
Kind regards,<br>
<br>
Jean-Baptiste<br>
<br>
<b>From: </b>RDS-WHOIS2-RT-Leadership_Staff <rds-whois2-rt-leadership_staff-bounces@icann.org> on behalf of Negar Farzinnia <negar.farzinnia@icann.org><br>
<b>Date: </b>Friday, September 21, 2018 at 6:33 PM<br>
<b>To: </b>Alan Greenberg <alan.greenberg@mcgill.ca>, Susan Kawaguchi <susankpolicy@gmail.com>, Stephanie Perrin <stephanie.perrin@mail.utoronto.ca><br>
<b>Cc: </b>RDS-WHOIS2-Leadership <rds-whois2-rt-leadership_staff@icann.org><br>
<b>Subject: </b>Re: [RDS-WHOIS2-RT-Leadership_Staff] Compliance meeting - LA - 27 September 2018<br>
<br>
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" eudora="autourl">https://mm.icann.org/mailman/listinfo/rds-whois2-rt-leadership_staff</a>
<br>
</blockquote>
</body>
</html>