You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 281 Next »

*Anticipated completed date to be provided once reasonable date is determined by appropriate subject-matter expert

OPEN ACTIONS/REQUESTS

Item #CategorySource of RequestDate of RequestAction Item RequestAction Owner

Anticipated Completion Date*

Progress NotesCompleted ResponseCompletion Date
156OutreachCo-Chairs29 September 2017Create first draft of ICANN60 outreach slides for Co-Chairs reviewICANN Org13 October 2017


155IANA
25 June 2017

Advise if the sub-team requires an NDA to access any of the following documents:

  • Business continuity plan for PTI.
    • Plan for migration
    • What kind of failure rollover documentation do you have. Day-to-day. Failure rollover.
  • Processes and training.
    • A presentation on training and processes documents to a good level of detail. To replace seeing the docs themselves.
  • Documented evidence of business continuity test (if it exists)
  • A high-level  walk through of RZMS, from perspective of cc and gTLDs (to clarify issues)
  • Field verification of RZMS – presentation on controls within the RZMS system
  • Documentation that identifies procedures for verifying authorized contact.
  • Presentation on relationship between PTI, ICANN and the root zone maintainer, post-transition (with roles and responsibilities, who works where, who have authority)
ICANN Org



152AdminCo-Chairs15 September 2017Review recorded decisions reached for accuracy and completeness.ICANN Org, SSR2-RT
New process for decisions reached proposed via email to Co-Chairs.

150Outreach2712 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



149NDA2712 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).

148ICANN SSR2712 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 Org4 October 2017


147ICANN SSRTrello27 August 2017ICANN 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
  • EBERO operator responded with questions for the team. Shared as part of the relevant task on Trello. Response provided by team and shared with SME for progression.
  • ICANN has sent a request to EBERO operators to gauge interest.


146SSR1Email26 August 2017Provide 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.



144IANAIANA Transition Subteam Meeting24 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.

143IANAIANA Transition Subteam Meeting24 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




141IANAIANA Transition Subteam Meeting24 August 2017Schedule 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 Org18 October 2017

In progress. KD OK to meet with Cathy, date/time TBD.



139SSR12422 August 2017Review Team members to volunteer if they feel they can contribute to the SSR1 implementation subgroup.SSR2-RT



136AdminEmail 16 August 2017

Respond to ICANN Travel ASAP & make flight reservations to travel to Abu Dhabi for the face-to-face meeeting.

SSR2-RT



135AdminEmail 16 August 2017

Report to Team on potential room availability at ICANN meeting for sub-group meetings during week.

ICANN Org28 October 2017


134AdminEmail 16 August 2017

Send calendar invites for Team meeting days in Abu Dhabi and additional invites as meetings are scheduled.

ICANN OrgAs needed.
  • Calendar invites for face-to-face confirmed meetings sent to team.


133AdminEmail 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
  • Access granted and request sent via Trello for all team members to access the SSR2 Review Team boards.


132AdminEmail 16 August 2017Draft updated work plan: Reply on email list to Denise’s Aug 14 note; details and your contributions to workplan are required.SSR2-RT



118AdminCo-Chairs4 August 2017Provide list of meetings of interest in Abu Dhabi for Review Team and sub-teams when schedule is available ICANN Org13 October 2017


101SSR1211 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
  1. In progress

  2. In progress

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.


98GeneralEmail19 June 2017Provide briefing on Framework for Registry Operators to Respond to Security ThreatsICANN Org4 November 2017
  • Co-Chairs advised if briefing could be scheduled in Abu Dhabi.
  • Asked Co-Chairs via email to advise if meeting with members of the drafting team should be scheduled in Abu Dhabi.
  • Briefing scheduled for 5 September 2017. Plenary meeting cancelled.
  • Briefing confirmed for 25 July 2017. Postponed per Co-Chairs
  • Briefing confirmed for 26 June 2017. Postponed per Co-Chairs.



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



80b.SSR11725 July 2017

Provide responses to questions from SSR1 briefings (Ops + Finance)

  1. To what extent do you work with the relevant standards bodies (UNICODE and the IETF) over the issues with the use of IDNs and longer label TLDs?
  2. There are many challenges in IDN WHOIS lookups.  How do we get an accurate IDN WHOIS database for the Incident Handling process?
  3. How is the expansion of the name space with more gTLDs contributing to the security and stability of the Internet?

  4. What metric is being used to ensure a "healthy" DNS marketplace?

  5. How does ICANN proactively make sure to implement policy (eg. New gTLD Program expansion) in a secure and stable manner?

  6. New gTLD contract has a lot on New gTLDs to make sure they are secure and stable. To clarify, the main means you see to do that in implementation is through contracts, vs.  that as an aspect? Is that the primary means for ICANN to push the SSR remit?

  7. Can GDD comment on the failures of both SLAM and EBERO where they apply to RSP failure scenarios, also implementation of EBERO testing took 3 years from implementation of the first new gTLD delegation, no security review of the EBERO’s has ever taken place, what is the justification for that?

  8. Can Francisco to brief us on both systems (EBERO and SLAM) from an SSR2 perspective (Rather than the SSR1 implementation perspective)?

  9. I’m also looking for not how much departments are spending but how much their spending on EBERO.

  10. Who will be the contracting entity for future SOC2/3 audits of PTI?

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



