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

Compare with Current View Page History

« Previous Version 207 Next »

OPEN ACTIONS/REQUESTS

Item #Source of RequestDate of RequestAction Item RequestAction OwnerRequest Clarified (link to email archive; date)Anticipated Completion DateCompleted ResponseCompletion Date
122Email 4 AugustComplete Doodle poll of preferred dates for potential ICANN SSR subgroup meeting in LA.ICANN SSR subgroup
11 August 2017

121Staff/Leadership Call4 AugustProvide response to request for notes to be provided for each sub-team call.ICANN Org



119Staff/Leadership Call4 August 2017Submit request for meeting room (50 ppl max) for community discussion with SSR2 in Abu Dhabi ICANN Org



118Staff/Leadership Call4 August 2017Provide list of meetings of interest in Abu Dhabi for Review Team and sub-teams when schedule is available ICANN Org



115Email5 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



108ICANN 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

107ICANN 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 team
11 September 2017

106ICANN 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 team
4 September 2017

101211 August 2017Provide responses to questions on SSR1 briefing: Recommendations 11, 12.ICANN Org

Clarity sought on some questions.




100Staff/Leadership Call28 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



99Email19 June 2017Provide briefing on DNS Abuse study final resultsICANN Org



9720 25 July 2017Staff to build out work plan template to include elements on information gathering, research and outreach.ICANN Org
11 August 2017

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



  • 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

  • 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


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


43. a. 26 June 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



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



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



801725 June 2017

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

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

751725 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.

75. a. 25 July 2017



  • 75.a. Questions sent to ICANN CIO.



75. a. 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



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



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





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, James Gannon

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


COMPLETED ACTIONS/REQUESTS

Item #Source of RequestDate of RequestAction Item RequestAction OwnerRequest Clarified (link to email archive; date)

Anticipated Completion Date

Completed ResponseCompletion Date
123SSR1 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
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

Answer provided via email. 9 August 2017
120DNS SSR Subtopic Meeting 37 August 2017Schedule time with Kim Davies on the next available Subtopic call to review draft work topics/answer questions.ICANN Org
14 August 2017Kim confirmed he is available to join the 14 August subgroup call, 20:00 UTC.8 August 2017
116Staff/Leadership Call4 August 2017Schedule call with ICANN Procurement team to review procurement process.ICANN Org
15 August 2017ICANN Procurement scheduled to attend SSR2 Plenary 23. 8 August 2017
98Email19 June 2017Provide briefing on Framework for Registry Operators to Respond to Security ThreatsICANN Org

4 August 2017
112DNS 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
117Staff/Leadership Call4 August 2017Draft note for Co-Chairs regarding Abu Dhabi meeting dates and potential options for informal subgroup meetings.ICANN Org
8 August
8 August 2017
1141725 June 2017Schedule interviews with Kim Davies, Elise Gerich, PTI at ICANN59.ICANN Org
29 June 2017
  • Interview complete and notes shared with subteam.
26 June 2017
113Future Challenges Subtopic Meeting 124 July 2017Input draft text to Google doc Future Challenges section on vendor security and performance security sub-sections.Mohamad Amin Hasbini
28 JulyEmailed text for team's consideration24 July 2017
111DNS SSR Subtopic Meeting 121 July 2017

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

Eric
21 July 2017Document shared via email.21 July 2017
110Plenary 1725 June 2017Write up DNS SSR topic areas and share with sub-team.Geoff
27 June 2017Proposed reorganization of study topics doc (GH) shared with team.26 June 2017
109Plenary 1726 June 2017Refine key action steps/work items and scope of the subtopic review.ICANN SSR subtopic team

31 July 2017
105SSR1 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
104Email24 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 Org
28 July 2017

7 August 2017

26 July 2017

