- RDS-WHOIS2-RT - lists.icann.org

Reminders
by Alan Greenberg Aug. 25, 2017

Aug. 25, 2017

Please note that if you have additional thoughts on the scope for our work, please send them to this list well in advance of next week's meeting. Also note that if you have questions for the Subject Matter Experts (SMEs) with respect to the implementation of the recommendations from the first WHOIS Review, please send them in by the end of the month if at all possible. You can find the Summary and Detailed Implementation Reports under item 4 on our Background Materials page (https://community.icann.org/display/WHO/Background+Materials) Alan

1 0

Latest WHOIS Roadmap June2017
by Karen Mulberry Aug. 21, 2017

Aug. 21, 2017

Attached is the latest WHOIS Roadmap that summarizes activities as of June 2017. I thought this might be of interest to the Review Team. Karen Mulberry Director, Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN 12025 Waterfront Dr., Suite 300 Los Angeles, CA 90094 Phone: +1 424 353 9745

1 0

Scope discussion
by Alan Greenberg Aug. 17, 2017

Aug. 17, 2017

In preparation for our discussion on Scope tomorrow, I have tried to collect all of the issues raised to date in a simple list. If I have missed something, I do apologize, and please raise it tomorrow. The list includes: - Origin of issue and reference to where there may be further information. The two sources so far are the ICANN Bylaws and the document that Karen distributed summarizing earlier e-mails. - A very brief description. - My take on whether it is something we could address - The final decision of the group as to whether to include it or not. (currently all blank) I have also outlined the start of what I think are reasonable principles to guide our work. Alan

3 2

ICANN's plans with respect to GDPR
by Alan Greenberg Aug. 16, 2017

Aug. 16, 2017