75ICANN SSR1725 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


  • Staff from the ICANN CIO office will be available during the ICANN SSR subteam meeting 9-10 October to answer the questions.
  • 75.a. Questions sent to ICANN CIO.



75. a. 25 July 2017

53SSR1

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



44Procurement

11

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.




COMPLETED ACTIONS/REQUESTS

Item #CategorySource of RequestDate of RequestAction Item RequestAction Owner

Anticipated Completion Date

Progress NotesCompleted ResponseCompletion Date
154ICANN SSRJames Gannon21 September 2017

Question for ICANN: Regarding the SSR implications of the .avianca tld https://www.icann.org/uploads/compliance_notice/attachment/957/serad-to-reyes-19sep17.pdf[icann.org] situation, i.e when and where do the decisions on enforcement of non compliance get evaluated for SSR impact (in this case where a gTLD is AWOL but for months no actual action is taken).

ICANN Org29 September 2017
Response circulated to the list via email.29 September 2017
151ProcurementCo-Chairs15 September 2017Provide 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.

Gap analysis RFP published to ICANN.org.

Review Team agreed to proceed with release of gap analysis specifications document on 26 September plenary call.

26 September 2017
153ProcurementCo-Chairs15 September 2017Provide Co-Chairs with information on a recent RFP process recently followed by the GNSO.SSR2-RT22 September 2017
Process for engaging contractors clarified via email per Co-Chairs request.21 September 2017
140Procurement2422 August 2017Review Team to submit consolidated input and edits on the RFP overview document and confirm their approval for ICANN organization to initiate a process to engage a contractor, based on qualifications, scope of work, timeline, deliverables and other essential components included in the RFP overview document modified by the Review Team (the cost not to exceed $50,000)SSR2-RT
  • 'Clean' RFP document and revised procurement process overview circulated to Co-Chairs 9/14. Co-Chairs to approve document for ICANN Procurement final review.
  • Edits provided on list. Further updates may be provided based on ICANN's response to action item 145.
Replaced by action item 151.15 September 2017
142IANAIANA Transition Subteam Meeting24 August 2017

Determine appropriate person to ask for training documentation for processes and procedures for PTI staff.

ICANN Org


Confirmed via email and asked if the subteam would like to set up a meeting.15 September 2017
145ProcurementEmail25 August 2017

Provide additional information about soliciting consultants with a budget under $50k (no RFP needed), and the difference between engaging a consultant and an “independent expert.”

ICANN Org12 September 2017Clarification email sent to Co-Chairs.Revised process overview circulated to Co-Chairs via email. 13 September 2017
106ICANN SSRICANN SSR Subtopic Meeting 131 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 team12 September 2017
Draft audit plan document reviewed during plenary call 27. Staff confirmed document has been shared with staff and items will be addressed during subtopic f2f meeting 9-10 October in LA.12 September 2017
46NDA

11

14 May 2017

Updated Per meeting 24: James and Kerry-Ann will provide briefing to Review Team on Non-Disclosure Agreement (NDA) and associated documents, when available. 

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

12 September 2017
  • Revised draft NDA and Confidential Disclosure Agreement circulated to review team via email.
  • James provided update to team via email.
  • Meeting to review revised documents scheduled with ICANN Legal Friday 18th August 2017.
  • Discussion with ICANN Legal took place on 5 June 2017. Kerry-Ann and James to follow-up with redline edits to document.

Documents circulated to the list (29 August) and overview provided by Kerry-Ann on plenary meeting 27 (12 September).

12 September 2017
43General11

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.

ICANN Org

8 September 2017
  • 43. a. Email circulated to Review Team 26 June 2017.
Email response sent to review team.

6 September 2017

89General1726 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 Board8 September 2017
Email response sent to review team.5 September 2017
99DNS SSREmail19 June 2017Provide briefing on DNS Abuse study final resultsICANN Org19 September 2017
  • ICANN staff working to schedule webinars for the community.
  • Briefing confirmed for 25 June 2017. Postponed per Co-Chairs.

Community webinars scheduled and information shared with the review team via email.

1 September 2017
126ICANN SSRICANN SSR Subtopic Meeting 214 August 2017

Request ICANN Legal to be present at ICANN SSR face-to-face meeting, October 9-10 to rule on availability of documents.

ICANN Org8 September 2017
  • Process for sharing confidential documents is in development. Team updated via email.

Update sent to the review team via email. Replaced by action item 144.

30 August 2017
119AdminCo-Chairs4 August 2017Submit request for meeting room (50 ppl max) for community discussion with SSR2 in Abu Dhabi ICANN Org30 August 2017
Meeting session request sent to ICANN Meetings team.30 August 2017
138AdminEmail 16 August 2017

