Page History
...
Item # | Category | Source of Request | Date of Request | Action Item Request | Action Owner | Anticipated Completion Date* | Progress Notes | Completed Response | Completion Date |
---|---|---|---|---|---|---|---|---|---|
99 | DNS SSR | 19 June 2017 | Provide briefing on DNS Abuse study final results | ICANN Org | 24 October 2017 |
| |||
167 | SSR1 | 9 October 2017 | Provide responses to SSR1 Implementation Recs 21-28 Questions and Information Requests provided by Denise. See progress of each request here. | ICANN Org | |||||
166 | IANA | 9 October 2017 | Advise if the sub-team requires an NDA to access any of the following documents:
| ICANN Org | |||||
160** | Outreach | 29 | 26 September 2017 | Subteam rapporteurs to prepare a short status update for the presentations to the SO/AC groups in Abu Dhabi | SSR2 Subteam Rapporteurs | ||||
147 | ICANN SSR | Trello | 27 August 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 | 5 November 2017 |
| ||
146 | SSR1 | 26 August 2017 | Provide responses to SSR1 Implementation Recs 1-20 Questions and Information Requests provided by Denise. See progress of each request here. | ICANN Org | In progress. Progress of requests is available on the SSR1 Subgroup page. | ||||
144 | IANA | IANA Transition Subteam Meeting | 24 August 2017 | 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 | Update email sent to review team. | |||
143 | IANA | IANA Transition Subteam Meeting | 24 August 2017 | 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 | ||||
141 | IANA | IANA Transition Subteam Meeting | 24 August 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 (Preferred time, beginning of the week). | ICANN Org | 26 October 5 November 2017 | In progress. KD OK to meet with Eric, date/time TBDProposed time slots sent to subteam via email. | ||
139 | SSR1 | 24 | 22 August 2017 | Review Team members to volunteer if they feel they can contribute to the SSR1 implementation subgroup. | SSR2-RT | ||||
135 | Admin | 16 August 2017 | Report to Team on potential room availability at ICANN meeting for sub-group meetings during week. | ICANN Org | 28 October 2017 | ||||
134 | Admin | 16 August 2017 | Send calendar invites for Team meeting days in Abu Dhabi and additional invites as meetings are scheduled. | ICANN Org | As needed. |
| |||
101 | SSR1 | 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 |
5. Clarity requested via email. Awaiting input from Denise Michel. 6. Clarity requested via email. Awaiting input from Denise Michel. 7. In progress 8. In progress 9. Clarity requested via email. Awaiting input from Denise Michel. 11. In progress | 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. 10. Question answered via email. 12. Question answered during the call. See meeting record. | ||
98 | General | 19 June 2017 | Provide briefing on Framework for Registry Operators to Respond to Security Threats | ICANN Org | 4 November 2017 |
| |||
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 | |||||
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 | ICANN Org provided outline of procurement process and input via email to support development of Statement of Work. |
...