Page History
...
Item # | Source of Request | Date of Request | Action Item Request | Action Owner | Anticipated Completion Date | Progress Notes | Completed Response | Completion Date |
---|---|---|---|---|---|---|---|---|
126 | 15 August 2017 |
| ICANN Org | See completed action item 104 for progress notes regarding related previous request. | ||||
125 | 14 August 2017 | Distribute SSR2 ICANN60 outreach note to SOs/ACs/constituency groups/PSWG. | ICANN Org | 17 August 2017 | ||||
124 | Co-Chairs | 11 August 2017 | 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. | ICANN Org | See completed action item 100 for progress notes regarding related previous request. | |||
122 | 4 August 2017 | ICANN SSR subgroup exploring potential face-to-face meeting in LA:
| ICANN SSR subgroup | 15 August 2017 |
| |||
121 | Co-Chairs | 4 August 2017 | ICANN Org to provide written response to request for notes to be provided for each sub-team call. | ICANN Org | ||||
119 | Co-Chairs | 4 August 2017 | Submit request for meeting room (50 ppl max) for community discussion with SSR2 in Abu Dhabi | ICANN Org | ||||
118 | Co-Chairs | 4 August 2017 | Provide list of meetings of interest in Abu Dhabi for Review Team and sub-teams when schedule is available | ICANN Org | ||||
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. Recommendation 11: 1. What was happening in the 5 years between when the recommendation was approved by the Board and when a draft consultant report was posted in April 2017? 2. On the status and deliverables of Rec 11 it says that ICANN has implemented measures of success for the gTLDs, but we haven’t seen how you’ve implemented measures of success for new gTLDs and IDNs. That’s the first check mark, but what we’ve been provided with is a draft report of some ideas that you could do. How is that considered full implementation of this recommendation? 3. Do you think it is ICANN staff’s responsibility to gather, analyze and publish this data or do you feel that it’s ICANN’s responsibility to facilitate others to do that? 4. In a commercialized world of DNS service provision where data is considered to be a corporate asset, do you feel that either ICANN or the community at large have access to meaningful metrics? I cite the barriers that exist on information on root servers. Is this a barrier to the entire objective, that access to data appears to be challenging? 5. The SSR1 review team called out a number of activities that were operational and within staff’s purview and contained in the SSR framework and called for implementation of measurements and metrics. Was that work done and is it captured anywhere? To clarify, as part of the SSR1 report related to rec 11, the SSR1 review team noted ICANN administration of the new gTLD Program, IDN program, significant SSR related issues that are in the framework. They called for more specific goals, measurements and impact assessment. Was that work done and is it captured somewhere else? 6. Is there more information on the steps that ICANN has taken in the past five years to facilitate data access and activities that involved other entities that had ownership or responsibilities on related activities? 7. Broadly, in looking at the dashboard for rec 11 and all the checkmarks including operational items, it’s really unclear how staff defined and measured success related to SSR. It’s hard to see how the basic sprit of this recommendation was implementation, especially with an idea paper from a consultant. But in terms of the last 5 years and what staff did to implement, it’s unclear. Can you gather more information and provide more clarity and facts? Recommendation 12: 8.With regards to establishing best practices and integrating these into agreements to which ICANN enters: It’s linked to a paper that raises a whole host of issues and addresses proposed activities but it’s unclear how that then relates to integrating those into agreements into which ICANN has entered over the past 5 years. Can you provide more specific information on how best practices are reflected in agreements that ICANN has entered into? 9. ‘Addressing SSR practices in MOUs’ links to a page that holds all of the MOUs. Can you provide some quantification of SSR-related practices in MOUs and more information on which ones contain SSR-related practices, which practices they contain, and how all that’s tracked or the implementation is assessed? 10. Is there any quantification or more detailed information on what the working relationship with the APWG has yielded? 11. Which sections of the revised new gTLD registry agreement does OCTO staff feel advance SSR best practices and objectives? 12. What has changed after the implementation of Rec#12 as compared with the past? | ICANN Org |
3. Question answered during the call. See meeting record. 4. Geoff Huston (asker) clarified that he feels this is a question for the review team to answer, not ICANN Org. 5. Clarity requested via email. Awaiting input from Denise. 6. Clarity requested via email. Awaiting input from Denise. 7. In progres 8. In progress 9. Clarity requested via email. Awaiting input from Denise. 10. Question answered via email. 11. In progress 12. Question answered during the call. See meeting record. | |||
99 | 19 June 2017 | Provide briefing on DNS Abuse study final results | ICANN Org | 19 September 2017 |
| |||
98 | 19 June 2017 | Provide briefing on Framework for Registry Operators to Respond to Security Threats | ICANN Org | 5 September 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 | ||||
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 | ||||
80b. | 17 | 25 July 2017 | Provide responses to questions from SSR1 briefings (Ops + Finance)
| ICANN Org | 1. In progress 2. In progress 3. In progress 8. In progress 9. In progress | 4. Question answered during the meeting. See meeting record. 5. Question answered during the meeting. See meeting record. 6. Question answered during the meeting. See meeting record. 7. Question answered during the meeting. See meeting record. 109. Question answered via email. 1110. Question answered via email | ||
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 | 29 August 2017 |
...