Send calendar invites for Team meeting days in Brussels, 22-24 January, and report to Team on how soon can ICANN travel can book arrangements.

ICANN Org

Calendar invites distributed to team.

Welcome email/initial travel correspondence sent to review team from ICANN Travel.

29 August 2017
130SSR1Email 14 August 2017
  1. Fix the broken links in the Final Implementation Report and ensure that relevant references have links (if it’s noted in the report as relevant to implementation, please make sure there’s a link to information about it).
  2. Put all the documentation/information (links) for each Recommendation together in one place. Some are linked in the Final Implementation Report, some are listed under “Background Materials” in our wiki and others…. ?
  3. In each Recommendation, provide completion dates for each listed “deliverable” that has a check-mark under “due date” instead of an actual date
ICANN Org

See completed action item 104 for progress notes regarding related previous request.


Response sent to review team via email. 25 August 2017
121AdminCo-Chairs4 August 2017ICANN Org to provide written response to request for notes to be provided for each review team call.ICANN Org

Email sent to co-chairs outlining new note-taking process.24 August 2017
107ICANN SSRICANN SSR Subtopic Meeting 131 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 team11 September 2017
Draft audit plan circulated to Review Team with questions to resolve during the meeting and email circulated with request to meet with ICANN staff from appropriate departments.22 August 2017
131AdminEmail 16 August 2017

Sub-team realignment: Reply on email list to Eric’s Aug 14 note about folding sub-group calls into Tuesday Team call to increase engagement and visibility

SSR2-RT

Rapporteurs confirmed preference for respective subgroup call schedules with MSSI secretaria. Update email shared with co-chairs.23 August 2017
108ICANN SSRICANN SSR Subtopic Meeting 131 July 2017

Circulate outline of detailed work items and proposed next steps after face-to-face meeting.

Žarko, Boban

31 August 2017
Draft audit plan and next steps circulated to the list via email.22 August 2017
128ICANN SSRICANN SSR Subtopic Meeting 214 August 2017

Finalize questions for ICANN subject-matter experts during potential ICANN SSR subgroup meeting in LA. Distribute to staff so they can identify appropriate resources.

ICANN SSR subtopic team25 August 2017
Draft audit work plan circulated via email.22 August 2017
122AdminEmail 4 August 2017

Confirm approval of ICANN SSR subgroup potential face-to-face meeting in LA

SSR2-RT22 August 2017
  • Cost estimate and staff availability circulated via email to Review Team.
  • Doodle poll closed. Email circulated identifying 9-10 October as most popular dates.
  • Staff requested via email additional information regarding meeting objectives/ desired outcomes.
Confirmation received via email.22 August 2017
129ICANN SSRICANN SSR Subtopic Meeting 214 August 2017

Report on results of NDA meeting with ICANN Legal scheduled for 18 August.

James, Kerry-Ann29 August 2017
Replaced by updated action item 4622 August 2017
137OutreachEmail 16 August 2017

Report to Co-chairs on outreach emails to ICANN groups regarding requested meetings in Abu Dhabi

ICANN Org18 August 2017
Email sent to co-chairs.18 August 2017
125OutreachEmail14 August 2017Distribute SSR2 ICANN60 outreach note to SOs/ACs/constituency groups/PSWG.ICANN Org17 August 2017


Note distributed to requested groups.17 August 2017
127AdminICANN SSR Subtopic Meeting 214 August 2017

Provide costing of ICANN SSR face-to-face meeting in LA, 9 and 10 October.

ICANN Org17 August 2017
See action item 122. Circulated via email to Review Team.16 August 2017
124ProcurementCo-Chairs11 August 2017Staff 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 Org17 August 2017See completed action item 100 for progress notes regarding related previous request.Email distributed to Review Team.17 August 2017
59Admin1223 May 2017Draft SSR2 Review Team work plan with key dates, circulate to RT for input.Co-Chairs, James Gannon, Boban Krsic
  • Staff sought clarification via email as to the style as it differs from the template outline agreed on 25 July plenary.
  • Work plan circulated via email by Co-Chairs.

Co-Charis circulated updated work plan via email.14 August 2017
115IANAEmail5 July 2017IANA Subgroup: Take the outcomes of our F2F meeting and turn that into a list of asks from the IANA team with regards to documentation and further follow-ups.Cathy

Subteam collectively preparing to draft document once requested documents have become available (pending discussion with ICANN Legal). Per subgroup update on 15 August plenary call.15 August 2017
81Future Challenges1726 June 2017SSR2-RT to share thoughts on top SSR concerns with Future Challenges subtopic team to inform work items/scope.SSR2-RT

Subteam has developed list of work items for plenary group's consensus. Per update on 15 August plenary call.15 August 2017
45Admin

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, James Gannon15 August 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.

Briefing provided during 15 August 2017 plenary meeting. Background information provided via email 14 August 2017.

15 August 2017
100ProcurementCo-Chairs28 July 2017

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. 

ICANN Org

Briefing with ICANN Procurement scheduled for 15 August 2017. Cancelled per co-chairs (staff/leadership call 11 August)

