Versions Compared

Old Version 150

changes.mady.by.user Jennifer Bryce

Saved on

compared with

New Version 151

changes.mady.by.user Jennifer Bryce

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Item #Source of RequestDate of RequestAction Item RequestAction OwnerRequest Clarified (link to email archive; date)Anticipated Completion DateCompleted ResponseCompletion Date
6815

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) 
ICANN Org
TBD



  • 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

43

11

14 May 2017

  • 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?

  • Provide the SSR2 RT a timeline of the ITHI project, when they have clarity on next steps and schedules.
ICANN Org
27 July 2017
  • Email circulated to Review Team 26 June 2017.



90Email10 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:

  • Is this a useful structure to use to organize this activity?
  • What is missing from this list?
  • Is there anything here that is perhaps out of scope?
  • Is this an achievable agenda?
SSR2-RT
21 July 2017

891726 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
25 July 2017

871726 June 2017Publish post-meeting blog on icann.orgICANN Org
19 July 2017


861726 June 2017Provide SSR2-RT with information on if ICANN Office of the CTO has plans to re-define “security”? If so, how and when?ICANN Org
25 July 2017

831726 June 2017Review 06:00 plenary call slot attendance and provide input to inform discussion around potential cancelation of call.Co-Chairs
25 July 2017

811726 June 2017SSR2-RT to share thoughts on top SSR concerns with Future Challenges subtopic team to inform work items/scope.aSSR2-RT
TBD

801725 June 2017Provide follow-up questions from the 25 June SSR1 briefings so that ICANN Org can prepare responses.SSR2-RT
25 July 2017

791725 June 2017Complete SSR1 implementation briefings.ICANN Org
August 2017

7617
25 June 2017
  • Complete Doodle poll on January 2018 face-to-face meeting.
  • Co-Chairs to identify date for face-to-face meeting and share with Review Team.
SSR2-RT, Co-Chairs
1 August 2017
  • Doodle poll completed.

751725 June 2017Prepare 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
25 July 2017

591223 May 2017Draft SSR2 Review Team work plan with key dates, circulate to RT for input.Co-Chairs, James Gannon, Boban Krsic
TBD

53

11

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

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, Emily Taylor, Kerry-Ann Barrett


25 July 2017

45

11

14 May 2017

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

Email request from James Gannon & PDF attachment

ICANN Org
25 July 2017
  • 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.

44

11

14 May 2017

Draft a Statement of Work for specialist technical writer.

James Gannon, Cathy Handley, Denise Michel


25 July 2017

...