Page History
...
Item # | Category | Source of Request | Date of Request | Action Item Request | Action Owner | Anticipated Completion Date* | Progress Notes | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
494 | General | 129 | 19 November 2020 | Team members to resolve assignments in the list of Heather’s outstanding questions regarding Appendix D: Findings related to SSR1 recommendations | RT | 3 December 2020 | 492 | General | 129 | 19 November 2020 | Heather to use the time from Monday 23rd November – Monday 7th December to compile the report to be shared with the team on Monday 7th December. | Heather | 7 December 2020 | 468 | General | 117 | 8 July 2020 | Staff to find out the process and timeline for next steps on the NCAP study, if ICANN org plans to publish a view on the report, and if so, when? | ICANN org | 15 July 2020 |
...
Item # | Category | Source of Request | Date of Request | Action Item Request | Action Owner | Anticipated Completion Date | Progress Notes | Completed Response | Completion Date |
---|---|---|---|---|---|---|---|---|---|
492 | General | 129 | 19 November 2020 | Heather to use the time from Monday 23rd November – Monday 7th December to compile the report to be shared with the team on Monday 7th December. | Heather | 7 December 2020 | Report shared with the team via email. | 13 Dec 2020 | |
494 | General | 129 | 19 November 2020 | Team members to resolve assignments in the list of Heather’s outstanding questions regarding Appendix D: Findings related to SSR1 recommendations | RT | 3 December 2020 | Resolved during the 3 December meeting. | 3 Dec 2020 | |
491 | General | 129 | 19 November 2020 | KC and Laurin will make the adjustments to the text as discussed on the plenary call today and hand off the document to Heather on Monday 23rd November. | KC and Laurin | 23 November 2020 | Discussed on the 23 Nov leadership team call - KC and Laurin will hand over the document to Heather on a seperate call. | 23 Nov 2020 | |
442 | General | 107 | 8 Apr 2020 | KC to share proposed text that she believes should be included in the report with regard to prioritization, as articulated on the call. | KC | 15 Apr 2020 | Action item closed. | 23 Nov 2020 | |
479 | General | 122 | 23 September 2020 | Eric to fill in the response column in the spreadsheet here for recommendation 21 where commenters support to say ‘noted’ or ‘thanks’. | Eric | 1 October 2020 | As discussed on 23 November leadership meeting, Heather will update the spreadsheet along with the report for distribution to the team on 7 December. | 23 Nov 2020 | |
452 | General | 110 | 20 May 2020 | Review team members to continue to work in subgroups and update the bar chart as work progresses. | Review Team | 1 July 2020 | Per discussion on 19 November plenary, Heather will compile the subteam documents into one document to be circulated to the full team for review on 7 December 2020. | 19 Nov 2020 | |
493 | General | 129 | 19 November 2020 | ICANN org to make the 10th December meeting a two-hour call, 15:00 – 17:00 UTC. | ICANN org | 26 November 2020 | Calendar invite updated. | 19 Nov 2020 | |
490 | General | 127 | 5 November 2020 | Heather to reach out to the original authors of the SSR1 text to ask for review of the proposed text additions to Appendix D. | Heather | 12 November 2020 | Individual emails sent off-list. | 12 Nov 2020 | |
489 | General | 127 | 5 November 2020 | Abuse subteam to suggest additional text to incorporate more context and explanations around the points that Danko raised in the document and as discussed on the call. | Abuse subteam | 19 November 2020 | Abuse text discussed during 12 November plenary. | 12 Nov 2020 | |
488 | General | 126 | 29 October 2020 | Team members should make comments in the abuse document ahead of the team’s next call on 5 November. | RT | 5 November 2020 | Abuse text discussed during 5 November plenary | 5 Nov 2020 | |
487 | General | 126 | 29 October 2020 | Brenda to update calendar invites to reflect the revised meeting time. | Brenda | 5 November 2020 | Calendar invites sent | 5 Nov 2020 | |
484 | General | 123 | 1 October 2020 | Recommendation 28: Russ will share his notes with Naveed on the discussion on recommendation 28. Naveed to make adjustments to the text on 28 based on the notes. | Russ & Naveed | 8 October 2020 | Naveed shared updated text to the list. | 27 Oct 2020 | |
480 | General | 122 | 23 September 2020 | Jennifer to recirculate to the SSR2 list the document containing the proposal for recommendation 29, with the instruction for team members to review and comment ahead of next week’s meeting. | Jennifer | 1 October 2020 | Jennifer circulated the document containing the proposal for recommendation 29 | 23 Oct 2020 | |
483 | General | 123 | 1 October 2020 | Recommendation 26: Heather will adjust text based on Žarko’s proposal and send to Žarko and Boban for review. | Heather | 8 October 2020 | Discussed on 15 Oct plenary - : Žarko will make the minor adjustments as discussed to recommendation 23 and 26 text and advise Heather once this is done so that she may move the text into the draft final report document. | 15 Oct 2020 | |
482 | General | 123 | 1 October 2020 | Recommendation 23: Heather will adjust text based on Žarko’s proposal and send to Žarko for review. | Heather | 8 October 2020 | Discussed on 15 Oct plenary - : Žarko will make the minor adjustments as discussed to recommendation 23 and 26 text and advise Heather once this is done so that she may move the text into the draft final report document. | 15 Oct 2020 | |
486 | General | 123 | 1 October 2020 | Team members to review slides and share any comments via email by Monday 5 October. | RT | 5 October 2020 | No feedback received - slides finalised. | 5 Oct 2020 | |
485 | General | 123 | 1 October 2020 | Recommendation 29: KC to respond on list to Kerry-Ann’s email per the discussion on the call today. | KC | 8 October 2020 | KC responded to Kerry-Ann via email | 4 Oct 2020 | |
481 | General | 122 | 23 September 2020 | SSR2 members to review and share any comments on the proposal for recommendation 29 in the document hereahead of next week’s meeting. | RT | 1 October 2020 | Recommendation 29 discussed on 1 Oct plenary. | 1 Oct 2020 | |
472 | General | 120 | 19 Aug 2020 | Alain to contact Zarko regarding how to move forward with recommendation 23. | Alain | 26 July 2020 | Recommendation 23 discussed on 1 Oct plenary. | 1 Oct 2020 | |
475 | General | 121 | 16 September 2020 | KC to share the document via email and receive input from review team members. | KC | 23 September 2020 | Rec 29 will be included in the abuse text as agreed on 23 Sep plenary. | 23 Sep 2020 | |
478 | General | 121 | 16 September 2020 | Heather to continue review of the document based on the input received. | Heather | 23 September 2020 | Complete. | 23 Sep 2020 | |
477 | General | 121 | 16 September 2020 | Heather to work with KC and Denise on merging Section 3.3 and 3.4. | Heather | 23 September 2020 | Complete. | 23 Sep 2020 | |
476 | General | 121 | 16 September 2020 | Review team members to raise any concerns on the risk subteam updates via the mailing list. | RT | 23 September 2020 | None raised. | 23 Sep 2020 | |
474 | General | 121 | 16 September 2020 | ICANN org to identify potential plenary call slots on Thursday and Friday that work for ICANN org and Heather, and send out an updated doodle poll version to the review team. | ICANN org | 16 September 2020 | Email sent to the SSR2 RT members | 16 Sep 2020 | |
455 | General | 111 | 27 May 2020 | Staff to provide information about the implementation of the CCT recommendations that have been accepted by the Board. | ICANN org | 10 June 2020 | Blog shared with SSR2 RT members. | 24 Aug 2020 | |
473 | General | 120 | 19 Aug 2020 | Russ to send a note to the list to ask team members to review the text for recommendations 20 and 24, and raise any concerns on list. | Russ | 20 Aug 2020 | Email sent to list. | 19 Aug 2020 | |
449 | General | 11 May 2020 | Q: It was announced earlier this year that Verisign will give ICANN $20 million over five years, beginning next year, “to support ICANN's initiatives to preserve and enhance the security, stability, and resiliency of the DNS.” Why (were there SSR vulnerabilities identified by Verisign and/or ICANN for which funding was needed)? Would you please provide the SSR2 with details on what specific activities ICANN will be using these funds for, next year and in subsequent years, (beyond the general categories mentioned in Goran’s March 27 announcement). What criteria and process is ICANN using to determine how to spend this SSR money? Goran stated that he “recognizes the request for accountability and transparency regarding how the funds are used and is committed to full transparency to provide the ICANN community the appropriate level of detail when available”-- please provide SSR2 more details on this, including how the funds and expenditures will be reflected and tracked in ICANN’s annual budget and operating plan. | ICANN org | 24 July 2020 | Response shared with the SSR2 via email. | 24 July 2020 | ||
467 | General | 115 | 24 June 2020 | Team members to review the Risk subteam text ahead of the 1 July meeting. | Team members | 1 July 2020 | Team discussed Risk text on 22 July meeting. | 22 July 2020 | |
471 | General | 118 | 22 July 2020 | Russ to send a note to the SSR2 RT email list to advise the whole team of the agreement taken on the call to the direction of the Risk subteam, and to ask for team members to raise any issues or concerns on list. | Russ | 22 July 2020 | Russ sent email to SSR2 RT email list | 22 July 2020 | |
470 | General | 118 | 22 July 2020 | Russ to send a note to the SSR2 RT email list to advise the whole team of the agreement taken on the call to the direction of the Abuse subteam, and to ask for team members to raise any issues or concerns on list. | Russ | 22 July 2020 | Russ sent email to SSR2 RT email list | 22 July 2020 | |
469 | General | 117 | 8 July 2020 | Laurin to review the recommendation 4 text in different documents and merge them ahead of next week’s meeting. | Laurin | 15 July 2020 | Team discussed Risk text on 22 July meeting. | 22 July 2020 | |
462 | General | 113 | 10 June 2020 | Kerry-Ann to update recommendation 6 to include privacy text once other changes to recommendation 6 have been made. | Kerry-Ann | 15 July 2020 | text shared to the list here. | 15 July 2020 | |
448 | General | 5 May 2020 | Q: ICANN reportedly will be adding supplemental questions and criteria on DNS abuse to the registrar accreditation application (sounds promising). Please provide SSR2 with information about this including: the final or draft supplemental text; how ICANN will assess the answers; whether and how the answers will factor into ICANN’s decision to approve or deny an application; how ICANN will track and hold an approved registrar accountable for the registrar’s statements in the application regarding how the applicant intends to address DNS abuse as a registrar; and whether ICANN has plans to add similar supplemental DNS abuse questions and criteria to registrar contract renewals (why, why not). | ICANN org | 13 July 2020 | Response shared with the SSR2 via email. | 13 July 2020 | ||
456 | General | 111 | 27 May 2020 | KC to help find resources related to NCAP and share these with Naveed. | KC | 3 June 2020 | Resources found and shared | 8 July 2020 | |
465 | General | 114 | 17 June 2020 | Team members to review the proposed changes to recommendation 27 and recommendation 6, as discussed on the call, ahead of final review of the text next week. | Team members | 1 July 2020 | Review completed | 1 July 2020 | |
466 | General | 114 | 17 June 2020 | Kaveh to put KC in touch with Ted Hardie, for a discussion regarding SSR2 recommendation 22. | Kaveh | 24 June 2020 | KC and Ted Hardie connected | 8 June 2020 | |
450 | General | 13 May 2020 | Q: It would be great if we could get updates on SSAC recommendations in SAC101v2, SAC097, and the 4 suggestions in :
| ICANN org | Responses shared with the SSR2 via email (see answers directly here). | 2 July 2020 | |||
456 | General | 111 | 27 May 2020 | KC to help find resources related to NCAP and share these with Naveed. | KC | 3 June 2020 | Complete - shared off-list. | 30 June 2020 | |
465 | General | 114 | 17 June 2020 | ICANN org to send an invite to the team for the DAAR call on 24 June. | ICANN org | 17 June 2020 | Invitations sent to the team | 20 June 2020 | |
461 | General | 112 | 3 June 2020 | ICANN org to provide information on work that is already underway with regard to DAAR, as noted in the ICANN org public comment response to the SSR2 draft report, and how ICANN org is measuring the effectiveness of this work. This information is preferred in writing although a call may also be helpful | ICANN org | 10 June 2020 | Information provided on work already underway | 17 June 2020 | |
463 | General | 113 | 10 June 2020 | Team members to review the proposed revised risk text in the document here. Changes with markup are here. Actions to address the public comments are here. | Review team | 17 June 2020 | Review completed during the 17 June meeting. | 17 June 2020 | |
458 | General | 112 | 3 June 2020 | Alain to update the public comment response spreadsheet to note how the public comment was handled in the revised text. | Alain | 10 June 2020 | Spreadsheet updated and presented during the 17 June meeting. | 17 June 2020 | |
457 | General | 112 | 3 June 2020 | Recommendation 27 subteam to look at SAC 107, 108, and 109 to ensure the content of these documents is considered in the revised text. | Rec 27 subteam | 10 June 2020 | Complete | 10 June 2020 | |
464 | General | 113 | 10 June 2020 | Laurin to update recommendation 6 to include budgetary information, as discussed on the call. | Laurin | 17 June 2020 | Updated recommendation 6 | 17 June 2020 | |
459 | General | 112 | 3 June 2020 | Leadership team to discuss a proposal for the path forward during the leadership meeting on 8 June | Leadership team | 8 June 2020 | Path forward presented on the 10 June plenary | 10 June 2020 | |
447 | General | 5 May 2020 | 3) The blog states (the obvious) that ICANN isn’t a regulator of Internet content, but it doesn’t address ICANN’s public interest remit. Multiple entities have asked ICANN to better govern the manner in which domain names are registered, and now especially, everyone is asking ICANN to hold contracted parties to greater accountability to prevent domains from being registered by malicious actors, especially for pandemic-related fraud and abuse. This requires greater scrutiny during the registration process. > What actions are ICANN taking that address this? > In addition to high volumes of fraudulent domain names containing pandemic-related strings with which criminals try to fool Internet users, random looking or otherwise auto-generated names that are easy to register in volume and are being used by the hundreds to perpetuate pandemic-related phishing attacks. What actions are ICANN taking that addresses this? > Recommended actions contained in SSR2’s draft report could help mitigate pandemic-related domain name abuse. Is the ICANN Board and staff reconsidering any of these actions? > Recommendations from others over the last few years also would help mitigate pandemic-related domain name abuse – especially the substantially increased phishing attacks that harm users. Is the ICANN Board and staff reconsidering any of these actions? Including: > - will ICANN move to ensure domain name registrant data is validated? Or at least implement cross-field validation? > - will ICANN put in place an Acceptable Use Policy that applies specifically to parties that register large numbers of domains, that requires registrants to apply for (and be validated for) bulk registration services? Further, will ICANN put in place an obligation to distinguish domain names registered by legal entities from those registered by > natural persons, classify parties that use bulk registration services as legal entities, and require unredacted access to the registration data of legal entities? > - will ICANN maintain and publish a current list of validated bulk registrants (who are from above defined as not natural persons)? > - will ICANN disallow registration transactions that involve large numbers of random-looking algorithmic domain names? > - will ICANN disallow, for a period of one year, the re-registration of any bulk-registered domain name that has been used in a criminal cyberattack? | ICANN org | 10 June 2020 | Answers shared via email (see answers directly here). | 10 June 2020 | ||
446 | General | 5 May 2020 | 2) What distinguishes ICANN's participation in the face of the pandemic from how they've participated in the past? > The blog says: “ICANN Compliance uses data collected in audits (described in more detail below) to assess whether registries and registrars are adhering to their DNS security threat obligations.” > What will Compliance do that it has not done until now? > Is Compliance making audit data associated with US-based registrars available to States Attorney Generals and the US Attorney General? | ICANN org | 10 June 2020 | Answers shared via email (see answers directly here). | 10 June 2020 | ||
445 | General | 5 May 2020 | 1) The blog says: " the domain names and the data collected by the system will be shared with parties > What specific actions is ICANN expecting registries and registrars to take? > For example, is ICANN encouraging suspension of name resolution or of the registration, or the registrant account? > Will ICANN ask registrars and registries to report on the efficacy of these actions? If so, when and on what cadence? > ICANN should publicly report per registrar & registry action: > How many names has it identified as suspicious/malicious? > What’s the number of domain names that each registry/registrar has taken action against? And what action was taken? > When can we expect ICANN public reporting and on what cadence? | ICANN org | 10 June 2020 | Answers shared via email (see answers directly here). | 10 June 2020 | ||
454 | General | 111 | 27 May 2020 | Staff to provide information on how the implementation shepherd concept is working in practice. | ICANN org | 10 June 2020 | Email sent to list with information | 3 June 2020 | |
462 | General | 112 | 3 June 2020 | ICANN org to provide a reference to the RySG comments on CCT recommendations related to pricing, per the reference in the public comment response to SSR2 recommendation 14 | ICANN org | 4 June 2020 | Email sent to list | 3 June 2020 | |
460 | General | 112 | 3 June 2020 | Russ to send KC’s proposal regarding a deadline on subteam work to the list for input. | Russ | 4 June 2020 | Email sent to list | 3 June 2020 | |
453 | General | 111 | 27 May 2020 | Staff to post the update blog to icann.org. | ICANN org | 1 June 2020 | Email sent to list with information | 1 June 2020 | |
451 | General | 110 | 20 May 2020 | Staff to update the work plan based on the review team’s new completion date. | ICANN org | 27 May 2020 | Workplan updated | 27 May 2020 | |
444 | General | 109 | 22 Apr 2020 | Subteams to get together and discuss the items assigned in the spreadsheet. Subteams should bring back to the plenary any major items that they believe may break consensus. | RT members | 6 May 2020 | Replaced by Action item 452 | 27 May 2020 | |
443 | General | 109 | 22 Apr 2020 | Staff to cancel the 29 April plenary call. | ICANN org | 29 Apr 2020 | Complete - cancellation notice sent. | 29 Apr 2020 | |
441 | General | 107 | 8 Apr 2020 | Russ to inform Scott, Noorul and Naveed of their subgroup assignments. | Russ | 9 Apr 2020 | Russ confirmed AI complete on 13 Apr leadership | 13 Apr 2020 | |
424 | General | 102 | 26 Feb 2020 | Team members to review the CCT prioritization approach (page 2) to factor this into the prioritization discussion on the next SSR2 call. | RT members | 6 Mar 2020 | Replaced by AI 442. | 8 Apr 2020 | |
439 | General | 106 | 1 Apr 2020 | Team members to volunteer for recommendation subgroups using the sign-up sheet, by Saturday 3 April. | RT members | 3 Apr 2020 | Team discussed subteam assignments on 8 April plenary. | 8 Apr 2020 | |
440 | General | 106 | 1 Apr 2020 | Russ will send a note to the team with the deadline to sign up to subgroups and the approach to work that the subgroups should follow. | Russ | 2 Apr 2020 | Email sent to list | 5 Apr 2020 | |
433 | General | 105 | 25 Mar 2020 | Review team members to put their initials in the spreadsheet next to the public comments that they will volunteer to help address ahead of the call next week. | RT members | 1 Apr 2020 | Team agreed to create subteams to address comments on each recommendation on 1 April plenary | 1 Apr 2020 | |
438 | General | 105 | 25 Mar 2020 | Denise and Laurin will work together in reviewing the ALAC document that Laurin will circulate to the list and will propose text to the relevant sections of the SSR2 report. | Denise / Laurin | 1 Apr 2020 | Team agreed to create subteams to address comments on each recommendation and in the document on 1 April plenary - this action item will be addressed in the subteam. | 1 Apr 2020 | |
437 | General | 105 | 25 Mar 2020 | Denise will propose edits to the Abuse and Compliance findings and rationale section on page 37 to address the highlighted comments. | Denise | 1 Apr 2020 | Team agreed to create subteams to address comments on each recommendation and in the document on 1 April plenary - this action item will be addressed in the subteam. | 1 Apr 2020 | |
436 | General | 105 | 25 Mar 2020 | Laurin will propose additional text for the findings section of recommendation 9 as it relates to 9.3 and 9.4. | Laurin | 1 Apr 2020 | Team agreed to create subteams to address comments on each recommendation and in the document on 1 April plenary - this action item will be addressed in the subteam. | 1 Apr 2020 | |
435 | General | 105 | 25 Mar 2020 | Heather to address KC’s comment on page 37 regarding the Board action on SSR1 in 2012, as discussed on the call. | Heather | 25 Mar 2020 | Complete | 25 Mar 2020 | |
434 | General | 105 | 25 Mar 2020 | Russ will send a note to Alain to seek clarification on recommendation 8.3. | Russ | 26 Mar 2020 | Email sent to Alain on list. | 25 Mar 2020 | |
432 | General | 104 | 18 Mar 2020 | Heather and Laurin will work together to propose a revised outline for recommendation 7 to incorporate the comments on the call. The proposal will be shared with the team for discussion next week. | Heather, Laurin | 25 Mar 2020 | Proposed outline presented and agreed to during 25 Mar plenary meeting. | 25 Mar 2020 | |
431 | General | 104 | 18 Mar 2020 | Laurin to propose text to merge recommendations 5 and 6. | Laurin | 25 Mar 2020 | Proposed outline presented and agreed to during 25 Mar plenary meeting. | 25 Mar 2020 | |
427 | General | 103 | 6 Mar 2020 | Laurin will suggest edits to recommendations 29.1 (to be merged with 30, 30 and 31. | Laurin | 18 Mar 2020 | To be included with action items 431 and 432. | Proposed outline presented and agreed to during 25 Mar plenary meeting. | 25 Mar 2020 |
426 | General | 103 | 6 Mar 2020 | Denise and Scott will suggest edits to recommendation 3 and the findings that support it. | Denise, Scott | 18 Mar 2020 | Complete - update shared to list. | 18 Mar 2020 | |
428 | General | 103 | 6 Mar 2020 | Naveed will suggest edits to recommendation 4. | Naveed | 18 Mar 2020 | Complete - discussed on plenary 104. | 18 Mar 2020 | |
429 | General | 103 | 6 Mar 2020 | Heather will share references to the specific sections of the document that were assigned as action items to the list. | Heather | 11 Mar 2020 | Complete - Heather working offline with RT members as necessary. | 11 Mar 2020 | |
425 | General | 102 | 26 Feb 2020 | With regard to SSR2 recommendation 3.3, staff to confirm with ICANN Legal whether ICANN is allowed to publish a case of breach at a contracted party. | ICANN org | 11 Mar 2020 | Danko shared the input from Legal, see comment on page 26 of the draft report document (Section 3.3). | 6 Mar 2020 | |
430 | General | 103 | 6 Mar 2020 | Jennifer to share the list the wiki page where review team documents are located. | Jennifer | 9 Mar 2020 | Link shared to chat during plenary call. | 6 Mar 2020 | |
423 | General | 102 | 26 Feb 2020 | Brenda to cancel the 5th and 6th March all-day face-to-face meetings and send an invite for 6th March at 15:00 – 18:00 UTC. | ICANN org | 27 Feb 2020 | Cancellation notices and new invite sent. | 26 Feb 2020 | |
422 | General | 102 | 26 Feb 2020 | Brenda to update the availability Doodle poll to include the first two weeks in May. | ICANN org | 27 Feb 2020 | Update shared via email. | 26 Feb 2020 | |
417 | General | 99 | 29 Jan 2020 | Team members to volunteer to add text regarding what needs to be done to measure completion of each SSR1 recommendation. | RT members | 5 Feb 2020 | Table complete and discussed on 19 Feb plenary meeting. | 19 Feb 2020 | |
421 | General | 101 | 19 Feb 2020 | Staff to share any new information to the list as it arises as a result of ongoing discussions with regard to the planned meeting in Cancun. | ICANN org | 20 Feb 2020 | Announcement shared to list by RT member. | 19 Feb 2020 | |
420 | General | 99 | 29 Jan 2020 | Heather to prepare a draft webinar slide deck for team consideration. | Heather | 5 Feb 2020 | Shared to list. | 7 Feb 2020 | |
415 | General | 99 | 29 Jan 2020 | Staff to follow up with travel to ask them to re-send the Cancun welcome email to Scott, confirming they have his current email address. | ICANN org | 30 Jan 2020 | Complete - Scott confirmed welcome email received. | 4 Feb 2020 | |
419 | General | 99 | 29 Jan 2020 | Team members to complete the webinar Doodle poll by the end of this week. | RT members | 31 Jan 2020 | Completed - Doodle poll closed. | 3 Feb 2020 | |
418 | General | 99 | 29 Jan 2020 | Staff to send a Doodle poll regarding webinar options for the week of the 10th February. | ICANN org | 29 Jan 2020 | Complete - shared via email | 29 Jan 2020 | |
416 | General | 99 | 29 Jan 2020 | Heather to send the table of SSR1 recommendations to the team. | Heather | 29 Jan 2020 | Complete - shared via email. | 29 Jan 2020 | |
413 | General | 96 | 8 Jan 2020 | ICANN org to share a pointer to the data catalogue to assist the SSR2 Review Team with identifying what it considers to be SSR-related data | ICANN org | 15 Jan 2020 | Draft report published for public comment. ICANN org SMEs remain available for discussion with the RT. | 26 Jan 2020 | |
412 | General | 96 | 8 Jan 2020 | ICANN org to share information on current and planned vulnerability disclosure activity. | ICANN org | 15 Jan 2020 | Draft report published for public comment. ICANN org SMEs remain available for discussion with the RT. | 26 Jan 2020 | |
411 | General | 96 | 8 Jan 2020 | ICANN org to share information in writing to the team on the planned facilitation center for DNS ecosystem security risks, including any available timing information. | ICANN org | 15 Jan 2020 | Draft report published for public comment. ICANN org SMEs remain available for discussion with the RT. | 26 Jan 2020 | |
410 | General | 96 | 8 Jan 2020 | ICANN org to share some examples of SSR2 recommendations where there may be multiple approaches to implementation and the recommendation could benefit from enhanced specificity or clarity on the preferred outcome. | ICANN org | 15 Jan 2020 | Draft report published for public comment. ICANN org SMEs remain available for discussion with the RT. | 26 Jan 2020 | |
406 | General | 7 Jan 2020 | ICANN org finance to respond to SSR2 RT question regarding SSR budget recommendation text. | ICANN org | 31 Jan 2020 | Staff proposed a discussion on this item to LT. | Draft report published for public comment. ICANN org SMEs remain available for discussion with the RT. | 26 Jan 2020 | |
393 | General | 90 | 1 Nov 2019 | Staff to find out whether the rec on Root server operation section is already happening (Mostly alignment so the rec could be dropped). | ICANN org | 30 Nov 2019 | Draft report published for public comment. ICANN org SMEs remain available for discussion with the RT. | 26 Jan 2020 | |
392 | General | 90 | 1 Nov 2019 | Follow up with E&IT team to find out whether they have any plans to implement ISO 31000, and other relevant security-related certifications (as requested as part of SSR1). | ICANN org | 30 Nov 2019 | Draft report published for public comment. ICANN org SMEs remain available for discussion with the RT. | 26 Jan 2020 | |
414 | General | 98 | 22 Jan 2020 | Heather to write the Executive Summary and make the other changes agreed to on the call and share to the list by the end of the day on Wednesday 22 January. | Heather | 22 Jan 2020 | Executive summary shared via email. | 22 Jan 2020 | |
400 | General | 95 | 18 Dec 2019 | Kaveh and staff to confirm the latest available information is included in the Privacy text. | ICANN org | 15 Jan 2020 | Information shared in Google doc. All text reviewed in DC. | 16 Jan 2020 | |
401 | General | 95 | 18 Dec 2019 | Heather and Kerry-Ann to work on cleaning up the ‘Privacy’ text. | Heather, Kerry-Ann | 20 Dec 2019 | Complete. All text reviewed in DC. | 16 Jan 2020 | |
409 | General | 96 | 8 Jan 2020 | Team members to complete the survey ahead of the face-to-face meeting in Washington, D.C. | Review Team | 15 Jan 2020 | Complete. | 15 Jan 2020 | |
414 | General | 96 | 8 Jan 2020 | ICANN org to share via email additional observations that were not discussed due to time constraints. | ICANN org | 15 Jan 2020 | Agreed on 13 Jan 2020 leadership call that these items will be discussed in person in DC. | 13 Jan 2020 | |
402 | General | 95 | 18 Dec 2019 | Russ to ask team members with outstanding writing assignments to notify the list once the text is in the Google doc. | Russ | 20 Dec 2019 | Team members will review all new writing assignments in DC during the f2f meeting. | 13 Jan 2020 | |
408 | General | 96 | 8 Jan 2020 | Laurin to coordinate sending the prioritization survey to team members. | Laurin | 9 Jan 2020 | Completed off list | 8 Jan 2020 | |
407 | General | 96 | 8 Jan 2020 | Staff to follow up with Eric regarding his outstanding travel issue. | Staff | 9 Jan 2020 | Resolved off list. | 8 Jan 2020 | |
399 | General | 94 | 11 Dec 2019 | Laurin to connect with Heather on how best to reference the recommendations and then input into the survey tool. | Laurin, Heather | 23 Dec 2019 | Survey shared direct to RT members. | 8 Jan 2020 | |
391 | General | 90 | 1 Nov 2019 | Ask Finance join one of the plenary calls to discuss budgeting and how SSR-related budget can be captured more clearly and effectively. | ICANN org | 30 Nov 2019 | Replaced by action 406 | 7 Jan 2020 | |
405 | General | 95 | 18 Dec 2019 | Staff to invite SMEs to the 8 January plenary call, as discussed with the review team. | ICANN org | 23 Dec 2019 | ICANN org to join 8 January plenary meeting. | 23 Dec 2019 | |
398 | General | 94 | 11 Dec 2019 | Team members to complete writing assignments in the Google doc ahead of the holiday break. | RT members | 23 Dec 2019 | All new draft report text will be reviewed at DC face-to–face meeting | 23 Dec 2019 | |
404 | General | 95 | 18 Dec 2019 | Heather to note page numbers of the outstanding writing tasks in the Google doc (see second tab). | Heather | 20 Dec 2019 | Compete. | 18 Dec 2019 | |
403 | General | 95 | 18 Dec 2019 | Russ to send a note to the list to seek volunteers for a review of the name collision findings, and the data access recommendation | Russ | 20 Dec 2019 | Email sent to list. | 18 Dec 2019 | |
341 | General | 63 | 14 Mar 2019 | Review team members to think about lessons learned that can be shared. Team will have a work topic on this area in the future. | Review Team | For discussion at a future date. | Suggestions are included in the draft report. | 16 Dec 2019 | |
400 | General | 94 | 11 Dec 2019 | Staff to find out from the meetings team the date by which the team should confirm if they want to meet in Cancun on 5 and 6 March. | ICANN org | 16 Dec 2019 | Information shared via email and discussed on 16 December leadership team meeting | 16 Dec 2019 | |
396 | General | 93 | 4 Dec 2019 | Team members to complete writing assignments in the Google doc ahead of the call next week. Team members to input text are Denise, Kerry-Ann, Matogoro, Eric, Scott, and Laurin. | RT Members | 11 Dec 2019 | Replaced by action item 398. | 16 Dec 2019 | |
397 | General | 93 | 4 Dec 2019 | Laurin to share examples of prioritization methods for the team’s consideration ahead of next week’s call. | Laurin | 11 Dec 2019 | Discussed during 11 Dec 2019 plenary meeting. | 11 Dec 2019 | |
395 | General | 91 | 13 Nov 2019 | KC to send a note to the review team to provide more information about the prioritization tool SSAC is using. | KC | 27 Nov 2019 | ICANN org provided a briefing on this topic during 27 November plenary | 27 Nov 2019 | |
394 | General | 90 | 2 Nov 2019 | Staff to enquire with SSAC support colleagues regarding a tool for prioritization | ICANN org | 15 Nov 2019 | Replaced by action item 395 | 13 Nov 2019 | |
382 | General | 86 | 9 Oct 2019 | After close of the team’s deadline for comments on the first draft, Denise and Matogoro will redraft the comment response to make it a draft letter to the Board, for team review. | Denise, Matogoro | 16 Oct 2019 | Action item closed as no further discussion | 2 Nov 2019 | |
380 | Compliance | 86 | 9 Oct 2019 | SSR2 compliance subteam to review the Contractual Compliance Audit Program and ensure that SSR2 draft recommendations related to audit clearly state what the audit program is not providing that SSR2 wants to see. | Compliance subteam | 16 Oct 2019 | Work progressed in Montreal on the report. | 2 Nov 2019 | |
376 | Compliance | 85 | 2 Oct 2019 | Heather to propose revised text in the Google doc based on the discussion on the call, to address Heather’s questions 3, 4, 7 and 9. | Heather | 9 Oct 2019 | Work progressed in Montreal on the report. | 2 Nov 2019 | |
375 | Compliance | 85 | 2 Oct 2019 | Compliance sub team members to provide clarifying text in the Google doc to address Heather’s question 2. | Compliance subteam | 9 Oct 2019 | Work progressed in Montreal on the report. | 2 Nov 2019 | |
390 | General | 88 | 23 Oct 2019 | Heather to suggest text for recommendation 3 to make it more measurable | Heather | 30 Oct 2019 | Work progressed in Montreal on the report. | 2 Nov 2019 | |
387 | General | 88 | 23 Oct 2019 | Heather will take the strategic objective text from all the recommendations and map in a separate table. | Heather | 30 Oct 2019 | Work progressed in Montreal on the report. | 2 Nov 2019 | |
389 | General | 88 | 23 Oct 2019 | Heather to cross check CCT recommendations against draft SSR2 recommendations text, for inclusion in the report. | Heather | 30 Oct 2019 | Google doc created. | 28 Oct 2019 | |
388 | General | 88 | 23 Oct 2019 | Denise to send clarifying text to the list regarding ‘abuse’ in recommendation 3. | Denise | 25 Oct 2019 | Sent to list. | 23 Oct 2019 | |
386 | General | 87 | 16 Oct 2019 | Team members to review the proposed edits to recommendations 3, 24, 25, and 26 ahead of the next call on Wednesday 23 October. | Review Team | 23 Oct 2019 | Discussed on 23 October call. | 23 Oct 2019 | |
385 | General | 87 | 16 Oct 2019 | KC to propose edits to recommendation 25 on-list, based on the team discussion on the call. Team members to respond with comments on-list ahead of the next call on Wednesday 23 October. | KC, Review Team | 23 Oct 2019 | Discussed on 23 October call. | 23 Oct 2019 | |
384 | General | 87 | 16 Oct 2019 | KC to share her proposal for deletion of some text in recommendation 24 on-list. Team members to share their responses to the proposal on-list ahead of the next call on Wednesday 23 October. | KC, Review Team | 23 Oct 2019 | Discussed on 23 October call. | 23 Oct 2019 | |
381 | General | 86 | 9 Oct 2019 | Team members to share comments on the first draft of comments on the CCT implementation plan on the list by 23:59 UTC on Friday 11 October. | Review Team | 16 Oct 2019 | Deadline passed. | 16 Oct 2019 | |
370 | General | 84 | 25 Sep 2019 | Eric and KC to work together to discuss recommendations 24 – 26 as flagged in KC’s email and propose more specific text for the 9 October SSR2 call. | KC, Eric | 16 Oct 2019 | Discussed on 16 October call | 16 Oct 2019 | |
374 | Compliance | 85 | 2 Oct 2019 | Denise to provide clarifying text in the Google doc to address Heather’s questions 1 and 8. | Denise | 9 Oct 2019 | Complete | 16 Oct 2019 | |
377 | Compliance | 85 | 2 Oct 2019 | Denise to share the word document of compliance subteam text with Heather. | Denise | 9 Oct 2019 | Complete - document shared off-list | 16 Oct 2019 | |
378 | Compliance | 85 | 2 Oct 2019 | Team members to address Heather’s questions regarding compliance subteam findings (see here and here) on list. | Compliance subteam | 9 Oct 2019 | Complete | 16 Oct 2019 | |
383 | General | 86 | 9 Oct 2019 | Staff to make the request for the team to meet with the SSR2 Board Caucus Group in Montreal. | ICANN org | 10 Oct 2019 | Board Ops has received the request. | 10 Oct 2019 | |
379 | General | 85 | 2 Oct 2019 | Team to share comments on the CCT implementation plan draft public comment from SSR2 Review Team by 8 October. | Review Team | 8 Oct 2019 | Replaced by action item 381 | 9 Oct 2019 | |
367 | General | 83 | 18 Sep 2019 | Staff to start the process of engaging a contractor for the Policy Researcher role. | ICANN org | 27 Sep 2019 | ICANN org shared candidate to SSR2 leadership list email. | 2 Oct 2019 | |
371 | General | 84 | 25 Sep 2019 | Team members to read through the compliance subteam recommendations (p30 – 38) in the recommendations document ahead of the 2 October call. | Review Team | 2 Oct 2019 | No comments shared - Heather and team discussed questions on 2 October call. | 2 Oct 2019 | |
372 | General | 84 | 25 Sep 2019 | Team members to share process-related comments on the CCT implementation plan to the list. | Review Team | 2 Oct 2019 | Replaced by action item 379. | ||
373 | General | 84 | 25 Sep 2019 | Staff to send the Operating Standards link to the team, and to pull out sections relevant to prioritization and cost effectiveness of recommendations. | ICANN org | 27 Oct 2019 | Shared via email. | 30 Sep 2019 | |
369 | Work plan | 84 | 25 Sep 2019 | Staff to post the updated work plan to the wiki. | ICANN org | 26 Sep 2019 | Posted to the wiki | 26 Sep 2019 | |
368 | Admin | 83 | 18 Sep 2019 | Staff to work with Meetings Team to plan for this face-to-face meeting in DC. | ICANN org | 18 Sep 2019 | Meetings team informed of meeting dates, plans in motion. | 18 Sep 2019 | |
364 | General | 82 | 11 Sep 2019 | Team members to read through the text and share any comments on-list ahead of the call by the next team meeting on Wednesday 18 September. | Review Team | 18 Sep 2019 | Deadline passed, text to be discussed on 25 September meeting. | 18 Sep 2019 | |
365 | General | 82 | 11 Sep 2019 | Jennifer to share the proposal to meet face-to-face on 16-17 January in Washington, D.C. on-list and ask team members to raise any concerns by the end of this week. | ICANN org | 11 Sep 2019 | Shared via email. | 11 Sep 2019 | |
363 | General | 81 | 4 Sep 2019 | Staff to send a Doodle poll to gauge team availability for a face-to-face meeting in mid-January 2020. | ICANN org | 9 Sep 2019 | Doodle poll shared via email. | 6 Sep 2019 | |
362 | General | 79 | 7 Aug 2019 | Penholders to complete the actions assigned to them (see email here for list of penholders/actions) | Review Team | 14 Aug 2019 | Russ sent a follow up email to list with 28 August deadline. | 19 Aug 2019 | |
361 | General | 79 | 7 Aug 2019 | Team members to share feedback on the compliance text discussed on the call. See the text in documents here and here. | Review Team | 14 Aug 2019 | Compliance items to be discussed again on 28 August per Russ's note to team. | 19 Aug 2019 | |
356 | General | 77 | 11 Jul 2019 | Penholders to move recommendations text from the draft document to the recommendations document for team review. | Review Team | 17 Jul 2019 | New action items list shared via email | 2 Aug 2019 | |
360 | General | 78 | 17 Jul 2019 | Staff to ask ICANN IT if there are alternative options to Zoom. | ICANN org | 25 Jul 2019 | Information shared via email. | 22 Jul 2019 | |
359 | General | 78 | 17 Jul 2019 | Staff to circulate a Doodle poll to the team to find out who is planning to be in Montreal on what dates. | ICANN org | 18 Jul 2019 | Sent via email. | 17 Jul 2019 | |
358 | Workplan | 78 | 17 Jul 2019 | Russ to share the proposed timeline via email for team feedback. | Russ | 17 Jul 2019 | Sent via email. | 17 Jul 2019 | |
343 | Outreach | 70 | 19 May 2019 | Staff to draft communication regarding review team's progress post Brussels and Marrakech. | ICANN org | 10 Jul 2019 | Review Team discussed new work plan dates during 17 July plenary call. Communication will be developed as appropriate once new work plan is agreed. | 17 Jul 2019 | |
357 | General | 77 | 11 Jul 2019 | Staff to ask ICANN IT to address the security issues with Zoom on Mac. | ICANN org | 19 Jul 2019 | Blog from ICANN IT shared via email. | 16 Jul 2019 | |
355 | General | 74 | 13 Jun 2019 | Kerry-Ann and Norm to add references to the strategic plan to their draft recommendations. | Kerry-Ann, Norm | 23 Jun 2019 | Changes incorporated into recommendations Google doc | 1 Jul 2019 | |
354 | General | 74 | 13 Jun 2019 | Russ will add the names of the penholders to each of the recommendations in the Google doc for ease of reference. | Russ | 17 Jun 2019 | Changes incorporated into recommendations Google doc | 1 Jul 2019 | |
352 | General | 73 | 6 Jun 2019 | RT members to finish editing the draft recommendations. | Review Team | 27 Jun 2019 | Changes incorporated into recommendations Google doc | 1 Jul 2019 | |
351 | General | 73 | 6 Jun 2019 | KC to provided suggested rewrite for recommendation 9 by next week. | KC | 27 Jun 2019 | Changes incorporated into recommendations Google doc | 1 Jul 2019 | |
346 | General | 70 | 19 May 2019 | Staff to send a summary of DNS Symposium activity relevant to the review team's work. | ICANN org | 17 Jun 2019 | Shared via email. | 19 June 2019 | |
353 | General | 73 | 6 Jun 2019 | Staff will copy the Google document to the SSR2 team drive | ICANN org | 7 Jun 2019 | New document shared via email. | 7 Jun 2019 | |
347 | General | 29 May 2019 | Provide answers to follow-up questions regarding Compliance | ICANN org | 27 Jun 2019 | Answers provided via email. | 7 Jun 2019 | ||
350 | General | 72 | 30 May 2018 | Denise to follow up with Eric and Laurin to confirm they have no updates to the work plan. Once confirmed, leadership team to advise staff to post the updated work plan to the wiki. | Denise / ICANN org | 31 May 2019 | Shared with leadership for final review via email. v8 Workplan posted to the wiki. | 31 May 2019 | |
349 | General | 72 | 30 May 2018 | Jennifer to work with KC to recover recommendation ‘L’ text to the document. | Jennifer / KC | 31 May 2019 | Resolved off list | 31 May 2019 | |
348 | General | 72 | 30 May 2018 | Angie to follow up on email with people assigned to the recommendations that are not included in the v3 recommendations document here. | Angie | 6 Jun 2019 | Follow-up note sent to team. | 30 May 2019 | |
345 | General | 71 | 23 May 2019 | Jennifer to re-send the two Google document links to the team with a reminder of the work request. | Jennifer | 23 May 2019 | Email sent to list. | 23 May 2019 | |
344 | General | 71 | 23 May 2019 | KC will send a note to the team with a proposal for recommendation 18. | KC | 23 May 2019 | Email sent to list. | 23 May 2019 | |
339 | Work plan | 63 | 14 Mar 2019 | Review team plans to update the workplan document in Brussels. | Review Team | 19 May 2019 | Updated work plan circulated to leadership for approval, will be shared with review team ahead of 30 May plenary. | 21 May 2019 | |
342 | SSR1 | 63 | 14 Mar 2019 | Denise, Laurin, Zarko will look through the team’s SSR1 recommendations work for quality assurance and report back to team. | Denise, Laurin, Zarko | 17 May 2019 | Denise and Laurin reported no response from Zarko. | 19 May 2019 | |
354 | General | 68 | 2 May 2019 | Team to collectively discuss how to address items that are blocked | Review Team | 17 May 2019 | Team addressed all items during Brussels face-to-face | 19 May 2019 | |
356 | General | 69 | 9 May 2019 | Staff to follow up with SMEs on the outstanding answers to get these ahead of the Brussels meeting. | ICANN Org | 17 May 2019 | Outstanding answer provided via email. | 18 May 2019 | |
357 | General | 69 | 9 May 2019 | Review team members to work on topic item write-ups to be ready for the Brussels meeting. | Review Team | 17 May 2019 | RT members worked on write ups ahead of meeting. | 17 May 2019 | |
353 | General | 66 | 18 Apr 2019 | All team members to keep working on their topic items. | Review Team | 17 May 2019 | Replaced by action 357. | 9 May 2019 | |
355 | General | 68 | 2 May 2019 | Request to increase the meeting duration to 90 minutes for the Compliance call on the 14th | ICANN org | 9 May 2019 | Completed - call extended to 90 mins | 9 May 2019 | |
351 | General | 67 | 25 Apr 2019 | Team members to fill in the status table where items are blank by next week’s call. For red items, team to work on progressing off of red where there are no roadblocks. | Review Team | 2 May 2019 | Table reviewed during meeting. | 2 May 2019 | |
350 | General | 67 | 25 Apr 2019 | Staff to share the questions with Compliance and set up the meeting with SSR2 RT members. | ICANN org | 10 May 2019 | Meeting scheduled for 14 May | 30 Apr 2019 | |
337 | General | 12 Mar 2019 | Review Team request to meet with ICANN compliance to discuss contractual compliance as it relates to SSR | ICANN Org | 17 May 2019 | Replaced by action 350. | 25 Apr 2019 | ||
349 | General | 67 | 25 Apr 2019 | Laurin will send the questions to staff to share with Compliance. | Laurin | 25 Apr 2019 | Shared via email. | 25 Apr 2019 | |
345 | General | 64 | 28 Mar 2019 | Laurin will take the lead to coordinate with the group to develop and formalize questions for compliance | Laurin | 17 May 2019 | Replaced by action 349. | 25 Apr 2019 | |
352 | General | 66 | 18 Apr 2019 | Boban to send a follow-up question today for staff based on the written responses provided to previous questions. | Boban | 22 Apr 2019 | Sent via email. | 23 Apr 2019 | |
340 | General | 63 | 14 Mar 2019 | Review team members to continue working on the items in the table, in time for Brussels. | Review Team | 17 May 2019 | Replaced by action item 353 | 18 Apr 2019 | |
343 | Outreach | 63 | 14 Mar 2019 | Staff to draft a note for Russ to send out to community SO/ACs to ask for time on the agenda to present the recommendations in Marrakech. | ICANN org | 29 Mar 2019 | Shared with leadership via email. | 15 Apr 2019 | |
348 | General | 65 | 11 Apr 2019 | Russ to send a note to each of the team leads to ensure items are moving and ask if there are any roadblocks they need help with. | Russ | 11 Apr 2019 | Note sent to team. | 11 Apr 2019 | |
346 | General | 64 | 28 Mar 2019 | Staff to contact Noorul to remind him he is the 'lead' on the future challenges item: Root server system protection: assess the threatscape of top threats (e.g. DDoS to the root system) | ICANN org | 29 Mar 2019 | Noorul sent email off-list | 1 Apr 2019 | |
347 | General | 64 | 28 Mar 2019 | Staff to send a reminder to everyone to check volunteer document to see their involvement and be ready to provide an update on next week’s call. | ICANN org | 29 Mar 2019 | Email sent to RT members. | 29 Mar 2019 | |
334 | General | 63 | 9 Mar 2019 | ICANN org to find out re: ITHI - how is it different from ODI, where does it get its data (from internal collection or external data) and where is its data. | ICANN org | 29 Mar 2019 | Questions recorded in Q&A Google doc. Response will be shared in the doc when available | 21 Mar 2019 | |
333 | General | 63 | 9 Mar 2019 | ICANN org to ask ICANN Ops about ODI to determine current status and location of ODI related items | ICANN org | 29 Mar 2019 | Questions recorded in Q&A Google doc. Response will be shared in the doc when available | 21 Mar 2019 | |
344 | Admin | 63 | 14 Mar 2019 | Staff to share contact information with each of the review team members individually. | ICANN org | 18 Mar 2019 | Email sent offlist | 18 Mar 2019 | |
335 | General | 63 | 9 Mar 2019 | Lead RT members bolded in the doc here to reach out to other volunteers listed for the topic and drive the process for developing text. | RT members | 14 Mar 2019 | Team members are continuing research on topics within volunteer group, to report back to team. | 14 Mar 2019 | |
331 | General | 63 | 8 Mar 2019 | KC to take the lead in research on any follow up from SSAC074, Denise offered to help. | KC, Denise | 13 Mar 2019 | Team members are continuing research on topics within volunteer group, to report back to team. | 14 Mar 2019 | |
338 | General | ICANN64 | 13 Mar 2019 | Review Team members to raise any objections to Danko Jevtovic as an additional Board liaison member | RT members | 14 Mar 2019 | Danko Jevtovic added to RT | 14 Mar 2019 | |
298 | SSR1 | 56 | 10 Jan 2019 | KC, Denise, Laurin, Alain, Scott to have a discussion with the RSSAC and SSAC regarding recommendation 23 (team members to volunteer if they want to participate). KC will talk to RSSAC/ SSAC chairs to set this up | KC to lead | 7 Mar 2019 | Team members are continuing research on topics within volunteer group, to report back to team. | 14 Mar 2019 | |
330 | General | 63 | 8 Mar 2019 | Denise to work with staff to set up a meeting with CCT RT members in Kobe, and any other groups/individuals the review team may wish to find time with in Kobe. | Denise, ICANN org | 13 Mar 2019 | Meeting took place on 11 March 2019, closed meeting | 11 Mar 2019 | |
336 | Admin | 63 | 9 Mar 2019 | Staff to send calendar invites for the writing time slots and room locations. | ICANN org | 9 Mar 2019 | Calendar invites sent | 9 Mar 2019 | |
332 | General | 63 | 8 Mar 2019 | Staff to go through the volunteers document and list how many questions are outstanding for each of the topics. | ICANN org | 8 Mar 2019 | Google doc updated. | 8 Mar 2019 | |
329 | Outreach | 63 | 8 Mar 2019 | Jennifer to finalize the slides. Content is finalized, formatting only required. | ICANN org | 8 Mar 2019 | Final slides shared to list | 8 Mar 2019 | |
328 | General | 61 | 21 Feb 2019 | Team members to continue working on the text for ICANN SSR, Future Challenges and DNS SSR worksteams. | RT members | 8 Mar 2019 | Ongoing with action 335 | 9 Mar 2019 | |
325 | Future Challenges | 60 | 14 Feb 2019 | Volunteers to do own research on future challenges topics | RT members | 6 Mar 2019 | Ongoing with action 335 | 9 Mar 2019 | |
324 | Future Challenges | 60 | 14 Feb 2019 | Future Challenges topic: Coalescence of registrars/registry/backend operators for multiple TLDs - Norm to research | Norm | 6 Mar 2019 | Replaced by action 335 | 9 Mar 2019 | |
322 | Future Challenges | 60 | 14 Feb 2019 | Kerry-Ann to work with staff to arrange a meeting with the workstream volunteers for future challenges. | Kerry-Ann, ICANN org | 6 Mar 2019 | Replaced by action 335 | 9 Mar 2019 | |
327 | DNS SSR | 61 | 21 Feb 2019 | Eric will put straw man text together for the DNS SSR items reviewed the call, and send to the volunteers for each item for input. | Eric | 28 Feb 2019 | Doc shared during face-to-face meeting day 2. | 9 Mar 2019 | |
313 | General | 58 | 27 Jan 2019 | Staff to Identify a couple of hours on the 12th and 13th March in Kobe for the SSR2 Review Team to work on the report. | ICANN org | 5 Mar 2019 | Times shared to the list. | 8 Mar 2019 | |
326 | General | 60 | 14 Feb 2019 | Add to leadership agenda on the 20th : opportunities for writing sessions in Kobe | ICANN org | 20 Feb 2019 | Discussed during leadership meeting. | 20 Feb 2019 | |
323 | Future Challenges | 60 | 14 Feb 2019 | Cryptosystems topic moved to Future Challenges - ICANN org to update team documents accordingly. | ICANN org | 19 Feb 2019 | Google docs updated. | 19 Feb 2019 | |
315 | General | 58 | 27 Jan 2019 | Team members to share any preferences for countries in Europe that are easy to meet based on your visa requirements. | RT members | 7 Feb 2019 | Request shared via email. Location suggestion shared with leadership via email. | 12 Feb 2019 | |
312 | General | 58 | 27 Jan 2019 | Create a page that captures all Google documents that the team is working on to identify the most current versions. | ICANN org | 1 Feb 2019 | Shared via email. | 11 Feb 2019 | |
308 | SSR1 | 58 | 27 Jan 2019 | SSR1 workstream: Laurin to fix intro to SSR1 section and recirculate to the list go through the SSR1 recommendations, circulate to team for final review. | Laurin | 7 Feb 2019 | Shared via email. | 10 Feb 2019 | |
319 | General | 59 | 31 Jan 2019 | Staff to share ICANN SSR and Future Challenges questions with SMEs and obtain answers, track status on the wiki. | ICANN org | 7 Feb 2019 | Questions shared with SMEs | ||
321 | Workplan | 59 | 31 Jan 2019 | Denise to send a proposed edit to the workplan to the list. | Denise | 4 Feb 2019 | Shared with staff; staff circulated to list for final edits. | 5 Feb 2019 | |
320 | DNS SSR | 59 | 31 Jan 2019 | RT members to add questions to the DNS SSR workstream by EOD Tuesday 5 February | RT members | 5 Feb 2019 | Staff shared list of questions with SMEs | 5 Feb 2019 | |
318 | General | 58 | 27 Jan 2019 | Leadership team to reach out to ICANN org management to let them know the importance of receiving answers to questions in a timely manner | Russ | 31 Jan 2019 | Email sent to David Conrad, ICANN CTO. | 31 Jan 2019 | |
317 | Workplan | 58 | 27 Jan 2019 | Staff to circulate updated workplan to the list. Team to review ahead of the call on Thursday, where there will be a call for approval. | ICANN org, RT members | 31 Jan 2019 | Workplan circulated to list via email. Discussion on plenary 59. | 31 Jan 2019 | |
316 | Outreach | 58 | 27 Jan 2019 | Staff to draft a blog post coming out of this meeting to highlight the teams progress, status of work, invitation to reach out via the mailing list if there is an interest to set up meetings consultation in Kobe. | ICANN org | 1 Feb 2019 | Draft blog shared with leadership team via email. | 31 Jan 2019 | |
310 | DNS SSR | 58 | 27 Jan 2019 | DNS SSR workstream: Team members who have volunteered for each DNS SSR work topic to develop questions. | RT members | 31 Jan 2019 | Replaced by action item | ||
309 | Future Challenges, ICANN SSR1 | 58 | 27 Jan 2019 | ICANN SSR workstream & Future challenges workstream: Staff to pull out the list of questions from the ICANN SSR and Future Challenges workstream topic for team’s review on Thursday. | ICANN org | 29 Jan 2019 | Questions circulated to list. | 29 Jan 2019 | |
314 | General | 58 | 27 Jan 2019 | Send a save the date for 17th, 18th, 19th May face-to-face meeting in Europe. Exact locations TBD. | ICANN org | 27 Jan 2019 | Save the date sent to list. | 27 Jan 2019 | |
311 | General | 58 | Staff to circulate the table of volunteers for each workstream item, team members to add their names to topics they wish to work on. | ICANN org | 27 Jan 2019 | Circulated to list. | 27 Jan 2019 | ||
294 | General | 55 | 20 Dec 2018 | Team to discuss a potential face-to face meeting in May 2019 during the January meeting in LA. Staff to give travel and meetings team the heads up. | ICANN org / RT members | 27 Jan 2019 | Team agreed to next meeting in Europe, 17-19 May 2019, during LA meeting. | 27 Jan 2019 | |
303 | SSR1 | 57 | 17 Jan 2019 | Leadership team will go through the changes in the document after the deadline, ahead of the consensus call to be held in LA during face-to-face meeting. | SSR2 Leadership Team | 25 Jan 2019 | Team reviewed the document during LA meeting. | 26 Jan 2019 | |
304 | ICANN SSR | 57 | 17 Jan 2019 | Those involved in ICANN SSR former subteam go through the outcomes from the LA meeting and previous subgroup work to flag any areas where more follow-up or interviews are required. | Boban, Denise, Eric, Kerry-Ann, Žarko, Norm, Noorul | 22 Jan 2019 | Team instead discussed this during LA meeting. | 25 Jan 2019 | |
302 | SSR1 | 57 | 17 Jan 2019 | Team members to use suggestion mode to make any final suggestions to the text in the Google document by Tuesday 22 January 23:59 UTC. | RT members | 22 Jan 2019 | See completed response to action item 303. | 22 Jan 2019 | |
306 | DNS SSR | 57 | 17 Jan 2019 | Eric will share DNS SSR topics to the list - for team member input | Eric | 18 Jan 2019 | Shared to list via email. | 23 Jan 2019 | |
307 | General | 57 | 17 Jan 2019 | Add to leadership agenda for next week, Amin's resignation. | ICANN org | 22 Jan 2019 | Note sent to GAC on behalf of leadership via email. | 23 Jan 2019 | |
230 | SSR1 | 42 | 6 Sep 2018 | Staff to pursue answers to and provide expected completion dates for all outstanding SSR1 implementation questions. | ICANN org | 27 Jan 2019 | Team are now finalizing text. All outstanding questions answered. | 19 Jan 2019 | |
296 | General | 56 | 10 Jan 2019 | Team members to complete Doodle poll for a potential f2f meeting in May (poll to be circulated on list). | RT members | 17 Jan 2019 | Reminders sent to RT members of 18 Jan deadline. | 19 Jan 2019 | |
301 | Admin | 56 | 10 Jan 2019 | Leadership will develop a draft agenda for the January f2f meeting. Team members to email suggestions to Russ ahead of Monday’s leadership call. | Leadership team | 14 Jan 2019 | Draft agenda to be finalized on upcoming leadership call. | 18 Jan 2019 | |
305 | ICANN SSR | 57 | 17 Jan 2019 | Jennifer to circulate information to the list that is on the wiki and would be helpful fo the team. | ICANN org | 18 Jan 2019 | Links shared via email. | 18 Jan 2019 | |
297 | SSR1 | 56 | 10 Jan 2019 | Scott will input text for SSR1 recommendations 17 & 18 into the Google doc. | Scott | 17 Jan 2019 | Replaced by action item 302. | 18 Jan 2019 | |
299 | SSR1 | 56 | 10 Jan 2019 | Kerry-Ann to input text to Google doc to explain that text for SSR1 recommendations 25 and 26 is contained within the text for recommendation 27. | Kerry-Ann | 17 Jan 2019 | Replaced by action item 302. | 18 Jan 2019 | |
300 | SSR1 | 56 | 10 Jan 2019 | Noorul to input text to the Google doc regarding overlap between recommendations 24 and 28, and that text for both recommendations is merged. | Noorul | 17 Jan 2019 | Replaced by action item 302. | 18 Jan 2019 | |
293 | SSR1 | 55 | 20 Dec 2018 | Team members to input draft text into the SSR1 recommendations Google doc using the findings recorded by the review team. Russ to send a reminder. Penholders are indicated in the document. | RT members | 10 Jan 2019 | Discussed during plenary 56. | 10 Jan 2019 | |
292 | DNS SSR | 55 | 20 Dec 2018 | Team members to review the DNS SSR preamble text and share any additional comments in the document or on-list ahead of the 10 January plenary call. | RT members | 10 Jan 2019 | Google doc available for team member edits. | 10 Jan 2019 | |
295 | SSR1 | 55 | 20 Dec 2018 | KC to reach out to Naveed regarding recommendation 23 draft text. | KC | 10 Jan 2019 | Draft text for recommendation 23 input to Google doc | 7 Jan 2019 | |
291 | Work plan | 55 | 20 Dec 2018 | Staff to post updated work plan as circulated to the list and approved on the 20 December. | ICANN org | 20 Dec 2018 | Posted to wiki page. | 21 Dec 2018 | |
289 | SSR1 | 54 | 13 Dec 2018 | Penholders to draft text for team review for each SSR1 recommendation, using the Google doc here: https://docs.google.com/document/d/1WwzmsBDEtI0uvrxqSIs7zaBZRalZkC-TwO1VE_pN_7A/edit. Use the same structure as recommendation 4, which Laurin presented on the call. | RT members | 20 Dec 2018 | See action item 293. | 20 Dec 2018 | |
285 | SSR1 | 53 | 6 Dec 2018 | RT members who did research on the SSR1 Recommendations to start write up of findings. For recommendations that have more than one person researching it, they should collaborate on the write-up. | RT members | 20 Dec 2018 | See action item 293 | 20 Dec 2018 | |
288 | General | 54 | 13 Dec 2018 | Team to review preamble documents (ICANN SSR, Future Challenges and DNS SSR when available) and add comments to the doc. Review of preambles will be added to the agenda of the next call (20 December) | RT members | 20 Dec 2018 | See action item 292. | 20 Dec 2019 | |
287 | Work plan | 53 | 6 Dec 2018 | Staff to monitor the work plan tasks and raise any upcoming tasks requiring attention to the leadership. Following that discussion, the work plan items will be raised during the plenary call. Once a month, an updated work plan will be posted to the Wiki page. | ICANN org | 20 Dec 2018 | Updated work plan agreed and posted to the wiki. | 20 Dec 2018 | |
290 | DNS SSR | 54 | 13 Dec 2018 | Russ to send note to Eric to find out the estimated delivery date of the DNS SSR subgroup preamble text. | Russ | 23 Dec 2018 | Discussed on 17 December leadership call - Eric will deliver text ahead of 20 December plenary | 17 Dec 2018 | |
272 | General | 50 | 8 Nov 2018 | Denise will hold the pen on the updated draft of the workstream report template based on comments from team, and share with the team for final review. | Denise | 17 May 2019 | See leadership action 79. | 17 Dec 2019 | |
282 | General | 52 | 29 Nov 2018 | Rapporteurs of other work streams (other than SSR1) to produce a draft methodology and distribute to the review team mailing list for feedback. | Boban, Eric, Kerry-Ann | 13 Dec 2018 | Preambles for workstreams #2 and #4 circulated to team. Workstream #3 will be circulated ahead of 20 December plenary. | 13 Dec 2018 | |
291 | Admin | 54 | 13 Dec 2018 | Staff to connect with meetings team to check on estimated date for notifications regarding LA meeting. | ICANN org | 13 Dec 2018 | Note sent to meetings team - staff will follow up with RT members with more information when available. | 13 Dec 2018 | |
244 | SSR1 | 47 | 11 Oct 2018 | Denise will send follow-up questions and suggestions regarding further work for the consideration of the review team, via email to the list. | Denise | 17 Oct 2018 | Action item closed. RT members may follow up with additional questions any time. | 12 Dec 2018 | |
286 | SSR1 | 53 | 6 Dec 2018 | Staff to create a new google doc with the approved SSR1 preamble and ensure all RT members have access to it, so the write-up of findings can start. | ICANN org | 10 Dec | Google doc created and circulated via email. | 10 Dec 2018 | |
284 | Future Challenges | 53 | 6 Dec 2018 | Kerry-Ann to send the preamble for her work stream to the RT Leadership team by noon EST so the leadership can review the write-up. | Kerry-Ann | 6 Dec 2018 | Preamble circulated to team via email for review/edits. | 11 Dec 2018 | |
283 | General | 53 | 6 Dec 2018 | Staff to send a doodle poll to the RT to choose between LA and Vancouver, (and indicate visa needs) as the location of the next meeting. Deadline for the doodle poll to be 23:59 UTC on sunday 09 December 2018. | ICANN org | 6 Dec 2018 | Doodle poll shared via email | 6 Dec 2018 | |
278 | SSR1 | 51 | 15 Nov 2018 | Staff to work with leadership to outline next steps & timeline for SSR1 recommendations text in the Google doc; add ‘owner of draft text’ field to the Google doc. | ICANN org/leadership | 22 Nov 2018 | 'Owner of draft text' field added to Google doc. SSR1 recommendations next steps added to 6 December plenary agenda per 3 Dec leadership meeting. | 3 Dec 2018 | |
281 | Admin | 52 | 29 Nov 2018 | Staff to send hold-calendar invites to the RT for the March meeting in Kobe. | ICANN org | 29 Nov 2018 | Hold invites sent to team members. | 29 Nov 2018 | |
280 | SSR1 | 52 | 29 Nov 2018 | Russ to send out the SSR1 methodology document to the RT mailing list for RT approval | Russ | 29 Nov 2018 | Circulated to team via email. | 29 Nov 2018 | |
279 | SSR1 | 52 | 29 Nov 2018 | Laurin to modify the SSR1 methodology document based on the discussion in the plenary call. | Laurin | 29 Nov 2018 | Updated doc circulated to team for final edits. | 29 Nov 2018 | |
258 | Admin | 48 | 24 Oct 2018 | Staff to research options for RT to book-end the ICANN64 meeting in Kobe with face-to-face meetings. | ICANN org | 9 Nov 2018 | Addressed on plenary call 52 | 29 Nov 2018 | |
276 | SSR1 | 51 | 15 Nov 2018 | Team members who would like to see changes in methodology to post thoughts specifically to the email list. | RT members | 22 Nov 2018 | 'SSR1 assessment methodology preamble' document circulated to team for feedback. | 22 Nov 2018 | |
277 | SSR1 | 51 | 15 Nov 2018 | Leadership to discuss SSR1 methodology concerns voiced by review team members to date and circle back to the team | Leadership | 22 Nov 2018 | Discussed during 19 Nov leadership call. Note to team to follow, see leadership action item 66 | 19 Nov 2018 | |
275 | Admin | 51 | 15 Nov 2018 | Staff to recirculate Doodle poll with reminder of deadline. Team members to complete Doodle poll by EOD Thursday. | ICANN org | 15 Nov 2018 | Sent directly via email to those required to take action. | 15 Nov 2018 | |
269 | SSR1 | 50 | 8 Nov 2018 | Leadership to send a note to the team noting that “email thread re: SSR1 recommendations methodology” will be addressed on next week’s plenary call, and those with questions/concerns should be ready to address this agenda item on the call. | SSR2 leadership | 12 Nov 2018 | Item added to plenary call 51. | 14 Nov 2018 | |
271 | Work plan | 50 | 8 Nov 2018 | Once adopted, staff to circulate the work plan to SO/AC leaders and Board on behalf of the SSR2 RT (RT in copy) and post to SSR2 wiki. | ICANN org | 12 Nov 2018 | Sent via email | 14 Nov 2018 | |
274 | SSR1 | 50 | 8 Nov 2018 | Add SSR1 recommendations work to leadership agenda. | ICANN org | 12 Nov 2018 | Discussed on leadership meeting 12 Nov. See leadership action items 60 & 61 | 12 Nov 2018 | |
268 | Admin | 50 | 8 Nov 2018 | Staff to send collated summary of conflicts to leadership team by end of this week, with the aim of sending a Doodle poll to team early next week (locations to include Vancouver, DC, LA, Brussels). | ICANN org | 9 Nov 2018 | Sent via email. | ||
273 | ICANN SSR, DNS SSR | 50 | 8 Nov 2018 | KC to send an FYI email to the team noting the summary of discussions around workstream 3 and 4, shared during call last week; members should raise any substantive issues on-list by the next call. | KC | 8 Nov 2018 | Sent via email. | 8 Nov 2018 | |
270 | Work plan | 50 | 8 Nov 2018 | Staff to recirculate work plan to the list, and ask team members to check over and raise any objections within 24 hours. Unless objections are raised, this work plan will be considered as adopted, noting that the work plan is a living document and will be updated as needed. | ICANN org | 8 Nov 2018 | Sent via email. | 8 Nov 2018 | |
267 | Admin | 50 | 8 Nov 2018 | Staff to send a note to the list and ask the team to send any personal conflicts or preferences in January or February to ssr2-staff@icann.org, off-list within 24 hours. | ICANN org | 8 Nov 2018 | Sent via email. | 8 Nov 2018 | |
266 | SSR1 | 49 | 1 Nov 2018 | Note Alain and Boban’s items raised via email for discussion on next week’s call if not resolved on-list beforehand. | RT members | 8 Nov 2018 | Added to agenda of meeting 50 and see action item 269. | 8 Nov 2018 | |
264 | Work plan | 49 | 1 Nov 2018 | By beginning of next plenary call, RT members to look at % completion and note whether they think this is accurate or not. Column G of work plan sheet. | RT members | 8 Nov 2018 | Replaced by action item 270 | 8 Nov 2018 | |
259 | Admin | 48 | 24 Oct 2018 | Staff to research options for the RT to have a face-to-face meeting in late January or February 2019, and circulate a Doodle poll to RT with options. | ICANN org | 9 Nov 2018 | Replaced by action item 268 | 8 Nov 2018 | |
248 | Outreach | 47 | 11 Oct 2018 | Leadership will post a draft of proposed outreach (blog) to the list for Review Team input. | SSR2 leadership | 8 Nov 2018 | Denise shared via email. | 7 Nov 2018 | |
265 | Work plan | 49 | 1 Nov 2018 | Naveed to update workplan with suggested dates and re-circulate within 48 hours to the team for agreement or discussion on-list ahead of next week's meeting. Staff to share notes from call with Naveed to incorporate comments from this meeting. | Naveed | 5 Nov 2018 | Laurin circulated Naveed's update via email. | 6 Nov 2018 | |
261 | Outreach | 48 | 24 Oct 2018 | Staff to create first draft of SSR2 post-ICANN63 blog and share with leadership for initial edits. | ICANN org | 2 Nov 2018 | Shared via email | 5 Nov 2018 | |
263 | General | 49 | 1 Nov 2018 | Staff to recirculate the template for findings and recommendations to the RT. Review team members to flag within 24 hours of the email distribution if any objections to adopting the template. | ICANN org | 5 Nov 2018 | Circulated via email. | 2 Nov 2018 | |
250 | SSR1 | 48 | 21 Oct 2018 | Staff to re-circulate to list any questions requiring clarification from RT and continue to pursue answers to outstanding questions/update delivery dates as required. | ICANN org | 1 Nov 2018 | Shared an update via email. | 1 Nov 2018 | |
257 | Future Challenges | 48 | 24 Oct 2018 | Review Team to determine next steps for work stream 4 (future challenges). Team discussed including moving relevant topics to other work streams, or shortening the list of items to address and rebranding the work steam. | Review Team | 9 Nov 2018 | Team discussed during meeting. | 1 Nov 2018 | |
219 | Restart | 40 | 24 Aug 2018 | Staff to check with SSR2 Board Caucus Group that it is comfortable with new template for terms of reference. | ICANN org | 7 Mar 2019 | RT adopted ToR | 1 Nov 2018 | |
260 | Work Plan | 48 | 24 Oct 2018 | Staff to update work plan based on RT notes in the Google sheet and circulate to RT. | ICANN org | 1 Nov 2018 | Shared with leadership via email. Team discussed during meeting. | 1 Nov 2018 | |
256 | DNS SSR | 48 | 24 Oct 2018 | KC, Eric and any other volunteers to work on moving topics from DNS SSR topics document to SSR2 work steam topics document. | KC, Eric | 31 Oct 2018 | KC sent email to list. | 31 Oct 2018 | |
254 | ICANN SSR | 48 | 24 Oct 2018 | Staff to provide all RT members with access to Trello and remove RT members who have resigned | ICANN Org | 29 Oct 2018 | All RT members invited to Trello, resigned RT members removed. | 29 Oct 2018 | |
262 | Admin | 48 | 24 Oct 2018 | Staff to send a note to the Review Team notifying them to the end of daylight savings time and impact on call time. Review Team members to advise any objections to keeping the call at 14:00 UTC by Friday 26 October EOD | ICANN org | 24 Oct 2018 | Circulated via email. | 24 Oct 2018 | |
255 | Admin | 48 | 21 Oct 2018 | Staff to circulate CCT briefing slides to the SSR2 RT | ICANN Org | 24 Oct 2018 | Circulated via email and posted to briefings page. | 24 Oct 2018 | |
252 | SSR1 | 48 | 21 Oct 2018 | Review Team members to complete text in Google doc for each SSR1 recommendation ahead of Wednesday 24 October meeting | Review Team | 24 Oct 2018 | RT reviewed additions to Google doc during 24 Oct meeting. | 24 Oct 2018 | |
253 | Admin | 48 | 21 Oct 2018 | Staff to update Wednesday 24 October meeting agenda and circulate to RT along with background materials | ICANN Org | 23 Oct 2018 | Circulated via email | 23 Oct 2018 | |
251 | SSR1 | 48 | 21 Oct 2018 | Scott to send question regarding recommendation 15 to staff via email | Scott | 21 Oct 2018 | Scott sent email off-list to staff. | 21 Oct 2018 | |
249 | Outreach | 48 | 21 Oct 2018 | Staff to update and finalize Engagement Session slides based on RT comments | ICANN Org | 22 Oct 2018 | ICANN Org updated the slides. | 22 Oct 2018 | |
245 | SSR1 | 47 | 11 Oct 2018 | Team to progress work on-list between now and Barcelona, with the aim of team members sharing initial strawman proposals on all SSR1 recommendations between now and Barcelona in Google doc. | Review Team | 21 Oct 2018 | RT members worked in Google doc ahead of Barcelona meeting. | 21 Oct 2018 | |
246 | Admin | 47 | 11 Oct 2018 | Staff to provide details regarding which SSR2 sessions in Barcelona will have remote participation on-list. | ICANN org | 16 Oct 2018 | Details circulated in draft agenda, via email. | 18 Oct 2018 | |
247 | General | 47 | 11 Oct 2018 | Leadership will post draft slides and meeting agenda for Barcelona to the list for Review Team input. | SSR2 leadership | 16 Oct 2018 | Shared via email. | 18 Oct 2018 | |
240 | Work plan | 46 | 4 Oct 2018 | Laurin to send an email to the team to ask for more volunteers to help Denise and Naveed with the work plan draft | Laurin | 5 Oct 2018 | Draft workplan shared via email for feedback. | 16 Oct 2018 | |
239 | Work plan | 46 | 4 Oct 2018 | Denise and Naveed volunteered to help begin drafting work plan skeleton to be shared with the review team for input. | Denise & Naveed | 11 Oct 2018 | Draft workplan shared via email | 16 Oct 2018 | |
243 | SSR1 | 46 | 4 Oct 2018 | Add as an agenda item to next week's call to discuss the methodology of assessing SSR1 recommendations and defining SMART recommendations. | ICANN org | 10 Oct 2018 | Item added to the agenda of 11 October meeting | 10 Oct 2018 | |
216 | Restart | 40 | 24 Aug 2018 | Kaveh to clarify if there is any disagreement from the Board on the approach regarding sending Terms of Reference to the Board as an FYI only | Kaveh | 10 Oct 2018 | Board response sent to RT via email. | 10 Oct 2018 | |
242 | SSR1 | 46 | 4 Oct 2018 | Staff to send an update to the SSR1 recommendations table document to include recommendations 1-28 to the list. | ICANN org | 10 Oct 2018 | Sent via email. | 10 Oct 2018 | |
241 | SSR1 | 46 | 4 Oct 2018 | Chairs have asked team members to sign up to SSR1 recommendations via the Doodle poll by the end of day October 5 | Review Team | 5 Oct 2018 | Deadline reached | 5 Oct 2018 | |
238 | SSR1 | 45 | 27 Sep 2018 | Review Team members to select which recommendations they wish to take the lead on developing a strawman proposal for. | Review Team | 4 Oct 2018 | Replaced by action item 241 | 4 Oct 2018 | |
237 | SSR1 | 45 | 27 Sep 2018 | Staff to prepare a Doodle poll of outstanding SSR1 recommendations. | ICANN org | 1 Oct 2018 | Sent via email. | 1 Oct 2018 | |
232 | General | 43 | 13 Sep 2018 | Staff to invite CCT review team to join a plenary meeting to answer questions. Review Team to confirm the best time for this to happen. | ICANN org/ Review Team | Replaced by action item 19 on leadership tracking tool. | 24 Sep 2018 | ||
236 | Admin | 44 | 20 Sep 2018 | Staff to send note to team regarding CT having sent emails out on 17th September. Team members to advise if they did not receive this email or require further support. | ICANN org | 20 Sep 2018 | Email sent to team. | 20 Sep 2018 | |
235 | General | 43 | 13 Sep 2018 | Staff to ask travel team to expedite travel request. | ICANN org | 17 Sep 2018 | Travel emails sent to team. | 17 Sep 2018 | |
234 | SSR1 | 43 | 13 Sep 2018 | Staff to add columns to the SSR1 questions table to capture the date of the ask, who asked the question and when it was answered, estimated completion date and additional notes for context. | ICANN org | 17 Sep 2018 | Table updated with requested columns | 17 Sep 2018 | |
227 | Admin | 42 | 6 Sep 2018 | ICANN org to plan for an engagement session at ICANN63. In the event there is no availability in the schedule, the SSR2 is open to holding the engagement session during its meeting on Wednesday. | ICANN org | 1 Oct 2018 | Request for an engagement session submitted. | 13 Sep 2018 | |
233 | Outreach | 43 | 13 Aug 2018 | Denise and Kerry-Ann to clarify via email with Matogoro that the comms plan is intended to be high-level | Denise / Kerry-Ann | 13 Sep 2018 | Response sent to Matogoro via email. | 13 Sep 2018 | |
206 | General | 40 | 22 Aug 2018 | Staff to arrange for CCT and RDS-WHOIS2 review teams to deliver briefings to the SSR2 review team. | ICANN Org | RDS webinar info shared with SSR2. See action item 232 for CCT info. | 13 Sep 2018 | ||
229 | Admin | 42 | 6 Sep 2018 | Staff to ensure that all of the questions RT has asked previously are posted in one table along with answers and expected completion date | ICANN org | 13 Sep 2018 | Table posted here. Delivery dates and answers to be populated as they are provided. | 13 Sep 2018 | |
231 | SSR1 | 42 | 6 Sep 2018 | Review team to take SSR1 rec 1 for discussion to the list and add to agenda for the next plenary call #43. | ICANN org | 13 Sep 2018 | Added to agenda of call 43. | 13 Sep 2018 | |
228 | Outreach | 42 | 6 Sep 2018 | Denise, and Kerry-Ann, with Laurin's help, to prepare a draft comms/outreach plan for review team consideration. Comms/outreach plan to be rediscussed on the next plenary call #43. | Denise, Kerry-Ann, Laurin | 13 Sep 2018 | Draft circulated to thelist and adopted during meeting 43 | 12 Sep 2018 | |
146 | SSR1 | 26 Aug 2017 | Provide responses to SSR1 Implementation Recs 1-20 Questions and Information Requests. See progress of each request here. | ICANN Org | Replaced by action item 230. | 6 Sep 2018 | |||
101 | SSR1 | 21 | 1 Aug 2017 | Provide responses to questions on SSR1 briefing: Recommendations 11, 12. | ICANN Org | Replaced by action item 230. | 6 Sep 2018 | ||
167 | SSR1 | 9 Oct 2017 | Provide responses to SSR1 Implementation Recs 21-28 Questions and Information Requests. See progress of each request here. | ICANN Org | Progress of requests is available on the SSR1 Subgroup page. | Replaced by action item 230. | 6 Sep 2018 | ||
226 | Outreach | 41 | 30 Aug 2018 | Move outreach template to the list and discuss further. | Review team | 6 Sep 2018 | Template circulated to list via email | Replaced by action item 228. | 6 Sep 2018 |
224 | Admin | 41 | 30 Aug 2018 | ICANN org to explore the possibility of holding meetings at alternative venue as a backup that can be cancelled if a venue room can be identified instead. | ICANN org | 6 Sep 2018 | Staff provided confirmation during meeting 42 that the team can meet at the ICANN venue. | 6 Sep 2018 | |
217 | Admin | 40 | 24 Aug 2018 | Staff to submit the request for SSR2 to meet during the chosen dates in Barcelona, and clarify what process is with meetings team & SO/AC Chairs for requesting such meetings, including expected timelines for planning purposes. | ICANN org | Update provided to leadership during the 5 September meeting. Item added to agenda of 6 September plenary to update review team. | 5 Sep 2018 | ||
206 | General | 40 | 22 Aug 2018 | Staff to arrange for CCT and RDS-WHOIS2 review teams to deliver briefings to the SSR2 review team. | ICANN Org | RDS webinar info shared with SSR2. See action item 4 of leadership tracking tool for CCT info. | 5 Sep 2018 | ||
205 | Admin | 40 | 22 Aug 2018 | Staff to create page on SSR2 wiki to include relevant ICANN org review reports for team to digest easily. | ICANN Org | 31 Aug 2017 | CCT and RDS reports added to background materials page of the SSR2 wiki. | 4 Sep 2018 | |
225 | Restart | 41 | 30 Aug 2018 | Review team members to send suggested edits and comments on communique to the mailing-list by Tuesday COB. Denise to hold the pen and to issue revised draft. | Review team | 4 Sep 2018 | Review team finalized the blog on-list. ICANN org proceeding with publication process. | 4 Sep 2018 | |
223 | Admin | 41 | 30 Aug 2018 | MSSI-Secretariat to circulate placeholder calendar invites for October 21 and October 24. | ICANN org | 31 Aug 2018 | Placeholder calendar invites sent to team. | 31 Aug 2018 | |
212 | General | 40 | 24 Aug 2018 | Subgroup rapporteurs to send bullet points of key reading materials to display on each subgroup page of the wiki. | Subgroup Rapporteurs | 18 Oct 2018 | Team decided to inline subgroup work to plenary level. | 30 Aug 2018 | |
53 | SSR1 | 15 May 2017 | Draft note and summary of SSR1 implementation for ICANN to send to SSR1 team members and invite them to share their assessment with the SSR2-RT. | Denise Michel | Team decided to inline subgroup work to plenary level. | 30 Aug 2018 | |||
166 | IANA | 9 Oct 2017 | Advise if the sub-team requires an NDA to access, and provide access to requested documents. | ICANN org | Team decided to inline subgroup work to plenary level. IANA workstream 5 not continuing. | 30 Aug 2018 | |||
166.1 | IANA | Email | 9 Oct 2017 | Provide access to Business continuity plan for PTI.
| ICANN org | Team decided to inline subgroup work to plenary level. IANA workstream 5 not continuing. | 30 Aug 2018 | ||
166.2 | IANA | 9 Oct 2017 | Processes and training.: Deliver a presentation on training and processes documents to a good level of detail. To replace seeing the docs themselves. | ICANN org | Team decided to inline subgroup work to plenary level. IANA workstream 5 not continuing. | 30 Aug 2018 | |||
166.3 | IANA | 9 Oct 2017 | Provide documented evidence of business continuity test (if it exists) | ICANN org | Team decided to inline subgroup work to plenary level. IANA workstream 5 not continuing. | 30 Aug 2018 | |||
166.4 | IANA | 9 Oct 2017 | Provide a high-level walk through of RZMS, from perspective of cc and gTLDs (to clarify issues) | ICANN org | Team decided to inline subgroup work to plenary level. IANA workstream 5 not continuing. | 30 Aug 2018 | |||
166.5 | IANA | 9 Oct 2017 | Field verification of RZMS – deliver a presentation on controls within the RZMS system | ICANN org | Team decided to inline subgroup work to plenary level. IANA workstream 5 not continuing. | 30 Aug 2018 | |||
166.6 | IANA | 9 Oct 2017 | Provide access to documentation that identifies procedures for verifying authorized contact. | ICANN org | Team decided to inline subgroup work to plenary level. IANA workstream 5 not continuing. | 30 Aug 2018 | |||
166.7 | IANA | 9 Oct 2017 | Deliver a presentation on relationship between PTI, ICANN and the root zone maintainer, post-transition (with roles and responsibilities, who works where, who have authority) | ICANN org | Team decided to inline subgroup work to plenary level. IANA workstream 5 not continuing. | 30 Aug 2018 | |||
147 | ICANN SSR | Trello | 27 Aug 2017 | ICANN to ID an EBERO operator that the ICANN SSR subgroup can interview to speak to the experience of acting in a provider capacity. | ICANN Org |
| Team decided to inline subgroup work to plenary level. | 30 Aug 2018 | |
141 | IANA | IANA Transition Subteam Meeting | 24 Aug 2017 | Schedule time for Eric to meet with Kim Davies in Abu Dhabi to answer questions on PGP alternatives to progress the IANA transition subteam's work. | ICANN Org |
| Team decided to inline subgroup work to plenary level. | 30 Aug 2018 | |
139 | SSR1 | 24 | 22 Aug 2017 | Review Team members to volunteer if they feel they can contribute to the SSR1 implementation subgroup. | SSR2-RT | Team decided to inline subgroup work to plenary level. | 30 Aug 2018 | ||
221 | Restart | 40 | Review team members to review the redline Terms of Reference document that Laurin circulated to the list. | Review team | Team discussed ToR and finalized during meeting 41. | ||||
222 | Admin | 40 | Staff to provide update to the review team on Barcelona meeting planning during the review team’s next conference call. | ICANN org | Update provided during meeting 41. New action items as a result. | ||||
213 | Restart | 40 | Staff to draft communique for review team leadership review feedback | ICANN org | Circulated to the list via email. | ||||
202 | Restart | 40 | Staff to send the SSR2 skills matrix the team completed during the pause to the list | ICANN org | Posted link to the A/C room during discussion and circulated via email. | ||||
99 | DNS SSR | 19 Jun 2017 | Provide briefing on DNS Abuse study final results | ICANN Org |
| 24 Aug 2018 | |||
98 | General | 19 Jun 2017 | Provide briefing on Framework for Registry Operators to Respond to Security Threats | ICANN Org |
| 24 Aug 2018 | |||
44 | Procurement | 14 May 2017 | Draft a Statement of Work for specialist technical writer: Co-Chairs to provide guidance on the scope of work and other requirements for the engagement of the technical writer. | Co-Chairs |
| 24 Aug 2018 | |||
220 | Restart | 40 | Laurin to circulate the updated timeline for inclusion in Terms of Reference | Laurin | Circulated via email. | ||||
218 | Admin | 40 | Staff to issue a doodle poll using the 13:00 - 17:00 UTC - Tuesday - Wednesday – Thursday, for team to complete within 12-hour deadline | ICANN org | Circulated via email. | ||||
215 | Admin | 40 | Staff to arrange for review team members to have editing rights for the wiki | ICANN org | Tech support confirmed emails sent. | ||||
214 | Admin | 40 | Staff to collect outstanding Barcelona availability from team members | ICANN org | Complete. | ||||
211 | Restart | 40 | Staff to send a note to the review team list formally announcing the new leadership | ICANN org | Shared via email. | ||||
199 | Restart | 39 | Review Team/Phil to add ‘consultant support’ as a discussion topic to the DC agenda. | Phil/Team | |||||
210 | Admin | 40 | Staff to fix mailing list mailing archives for subgroups | ICANN org | All links open to public viewing. | ||||
209 | Restart | 40 | Laurin to apply edits flagged in today’s session to terms of reference draft | Laurin | Shared via email | ||||
208 | Restart | 40 | Staff to circulate new Terms of Reference template to the list | ICANN org | Shared via email. | ||||
204 | Outreach | 40 | Kerry-Ann to share communications matrix with the team | Kerry-Ann | Shared via email. | ||||
203 | Restart | 40 | Phil to update slide regarding expectations of team members to communicate with community based on team’s comments. | Phil | Completed and displayed during day 2 of the meeting. | ||||
207 | Restart | 40 | Staff to circulate the adopted consensus methodology and roles/responsibilities for leadership to the review | ICANN org | Shared via email. | ||||
201 | Restart | 39 | Phil to finalize summary slides of subgroup progress, and work with staff to suggest any edits/additions to the wiki that might help new members with summarizing work to date. | Phil/ICANN org | Summary slides circulated via email. Discussions during face-to-face meeting will influence next steps regarding wiki updates. | ||||
200 | Restart | 39 | Team to share any absences they expect to have during the f2f meeting via email with Phil as well as any additional feedback to the draft session plan that was circulated to the list. | Review team | |||||
194 | NDA | 38 |
| Staff to provide a brief email summary of the position arrived at by the review team regarding the NDA prior to the pause (include NDA as attachment to the email). | ICANN org | Summary circulated via email. | |||
193 | Admin | 38 |
| Staff to complete task of posting records of leadership meetings and emails to the wiki. | ICANN org | Archives of leadership meetings posted to the wiki here. | |||
181 | Restart | 37 |
| Team members to provide Phil with suggestions on how to recommence review work in preparation for the DC meeting | Review team | Subgroup summary circulated to group via email to help discussions in DC. | |||
198 | Admin | 39 | | Staff/Phil to circulate a revised email regarding options to meet at ICANN63 and a Doodle poll with the options. | Staff/Phil | Doodle poll circulated to team via email. | |||
197 | Admin | 39 |
| Phil to update meeting record of previous meeting, August 2, and re-circulate. | Phil | Updated notes sent to team via email and posted to the Meeting 38 wiki page. | |||
192 | Admin | 38 | Staff to share information about options to meet in Barcelona and circulate a Doodle poll. | ICANN org | Information about options to meet circulated via email. Doodle poll action replaced by action item 198. | ||||
196 | Restart | 38 |
| Phil to send questions via email for the review team to react to regarding methodology and approach to work | Phil | During meeting 39 Phil asked the team to share if they have any methodology suggestions or resources that would be useful to help the team find common language when talking about different approaches to work. | |||
185 | Restart | 37 |
| Include budget discussion in the DC meeting objectives | Review team/Phil | Budget process included as agenda item on the draft DC meeting session plan circulated via email. | |||
195 | Restart | 38 |
| Phil to circulate a draft session plan for the DC meeting prior to the next review team meeting. | Phil | Circulated to team via email. | |||
182 | Restart | 37 |
| RT members to provide feedback on draft set of objectives for DC face-to-face meeting. | Review team | Review team members provided feedback during 2 August meeting. As a next step Phil will circulate a session plan for review team member feedback. | |||
175 | Admin | 36 |
| Denise and Eric to work with staff to progress Washington D.C. meeting planning. | ICANN Org, Denise & Eric |
| Budget update email sent to leadership 19 July, Update on attendance provided verbally during RT meeting 2 August. |
| |
179 | Restart | 37 |
| Phil to circulate a request for volunteers to produce a narrative of methodology used to determine scope of work, division of work/subgroups (incl. progress) | Phil |
| Requests sent to RT members. |
| |
180 | SSR1 | 37 |
| ICANN org to pull together a SSR1 implementation package (briefing materials, SSR1 implementation related questions) for posting on the ICANN wiki | ICANN org | New Briefing Materials page created on the wiki. Information circulated to the team. See email. |
| ||
191 | Admin | 37 |
| ICANN org to find out what the current FY budget is | ICANN org | Budget information circulated to the team. See email. |
| ||
173 | Admin | 36 |
| Phil to summarize and share stock-take on the status of the review team’s work. | Phil |
| Shared with Review Team members off-list (for Review Team only) |
| |
189 | Admin | 37 |
| ICANN org/Phil to put forward proposed times in next couple of days | ICANN org | Calendar invites for team next 3 meetings sent to all RT members and observers. |
| ||
188 | Admin | 37 |
| ICANN org to provide an overview of restrictions associated scheduling during ICANN meetings | ICANN org | Circulated to the team. See email. |
| ||
178 | Restart | 37 |
| Phil to provide a summary of deliverables established in contract | Phil | Circulated to the team. See email. |
| ||
174 | Admin | 36 |
| Review team members to review digest of background information circulated to list and provide suggestions/questions for anything that’s missing. New team members to advise what they would find most useful to be included in the digest. | Review team | New action items 179 & 180. | |||
184 | Admin | 37 |
| ICANN org to provide Phil with information on meeting room layout/size etc. | ICANN org | Information sent to Phil 23 July |
| ||
183 | Admin | 37 |
| ICANN org to continue reminding people that they should book flights for the DC meeting asap. | ICANN org | Reminders sent to RT members. |
| ||
190 | Admin | 37 |
| ICANN org to send meeting minutes to Phil for edits | ICANN org | Meeting minutes sent to Phil 20 July 2018. |
| ||
187 | Admin | 37 |
| ICANN org to submit a request for a two-day face-to-face meeting prior to ICANN63 | ICANN org | Request submitted for a meeting 18 & 19 October. |
| ||
177 | Admin | 36 |
| Review team members to share on-list any comments on the proposed call time slots/days within 24 hours. | Review team |
| Doodle poll circulated 9 July, closed 11 July. Poll result shared with leadership. |
| |
176 | Admin | 36 |
| Review team members who require a letter of invitation for visa procedures are asked to send a request to ssr2-staff@icann.org by 23:59 UTC on Friday 6 July. | Review team |
| Invitation letters distributed as required. |
| |
172 | Admin | 35 |
| RT members to fill out June/July/August blackout dates in Google doc to aid scheduling of next f2f meeting. | Review team |
| Team members completed Google doc. |
| |
171 | Admin | 35 |
| Staff to collate team member email addresses, time zone and location information and share off-list with RT members to aid scheduling of a regular team call. | ICANN Org |
| Information shared off-list with Review Team members upon receipt of permission to share from each team member. |
| |
170 | Admin | 35 |
| Staff to circulate Doodle poll to the team re: team’s next conference call meeting. Suggested date for meeting, week of July 3rd. | ICANN Org |
| Doodle poll circulated to mailing list. See email. |
| |
169 | Admin | 35 |
| Phil to work with co-chairs to prepare agenda/materials ahead of the next meeting for RT members to respond to. | Phil, Eric & Denise |
| Agenda circulated to mailing list. See email. |
| |
168 | Admin | 35 |
| Eric and Denise to draft a digest of reading materials ahead of the face-to-face meeting and share with the RT for feedback. | Eric & Denise |
| Draft digest circulated to mailing list. See email. |
| |
135 | Admin |
| Report to Team on potential room availability at ICANN meeting for sub-group meetings during week. | ICANN Org |
| No subteam meetings scheduled. |
| ||
160** | Outreach | 29 |
| Subteam rapporteurs to prepare a short status update for the presentations to the SO/AC groups in Abu Dhabi | SSR2 Subteam Rapporteurs | Review Team collaboratively created the slide deck during F2F meeting day 1 at ICANN60. |
| ||
134 | Admin |
| Send calendar invites for Team meeting days in Abu Dhabi and additional invites as meetings are scheduled. | ICANN Org | As needed. | Calendar invites for confrmed meetings, including outreach sessions, sent to team. |
| ||
118 | Admin | Co-Chairs |
| Provide list of meetings of interest in Abu Dhabi for Review Team and sub-teams when schedule is available | ICANN Org |
| List distributed to SSR2 Review Team via email. |
| |
152 | Admin | Co-Chairs |
| Review recorded decisions reached for accuracy and completeness. | ICANN Org, SSR2-RT | New process for decisions reached proposed via email to Co-Chairs. | Complete list of decisions circulated to Co-Chairs via email for review and approval. Disclaimer suggested to be added to the 'Decisions Reached' page of the wiki. |
| |
162 | Outreach | 29 |
| ICANN org to arrange meeting with Board Caucus group in Abu Dhabi. | ICANN Org | Meeting scheduled on Thursday 2 November. See ICANN60 schedule. |
| ||
83 | Admin | 17 |
| Review 06:00 plenary call slot attendance and provide input to inform discussion around potential cancelation of call. | Co-Chairs | Staff will revisit action item with Co-Chairs during Abu Dhabi meeting. |
| ||
80b. | SSR1 | 17 |
| Provide responses to questions from SSR1 briefings (Ops + Finance). | ICANN Org |
| Answers provided in Google document and circulated to Review Team. |
| |
75 | ICANN SSR | 17 |
| 75, b. Provide responses to draft questions for ICANN Chief Innovation & Information Officer (CIO). 75. a. Prepare draft questions for ICANN Chief Innovation & Information Officer (CIO). Questions will be sent to the CIO in preparation for holding a briefing for the RT. | 75.b. ICANN Org 75. a. SSR2-RT | 75. b. 75. a. |
| 75b. 75. a. | |
149 | NDA | 27 |
| Review Team members to review the Non-Disclosure Agreement and Confidential Disclosure Framework documents and raise any questions on the list. | SSR2-RT | Documents circulated to the list (29 August) and overview provided by Kerry-Ann on plenary meeting 27 (12 September). | Signed NDA documents posted on wiki and updated accordingly. |
| |
155 | Outreach | Co-Chairs |
| Create first draft of ICANN60 outreach slides for Co-Chairs review | ICANN Org |
| v1 draft slides circulated to Co-Chairs via email. |
| |
133 | Admin |
| Try www.trello.com and give your feedback on email list. Co-Chairs will assume Team members are comfortable using this unless otherwise informed. | SSR2-RT | Access granted and request sent via Trello for all team members to access the SSR2 Review Team boards. See action item 166 for workaround for team members unable to access Trello. |
| |||
136 | Admin |
| Respond to ICANN Travel ASAP & make flight reservations to travel to Abu Dhabi for the face-to-face meeeting. | SSR2-RT | Constituency Travel team working with RT to confirm travel arrangements. |
| |||
143 | IANA | IANA Transition Subteam Meeting |
| Break out IANA subteam document requests in order of priority to help expedite access to documents, once NDAs have been finalized and signed. | James Gannon | Replaced by action item 166. |
| ||
157** | ICANN SSR | ICANN SSR Subgroup Meeting |
| Team members to indicate which work item topics they wish to volunteer for. Boban to mirror in Trello. | ICANN SSR Subteam members | Review of Trello tasks completed during subgroup face-to-face meeting in LA. |
| ||
165 | Admin | 30 |
| Staff to explore options for team members who are unable to access Google docs/Trello | ICANN Org | Alternative options proposed and agreed with affected team member via email |
| ||
164** | Future Challenges | 30 |
| Staff to circulate send a final version of Future Challenges topics list to plenary email list for approval by the plenary – allow 7 days for Review Team approval on list. | ICANN Org | Document circulated via email list. |
| ||
144 | IANA | IANA Transition Subteam Meeting |
| Provide feedback to the IANA subgroup team on how quickly team can expect access to documents requested once NDAs are finalized and signed. | ICANN Org | Replaced by action item 166. |
| ||
161** | ICANN SSR | 29 |
| SSR2 to share thoughts on ICANN SSR scope related discussion on email list | SSR2-RT | ICANN SSR Subgroup response to scope concerns provided to ICANN Board via email. |
| ||
132 | Admin |
| Draft updated work plan: Reply on email list to Denise’s Aug 14 note; details and your contributions to workplan are required. | SSR2-RT | Revised work plan with subgroup detail posted to wiki and circulated to rapporteurs via email for input. |
| |||
163** | ICANN SSR | 29 |
| ICANN Org to share ICANN SSR subgroup audit plan and the document ‘SSR2_sub_topic_ICANN.SSR’ on email list. | ICANN Org |
| Documents posted to the ICANN SSR subgroup wiki page. |
| |
159** | ICANN SSR | ICANN SSR Subgroup Meeting |
| ICANN Org to circulate update to list of staff members attending LA subgroup meeting. | ICANN Org | List circulated via email. |
| ||
150 | Outreach | 27 |
| Review Team members to share expected outcomes of outreach meetings in Abu Dhabi to the list to ensure team is in alignment. | SSR2-RT | Repaced by action item 161, Rapporteurs to input to the slide deck for outreach meetings. |
| ||
158** | ICANN SSR | ICANN SSR Subgroup Meeting |
| Add “ICANN SSR sub-team scope discussion” as item #1 to 26 September plenary agenda | ICANN Org | Topic discussed on 26 September plenary call. |
| ||
156** | ICANN SSR | ICANN SSR Subgroup Meeting |
| ICANN Org to circulate a Doodle poll and schedule a conference call next week to prepare for LA | ICANN Org | Decision via email to have planned discussion during 3 October plenary meeting. |
| ||
148 | ICANN SSR | 27 |
| ICANN Org to publish agenda and participants of the ICANN SSR subgroup meeting in LA by Monday 25 September, 23:59 UTC to the subgroup wiki and email list. | ICANN Org |
| Draft agenda circulated to RT email list and added to wiki page. |
| |
154 | ICANN SSR | James Gannon |
| Question for ICANN: Regarding the SSR implications of the .avianca tld https://www.icann.org/uploads/compliance_notice/attachment/957/serad-to-reyes-19sep17.pdf[icann.org] situation, i.e when and where do the decisions on enforcement of non compliance get evaluated for SSR impact (in this case where a gTLD is AWOL but for months no actual action is taken). | ICANN Org |
| Response circulated to the list via email. |
| |
151 | Procurement | Co-Chairs |
| Provide suggested edits to the SSR1 gap analysis contractor draft RFP to reflect the Co-Chairs' requests for clarification on the procurement process. | Eric | Replaces action item 140. | Gap analysis RFP published to ICANN.org. Review Team agreed to proceed with release of gap analysis specifications document on 26 September plenary call. |
| |
153 | Procurement | Co-Chairs |
| Provide Co-Chairs with information on a recent RFP process recently followed by the GNSO. | SSR2-RT |
| Process for engaging contractors clarified via email per Co-Chairs request. |
| |
140 | Procurement | 24 |
| Review Team to submit consolidated input and edits on the RFP overview document and confirm their approval for ICANN organization to initiate a process to engage a contractor, based on qualifications, scope of work, timeline, deliverables and other essential components included in the RFP overview document modified by the Review Team (the cost not to exceed $50,000) | SSR2-RT |
| Replaced by action item 151. |
| |
142 | IANA | IANA Transition Subteam Meeting |
| Determine appropriate person to ask for training documentation for processes and procedures for PTI staff. | ICANN Org | Confirmed via email and asked if the subteam would like to set up a meeting. |
| ||
145 | Procurement |
| Provide additional information about soliciting consultants with a budget under $50k (no RFP needed), and the difference between engaging a consultant and an “independent expert.” | ICANN Org |
| Clarification email sent to Co-Chairs. | Revised process overview circulated to Co-Chairs via email. |
| |
106 | ICANN SSR | ICANN SSR Subtopic Meeting 1 |
| Team to provide feedback on the structure of the 9 work items, including identifying items which staff may be able to provide more information or help build out. | ICANN SSR subtopic team |
| Draft audit plan document reviewed during plenary call 27. Staff confirmed document has been shared with staff and items will be addressed during subtopic f2f meeting 9-10 October in LA. |
| |
46 | NDA |
| Updated Per meeting 24: James and Kerry-Ann will provide briefing to Review Team on Non-Disclosure Agreement (NDA) and associated documents, when available. Review non-disclosure form with ICANN Legal and report back to RT on any updates or edits to the circulated form. | James Gannon, Kerry-Ann Barrett |
|
| Documents circulated to the list (29 August) and overview provided by Kerry-Ann on plenary meeting 27 (12 September). |
| |
43 | General | 11 |
|
| ICANN Org |
|
| Email response sent to review team. |
|
89 | General | 17 |
| The ICANN security team (now OCTO/SSR) developed a framework that provided a definition for "security". The SSR2 team used that definition. The Board response to the Terms of Reference expressed that this definition is too broad for the Review Team’s use. Is Board asking staff to redefine definition of “security”? | ICANN Board |
| Email response sent to review team. |
| |
99 | DNS SSR |
| Provide briefing on DNS Abuse study final results | ICANN Org |
|
| Community webinars scheduled and information shared with the review team via email. |
| |
126 | ICANN SSR | ICANN SSR Subtopic Meeting 2 |
| Request ICANN Legal to be present at ICANN SSR face-to-face meeting, October 9-10 to rule on availability of documents. | ICANN Org |
|
| Update sent to the review team via email. Replaced by action item 144. |
|
119 | Admin | Co-Chairs |
| Submit request for meeting room (50 ppl max) for community discussion with SSR2 in Abu Dhabi | ICANN Org |
| Meeting session request sent to ICANN Meetings team. |
| |
138 | Admin |
| Send calendar invites for Team meeting days in Brussels, 22-24 January, and report to Team on how soon can ICANN travel can book arrangements. | ICANN Org | Calendar invites distributed to team. | Welcome email/initial travel correspondence sent to review team from ICANN Travel. |
| ||
130 | SSR1 |
|
| ICANN Org | See completed action item 104 for progress notes regarding related previous request. | Response sent to review team via email. |
| ||
121 | Admin | Co-Chairs |
| ICANN Org to provide written response to request for notes to be provided for each review team call. | ICANN Org | Email sent to co-chairs outlining new note-taking process. |
| ||
107 | ICANN SSR | ICANN SSR Subtopic Meeting 1 |
| Outline in writing a request to meet with ICANN staff responsible for Information Security Management, Auditing, Risk Management and Business Continuity Management. Request to include details of expected goals and outcomes of the meeting. | ICANN SSR subtopic team |
| Draft audit plan circulated to Review Team with questions to resolve during the meeting and email circulated with request to meet with ICANN staff from appropriate departments. |
| |
131 | Admin |
| Sub-team realignment: Reply on email list to Eric’s Aug 14 note about folding sub-group calls into Tuesday Team call to increase engagement and visibility | SSR2-RT | Rapporteurs confirmed preference for respective subgroup call schedules with MSSI secretaria. Update email shared with co-chairs. |
| |||
108 | ICANN SSR | ICANN SSR Subtopic Meeting 1 |
| Circulate outline of detailed work items and proposed next steps after face-to-face meeting. | Žarko, Boban |
| Draft audit plan and next steps circulated to the list via email. |
| |
128 | ICANN SSR | ICANN SSR Subtopic Meeting 2 |
| Finalize questions for ICANN subject-matter experts during potential ICANN SSR subgroup meeting in LA. Distribute to staff so they can identify appropriate resources. | ICANN SSR subtopic team |
| Draft audit work plan circulated via email. |
| |
122 | Admin |
| Confirm approval of ICANN SSR subgroup potential face-to-face meeting in LA | SSR2-RT |
|
| Confirmation received via email. |
| |
129 | ICANN SSR | ICANN SSR Subtopic Meeting 2 |
| Report on results of NDA meeting with ICANN Legal scheduled for 18 August. | James, Kerry-Ann |
| Replaced by updated action item 46 |
| |
137 | Outreach |
| Report to Co-chairs on outreach emails to ICANN groups regarding requested meetings in Abu Dhabi | ICANN Org |
| Email sent to co-chairs. |
| ||
125 | Outreach |
| Distribute SSR2 ICANN60 outreach note to SOs/ACs/constituency groups/PSWG. | ICANN Org |
| Note distributed to requested groups. |
| ||
127 | Admin | ICANN SSR Subtopic Meeting 2 |
| Provide costing of ICANN SSR face-to-face meeting in LA, 9 and 10 October. | ICANN Org |
| See action item 122. Circulated via email to Review Team. |
| |
124 | Procurement | Co-Chairs |
| Staff to publish on SSR2 email list the process options for hiring a technical writer and resource to undertake the gap analysis of the SSR1 recommendations. |
| See completed action item 100 for progress notes regarding related previous request. | Email distributed to Review Team. |
| |
59 | Admin | 12 |
| Draft SSR2 Review Team work plan with key dates, circulate to RT for input. | Co-Chairs, James Gannon, Boban Krsic |
| Co-Charis circulated updated work plan via email. |
| |
115 | IANA |
| IANA Subgroup: Take the outcomes of our F2F meeting and turn that into a list of asks from the IANA team with regards to documentation and further follow-ups. | Cathy | Subteam collectively preparing to draft document once requested documents have become available (pending discussion with ICANN Legal). Per subgroup update on 15 August plenary call. |
| |||
81 | Future Challenges | 17 |
| SSR2-RT to share thoughts on top SSR concerns with Future Challenges subtopic team to inform work items/scope. | SSR2-RT | Subteam has developed list of work items for plenary group's consensus. Per update on 15 August plenary call. |
| ||
45 | Admin |
| Research collaborative tools the RT may use that can be publicly archived. | ICANN Org, James Gannon |
|
| Briefing provided during 15 August 2017 plenary meeting. Background information provided via email 14 August 2017. |
| |
100 | Procurement | Co-Chairs |
| Potential engagement of a third party to complete SSR1 implementation gap analysis: Draft a document to address statement of work, required skills and expertise, expected deliverables, timelines and work methods for co-chairs’ review and approval. | ICANN Org | Briefing with ICANN Procurement scheduled for 15 August 2017. Cancelled per co-chairs (staff/leadership call 11 August) | Draft RFP overview document shared with Co-Chairs via email 11 August 2017. |
| |
97 | Admin | 20 |
| Staff to build out work plan template to include elements on information gathering, research and outreach. Co-Chairs to provide feedback before sharing with the Review Team. | ICANN Org |
| Work plan template agreed by SSR2-RT during 25 July plenary. | Draft work plan template shared with Co-Chairs via email 11 August 2017. |
|
123 | SSR1 | SSR1 Subtopic Meeting 1 |
| Open a discussion on the email list regarding work items, eg. redundancies and prioritization. Share document with team for their input on more detailed work plan and timeline. | SSR1 Subgroup | Subgroup activities suspended per email from Rapporteur |
| ||
86 | General | 17 |
| Provide SSR2-RT with information on if ICANN Office of the CTO has plans to re-define “security”? If so, how and when? | ICANN Org | Answer provided via email. |
| ||
120 | DNS SSR | DNS SSR Subtopic Meeting 3 |
| Schedule time with Kim Davies on the next available Subtopic call to review draft work topics/answer questions. | ICANN Org |
| Kim confirmed he is available to join the 14 August subgroup call, 20:00 UTC. |
| |
116 | Procurement | Co-Chairs |
| Schedule call with ICANN Procurement team to review procurement process. | ICANN Org |
| ICANN Procurement scheduled to attend SSR2 Plenary 23. |
| |
1124 | DNS SSR | DNS SSR Subtopic Meeting 1 |
| Team to share thoughts on DNS SSR work topics draft doc. | DNS SSR subtopic team | Team agreed next step is to schedule a discussion with Kim Davies to progress work items (see action 120) |
| ||
117 | Admin | Co-Chairs |
| Draft note for Co-Chairs regarding Abu Dhabi meeting dates and potential options for informal subgroup meetings. | ICANN Org |
|
| ||
80a. | SSR1 | 17 |
| 80. Provide follow-up questions from the 25 June SSR1 briefings so that ICANN Org can prepare responses. | ICANN Org SSR2-RT |
| |||
460460G 25/07/2017114 | IANA | 17 |
| Schedule interviews with Kim Davies, Elise Gerich, PTI at ICANN59. | ICANN Org |
| Interview complete and notes shared with subteam. |
| |
113 | Future Challenges | Future Challenges Subtopic Meeting 1 |
| Input draft text to Google doc Future Challenges section on vendor security and performance security sub-sections. | Mohamad Amin Hasbini |
| Emailed text for team's consideration | ||
111 | DNS SSR | DNS SSR Subtopic Meeting 1 |
| Share redline version of DNS SSR work topics draft to the subtopic email list. | Eric |
| Document shared via email. |
| |
68 | DNS SSR | 15 |
| ICANN Org | ICANN DNS Engineering team provided proposed reframe of the question: "What measures are undertaken by ICANN for the anycast deployment for L-Root to ensure physical and network security and stability?" |
|
| ||
110 | DNS SSR | Plenary 17 |
| Write up DNS SSR topic areas and share with sub-team. | Geoff |
| Proposed reorganization of study topics doc (GH) shared with team. |
| |
109 | ICANN SSR | Plenary 17 |
| Refine key action steps/work items and scope of the subtopic review. | ICANN SSR subtopic team | Re-organized work items shared with plenary for input (see Item 90 on Tracking Tool). Replaced by actions S2.2 |
| ||
105 | SSR1 | SSR1 Subtopic Meeting 1 |
| Determine if there is an owner of the SSR1 implementation report, and who was determining the goals and outcome of each recommendation. | ICANN Org | Email to Review Team. |
| ||
104 | SSR1 |
| Provide completion dates for each recommendation (date it was designated as “complete”); if there was multiple activities or deliverables in a recommendation, include the dates those were completed too. | ICANN Org |
|
|
| ||
103 | SSR1 | SSR1 Subtopic Meeting 1 |
| Gather information regarding SSR1 implementation together in logical groupings and index within the Google doc. | ICANN Org |
| Background materials section added to SSR1 Subteam wiki page including links to all briefing materiasl and SSR1 implementation final report |
| |
102 | Admin | 21 |
| Review Team members to email staff with Abu Dhabi full-day meeting preferences. Options are 27 October and 3 November. | SSR2-RT |
| A number of review team members responded off-list to email. |
| |
79 | SSR1 | 17 |
| Complete SSR1 implementation briefings. | ICANN Org |
| All briefings complete and materials posted to the wiki. |
| |
96 | Admin | Co-Chairs |
| Review other meeting date/time options for F2F meeting at ICANN60 due to conflict for one of the co-chairs | ICANN Org |
| Available options for full Review Team meeting provided via email to Co-Chairs. Presented on plenary 21 and via email to SSR2 RT. |
| |
90 | ICANN SSR |
| Review ICANN SSR re-organized work items (37 items in 8 groups) and send feedback to ICANNsecurity-SSR2-RT@icann.org. Please bear in mind the following questions:
| SSR2-RT | Replaced by Subtopic group action item 2.3 |
| |||
101 | Admin | Co-Chairs |
| Confirm if staff responsible for the outstanding SSR1 Recommendations (11, 12) can attend the SSR2 plenary call to present the recommendation implementation. | ICANN Org |
| Email sent to Co-Chairs. |
| |
76 | Admin | 17 |
|
| 76. d. Co-Chairs 76. c. ICANN Org 76. b. Co-Chairs 76. a. SSR2-RT |
|
| 76.e. 76. d. 76. c 76. b. 76. a. | |
91 | SSR1 | 18 |
| Provide follow-up questions via email regarding the SSR1 implementation briefing by ICANN Compliance – recommendation 10. | SSR2-RT |
| No follow-up questions provided but SSR2 Review Team is free to provide follow-up questions at any time. |
| |
95 | Admin | Co-Chairs |
| Build out the SSR2 Review Team work plan to provide additional substance and practical steps to share with Co-Chairs for initial input. | ICANN Org |
| Shared via email. |
| |
87 | Admin | 17 |
| Publish post-meeting blog on icann.org | ICANN Org |
| Published here. |
| |
94 | Outreach | Co-Chairs |
| Draft note to SO/AC leaders asking for time on their agenda at ICANN60 for SSR2 update and discussion on shared items of interest. Share with Co-Chairs. | ICANN Org |
| Draft provided to co-chairs via email. |
| |
93 | SSR1 | 18 |
| Share link to the published ICANN Compliance Audit Report. | ICANN Org |
| Shared via email: https://www.icann.org/resources/pages/compliance-reports-2016 |
| |
92 | SSR1 | 18 |
| Respond to questions asked by the Review Team during the SSR1 implementation briefing by ICANN Compliance – recommendation 10. | ICANN Org |
| Answers provided via email. |
| |
78 | SSR1 | 17 |
| Populate the table of remaining SSR1 recommendations, with department, name of staff and Tuesday July Plenary meeting schedule availability. | ICANN Org |
| Google document updated. |
| |
85 | General | 17 |
|
| ICANN Org |
|
| ||
84 | Admin | 17 |
| Establish staff support requirements and availability to support SSR2-RT subgroups. | ICANN Org, Co-Chairs |
| Available time slots to support subgroup calls circulated via email to Review Team |
| |
88 | General | 17 |
| Identify Board members on “caucus” reviewing SSR2 work. | ICANN Board |
| Board Caucus details circulated via email. |
| |
82 | Admin | 17 |
| Update SSR2-RT action items wiki page with new request reporting tool. | ICANN Org |
| New 'Tracking Tool' wiki page live. |
| |
77 | SSR1 | 17 |
| Provide final SSR1 implementation report. | ICANN Org |
| Link circulated to Review Team via email. |
| |
76 | Admin | 17 |
| Complete Doodle poll on January 2018 face-to-face meeting. Co-Chairs to identify date for face-to-face meeting and share with Review Team. | SSR2-RT, Co-Chairs |
| Doodle poll completed. |
| |
74 | Admin | 16 |
| SSR2-RT members to volunteer for sub-topic rapporteur roles within each sub-team. | SSR2-RT |
| Subtopic rapporteurs recorded in Google doc. |
| |
73 | Admin | 16 | | SSR2-RT to share any objections on list to dropping the 0600 UTC call slot and address call schedule rotation in the Johannesburg meeting. | SSR2-RT | Item addressed in Plenary 17. Replaced by action item #83. |
| ||
72 | Admin | 16 |
| Update the January 2018 face-to-face meeting Doodle poll with option for weekend meeting. | ICANN Org, Co-Chairs |
| Doodle poll updated and circulated to Review Team via email. |
| |
71 | Outreach | 16 |
| Send SSR2 June progress update to leaders/lists for each SO, AC, stakeholder group, constituency, PSWG and the Board. | ICANN Org |
| Correspondence shared with SO/AC leaders email distribution list and ICANN Board. |
| |
70 | Admin | 15 |
| Post attendance participation rates to wiki on a monthly basis. | ICANN Org |
| Posted on Fact Sheet wiki page |
| |
69 | Outreach | 15 | | Staff to capture and share all discussions to-date around outreach. | ICANN Org |
| Google document shared with Review Team via email. |
| |
67 | General |
| Email request to adopt the title "Security Review" in public communications. | ICANN Org | TBD |
| |||
66 | Outreach | 14 |
| Send written responses to RT questions asked during the presentation on ICANN’s Global Stakeholder Engagement outreach efforts to SSR technical community.
| ICANN Org |
|
|
| |
65 | Admin | 14 | | Share thoughts and continue discussion on list regarding presentation of ICANN Security and SSR1 subtopic work plans. | SSR2-RT |
| See email thread. |
| |
64 | Admin | 14 | | Share thoughts on list on how to be more open to observer inputs. | SSR2-RT | TBD | Thoughts shared via email and addressed during plenary 15. Conclusion: Keep interactions as-is for now. |
| |
63 | Admin | 12 |
| RT members to continue to volunteer for subtopics. More volunteers particularly needed for group 1: SSR. | SSR2-RT | TBD | Volunteers recorded in Subtopics document. |
| |
62 | Admin | 12 | | Prepare a draft work plan proposal for SSR1 Review and ICANN Security topics. | Boban Krsic, Žarko Kecić | Document shared via email |
| ||
61 | Admin | 12 | | Consolidate duplicative items, create subheadings for each topic groups within volunteer groups. | SSR2-RT |
| Subtopics document updated. |
| |
60 | Admin | 12 | | Record volunteers from plenary call in the subtopics document on wiki. | ICANN Org |
| Subtopics document updated. |
| |
58 | Outreach | 12 | | Share thoughts on list regarding outreach and engagement, and possible guidelines. | SSR2-RT |
| Thoughts shared via email. |
| |
57 | Admin | 12 | | Share thoughts on list regarding Johannesburg agenda topics. | SSR2-RT |
| Thoughts shared via email. |
| |
56 | Admin | 12 | | Distribute draft Johannesburg agenda to email list. | Co-Chairs |
| Circulated via email. |
| |
55 | Admin | 12 | | Add agenda item regarding how Observers can participate and contribute to sub topic work to plenary call #13. | Co-Chairs |
| Replaced by action item #64. |
| |
54 | Admin | 11 |
| Publish blog on ICANN.org regarding SSR2 face-to-face meeting in Madrid. | ICANN Org |
| Blog published on ICANN.org. |
| |
52 | Admin | | Schedule remainder of briefings related to SSR1. | ICANN Org |
| Briefings schedule google document shared with Review Team. |
| ||
51 | Outreach | | Staff to provide RT with explanation and background information from ICANN Global Stakeholder Engagement and Adiel Akplogan (ICANN VP Technical Engagement) regarding current outreach efforts to SSR technical community (responsibility, focus, accomplishments) for RT’s consideration. | ICANN Org | TBD | Patrick Jones, Senior Director, GSE and Adiel Akplogan, Vice President, Technical Engagement joined SSR2 plenary 14. |
| ||
50 | Admin | | Circulate list of potential scope topics and list of sub team volunteers. | ICANN Org |
| Google doc shared with Review Team. |
| ||
49 | Admin | 11 |
| Circulate link to ICANN technical portal | ICANN Org | TBD | Link circulated to Review Team. |
| |
48 | General | | Share links to relevant articles regarding threat mitigation and classification of threats. | ICANN Org |
| Links circulated to Review Team: Threat Mitigation
Classification of Threats |
| ||
47 | Admin |
| Circulate Google doc for RT to input their SSR concerns. Inputs to form substance of scope discussion. | ICANN Org |
| Google document circulated via email to Review Team. |
| ||
43 | General |
| Provide the SSR2 RT a timeline of the ITHI project, when they have clarity on next steps and schedules. | ICANN Org | TBD | Email circulated to Review Team. |
| ||
IANA |
| Post PTI briefing materials and relevant materials to the SSR2 wiki background materials page. | ICANN Org | TBD | Links posted to SSR2 background materials wiki page. |
| |||
41 | Admin | 9 |
| Circulate clean version of Terms of Reference to list for final 24-hour consideration. | Co-Chairs | TBD | Shared via email. |
| |
40 | Admin | 9 | | Send adopted Terms of Reference to ICANN Board, should no objections occur in the 24 hours from circulation. | Kaveh Ranjbar | TBD | Sent to Board Chair via email. |
| |
39 | Admin | 9 | | Prepare proposal for initial structuring of RT work for Madrid meeting. | James Gannon | TBD | Shared via email. |
| |
38 | Admin | 9 |
| Provide a decision to the Review Team on whether a face-to-face meeting will take place in Johannesburg, and on what dates. | Co-Chairs |
| Johannesburg meeting confirmed to take place 25 & 26 June. |
| |
37 | IANA | 8 | Schedule a briefing on PTI, the Bylaws and the relationship with ICANN to share input to assist in determining its possible inclusion in the scope of SSR2 review. | ICANN Org |
| Elise Gerich and Samantha Eisner joined 9 May plenary call and provided briefing. |
| ||
36 | Admin | 8 | Provide draft agenda for Madrid face-to-face meeting to Review Team for input. | Co-Chairs | TBD | Shared via email. |
| ||
35 | SSR1 | 8 | Circulate current summary of SSR1 review implementation to SSR2-RT list. | ICANN Org |
| Email circulated to Review Team. |
| ||
34 | Admin | 8 |
| Provide update to SSR2-RT after scheduled SO/AC Chair call to inform decision regarding potential meeting dates in Johannesburg at ICANN59. | Co-Chairs | TBD | Replaced by action item #38. |
| |
33 | Admin | 7 |
| Share link to Bylaws Article 18 and appropriate context. | ICANN Org |
| Bylaw article and context distributed via email to RT. |
| |
32 | Admin | 7 | | Provide v3 draft scope for Terms of Reference based on discussions and comments. | Eric Osterweil | TBD | Document circulated via email. |
| |
31 | Admin | 7 | | Provide availability of OCTO – SSR team in Madrid to Co-Chairs to inform Madrid meeting agenda development. | ICANN Org |
| Information provided to Co-Chairs on staff coordination call. |
| |
30 | Admin | 7 | | Circulate Doodle poll to establish RT availability for F2F meeting in Johannesburg. | ICANN Org |
| Doodle poll circulated. |
| |
29 | Admin | 7 |
| Circulate updated open action items list to RT. | ICANN Org |
| Updated action items list circulated. |
| |
28 | NDA |
| Non-Disclosure (NDA) and Conflicts Disclosure (CDA) documentation for RT. | ICANN Org |
|
|
| ||
27 | Admin | 6 |
| Clean up draft Terms of Reference (accept points of agreement). Pull out points of disagreement for discussion on email list. | ICANN Org |
| Circulated via email. |
| |
26 | Admin | 6 | | Review v2 draft Terms of Reference and share thoughts on email list. | RT Members | TBD | Document shared. Review Team shared feedback via email. |
| |
25 | General | 6 |
| Propose timeline for finalizing scope. | Co-Chairs | TBD | Item added to Madrid face-to-face meeting agenda. |
| |
24 | General | 4 |
| Review brainstorming capture slides from 15 March meeting and share thoughts on email list. | RT Members | TBD | Item added to Plenary 11 Madrid face-to-face meeting agenda. |
| |
23 | Admin | 4 |
| Schedule weekly RT calls per agreed rotation schedule. | ICANN Org |
| Call invites sent to Review Team. |
| |
22 | General | 4 |
| Review draft Scope and Work Plan and make comments on the email list. | RT Members | from |
|
| |
21 | Admin | 3 | | Schedule 60-minute plenary call #4, 14:00 UTC Tuesday 28 March. | ICANN Org |
| Call invite circulated to Review Team. |
| |
20 | General | 3 | | Co-Chairs to coordinate and formulate a proposal as to how to separate duties and present it to the RT. | SSR2 Co-Chairs | TBD | Co-Chairs agreed to informal separation of duties. |
| |
19 | Admin | 3 | | Prepare a plan for a rotation schedule for RT calls to the Co-Chairs for the next meeting. | ICANN Org |
| Excel worksheet planning document shared with Co-Chairs. |
| |
18 | SSR1 | | 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 |
| Recommendation 11 implementation completed: https://community.icann.org/display/SSR/Rec+%2311 |
| ||
17 | SSR1 | | 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 |
| Recommendation 20 implementation completed: https://community.icann.org/display/SSR/Rec+%2320 Recommendation 21 implementation completed: https://community.icann.org/display/SSR/Rec+%2321 Recommendation 22 implementation completed: https://community.icann.org/display/SSR/Rec+%2322 |
| ||
16 | Admin | 3 | | 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 |
| Kaveh Ranjbar provided update to the Board. |
| |
15 | Admin | 3 | | Prepare straw-man versions of the Terms of Reference and Work plan for the RT to consider. | ICANN Org |
|
|
| |
14 | Admin | 3 |
| Generate a list of official observers and their relevant skill sets for RT consideration. | ICANN Org |
|
| ||
13 | Admin | 2 | | Circulate slide deck from 3/15 SSR2 face to face meeting. | ICANN Org |
| Slide deck uploaded to SSR2 plenary 2 wiki page. |
| |
12 | Admin | 2 |
| Add OCTO KPIs, ICANN 2016 strategic plan and Emerging Technology Identifiers ICANN58 presentation to wiki background materials. | ICANN Org |
| Materials added to SSR2 background materials wiki page. |
| |
11 | General | 2 |
| Provide a list of existing definitions of terms: Security, Stability, Resiliency and Unique Identifiers. Reference where they are located. | ICANN Org |
| List of definitions compiled and provided to Review Team. |
| |
10 | Admin | 2 | | Circulate names / contact information for SADAG vendors to SSR2 RT list. | ICANN Org |
| Vendor contact details provided via email. |
| |
9 | Admin | 2 |
| Circulate CDAR study report and contact information to SSR2 RT list. | ICANN Org |
|
| ||
8 | Admin | 2 |
| Provide SSR2 Fact Sheet sample and schedule. | ICANN Org |
| Sample Fact Sheet and schedule posted to wiki and circulated to Review Team via email. |
| |
7 | Admin | 2 |
| Schedule 60-minute plenary call, Wednesday 22 March, 19:00 UTC. | ICANN Org |
| Call invite circulated to Review Team. |
| |
6 | Admin | 2 |
| Develop and circulate time zone mapping to support scheduling of regular plenary calls discussion on next plenary call. | ICANN Org |
| Excel worksheet planning document shared with Co-Chairs. |
| |
5 | Admin | 2 |
| 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 | Document circulated to Review Team. |
| |
4 | Admin |
| Draft document about what other review teams have used for chairs and co-chairs and send to the list. | ICANN Org | n/a | Email circulated to Review Team. |
| ||
3 | Admin | 1 |
| Produce a summary of how other review teams have handled Observers and post to the list. | ICANN Org | n/a | Email circulated to Review Team. |
| |
2 | Admin | 1 |
| Post staff structure responsibilities on wiki background page. | ICANN Org | n/a | ICANN Organization Support Team page created on SSR2 wiki. |
| |
1 | Admin | 1 | 22 Apr | Provide terms of reference to the ICANN Board. | SSR2 | TBD | Email sent to Board Chair on behalf of Review Team. |
|
...