Draft RFP overview document shared with Co-Chairs via email 11 August 2017.

11 August 2017
97Admin20 25 July 2017Staff to build out work plan template to include elements on information gathering, research and outreach. Co-Chairs to provide feedback before sharing with the Review Team.ICANN Org11 August 2017Work plan template agreed by SSR2-RT during 25 July plenary.

Draft work plan template shared with Co-Chairs via email 11 August 2017.

11 August 2017
123SSR1SSR1 Subtopic Meeting 120 July 2017Open a discussion on the email list regarding work items, eg. redundancies and prioritization. Share document with team for their input on more detailed work plan and timeline. SSR1 Subgroup

Subgroup activities suspended per email from Rapporteur9 August 2017
86General1726 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

Answer provided via email. 9 August 2017
120DNS SSRDNS SSR Subtopic Meeting 37 August 2017Schedule time with Kim Davies on the next available Subtopic call to review draft work topics/answer questions.ICANN Org14 August 2017
Kim confirmed he is available to join the 14 August subgroup call, 20:00 UTC.8 August 2017
116ProcurementCo-Chairs4 August 2017Schedule call with ICANN Procurement team to review procurement process.ICANN Org15 August 2017
ICANN Procurement scheduled to attend SSR2 Plenary 23. 8 August 2017
112DNS SSRDNS SSR Subtopic Meeting 121 July 2017Team to share thoughts on DNS SSR work topics draft doc.DNS SSR subtopic team

Team agreed next step is to schedule a discussion with Kim Davies to progress work items (see action 120)7 August 2017
117AdminCo-Chairs4 August 2017Draft note for Co-Chairs regarding Abu Dhabi meeting dates and potential options for informal subgroup meetings.ICANN Org8 August

8 August 2017
80a.SSR11725 June 2017

80. Provide follow-up questions from the 25 June SSR1 briefings so that ICANN Org can prepare responses.

ICANN Org

SSR2-RT

25 July 2017



25 July 2017

114IANA1725 June 2017Schedule interviews with Kim Davies, Elise Gerich, PTI at ICANN59.ICANN Org29 June 2017

Interview complete and notes shared with subteam.

26 June 2017
113Future ChallengesFuture Challenges Subtopic Meeting 124 July 2017Input draft text to Google doc Future Challenges section on vendor security and performance security sub-sections.Mohamad Amin Hasbini28 July
Emailed text for team's consideration24 July 2017
111DNS SSRDNS SSR Subtopic Meeting 121 July 2017

Share redline version of DNS SSR work topics draft to the subtopic email list.

Eric21 July 2017
Document shared via email.21 July 2017
68DNS SSR15

13 June 2017

  • Follow-up via email: Please provide a written explanation as to how the original question was felt to be objectionable.
  • 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

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

  • Question reframe response circulated via email 11 July 2017.


11 July 2017

110DNS SSRPlenary 1725 June 2017Write up DNS SSR topic areas and share with sub-team.Geoff27 June 2017
Proposed reorganization of study topics doc (GH) shared with team.26 June 2017
109ICANN SSRPlenary 1726 June 2017Refine key action steps/work items and scope of the subtopic review.ICANN SSR subtopic team

Re-organized work items shared with plenary for input (see Item 90 on Tracking Tool). Replaced by actions S2.2

31 July 2017
105SSR1SSR1 Subtopic Meeting 120 July 2017Determine if there is an owner of the SSR1 implementation report, and who was determining the goals and outcome of each recommendation.ICANN Org

Email to Review Team.31 July 2017
104SSR1Email24 July 2017

Provide completion dates for each recommendation (date it was designated as “complete”); if there was multiple activities or deliverables in a recommendation, include the dates those were completed too.

ICANN Org28 July 2017

7 August 2017

26 July 2017

103SSR1SSR1 Subtopic Meeting 120 July 2017Gather information regarding SSR1 implementation together in logical groupings and index within the Google doc. ICANN Org28 July 2017
Background materials section added to SSR1 Subteam wiki page including links to all briefing materiasl and SSR1 implementation final report26 July 2017
102Admin211 August 2017Review Team members to email staff with Abu Dhabi full-day meeting preferences. Options are 27 October and 3 November.  SSR2-RT3 August 2017
A number of review team members responded off-list to email.3 August 2017
79SSR11725 June 2017Complete SSR1 implementation briefings.ICANN Org1 August 2017
All briefings complete and materials posted to the wiki.1 August 2017
96AdminCo-Chairs21 July 2017Review other meeting date/time options for F2F meeting at ICANN60 due to conflict for one of the co-chairsICANN Org1 August 2017
Available options for full Review Team meeting provided via email to Co-Chairs. Presented on plenary 21 and via email to SSR2 RT.1 August 2017
90ICANN SSREmail5 June 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

Replaced by Subtopic group action item 2.331 July 2017
101AdminCo-Chairs28 July 2017

Confirm if staff responsible for the outstanding SSR1 Recommendations (11, 12) can attend the SSR2 plenary call to present the recommendation implementation.