103SSR1 Subtopic Meeting 120 July 2017Gather information regarding SSR1 implementation together in logical groupings and index within the Google doc. ICANN Org
28 July 2017Background materials section added to SSR1 Subteam wiki page including links to all briefing materiasl and SSR1 implementation final report26 July 2017
102211 August 2017Review Team members to email staff with Abu Dhabi full-day meeting preferences. Options are 27 October and 3 November.  SSR2-RT
3 August 2017A number of review team members responded off-list to email.3 August 2017
791725 June 2017Complete SSR1 implementation briefings.ICANN Org
1 August 2017All briefings complete and materials posted to the wiki.1 August 2017
96Staff/Leadership Call21 July 2017Review other meeting date/time options for F2F meeting at ICANN60 due to conflict for one of the co-chairsICANN Org
1 August 2017Available 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
90Email5 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
101Staff/Leadership Call28 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 Org
31 July 2017Email sent to Co-Chairs.31 July 2017
7617
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

911811 July 2017

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

SSR2-RT


25 July 2017No follow-up questions provided but SSR2 Review Team is free to provide follow-up questions at any time.25 July 2017
95Staff/Leadership call14 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 Org
21 July 2017Shared via email.21 July 2017
871726 June 2017Publish post-meeting blog on icann.orgICANN Org
19 July 2017Published here.19 July 2017
94Staff/Leadership call14 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 Org
20 July 2017Draft provided to co-chairs via email.19 July 2017
931811 July 2017Share link to the published ICANN Compliance Audit Report.ICANN Org
18 July 2017Shared via email:

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

13 July 2017
921811 July 2017

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

ICANN Org


25 July 2017Answers provided via email.13 July 2017
44

11

14 May 2017

Draft a Statement of Work for specialist technical writer.

James Gannon, Cathy Handley, Denise Michel



7 July 2017
781725 June 2017Populate the table of remaining SSR1 recommendations, with department, name of staff and Tuesday July Plenary meeting schedule availability. ICANN Org
7 July 2017Google document updated.7 July 2017
851726 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 Org
14 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
841726 June 2017Establish staff support requirements and availability to support SSR2-RT subgroups.ICANN Org, Co-Chairs
11 July 2017Available time slots to support subgroup calls circulated via email to Review Team11 July 2017
881726 June 2017

Identify Board members on “caucus” reviewing SSR2 work.

ICANN Board
14 July 2017Board Caucus details circulated via email.11 July 2017
821726 June 2017Update SSR2-RT action items wiki page with new request reporting tool.ICANN Org
7 July 2017New 'Tracking Tool' wiki page live.7 July 2017
771725 June 2017Provide final SSR1 implementation report.ICANN OrgN/A26 June 2017Link circulated to Review Team via email.26 June 2017
7617
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-Chairs
7 July 2017
  • Doodle poll completed.
6 July 2017
741620 June 2017

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

SSR2-RT
23 June 2017Subtopic rapporteurs recorded in Google doc.26 June 2017
7316

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-RT
26 June 2017Item addressed in Plenary 17. Replaced by action item #83.26 June 2017
7216

20 June 2017

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

ICANN Org, Co-ChairsN/A21 June 2017Doodle poll updated and circulated to Review Team via email.25 June 2017
7116

15 June 2017

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

Post attendance participation rates to wiki on a monthly basis.

ICANN OrgN/A23 June 2017Posted on Fact Sheet wiki page20 June 2017
6915

13 June 2017

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

ICANN OrgN/A16 June 2017Google document shared with Review Team via email.16 June 2017
67
12 June 2017

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

ICANN OrgN/ATBD
  • 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
66146 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 OrgN/A23 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
65146 June 2017Share thoughts and continue discussion on list regarding presentation of ICANN Security and SSR1 subtopic work plans. SSR2-RT
23 June 2017See email thread.23 June 2017
64146 June 2017Share thoughts on list on how to be more open to observer inputs. SSR2-RT
TBDThoughts shared via email and addressed during plenary 15. Conclusion: Keep interactions as-is for now.13 June 2017
631223 May 2017RT members to continue to volunteer for subtopics. More volunteers particularly needed for group 1: SSR.SSR2-RT
TBDVolunteers recorded in Subtopics document.26 June 2017
6212

23 May 2017

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