As you may be aware, ICANN is (finally) beginning to address the GDPR and its implications on ICANN itself and its contracted parties (https://www.icann.org/news/blog/evolving-data-privacy-and-protection-regula… and https://www.icann.org/news/blog/personal-data-use-matrix-now-available-for-…) Unless I hear that it is not the wish of the RT, I would like to ask ICANN to brief the RT on exactly what ICANN is doing and how it will address the concerns. My hope is that we could arrange such a briefing for our call of 31 August 2017. Whether that is practical or not I cannot say until the request is made. Is there anyone who believes that this should not be requested? Alan

5 5

Plenary Call #4 - Action Items/Decisions Reached
by Alice Jansen Aug. 16, 2017

Aug. 16, 2017

Dear Review Team Members, Thank you for attending plenary call #4. Call archives will be posted on your wiki page https://community.icann.org/display/WHO/Meeting+%234+-+3+August Action items<https://community.icann.org/display/WHO/Tracking+Tool> and decisions reached<https://community.icann.org/display/WHO/Decisions+reached> are as follows: Decisions Reached: * On observers - Review Team adopts SSR2 approach with caveat that adjustments may be made, as needed * Review Team Members are expected to prepare questions in advance of implementation briefings and to share with ICANN org/presenters beforehand Action Items: * ICANN org to follow up on Statements of Interest * By Aug 14 - 23:59 UTC - Review Team Members to read draft Terms of Reference and to suggest edits and/or offer comments in comment boxes or track-changes * ICANN org to circulate a v2 that includes comments/input received on draft ToR for Review Team to discuss on plenary call #5 * ICANN org to provide overview of methodology used for implementation and difficulties encountered * By Aug 14 - 23:59 UTC – Review Team Members to put together short clear paragraph that includes issues you believe should be in the scope, in addition to mandatory items listed in Bylaws A copy of the Terms of Reference is included in the attached. Thanks, Kind regards Alice

6 5

Reminder - Input needed by Aug 14th
by Alice Jansen Aug. 15, 2017

Aug. 15, 2017

Dear Review Team Members, This is to kindly remind you of your action items: By August 14th (23:59 UTC), please: * Read the attached draft Terms of Reference (attached) and suggest edits and/or offer comments in comment boxes or track-changes; * Circulate short and clear paragraph that includes issues you believe should be in the scope. Thanks, Best regards Alice From: Alice Jansen <alice.jansen(a)icann.org> Date: Thursday 3 August 2017 at 18:23 To: RDS WHOIS2-RT List <rds-whois2-rt(a)icann.org> Subject: Plenary Call #4 - Action Items/Decisions Reached Dear Review Team Members, Thank you for attending plenary call #4. Call archives will be posted on your wiki page https://community.icann.org/display/WHO/Meeting+%234+-+3+August Action items<https://community.icann.org/display/WHO/Tracking+Tool> and decisions reached<https://community.icann.org/display/WHO/Decisions+reached> are as follows: Decisions Reached: * On observers - Review Team adopts SSR2 approach with caveat that adjustments may be made, as needed * Review Team Members are expected to prepare questions in advance of implementation briefings and to share with ICANN org/presenters beforehand Action Items: * ICANN org to follow up on Statements of Interest * By Aug 14 - 23:59 UTC - Review Team Members to read draft Terms of Reference and to suggest edits and/or offer comments in comment boxes or track-changes * ICANN org to circulate a v2 that includes comments/input received on draft ToR for Review Team to discuss on plenary call #5 * ICANN org to provide overview of methodology used for implementation and difficulties encountered * By Aug 14 - 23:59 UTC – Review Team Members to put together short clear paragraph that includes issues you believe should be in the scope, in addition to mandatory items listed in Bylaws A copy of the Terms of Reference is included in the attached. Thanks, Kind regards Alice

5 4

Re: [RDS-WHOIS2-RT] Privacy issue
by Alan Greenberg Aug. 15, 2017

Aug. 15, 2017

Thanks Erika, On reading your note, I realized that there is an implication that I missed. As I mentioned, by the time we issue our report, the GDPR deadline will likely have passed. But that means we will know to a large extent if ICANN has been successful in addressing the issue or not, and out of that there may well come some recommendations. Alan At 15/08/2017 10:41 AM, Erika Mann wrote: >Alan - > >I agree with your approach. > >Few things to consider in addition to what you recommend. GDPR is such >a drastic law with immense extra territorial law implications that we >might not be able to avoid it completely because of the way ICANN >responded to it and the implication it may have on ICANN and its >ecosystem.. I would agree with you that we should develop >recommendations that are high level and should work in all (most) >legal environments. > >Nonetheless I wouldn't rule out to touch, when appropriate, on the way >the GDRP was handled to allow future processes to evolve. There will >always be a new GDRP-alike legislation showing up on the horizon. And, >a proper response to such a future challenge should become ingrained >in ICANN's DNR. > >Thanks, >Erika > > > >Sent from my iPhone > > > On Aug 15, 2017, at 7:12 AM, Alan Greenberg > <alan.greenberg(a)mcgill.ca> wrote: > > > > At our meeting two weeks ago, we discussed privacy and the place > it holds in our review process. I have thought about it a lot since > then, and would like to summarize my feelings. > > > > It is clear in my mind that: > > > > - the current WHOIS implementation ignores privacy issues, and > this has been a known issue for a long time; > > - for whatever reasons, ICANN has chosen to largely ignore the > issue, even though it has become of increasing importance to many > parties and in multiple jurisdictions; > > - the GDPR deadline has raised the importance and priority of the issue; > > - ICANN is working on a GDPR response, and while opinions differ > on whether their plans are reasonable or appropriate, the deadline > of 25 May 2018 will almost surely have passed by the time we > deliver our final report; > > - as important as GDPR (and its penalties for non-compliance) are > it is not the only privacy issue that ICANN is facing or will face > and we need to address the generic issue in any recommendations we > make; and finally > > - our recommendations need to be high level and not attempt to > provide detailed policy or implementation which is the domain of > the GNSO PDP and its follow-on activities. > > > > Although this message is being sent on my own behalf as a RT > Member, it has been reviewed by both Vice-Chairs and they are in > general agreement. > > > > I welcome thoughts on this. > > > > Alan > > > > _______________________________________________ > > RDS-WHOIS2-RT mailing list > > RDS-WHOIS2-RT(a)icann.org > > https://mm.icann.org/mailman/listinfo/rds-whois2-rt

2 1

Privacy issue
by Alan Greenberg Aug. 15, 2017

Aug. 15, 2017

At our meeting two weeks ago, we discussed privacy and the place it holds in our review process. I have thought about it a lot since then, and would like to summarize my feelings. It is clear in my mind that: - the current WHOIS implementation ignores privacy issues, and this has been a known issue for a long time; - for whatever reasons, ICANN has chosen to largely ignore the issue, even though it has become of increasing importance to many parties and in multiple jurisdictions; - the GDPR deadline has raised the importance and priority of the issue; - ICANN is working on a GDPR response, and while opinions differ on whether their plans are reasonable or appropriate, the deadline of 25 May 2018 will almost surely have passed by the time we deliver our final report; - as important as GDPR (and its penalties for non-compliance) are it is not the only privacy issue that ICANN is facing or will face and we need to address the generic issue in any recommendations we make; and finally - our recommendations need to be high level and not attempt to provide detailed policy or implementation which is the domain of the GNSO PDP and its follow-on activities. Although this message is being sent on my own behalf as a RT Member, it has been reviewed by both Vice-Chairs and they are in general agreement. I welcome thoughts on this. Alan

3 2

Re: [RDS-WHOIS2-RT] ICANN's plans with respect to GDPR
by Alan Greenberg Aug. 15, 2017

Aug. 15, 2017

Yes, as I said in my other message with the subject "Privacy Issue", the GDPR is just one of many privacy issues that ICANN needs to address. This recommendation was just to brief us on ICANN's current plans regarding GDPR. Alan At 15/08/2017 03:31 AM, Dmitry Belyavsky wrote: >Dear Alan, > >On Tue, Aug 15, 2017 at 8:27 AM, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >As you may be aware, ICANN is (finally) beginning to address the >GDPR and its implications on ICANN itself and its contracted parties >(<https://www.icann.org/news/blog/evolving-data-privacy-and-protection-regula…>https://www.icann.org/news/blog/evolving-data-privacy-and-protection-regula… >and ><https://www.icann.org/news/blog/personal-data-use-matrix-now-available-for-…>https://www.icann.org/news/blog/personal-data-use-matrix-now-available-for-…) > >Unless I hear that it is not the wish of the RT, I would like to ask >ICANN to brief the RT on exactly what ICANN is doing and how it will >address the concerns. My hope is that we could arrange such a >briefing for our call of 31 August 2017. Whether that is practical >or not I cannot say until the request is made. > >Is there anyone who believes that this should not be requested? > > > I totally agree with you request. But it is worth mentioning that > GDPR is not the only legislation privacy-related requirement to be addressed. > >-- >SY, Dmitry Belyavsky

1 0

Apologize for being absent of Plenary Call #5
by SUN Lili Aug. 13, 2017

Aug. 13, 2017

Dear all, I’m writing to apologize my absence for Plenary Call #5 on 17 August due to my vocation plan, than you for your understanding. Best regards, Lili SUN *************************************************************************************************** This message, and any attachment contained, are confidential and subject of legal privilege. It may be used solely for the designated police/justice purpose and by the individual or entity to whom it is addressed. The information is not to be disseminated to another agency or third party without the author’s consent, and must not be retained longer than is necessary for the fulfilment of the purpose for which the information is to be used. All practicable steps shall be taken by the recipients to ensure that information is protected against unauthorised access or processing. INTERPOL reserves the right to enquire about the use of the information provided. If you are not the intended recipient, be advised that you have received this message in error. In such a case, you should not print it, copy it, make any use of it or disclose it, but please notify us immediately and delete the message from any computer. *************************************************************************************************

1 0