[RDS-WHOIS2-RT-Leadership_Staff] [Ext] Re: Compliance meeting - LA - 27 September 2018

Tue Sep 25 19:22:48 UTC 2018

Hi Alan,

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. 

We will work to find the right resources who may be able to answer your questions about ARS record selections, etc. 

Kind regards,

--

Negar

From: Alan Greenberg <alan.greenberg at mcgill.ca>
Date: Tuesday, September 25, 2018 at 11:30 AM
To: Negar Farzinnia <negar.farzinnia at icann.org>, Susan Kawaguchi <susankpolicy at gmail.com>
Cc: RDS-WHOIS2-Leadership <rds-whois2-rt-leadership_staff at icann.org>
Subject: [Ext] Re: [RDS-WHOIS2-RT-Leadership_Staff] Compliance meeting - LA - 27 September 2018

Sorry for not getting back quicker.

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.

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.

Alan

At 21/09/2018 12:33 PM, Negar Farzinnia wrote:

Dear Alan, Susan, and Stephanie,

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.

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 please provide your feedback by Monday, 24 September 2018.  

Kind regards,

-- 

Negar Farzinnia
Director, MSSI Technical Reviews & Review Implementation
MSSI | Multistakeholder Strategy and Strategic Initiatives
negar.farzinnia at icann.org | (310) 578-8977

ICANN | Internet Corporation for Assigned Names and Numbers
12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094

From: RDS-WHOIS2-RT-Leadership_Staff <rds-whois2-rt-leadership_staff-bounces at icann.org> on behalf of Alan Greenberg <alan.greenberg at mcgill.ca>
Date: Thursday, August 23, 2018 at 2:28 PM
To: RDS-WHOIS2-Leadership <rds-whois2-rt-leadership_staff at icann.org>
Subject: [RDS-WHOIS2-RT-Leadership_Staff] Compliance meeting - LA - 27 September 2018

After discussing it with Susan, we want to keep the meeting as 
scheduled. We will work with Compliance and SMEs until then to refine 
what we are looking for in this or other compliance areas.

If we defer the meeting, instead of a few hundred dollars it will be 
a few thousand, possible more depending on who we need to bring with 
us (in this case, Susan and I will both already be there).

Please inform Constituency Travel that the RDS-WHOIS2 Review Team 
budget will cover one additional day hotel and per diem for me and 
whatever incidental costs Susan may incur.

Also, please find out what hotel the EPDP will be using to see if it 
makes sense to stay there or move to the Doubletree.

Alan

_______________________________________________
RDS-WHOIS2-RT-Leadership_Staff mailing list
RDS-WHOIS2-RT-Leadership_Staff at icann.org
https://mm.icann.org/mailman/listinfo/rds-whois2-rt-leadership_staff 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt-leadership_staff/attachments/20180925/150ef598/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4615 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/rds-whois2-rt-leadership_staff/attachments/20180925/150ef598/smime.p7s>