Page History
| Mtg | Date | Decision |
|---|---|---|
| #9 |
| Interim leadership is confirmed to continue leading the full review (Alan Greenberg as Chair – Cathrin Bauer-Bulst and Susan Kawaguchi as Vice Chairs) |
| #9 |
| Subgroups have a target of completing their recommendations by San Juan (ICANN61) |
| #9 |
| Time of plenary call to be discussed after Abu Dhabi |
| #9 |
| The ICANN60 informal meeting is confirmed for October 31 – 12:15-13:15 |
| #9 |
| Review Team reached preliminary agreements on scope, to be reflected in an updated Scope and Objectives table for review and insertion into ToR |
| #8 | Face-to-face meeting agenda has been approved. | |
| #6 |
| On timeline (cf Fact Sheet): agreement to publicize 12-month timeframe |
| #6 |
| On scope: IDN: Within Scope, with minimal effort on it. |
| #6 |
| On scope - Calton’s issue to “assess the value and timing of RDAP as a replacement protocol is suitable, a low effort one and will be included in the review, the wording will be refined slightly. |
| #6 |
| On scope - Compliance is within scope, and Review Team will take a look at it deeper. |
| #6 |
| On scope - Review will evaluate whether RDAP should be implemented before policy is developed. |
| #6 |
| On scope - Review Team won't be addressing GNSO suggestion "Assess how RDS current & future recommendations might be improved and better coordinated" |
| #6 |
| On scope: On OECD, Review Team will conduct: simple review noting that there are issues and pointing at other groups which have more in-depth on the issue, and may consider recommending that it be dropped or replaced for future reviews |
| #6 |
| On scope as per the Bylaws section 4.6.e.ii: Review Team agreed to treat separately:
The team also agreed that it may be useful to draw on the first WHOIS Review Team Scope of Work discussions for guidance on further defining the criterion of effectiveness. |
| #5 |
| Review Team adopts proposed decision-making methodology on Terms of Reference |
| #4 |
| Review Team Members are expected to prepare questions in advance of implementation briefings and to share with ICANN org/presenters beforehand. |
| #4 |
| On observers - Review Team adopts SSR2 approach with caveat that adjustments may be made, as needed. |
| #3 |
| RT agreed to bi-weekly 90 minute calls and to plan agenda for 60 minutes with option to run over, as needed. |
| #2 | RT agreed to interim leadership structure. | |
| #2 | RT confirmed its first Face-to-Face: October 2-3 2017. RT members will be contacted by ICANN Constituency Travel to make their arrangements and other meeting details to be sent out to Review Team by Staff Support. | |
| #2 |
| RT discussed holding a formal meeting at ICANN60 and determined that an informal meeting of those who will be attending the ICANN might be a better option depending on the number of RT members who are already attending the ICANN meeting. |
---
Day 1 – Monday, 2 October | 09:00 – 17:30 CET | 07:00 – 15:30 UTC (timezone converter)
