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 |
---|---|---|---|---|---|---|---|---|
90 | 10 July 2017 | 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 | 21 July 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 | 14 July 2017 | |||
88 | 17 | 26 June 2017 | Identify Board members on “caucus” reviewing SSR2 work. | ICANN Board | 14 July 2017 | |||
87 | 17 | 26 June 2017 | Publish post-meeting blog on icann.org | ICANN Org | 13 19 July 2017 | |||
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 | 14 July 2017 | |||
85 | 17 | 26 June 2017 | Provide SSR2-RT with information on if ICANN Org will accept Board proposal for a new, template “Terms of Reference in Operating Standards”? If so, when will it be issued? | ICANN Org | 14 July 2017 | |||
84 | 17 | 26 June 2017 | Establish staff support requirements and availability to support SSR2-RT subgroups. | ICANN Org, Co-Chairs | 11 July 2017 | |||
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 | 25 July 2017 | |||
81 | 17 | 26 June 2017 | SSR2-RT to share thoughts on top SSR concerns with Future Challenges subtopic team to inform work items/scope.a | SSR2-RT | TBD | |||
80 | 17 | 25 June 2017 | Provide follow-up questions from the 25 June SSR1 briefings so that ICANN Org can prepare responses. | SSR2-RT | 7 July 2017 | |||
79 | 17 | 25 June 2017 | Complete SSR1 implementation briefings. | ICANN Org | August 2017 | |||
78 | 17 | 25 June 2017 | Populate the table of remaining SSR1 recommendations, with department, name of staff and Tuesday July Plenary meeting schedule availability. | ICANN Org | 7 July 2017 | |||
75 | 17 | 25 June 2017 | 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. | SSR2-RT | 7 July 2017 | |||
68 | 15 | 13 June 2017 | ICANN DNS Engineering team to reframe the following question (Q3 from SSR2 Plenary 14, 6 June GSE presentation) so as to better align with the RT mandate: Regarding L-root operations and hosting: What is the planning process vs. passive response? Is there a master plan for anyone who operates, in terms of Anycast? And how is that overall process implemented? (GH) | ICANN Org | TBD | 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?" | ||
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 | TBD | |||
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 | TBD | ||||
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, Emily Taylor, Kerry-Ann Barrett | 18 July 2017 | ||||
45 | 14 May 2017 | Research collaborative tools the RT may use that can be publicly archived. | ICANN Org | 11 July 2017 |
| |||
44 | 14 May 2017 | Draft a Statement of Work for specialist technical writer. | James Gannon, Cathy Handley, Denise Michel | 25 July 2017 |
|
...