Page History
...
Item # | Category | Source of Request | Date of Request | Action Item Request | Action Owner | Anticipated Completion Date *To be provided once reasonable date is determined by appropriate subject-matter expert | Progress Notes | Completed Response | Completion Date |
---|---|---|---|---|---|---|---|---|---|
153 | Procurement | Co-Chairs | 15 September 2017 | Provide Co-Chairs with information on a recent RFP process recently followed by the GNSO. | SSR2-RT | 22 September 2017 | |||
152 | Admin | Co-Chairs | 15 September 2017 | Review recorded decisions reached for accuracy and completeness. | ICANN Org, SSR2-RT | ||||
151 | Procurement | Co-Chairs | 15 September 2017 | 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. | |||
150 | Outreach | 27 | 12 September 2017 | Review Team members to share expected outcomes of outreach meetings in Abu Dhabi to the list to ensure team is in alignment. | SSR2-RT | ||||
149 | NDA | 27 | 12 September 2017 | 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). | |||
148 | ICANN SSR | 27 | 12 September 2017 | 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 | 25 September 2017 | |||
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 |
| |||
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 Cathy, 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 | 18 October 2017 | In progress. KD OK to meet with Cathy, date/time TBD. | ||
139 | SSR1 | 24 | 22 August 2017 | Review Team members to volunteer if they feel they can contribute to the SSR1 implementation subgroup. | SSR2-RT | ||||
136 | Admin | 16 August 2017 | Respond to ICANN Travel ASAP & make flight reservations to travel to Abu Dhabi for the face-to-face meeeting. | 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. |
| |||
133 | Admin | 16 August 2017 | 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 |
| ||||
132 | Admin | 16 August 2017 | Draft updated work plan: Reply on email list to Denise’s Aug 14 note; details and your contributions to workplan are required. | SSR2-RT | |||||
118 | Admin | 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 | 13 October 2017 | |||
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 |
| |||
68 | DNS SSR | 15 | 13 June 2017 |
| ICANN Org |
| 68.a. 11 July 2017 | ||
83 | Admin | 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. | SSR1 | 17 | 25 July 2017 | Provide responses to questions from SSR1 briefings (Ops + Finance)
| ICANN Org | 1. In progress 2. Review team to provide clarification per email request. 7. In progress. James Gannon provided clarification upon request. 8. In progress. James Gannon provided clarification upon request. | 3. Question answered during the meeting. See meeting record. 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. 9. Question answered via email. 10. Question answered via email | ||
75 | ICANN SSR | 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. 9 October 2017 75. a. 25 July 2017 |
| 75. a. 25 July 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. |
...