Boban Krsic, Žarko Kecić
26 May 2017Document shared via email5 June 2017
611223 May 2017Consolidate duplicative items, create subheadings for each topic groups within volunteer groups.SSR2-RT
23 June 2017Subtopics document updated.26 June 2017
601223 May 2017Record volunteers from plenary call in the subtopics document on wiki. ICANN OrgN/A23 May 2017Subtopics document updated.23 May 2017
581223 May 2017Share thoughts on list regarding outreach and engagement, and possible guidelines.SSR2-RT
23 June 2017Thoughts shared via email.26 June 2017
571223 May 2017Share thoughts on list regarding Johannesburg agenda topics.SSR2-RT
25 May 2017Thoughts shared via email.20 June 2017
561223 May 2017Distribute draft Johannesburg agenda to email list.Co-Chairs
30 May 2017Circulated via email.16 June 2017
5512

23 May 2017

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

Co-Chairs
30 May 2017Replaced by action item #64. 6 June 2017
541115 May 2017

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

ICANN OrgN/A31 May 2017Blog published on ICANN.org.26 May 2017
52

11

15 May 2017

Schedule remainder of briefings related to SSR1.

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

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 OrgN/ATBD

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

6 June 2017
50

11

15 May 2017

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

ICANN OrgN/A18 May 2017Google doc shared with Review Team.18 May 2017
491114 May 2017

Circulate link to ICANN technical portal

ICANN OrgN/ATBDLink circulated to Review Team.18 May 2017
48

11

14 May 2017

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

ICANN OrgN/A22 June 2017

Links circulated to Review Team:

Threat Mitigation

Classification of Threats 

14 June 2017
47

11

14 May 2017

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

ICANN OrgN/A16 May 2017Google document circulated via email to Review Team.14 May 2017
43

11

14 May 2017

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

ICANN Org
TBDEmail circulated to Review Team.26 June 2017

42

10

9 May 2017

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

ICANN OrgN/ATBDLinks posted to SSR2 background materials wiki page.11 May 2017
4192 May 2017

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

Co-Chairs
TBDShared via email.3 May 2017
409

2 May 2017

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

Kaveh Ranjbar
TBDSent to Board Chair via email.11 May 2017
399

2 May 2017

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

James Gannon
TBDShared via email.8 May 2017
389

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-Chairs
5 May 2017Johannesburg meeting confirmed to take place 25 & 26 June.10 May 2017
37825 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 OrgN/A28 Apr 2017Elise Gerich and Samantha Eisner joined 9 May plenary call and provided briefing.9 May 2017
36825 April 2017Provide draft agenda for Madrid face-to-face meeting to Review Team for input. Co-Chairs
TBDShared via email. 1 May 2017
35825 April 2017Circulate current summary of SSR1 review implementation to SSR2-RT list. ICANN Org
25 Apr 2017Email circulated to Review Team.25 April 2017
34825 April 2017Provide update to SSR2-RT after scheduled SO/AC Chair call to inform decision regarding potential meeting dates in Johannesburg at ICANN59. Co-Chairs
TBDReplaced by action item #38.4 May 2017
33  718 April 2017

Share link to Bylaws Article 18 and appropriate context.

ICANN OrgN/A20 Apr 2017Bylaw article and context distributed via email to RT.20 March 2017
32  7

18 April 2017

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

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

18 April 2017

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

ICANN OrgN/A18 Apr 2017Doodle poll circulated. 18 April 2017
29  7

18 April 2017

Circulate updated open action items list to RT.

ICANN OrgN/A20 Apr 2017Updated action items list circulated. 20 April 2017
28 13 April 2017

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

ICANN OrgN/A1 May 20172 May 2017
27611 April 2017

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

ICANN Org
13 April 2017Circulated via email.14 April 2017
26611 April 2017Review v2 draft Terms of Reference and share thoughts on email list.RT Members
TBDDocument shared. Review Team shared feedback via email.25 April 2017

25

611 April 2017

Propose timeline for finalizing scope.

Co-Chairs
TBDItem added to Madrid face-to-face meeting agenda.16 May 2017
24428 March 2017Review brainstorming capture slides from 15 March meeting  and share thoughts on email list.RT Members
TBDItem added to Plenary 11 Madrid face-to-face meeting agenda. 16 May 2017
23428 March 2017Schedule weekly RT calls per agreed rotation schedule.ICANN OrgN/A28 March 2017Call invites sent to Review Team.28 March
22428 March 2017Review draft Scope and Work Plan and make comments on the email list. RT Members
from 1 April 2017
  • Replaced by action item #26.
  • Thoughts shared via email.
