Page History

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. 

• Briefing confirmed for 25 June 2017. Postponed per Co-Chairs.

• Briefing confirmed for 25 July 2017. Postponed per Co-Chairs
• Briefing confirmed for 26 June 2017. Postponed per Co-Chairs.

13 June 2017

• 68. b. Follow-up via email: Please provide a written explanation as to how the original question was felt to be objectionable.
  
  
• 68. a. ICANN DNS Engineering team to reframe the following question and provide an answer (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) 

• 68. a. Question reframe response circulated via email 11 July 2017.
• 68. a. 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?"

68.a. 11 July 2017

11

14 May 2017

• 43. b. Follow-up via email: Could you please clarify when ITHI will start regularly publishing (or giving the public access to) data? It seems that the “schedule” below is about discussions rather than production, or am I misunderstanding?

• 43. a. Provide the SSR2 RT a timeline of the ITHI project, when they have clarity on next steps and schedules.

• 43. a. Email circulated to Review Team 26 June 2017.

43. a. 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”?

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, 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. Questions sent to ICANN CIO.

75. a. 25 July 2017

11

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.

11

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

11

14 May 2017

Research collaborative tools the RT may use that can be publicly archived.

Email request from James Gannon & PDF attachment

• ICANN IT researched requested tools and provided response to James Gannon and Co-Chairs.
• Face-to-face meeting with ICANN IT, MSSI support staff and James Gannon in Johannesburg, June 24.
• Tools demonstration scheduled for SSR2 plenary meeting 18, with ICANN and MSSI support staff.

11

14 May 2017

Draft a Statement of Work for specialist technical writer.

James Gannon, Cathy Handley, Denise Michel

• ICANN Org provided outline of procurement process and input via email to support development of Statement of Work.