Page History
...
Item # | Source of Request | Date of Request | Action Item Request | Action Owner | Request Clarified (link to email archive; date) | Anticipated Completion Date | Completed Response | Completion Date |
---|---|---|---|---|---|---|---|---|
120 | Staff/Leadership Call | 4 August 2017 | Provide draft of RFP overview document and the questions to be answered / information to be provided by the candidates to Co-Chairs. | ICANN Org | 10 August | |||
119 | Staff/Leadership Call | 4 August 2017 | Submit request for meeting room (50 ppl max) for community discussion with SSR2 in Abu Dhabi | ICANN Org | ||||
118 | Staff/Leadership Call | 4 August 2017 | Provide list of meetings of interest in Abu Dhabi for Review Team and sub-teams when schedule is available | ICANN Org | ||||
116 | Staff/Leadership Call | 4 August 2017 | Schedule call with ICANN Procurement team to review procurement process. | ICANN Org | 15 August | |||
115 | 5 July 2017 | 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 | |||||
112 | DNS SSR Subtopic Meeting 1 | 21 July 2017 | Team to share thoughts on DNS SSR work topics draft doc. | DNS SSR subtopic team | ||||
108 | ICANN SSR Subtopic Meeting 1 | 31 July 2017 | Circulate outline of detailed work items and proposed next steps after face-to-face meeting. | Žarko, Boban | 31 August 2017 | |||
107 | ICANN SSR Subtopic Meeting 1 | 31 July 2017 | 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 | 11 September 2017 | |||
106 | ICANN SSR Subtopic Meeting 1 | 31 July 2017 | 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 | 4 September 2017 | |||
101 | 21 | 1 August 2017 | Provide responses to questions on SSR1 briefing: Recommendations 11, 12. | ICANN Org | ||||
100 | Staff/Leadership Call | 28 July 2017 | 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 | ||||
99 | 19 June 2017 | Provide briefing on DNS Abuse study final results | ICANN Org |
| ||||
98 | 19 June 2017 | Provide briefing on Framework for Registry Operators to Respond to Security Threats | ICANN Org | 5 September 2017 |
| |||
97 | 20 | 25 July 2017 | Staff to build out work plan template to include elements on information gathering, research and outreach. | ICANN Org | 11 August 2017 | |||
68 | 15 | 13 June 2017 |
| ICANN Org |
| 68.a. 11 July 2017 | ||
43 | 14 May 2017 |
| ICANN Org |
| 43. a. 26 June 2017 | |||
89 | 17 | 26 June 2017 | 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 | ||||
86 | 17 | 26 June 2017 | 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 | ||||
83 | 17 | 26 June 2017 | Review 06:00 plenary call slot attendance and provide input to inform discussion around potential cancelation of call. | Co-Chairs | ||||
81 | 17 | 26 June 2017 | SSR2-RT to share thoughts on top SSR concerns with Future Challenges subtopic team to inform work items/scope. | SSR2-RT | ||||
80 | 17 | 25 June 2017 | 80.b. Provide responses to follow-up questions from the 25 June SSR1 briefings 80. a. Provide follow-up questions from the 25 June SSR1 briefings so that ICANN Org can prepare responses. | ICANN Org SSR2-RT | 80. b. 80. a. 25 July 2017 | 80. a. 25 July 2017 | ||
75 | 17 | 25 June 2017 | 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. 25 July 2017 |
| 75. a. 25 July 2017 | |
59 | 12 | 23 May 2017 | Draft SSR2 Review Team work plan with key dates, circulate to RT for input. | Co-Chairs, James Gannon, Boban Krsic | ||||
53 | 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 | |||||
46 | 14 May 2017 | 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 | |||||
45 | 14 May 2017 | Research collaborative tools the RT may use that can be publicly archived. | ICANN Org, James Gannon |
| ||||
44 | 14 May 2017 | Draft a Statement of Work for specialist technical writer. | James Gannon, Cathy Handley, Denise Michel |
|
...