16 May 2017
21322 March 2017Schedule 60-minute plenary call #4, 14:00 UTC Tuesday 28 March.ICANN OrgN/A22 March 2017Call invite circulated to Review Team.22 March 2017
20322 March 2017Co-Chairs to coordinate and formulate a proposal as to how to separate duties and present it to the RT.SSR2 Co-Chairs
TBDCo-Chairs agreed to informal separation of duties. 28 April 2017
19322 March 2017Prepare a plan for a rotation schedule for RT calls to the Co-Chairs for the next meeting.ICANN OrgN/A24 March 2017Excel worksheet planning document shared with Co-Chairs.24 March 2017
18

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 OrgN/A28 April 2017Recommendation 11 implementation completed: https://community.icann.org/display/SSR/Rec+%231114 April 2017
17

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 OrgN/A15 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
16322 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 Ranjbar
28 March 2017Kaveh Ranjbar provided update to the Board.28 March 2017
15322 March 2017Prepare straw-man versions of the Terms of Reference and Work plan for the RT to consider.ICANN OrgN/A31 March 20174 April 2017
14322 March 2017Generate a list of official observers and their relevant skill sets for RT consideration.ICANN OrgN/A28 March 2017
  • Email circulated to Review Team
  • SSR2 Observers wiki page updated with link to requested information.
27 March 2017
13215 March 2017Circulate slide deck from 3/15 SSR2 face to face meeting.ICANN OrgN/A16 March 2017Slide deck uploaded to SSR2 plenary 2 wiki page.16 March 2017
12215 March 2017Add OCTO KPIs, ICANN 2016 strategic plan and Emerging Technology Identifiers ICANN58 presentation to wiki background materials.ICANN OrgN/A16 March 2017Materials added to SSR2 background materials wiki page.16 March 2017
11215 March 2017Provide a list of existing definitions of terms: Security, Stability, Resiliency and Unique Identifiers. Reference where they are located.ICANN OrgN/A15 March 2017List of definitions compiled and provided to Review Team.16 March 2017
10215 March 2017Circulate names / contact information for SADAG vendors to SSR2 RT list.ICANN OrgN/A20 March 2017Vendor contact details provided via email.17 March 2017
9215 March 2017Circulate CDAR study report and contact information to SSR2 RT list.ICANN OrgN/A20 March 2017
  • Slide deck circulated and uploaded to SSR2 plenary 2 wiki page.
  • Contact details provided via email.
17 March 2017
8215 March 2017Provide SSR2 Fact Sheet sample and schedule.ICANN OrgN/A16 March 2017Sample Fact Sheet and schedule posted to wiki and circulated to Review Team via email.16 March 2017
7215 March 2017Schedule 60-minute plenary call, Wednesday 22 March, 19:00 UTC.ICANN OrgN/A15 March 2017Call invite circulated to Review Team.15 March 2017
6215 March 2017Develop and circulate time zone mapping to support scheduling of regular plenary calls discussion on next plenary call.ICANN OrgN/A21 March 2017Excel worksheet planning document shared with Co-Chairs. 24 March 2017
52

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 OrgN/ATBDDocument circulated to Review Team.18 April 2017
4

 1 

2 March 2017Draft document about what other review teams have used for chairs and co-chairs and send to the list.ICANN OrgN/An/aEmail circulated to Review Team.7 March 2017
312 March 2017Produce a summary of how other review teams have handled Observers and post to the list.ICANN OrgN/An/aEmail circulated to Review Team. 7 March 2017
212 March 2017Post staff structure responsibilities on wiki background page.ICANN OrgN/An/aICANN Organization Support Team page created on SSR2 wiki.31 March 2017
112 March 2017Provide terms of reference to the ICANN Board.SSR2N/ATBDEmail sent to Board Chair on behalf of Review Team.11 May 2017






  • No labels