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

ACTION REQUIRED: RDS-WHOIS2-RT Doodle for F2F Meeting in Brussels
by MSSI Secretariat June 6, 2018

June 6, 2018

Dear Review Team Members, As requested by the RDS-WHOIS2 Leadership, we have new supplementary dates for the face-to-face meeting #3 that will be held at the ICANN office in Brussels, Belgium. Please complete this new poll https://doodle.com/poll/8un7nvkcv8mb5w8v, using the following color code: * Green - I can make it in person (1 click) * Yellow - I can join remotely (2 clicks) * Red – I am not available (0 click) We look forward to your speedy input. This poll will close at 23:59 UTC tomorrow, Thursday, 7 June 2018. Thank you, Brenda

1 0

For RT Review: Outreach Draft Report Section
by Alan Greenberg June 6, 2018

June 6, 2018

Please find for RT consideration the draft report section on Outreach. Alan

3 2

Compliance subgroup draft report
by Susan Kawaguchi June 6, 2018

June 6, 2018

Hello All, Please see the attached Compliance subgroup draft report. Apologies to the subgroup in not providing this to you earlier in the week for your review but thought it best to hit the deadline for the draft report to the full working group. This report still needs more work, I definitely did not organize the information optimally and will continue to work on that. I intend to use a table format for some of our analysis as we did for the RT1 compliance recommendation. Also there may be duplicative language as I moved things around I may not have caught all of the changes. I also intentionally left some duplicative language to remind me to continue editing. I am hoping the subgroup will meet next week for additional discussion on the findings and recommendations. Best regards, Susan

4 8

Short-Term Options to Adjust the Timeline for Specific Reviews
by Alan Greenberg June 5, 2018

June 5, 2018

Dear Theresa, Please find attached a letter from the RDS-WHOIS2 Review Team with regard to the ongoing Public Comment on Short-Term Options to Adjust the Timeline for Specific Reviews. The letter is also being sent to the Public Comment mailing list. I understand that two webinars have been scheduled in regard to this Public Comment, and I would be pleased to participate in them to present the views of the Review Team if that is your wish. Regards, Alan (acting in the capacity of Chair of the RDS-WHOIS2-RT)

2 2

Re: [RDS-WHOIS2-RT] URGENT: Possible Change - F2F #3
by Alan Greenberg June 5, 2018

June 5, 2018

Do not worry about that date. They should be aware of the possible change. We'll get back to you after the leadership call tomorrow. Alan At 05/06/2018 08:54 AM, Dmitry Belyavsky wrote: >Dear Alan, > >So are the dates finalized? The Travel team requested the variant to >be selected not later than June 6. > >Thank you! > >On Mon, Jun 4, 2018 at 10:36 AM, Dmitry Belyavsky ><<mailto:beldmit@gmail.com>beldmit(a)gmail.com> wrote: >Dear Alan, > >1. No >2. Yes >3. Yes. > >Variant 2 seems slightly better. > >On Sun, Jun 3, 2018 at 2:13 AM, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >Due to a sudden change in work commitment, Cathrin will no longer be >able to participate in the 19-20 July F2F meeting. > >I do not know if the facilities are available, but could each of you >please indicate: > >1. Has your ticket already been purchased for the 19-20 July meeting? > >2. Could you attend if the meeting was rescheduled to 23-24 July? > >3. Could you attend if the meeting was rescheduled to 24-25 July? > >Alan > > >_______________________________________________ >RDS-WHOIS2-RT mailing list ><mailto:RDS-WHOIS2-RT@icann.org>RDS-WHOIS2-RT(a)icann.org >https://mm.icann.org/mailman/listinfo/rds-whois2-rt > > > > >-- >SY, Dmitry Belyavsky > > > > >-- >SY, Dmitry Belyavsky

1 0

Data Accuracy subgroup draft report
by SUN Lili June 5, 2018

June 5, 2018

Dear all, Sorry for the late submission. Please refer to attached the revised version of the Data Accuracy subgroup draft report, which incorporated the discussion of 2nd F2F meeting and answers to the follow up questions on Data accuracy and Compliance from ICANN. As to the proposed recommendations, I’ll reflect in Compliance subgroup draft report. Thanks, Lili *************************************************************************************************** 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. *************************************************************************************************

3 8

URGENT: Possible Change - F2F #3
by Alan Greenberg June 5, 2018

June 5, 2018