ICANN Org31 July 2017
Email sent to Co-Chairs.31 July 2017
76Admin17
25 June 2017
  • 76. e. Review Team members to share edits to availability with staff off-list. Co-Chairs to confirm meeting dates.
  • 76. d. Co-Chairs to confirm location of face-to-face meeting.
  • 76. c. Identify most cost-effective meeting location with Meetings team.
  • 76. b. Co-Chairs to identify date for face-to-face meeting and share with Review Team.
  • 76. a. Complete Doodle poll on January 2018 face-to-face meeting.

76. d. Co-Chairs

76. c. ICANN Org

76. b. Co-Chairs

76. a. SSR2-RT

25 July 2017
  • 76. e. James Gannon and Cathy Handley shared updates July 14. No additional follow-up received.
  • 76. d. Email sent to Review Team confirming Brussels as the location.
  • 76. c. Email sent to co-chairs identifying Brussels as the most cost-effective location.
  • 76. b. 22-24 January identified by Co-Chairs per Doodle poll responses. Save-the-date invites distributed.
  • 76. a. Doodle poll completed.

76.e. 27 July 2017

76. d. 25 July 2017

76. c 19 July 2017

76. b. 14 July 2017

76. a. 27 June 2017

91SSR11811 July 2017

Provide follow-up questions via email regarding the SSR1 implementation briefing by ICANN Compliance – recommendation 10.

SSR2-RT

25 July 2017
No follow-up questions provided but SSR2 Review Team is free to provide follow-up questions at any time.25 July 2017
95AdminCo-Chairs14 July 2017

Build out the SSR2 Review Team work plan to provide additional substance and practical steps to share with Co-Chairs for initial input.

ICANN Org21 July 2017
Shared via email.21 July 2017
87Admin1726 June 2017Publish post-meeting blog on icann.orgICANN Org19 July 2017
Published here.19 July 2017
94OutreachCo-Chairs14 July 2017Draft note to SO/AC leaders asking for time on their agenda at ICANN60 for SSR2 update and discussion on shared items of interest. Share with Co-Chairs.ICANN Org20 July 2017
Draft provided to co-chairs via email.19 July 2017
93SSR11811 July 2017Share link to the published ICANN Compliance Audit Report.ICANN Org18 July 2017
Shared via email:

https://www.icann.org/resources/pages/compliance-reports-2016

13 July 2017
92SSR11811 July 2017

Respond to questions asked by the Review Team during the SSR1 implementation briefing by ICANN Compliance – recommendation 10.

ICANN Org

25 July 2017
Answers provided via email.13 July 2017
78SSR11725 June 2017Populate the table of remaining SSR1 recommendations, with department, name of staff and Tuesday July Plenary meeting schedule availability. ICANN Org7 July 2017
Google document updated.7 July 2017
85General1726 June 2017
  • Follow-up question: Please clarify when.
  • Provide SSR2-RT with information on if ICANN Org will accept Board proposal for a new, template “Terms of Reference in Operating Standards”? If so, when will it be issued?
ICANN Org14 July 2017
  • Response provided via email to Review Team. Terms of Reference template estimated to be completed 28 July 2017.
  • Response provided via email to Review Team.
13 July 2017
84Admin1726 June 2017Establish staff support requirements and availability to support SSR2-RT subgroups.ICANN Org, Co-Chairs11 July 2017
Available time slots to support subgroup calls circulated via email to Review Team11 July 2017
88General1726 June 2017

Identify Board members on “caucus” reviewing SSR2 work.

ICANN Board14 July 2017
Board Caucus details circulated via email.11 July 2017
82Admin1726 June 2017Update SSR2-RT action items wiki page with new request reporting tool.ICANN Org7 July 2017
New 'Tracking Tool' wiki page live.7 July 2017
77SSR11725 June 2017Provide final SSR1 implementation report.ICANN Org26 June 2017
Link circulated to Review Team via email.26 June 2017
76Admin17
25 June 2017Complete 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-Chairs7 July 2017

Doodle poll completed.

6 July 2017
74Admin1620 June 2017

SSR2-RT members to volunteer for sub-topic rapporteur roles within each sub-team.

SSR2-RT23 June 2017
Subtopic rapporteurs recorded in Google doc.26 June 2017
73Admin16

20 June 2017

SSR2-RT to share any objections on list to dropping the 0600 UTC call slot and address call schedule rotation in the Johannesburg meeting.

SSR2-RT26 June 2017
Item addressed in Plenary 17. Replaced by action item #83.26 June 2017
72Admin16

20 June 2017

Update the January 2018 face-to-face meeting Doodle poll with option for weekend meeting.

ICANN Org, Co-Chairs21 June 2017
Doodle poll updated and circulated to Review Team via email.25 June 2017
71Outreach16

15 June 2017

Send SSR2 June progress update to leaders/lists for each SO, AC, stakeholder group, constituency, PSWG and the Board.ICANN Org20 June 2017
Correspondence shared with SO/AC leaders email distribution list and ICANN Board.20 June 2017
70Admin1513 June 2017

