3,197
edits
Changes
Jump to navigation
Jump to search
Line 17:
Line 17: − + − + + + + + + + + + + + + + + + +
First Security, Stability, and Resiliency Review (view source)
Revision as of 22:15, 24 May 2021
, 3 years agono edit summary
Applications for volunteers began in June 2010.<ref name="dashboard" /> in addition, the review planning team solicited applications from independent experts to serve on the review team.<ref>[https://www.icann.org/resources/pages/call-for-experts-dns-2012-02-25-en ICANN.org - Call for Experts, SSR1], July 26, 2010</ref> The review team was appointed in September of 2010.<ref name="dashboard" />
Applications for volunteers began in June 2010.<ref name="dashboard" /> in addition, the review planning team solicited applications from independent experts to serve on the review team.<ref>[https://www.icann.org/resources/pages/call-for-experts-dns-2012-02-25-en ICANN.org - Call for Experts, SSR1], July 26, 2010</ref> The review team was appointed in September of 2010.<ref name="dashboard" />
The team held its first in-person meetings at [[ICANN 39]] in Colombia and used those meetings to draft its Terms of Reference (ToR).<ref>[https://www.icann.org/en/announcements/details/call-for-public-comments-the-security-stability-and-resiliency-of-the-dns-review-team-21-2-2011-en ICANN.org - Call for Public Comment - SSR1 ToR]</ref> The team held a day-long public session at [[ICANN 40]] to refine the Terms of Reference and receive comments and suggestions from the community.<ref>[https://archive.icann.org/en/meetings/siliconvalley2011/node/22237.html ICANN 40 Meeting Archive - Schedule]</ref> The final version of the Terms of Reference was submitted to the board in June 2011.<ref name="dashboard" /> The ToR highlighted three central themes for investigation and review:
The team held its first in-person meetings at [[ICANN 39]] in Colombia and used those meetings to draft its Terms of Reference (ToR).<ref>[https://www.icann.org/en/announcements/details/call-for-public-comments-the-security-stability-and-resiliency-of-the-dns-review-team-21-2-2011-en ICANN.org - Call for Public Comment - SSR1 ToR]</ref> The team held a day-long public session at [[ICANN 40]] to refine the Terms of Reference and receive comments and suggestions from the community.<ref>[https://archive.icann.org/en/meetings/siliconvalley2011/node/22237.html ICANN 40 Meeting Archive - Schedule]</ref> The final version of the Terms of Reference was submitted to the board in June 2011.<ref name="dashboard" /> The ToR highlighted three central issue areas for investigation and review:
#
#The scope of ICANN's SSR responsibilities;
#Effectiveness and implementation of ICANN's SSR plan; and
#Risk landscape and contingency plan.<ref name="tor">[https://community.icann.org/display/SSR/Terms+of+Reference+-+23+June+2011]</ref>
Within each of the issue areas, multiple topics were identified for the review team to examine as part of its fact finding.<ref>[https://community.icann.org/display/SSR/SSR+Review+Fieldwork+Planning SSR1 Workspace - Fieldwork Planning]</ref> The ToR formed the basis for dividing into three subteams, based around the topic areas.<ref>[https://community.icann.org/display/SSR/SSR+Review+Fieldwork+Planning SSR1 Workspace - Fieldwork Planning</ref>
==Findings and Draft Report==
The review team published its draft report for public comment in March 2012.<ref name="dashboard" /> The draft report listed twenty-eight recommendations based on the team's findings.<ref>[https://www.icann.org/en/system/files/files/draft-report-15mar12-en.pdf SSR1 Draft Report], March 15, 2012</ref>. A common theme was improving clarity of mission and messaging around each of the main topic areas.
ICANN staff also prepared and published a mission statement document for public comment in response to recommendations #1 and #3.<ref>[https://www.icann.org/en/announcements/details/draft-statement-of-icanns-role-and-remit-in-security-stability-and-resiliency-of-the-internets-unique-identifier-systems-17-5-2012-en ICANN.org - Draft statement of ICANN's role and remit], May 17, 2012</ref> The statement was intended to refine and spell out ICANN's obligations and commitments to the stability, security, and resilience of the Internet's unique identifier systems. Public comment was substantial and largely positive toward the effort to clarify and synthesize ICANN's mission.<ref>[https://www.icann.org/en/system/files/files/report-comments-draft-ssr-role-remit-04oct12-en.pdf ICANN.org - Staff Report on Public Comment Proceeding], October 4, 2012</ref>
==Final Report and Implementation==
The final report was submitted to the ICANN board and published for public comment in June 2012. Public comments on the final report were minimal: only [[ALAC]], [[RySG]], and [[Andrew Sullivan]] on behalf of [[Dynamic Network Services]] posted comments. These were largely congratulatory, with some issues raised regarding the clarity and purpose of some specific recommendations, and the need for close and nuanced reading of the report itself.<ref>[https://www.icann.org/resources/pages/ssr-rt-final-report-2012-06-21-en ICANN.org Listserv Archive - SSR1 Final Report]</ref>
The board acknowledged receipt of the report in September 2012, and instructed staff to present feasibility assessments and propose an implementation plan on the recommendations.<ref>[https://www.icann.org/resources/board-material/minutes-2012-09-13-en#1.b Resolution of the Board], September 13, 2012</ref> In October 2012, the board took action on the recommendations, noting that ICANN staff had proposed implementation of all of the recommendations, finding them all feasible. The board approved the report and the implementation of all of its recommendations.<ref>[https://www.icann.org/resources/board-material/resolutions-2012-10-18-en#1.e Resolution of the Board], October 18, 2012</ref>
The final implementation update report was published in June 2015.<ref>[https://www.icann.org/en/system/files/files/ssr-review-implementation-30jun15-en.pdf ICANN.org - SSR1 Implementation Update], June 30, 2015</ref> As of December 2015, the SSR1 implementation has been deemed complete.<ref name="dashboard" />
==References==
==References==
{{reflist}}
{{reflist}}
__NOTOC__
__NOTOC__