Due to a sudden change in work commitment, Cathrin will no longer be able to participate in the 19-20 July F2F meeting. I do not know if the facilities are available, but could each of you please indicate: 1. Has your ticket already been purchased for the 19-20 July meeting? 2. Could you attend if the meeting was rescheduled to 23-24 July? 3. Could you attend if the meeting was rescheduled to 24-25 July? Alan

8 8

Re: [RDS-WHOIS2-RT] Plenary #30 | 4 June 2018 | 15:00 UTC
by Jean-Baptiste Deroulez June 5, 2018

June 5, 2018

Dear Review Team Members, In preparation for today’s call, please find attached the updated slide deck, and the updated agenda below: * Welcome, roll-call, SoI Updates * Short-Term Options to Adjust the Timeline for Specific Reviews * Face-to-Face Meeting #3 * Subgroups Status Update * ICANN62 * A.O.B. * Confirm Decisions Reached and Action Items Kind regards, Jean-Baptiste From: RDS-WHOIS2-RT <rds-whois2-rt-bounces(a)icann.org> on behalf of Jean-Baptiste Deroulez <jean-baptiste.deroulez(a)icann.org> Date: Friday, June 1, 2018 at 11:04 PM To: Cathrin Bauer via RDS-WHOIS2-RT <rds-whois2-rt(a)icann.org> Subject: [RDS-WHOIS2-RT] Plenary #30 | 4 June 2018 | 15:00 UTC Dear Review Team Members, In preparation for your call #30 [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> scheduled for Monday 4 June 2018 – 15:00 – 16:30 UTC, please find below the meeting agenda: * Welcome, roll-call, SoI Updates * Short-Term Options to Adjust the Timeline for Specific Reviews * Subgroups Status Update * ICANN62 * A.O.B. * Confirm Decisions Reached and Action Items You should all have received dial-in details to join this call. If not, please contact us (off list) at rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org>. As always, let us know if you have any questions or concerns. Kind regards, Jean-Baptiste

1 1

DRAFT: Request to Remove RDS-WHOIS2 Review from Short-term options Public Comment
by Alan Greenberg June 3, 2018

June 3, 2018

Attached is a draft of the letter to Theresa requesting that the RDS-WHOIS2 Review be removed from the PC (DOCX and PDF). We will further discuss this on Monday. Comments of suggested changes welcome. If you cannot join the call on Monday, please let us know whether you support sending this (or a similar) letter. Alan

2 1

Request to Remove RDS-WHOIS2 Review from Short-term options Public Comment
by Alan Greenberg June 3, 2018

June 3, 2018

During our meeting last Monday, we decided to request that ICANN Org remove the RDS-WHOIS2 from the Public Comment(PC) on Short-Term Options to Adjust the Timeline for Specific Reviews. Part of the argument for doing so is that we will be almost finished the bulk of our work by the time the PC completes, and the other part is that the financial savings that the PC presume from our changing scope or pausing the review - $460k is far too high. For this 2nd part, I have summarized our past and projected expenses. If the RT does not agree with these projections, they must be adjusted prior to us making the request (which I hope we can do next Monday). Facts/Assumptions: We had a cost of $15k for the Abu Dhabi meeting (people were brought in even though we did not end up having a formal meeting). We have had 2 F2F meetings to date at a cost of about $30k each. To complete its final report, the RT will need the planned F2F meeting in July, and possibly another F2F to complete the final report, potentially in November. We have currently spent about $46k on external contract support (largely Lisa) and I have projected another $40k presuming a large part of the work has already been carried out, but there may be some editing and other needs near the end. It is possible that we may want to bring several people to the March 2019 ICANN meeting to formally present the report. I have allowed $20k for that (per person costs will be higher than our Brussels meetings) For general contingency I have added $19k, and also an additional $30k in case, for whatever reason, we need one more F2F meeting. The original review budget allowed $200k for an external study, but there is no indication that this will be used. That results in a total Review Budget $290 compared to the original ICANN estimate of $690k. The FY breakdown is: FY17: $15k; FY18: $130k; FY19: $145k. MSSI has reviewed this and presuming the assumptions of number of meetings and no external contract is correct, they believe that this is reasonable. Are there any questions, and do you feel comfortable proceeding on this basis? THIS WILL BE DISCUSSED DURING OUR MONDAY MEETING. IF YOU CANNOT ATTEND, PLEASE SEND COMMENTS AHEAD OF TIME. Alan

3 4