Post attendance participation rates to wiki on a monthly basis.

ICANN Org23 June 2017
Posted on Fact Sheet wiki page20 June 2017
69Outreach15

13 June 2017

Staff to capture and share all discussions to-date around outreach.

ICANN Org16 June 2017
Google document shared with Review Team via email.16 June 2017
67General
12 June 2017

Email request to adopt the title "Security Review" in public communications.

ICANN OrgTBD
  • Follow-up email sent from ICANN Comms.
  • Follow-up meeting with Eric Osterweil, Denise Michel, Duncan Burns, Emily Pimentel, MSSI support staff - Johannesburg, 28 June
  • Email response provided, 15 June
7 July 2017
66Outreach146 June 2017

Send written responses to RT questions asked during the presentation on ICANN’s Global Stakeholder Engagement outreach efforts to SSR technical community.

  1. We’re hearing that the GSE is supporting the work done by CTO. So, what do we mean by help support? And what is the relationship between this engagement and the IANA functions? (AA)
  2. A lot of the presentation was about sending the message out. How does it work going the other way? You point to passive mechanisms but what about active measures? (GH)
  3. 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)
  4. What efforts does ICANN take to inform the policy debate as it is taking place vs. after the fact? (GH)
  5. How does GSE work specifically with the ccTLD community on SSR? (JM)
  6. How is your work is coordinated and support the OCTO and SSR teams commitment to engage and seek input from the broader SSR community that’s not necessarily active in ICANN. Including their obligation to get input/interaction from them on SSR Framework and strategic priorities. How are you involved and how does the coordination occur? (DM)
  7. When do you think in terms of GSE that the focus on explanation/teaching of what ICANN does will shift to more of an interaction/ substantive engagement? (GH)
ICANN Org23 June 2017
  • Answers to follow-up questions circulated to Review Team.
  • ICANN DNS Engineering team asked RT to reframe the following question (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) 

  • RT asked ICANN DNS Engineering to reframe the question and provide an answer.
14 June 2017
65Admin146 June 2017Share thoughts and continue discussion on list regarding presentation of ICANN Security and SSR1 subtopic work plans. SSR2-RT23 June 2017
See email thread.23 June 2017
64Admin146 June 2017Share thoughts on list on how to be more open to observer inputs. SSR2-RTTBD
Thoughts shared via email and addressed during plenary 15. Conclusion: Keep interactions as-is for now.13 June 2017
63Admin1223 May 2017RT members to continue to volunteer for subtopics. More volunteers particularly needed for group 1: SSR.SSR2-RTTBD
Volunteers recorded in Subtopics document.26 June 2017
62Admin12

23 May 2017

Prepare a draft work plan proposal for SSR1 Review and ICANN Security topics.

Boban Krsic, Žarko Kecić26 May 2017
Document shared via email5 June 2017
61Admin1223 May 2017Consolidate duplicative items, create subheadings for each topic groups within volunteer groups.SSR2-RT23 June 2017
Subtopics document updated.26 June 2017
60Admin1223 May 2017Record volunteers from plenary call in the subtopics document on wiki. ICANN Org23 May 2017
Subtopics document updated.23 May 2017
58Outreach1223 May 2017Share thoughts on list regarding outreach and engagement, and possible guidelines.SSR2-RT23 June 2017
Thoughts shared via email.26 June 2017
57Admin1223 May 2017Share thoughts on list regarding Johannesburg agenda topics.SSR2-RT25 May 2017
Thoughts shared via email.20 June 2017
56Admin1223 May 2017Distribute draft Johannesburg agenda to email list.Co-Chairs30 May 2017
Circulated via email.16 June 2017
55Admin12

23 May 2017

Add agenda item regarding how Observers can participate and contribute to sub topic work to plenary call #13. 

Co-Chairs30 May 2017
Replaced by action item #64. 6 June 2017
54Admin1115 May 2017

Publish blog on ICANN.org regarding SSR2 face-to-face meeting in Madrid.

ICANN Org31 May 2017
Blog published on ICANN.org.26 May 2017
52Admin

11

15 May 2017

Schedule remainder of briefings related to SSR1.

ICANN Org7 July 2017
Briefings schedule google document shared with Review Team. 7 July 2017
51Outreach

11

15 May 2017

Staff to provide RT with explanation and background information from ICANN Global Stakeholder Engagement and Adiel Akplogan (ICANN VP Technical Engagement) regarding current outreach efforts to SSR technical community (responsibility, focus, accomplishments) for RT’s consideration.

ICANN OrgTBD

Patrick Jones, Senior Director, GSE and Adiel Akplogan, Vice President, Technical Engagement joined SSR2 plenary 14.

6 June 2017
50Admin

11

15 May 2017

Circulate list of potential scope topics and list of sub team volunteers.

ICANN Org18 May 2017
Google doc shared with Review Team.18 May 2017
49Admin1114 May 2017

Circulate link to ICANN technical portal

