| Mtg | Date | Action | Action Owner | Due Date (2017) | Status |
|---|---|---|---|---|---|
| 2 March 2017 | Draft document about what other review teams have used for chairs and co-chairs and send to the list. | ICANN Org | n/a |  |
| Produce a summary of how other review teams have handled Observers and post to the list. | ICANN Org | n/a | | ||
| Post staff structure responsibilities on wiki background page. | ICANN Org | n/a | | ||
| Provide terms of reference to the ICANN Board for 30 March. | SSR2 | 30 March | |||
| 2 | 15 March 2017
| Circulate slide deck from 3/15 SSR2 face to face meeting. | ICANN Org | 16 March | |
Add OCTO KPIs, ICANN 2016 strategic plan and Emerging Technology Identifiers ICANN58 presentation to wiki background materials. | ICANN Org | 16 March | | ||
Provide a list of existing definitions of terms: Security, Stability, Resiliency and Unique Identifiers. Reference where they are located. | ICANN Org | 15 March | | ||
Circulate names / contact information for SADAG vendors to SSR2 RT list. | ICANN Org | 20 March | | ||
Circulate CDAR study report and contact information to SSR2 RT list. | ICANN Org | 20 March | | ||
SSR2 Fact Sheet sample and schedule. | ICANN Org | 16 March | | ||
Schedule 60-minute plenary call, Wednesday 22 March, 19:00 UTC. | ICANN Org | 15 March | | ||
Develop and circulate time zone mapping to support scheduling of regular plenary calls discussion on next plenary call. | ICANN Org | 21 March | | ||
Request for the IS-SSR team to provide a summary of the types of requests for assistance that they receive from the community. | ICANN Org | TBD | |||
| 3 | 22 March 2017
| Schedule 60-minute plenary call #4, 14:00 UTC Tuesday 28 March. | ICANN Org | 22 March | |
Co-Chairs to coordinate and formulate a proposal as to how to separate duties and present it to the RT. | SSR2 Co-Chairs | TBD | |||
Prepare a plan for a rotation schedule for RT calls to the Co-Chairs for the next meeting. | ICANN Org | 24 March | | ||
Open SSR1 Rec 11 - Effectiveness of mechanisms to mitigate abuse. Implementation description: ICANN should finalize and implement measures of success for new gTLDs and IDN fast track that expressly relate to its SSR-related program objectives, including measurements for the effectiveness of mechanisms to mitigate domain name abuse. | ICANN Org | April TBD | |||
The following three open SSR1 Recommendations are interrelated and are being implemented together: Rec 20 - SSR budget Implementation description: ICANN should increase the transparency of information about organization and budget related to implementing the SSR Framework and performing SSR-related functions. Rec 21 - SSR budget Implementation description: ICANN should establish a more structured internal process for showing how organization and budget decisions relate to the SSR Framework, including the underlying cost-benefit analysis. Rec 22 - SSR resources for new gTLDs Implementation description: ICANN should publish, monitor and update documentation on the organization and budget resources needed to manage SSR issues in conjunction with introduction of new gTLDs. | ICANN Org | April TBD | |||
Update the ICANN Board that the deadline of the end of the month will not be met but note that the RT is working to prepare its Terms of Reference and Work Plan per the Boards request. | Kaveh Ranjbar | 28 March | | ||
Prepare straw-man versions of the Terms of Reference and Work plan for the RT to consider. | ICANN Org | 31 March | |||
Generate a list of official observers and their relevant skill sets for RT consideration. | ICANN Org | 28 March | | ||
| 4 | 28 March 2017 | Review brainstorming capture slides from 15 March meeting and share thoughts on email list | RT Members | TBD | |
Schedule weekly RT calls per agreed rotation schedule | ICANN Org | 28 March | | ||
Review draft Scope and Work Plan and make comments on the email list | RT Members | from 1 April |