ICANN OrgTBD
Link circulated to Review Team.18 May 2017
48General

11

14 May 2017

Share links to relevant articles regarding threat mitigation and classification of threats.

ICANN Org22 June 2017

Links circulated to Review Team:

Threat Mitigation

Classification of Threats 

14 June 2017
47Admin

11

14 May 2017

Circulate Google doc for RT to input their SSR concerns. Inputs to form substance of scope discussion.

ICANN Org16 May 2017
Google document circulated via email to Review Team.14 May 2017
43General

11

14 May 2017

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

ICANN OrgTBD
Email circulated to Review Team.26 June 2017

42

IANA

10

9 May 2017

Post PTI briefing materials and relevant materials to the SSR2 wiki background materials page.

ICANN OrgTBD
Links posted to SSR2 background materials wiki page.11 May 2017
41Admin92 May 2017

Circulate clean version of Terms of Reference to list for final 24-hour consideration.

Co-ChairsTBD
Shared via email.3 May 2017
40Admin9

2 May 2017

Send adopted Terms of Reference to ICANN Board, should no objections occur in the 24 hours from circulation.

Kaveh RanjbarTBD
Sent to Board Chair via email.11 May 2017
39Admin9

2 May 2017

Prepare proposal for initial structuring of RT work for Madrid meeting.

James GannonTBD
Shared via email.8 May 2017
38Admin9

2 May 2017

Provide a decision to the Review Team on whether a face-to-face meeting will take place in Johannesburg, and on what dates. 

Co-Chairs5 May 2017
Johannesburg meeting confirmed to take place 25 & 26 June.10 May 2017
37IANA825 April 2017Schedule a briefing on PTI, the Bylaws and the relationship with ICANN to share input to assist in determining its possible inclusion in the scope of SSR2 review. ICANN Org28 Apr 2017
Elise Gerich and Samantha Eisner joined 9 May plenary call and provided briefing.9 May 2017
36Admin825 April 2017Provide draft agenda for Madrid face-to-face meeting to Review Team for input. Co-ChairsTBD
Shared via email. 1 May 2017
35SSR1825 April 2017Circulate current summary of SSR1 review implementation to SSR2-RT list. ICANN Org25 Apr 2017
Email circulated to Review Team.25 April 2017
34Admin825 April 2017Provide update to SSR2-RT after scheduled SO/AC Chair call to inform decision regarding potential meeting dates in Johannesburg at ICANN59. Co-ChairsTBD
Replaced by action item #38.4 May 2017
33Admin  718 April 2017

Share link to Bylaws Article 18 and appropriate context.

ICANN Org20 Apr 2017
Bylaw article and context distributed via email to RT.20 March 2017
32Admin  7

18 April 2017

Provide v3 draft scope for Terms of Reference based on discussions and comments.

Eric OsterweilTBD
Document circulated via email.29 April 2017
31Admin  718 April 2017Provide availability of OCTO – SSR team in Madrid to Co-Chairs to inform Madrid meeting agenda development.ICANN Org21 Apr  2017
Information provided to Co-Chairs on staff coordination call.21 April 2017
30Admin  7

18 April 2017

Circulate Doodle poll to establish RT availability for F2F meeting in Johannesburg.

ICANN Org18 Apr 2017
Doodle poll circulated. 18 April 2017
29Admin  7

18 April 2017

Circulate updated open action items list to RT.

ICANN Org20 Apr 2017
Updated action items list circulated. 20 April 2017
28NDA 13 April 2017

Non-Disclosure (NDA) and Conflicts Disclosure (CDA) documentation for RT.

ICANN Org1 May 2017
2 May 2017
27Admin611 April 2017

Clean up draft Terms of Reference (accept points of agreement). Pull out points of disagreement for discussion on email list.

ICANN Org13 April 2017
Circulated via email.14 April 2017
26Admin611 April 2017Review v2 draft Terms of Reference and share thoughts on email list.RT MembersTBD
Document shared. Review Team shared feedback via email.25 April 2017

25

General611 April 2017

Propose timeline for finalizing scope.

Co-ChairsTBD
Item added to Madrid face-to-face meeting agenda.16 May 2017
24General428 March 2017Review brainstorming capture slides from 15 March meeting  and share thoughts on email list.RT MembersTBD
Item added to Plenary 11 Madrid face-to-face meeting agenda. 16 May 2017
23Admin428 March 2017Schedule weekly RT calls per agreed rotation schedule.ICANN Org28 March 2017
Call invites sent to Review Team.28 March
22General428 March 2017Review draft Scope and Work Plan and make comments on the email list. RT Membersfrom 1 April 2017
  • Replaced by action item #26.
  • Thoughts shared via email.
16 May 2017
21Admin322 March 2017Schedule 60-minute plenary call #4, 14:00 UTC Tuesday 28 March.ICANN Org22 March 2017
Call invite circulated to Review Team.22 March 2017
20General322 March 2017Co-Chairs to coordinate and formulate a proposal as to how to separate duties and present it to the RT.SSR2 Co-ChairsTBD
Co-Chairs agreed to informal separation of duties. 28 April 2017
19Admin322 March 2017Prepare a plan for a rotation schedule for RT calls to the Co-Chairs for the next meeting.ICANN Org24 March 2017
Excel worksheet planning document shared with Co-Chairs.24 March 2017
18SSR1

3

22 March 2017

Open SSR1 Rec 11 - Effectiveness of mechanisms to mitigate abuse. 

Implementation description: ICANN should finalize and implement measures of success for new gTLDs and IDN fast track that expressly relate to its SSR-related program objectives, including measurements for the effectiveness of mechanisms to mitigate domain name abuse.

ICANN Org28 April 2017
Recommendation 11 implementation completed: https://community.icann.org/display/SSR/Rec+%231114 April 2017
17SSR1

3

22 March 2017

The following three open SSR1 Recommendations are interrelated and are being implemented together:

Rec 20 - SSR budget

Implementation description: ICANN should increase the transparency of information about organization and budget related to implementing the SSR Framework and performing SSR-related functions. 

Rec 21 - SSR budget 

Implementation description: ICANN should establish a more structured internal process for showing how organization and budget decisions relate to the SSR Framework, including the underlying cost-benefit analysis.

Rec 22 - SSR resources for new gTLDs

Implementation description: ICANN should publish, monitor and update documentation on the organization and budget resources needed to manage SSR issues in conjunction with introduction of new gTLDs.  

ICANN Org15 April 2017

Recommendation 20 implementation completed:

https://community.icann.org/display/SSR/Rec+%2320

Recommendation 21 implementation completed:

https://community.icann.org/display/SSR/Rec+%2321

Recommendation 22 implementation completed:

https://community.icann.org/display/SSR/Rec+%2322



4 April 2017
16Admin322 March 2017Update the ICANN Board that the deadline of the end of the month will not be met but note that the RT is working to prepare its Terms of Reference and Work Plan per the Boards request.Kaveh Ranjbar28 March 2017
Kaveh Ranjbar provided update to the Board.28 March 2017
15Admin322 March 2017Prepare straw-man versions of the Terms of Reference and Work plan for the RT to consider.ICANN Org31 March 2017
4 April 2017
14Admin322 March 2017Generate a list of official observers and their relevant skill sets for RT consideration.ICANN Org28 March 2017
  • Email circulated to Review Team
  • SSR2 Observers wiki page updated with link to requested information.
27 March 2017
13Admin215 March 2017Circulate slide deck from 3/15 SSR2 face to face meeting.ICANN Org16 March 2017
Slide deck uploaded to SSR2 plenary 2 wiki page.16 March 2017
12Admin215 March 2017Add OCTO KPIs, ICANN 2016 strategic plan and Emerging Technology Identifiers ICANN58 presentation to wiki background materials.ICANN Org16 March 2017
Materials added to SSR2 background materials wiki page.16 March 2017
11General215 March 2017Provide a list of existing definitions of terms: Security, Stability, Resiliency and Unique Identifiers. Reference where they are located.ICANN Org15 March 2017
List of definitions compiled and provided to Review Team.16 March 2017
10Admin215 March 2017Circulate names / contact information for SADAG vendors to SSR2 RT list.ICANN Org20 March 2017
Vendor contact details provided via email.17 March 2017
9Admin215 March 2017Circulate CDAR study report and contact information to SSR2 RT list.ICANN Org20 March 2017
  • Slide deck circulated and uploaded to SSR2 plenary 2 wiki page.
  • Contact details provided via email.
17 March 2017
8Admin215 March 2017Provide SSR2 Fact Sheet sample and schedule.ICANN Org16 March 2017
Sample Fact Sheet and schedule posted to wiki and circulated to Review Team via email.16 March 2017
7Admin215 March 2017Schedule 60-minute plenary call, Wednesday 22 March, 19:00 UTC.ICANN Org15 March 2017
Call invite circulated to Review Team.15 March 2017
6Admin215 March 2017Develop and circulate time zone mapping to support scheduling of regular plenary calls discussion on next plenary call.ICANN Org21 March 2017
Excel worksheet planning document shared with Co-Chairs. 24 March 2017
5Admin2

15 March 2017

Request for the IS-SSR team to provide a summary of the types of requests for assistance that they receive from the community.

ICANN OrgTBD
Document circulated to Review Team.18 April 2017
4Admin

 1 

2 March 2017Draft document about what other review teams have used for chairs and co-chairs and send to the list.ICANN Orgn/a
Email circulated to Review Team.7 March 2017
3Admin12 March 2017Produce a summary of how other review teams have handled Observers and post to the list.ICANN Orgn/a
Email circulated to Review Team. 7 March 2017
2Admin12 March 2017Post staff structure responsibilities on wiki background page.ICANN Orgn/a
ICANN Organization Support Team page created on SSR2 wiki.31 March 2017
1Admin12 March 2017Provide terms of reference to the ICANN Board.SSR2TBD
Email sent to Board Chair on behalf of Review Team.11 May 2017






  • No labels