Difference between revisions of "ICANN Reviews"

From ICANNWiki
Jump to navigation Jump to search
Line 58: Line 58:
  
 
An Independent Examiner is contracted to perform the fact finding, assessment, reporting, and recommendations of the review process. The examiner is selected through a competitive bid process.<ref name="orflow">[https://www.icann.org/en/system/files/files/org-reviews-process-flowchart-31aug17-en.pdf ICANN.org - Organizational Review Process Flowchart], August 31, 2017 (PDF)</ref> The review timeline for organization reviews can stretch between three to five years.<ref name="orgrvw" /> Like specific reviews, the process has multiple stages of public comment, as well as interaction and comment between the organization being reviewed and the Independent Examiner.<ref name="orflow" />
 
An Independent Examiner is contracted to perform the fact finding, assessment, reporting, and recommendations of the review process. The examiner is selected through a competitive bid process.<ref name="orflow">[https://www.icann.org/en/system/files/files/org-reviews-process-flowchart-31aug17-en.pdf ICANN.org - Organizational Review Process Flowchart], August 31, 2017 (PDF)</ref> The review timeline for organization reviews can stretch between three to five years.<ref name="orgrvw" /> Like specific reviews, the process has multiple stages of public comment, as well as interaction and comment between the organization being reviewed and the Independent Examiner.<ref name="orflow" />
 +
 +
===Board Review===
 +
During the development of the organizational review process, the [[ICANN Board]] determined that it would be good for the organization if it also participated in a review process under the organizational review model. The [[ICANN Board Review]] occurred between 2007 and 2010, but was not repeated.<ref>[https://www.icann.org/resources/reviews/org/board ICANN Board Review Dashboard]</ref> The [[Organizational Effectiveness Committee|Structural Improvements Committee]] (now known as the Organizational Effectiveness Committee) was tasked with presenting a set of actions and improvements based on the report of the board review working group.<ref>[https://www.icann.org/resources/board-material/resolutions-2010-06-25-en#1.4 Resolution of the Board], June 25, 2010</ref>
  
 
==Past Reviews==
 
==Past Reviews==

Revision as of 15:30, 5 June 2021

As a public service organization, ICANN's bylaws establish the scope and direction of the organization's mission, commitments, and core values.[1] The Bylaws specify review processes for ICANN and its stakeholder organizations.[2] The review processes are designed to ensure that ICANN is performing its mission in the best way possible.[3] Reviews aim to evaluate the health of the multistakeholder model, ICANN transparency and accountability, organizational effectiveness, and the security and stability of the DNS.[3]

ICANN Review Cycle

Specific and Organizational Reviews each follow process models that share a common set of themes and expectations. In each process, the review is planned by a team or work party. In the case of Organizational Reviews, there is then the intervening step of selecting and engaging an Independent Examiner. Then, the review is conducted. Organization Reviews move directly to implementation, while Specific Reviews submit findings and recommendations to the ICANN Board, which then acts on the recommendations. In each case, the implementation of recommendations is refined and improved, and the implemented improvements become standard procedure. The different action phases are laid out below:

Action Phase Specific Reviews Organizational Reviews
Phase 1 Assemble a Review Team Assemble a Working Party
Phase 2 Plan Review Plan Review
Phase 3 Conduct Review Engage Independent Examiner
Phase 4 Board Action Conduct Review
Phase 5 Plan Implementation Plan Implementation
Phase 6 Implement Improvements Implement Improvements
Phase 7 New Standard Operating Procedure New Standard Operating Procedure

Specific Reviews

ICANN's operations are subject to periodic Specific Reviews, enumerated in Article 4.6 of the bylaws:[4]

  • Accountability and Transparency (ATRT) - focused on ICANN operations[5]
  • Security, Stability, & Resiliency (SSR) - focused on the DNS[6]
  • Registration Directory Service (RDS/WHOIS) - focused on registration data and public access to registration information[7]
  • Competition, Consumer Trust, and Consumer Choice (CCT) - ushered in as part of the New gTLD Program, this review is focused on the domain marketplace and the experience of registrants and other consumers[8]

Timing & Process

ATRT, SSR, and RDS/WHOIS reviews must take place periodically, and no more than five years after the last review team was convened[9] A CCT review is initiated one year after the launch of a New gTLD application round.[9]

Review teams typically include members, observers, and/or liaisons from stakeholder groups, supporting organizations and advisory committees.[9] The review process timeline runs between three to nearly five years, and involves multiple opportunities for participation, public comment, and deliberation among stakeholders.[10]

Organizational Reviews

Each supporting organization and advisory committee, as well as the Nominating Committee is periodically reviewed pursuant to Article 4.4 of the Bylaws.[11] The GAC is exempted from Article 4.4, although it is charged to implement and deploy its own review processes.[12]

Timing & Process

The bylaws state that organizational reviews should take place no more than five years from the submission of the final report of the last review to the ICANN Board. However, that requirement is flexible, and "based on feasibility as determined by the Board."[12]

An Independent Examiner is contracted to perform the fact finding, assessment, reporting, and recommendations of the review process. The examiner is selected through a competitive bid process.[13] The review timeline for organization reviews can stretch between three to five years.[11] Like specific reviews, the process has multiple stages of public comment, as well as interaction and comment between the organization being reviewed and the Independent Examiner.[13]

Board Review

During the development of the organizational review process, the ICANN Board determined that it would be good for the organization if it also participated in a review process under the organizational review model. The ICANN Board Review occurred between 2007 and 2010, but was not repeated.[14] The Structural Improvements Committee (now known as the Organizational Effectiveness Committee) was tasked with presenting a set of actions and improvements based on the report of the board review working group.[15]

Past Reviews

Specific Reviews

Review Type & Number Status Date Initiated Date Completed ICANNWiki Page Documents
CCT #1 Implementation Phase October 1, 2015 CCT1 CCT1 Final Report - PDF
ATRT #1 Complete January 11, 2010 January 29, 2013 ATRT1 ATRT1 Final Report - PDF
ATRT1 Implementation Report - PDF
ATRT #2 Complete October 5, 2012 December 31, 2015 ATRT2 ATRT1 Final Report - PDF
ATRT2 Implementation Report - PDF
ATRT #3 Implementation Phase January 31, 2017 ATRT3 ATRT3 Final Report
RDS/WHOIS #1 Complete June 1, 2010 December 31, 2015 RDS1 RDS1 Final Report (PDF)
RDS1 Implementation Report (PDF)
RDS/WHOIS #2 Implementation Phase October 28, 2016 RDS2 RDS2 Final Report (PDF)
SSR #1 Complete June 1, 2010 December 31, 2015 SSR1 SSR1 Final Report (PDF)
SSR1 Implementation Report (PDF)
SSR #2 Awaiting Board Action June 30, 2016 SSR2 SSR2 Final Report (PDF)

Organizational Reviews

Review Type & Number Status Date Initiated Date Completed ICANNWiki Page Documents
ALAC #1 Complete January 23, 2008 June 14, 2012 At-Large1 At-Large1 Final Report (PDF)
At-Large1 Implementation Project Final Report (PDF)
ALAC #2 Complete January 6, 2016 December 18, 2020 At-Large2 At-Large2 Final Report (PDF)
At-Large2 Implementation Status Report (PDF)
ASO #1 Complete December 12, 2010 November 17, 2014 ASO1 ASO1 Final Report (PDF)
Letter Re: Finalization of ASO1 Implementation (PDF)
ASO #2 Complete November 18, 2016 August 31, 2017 ASO2 ASO2 Final Report (PDF)
ccNSO #1 Complete June 26, 2009 September 11, 2013 ccNSO1 ccNSO2 Final Report (PDF)
ccNSO2 Implementation Status Report (PDF)
ccNSO #2 Implementation Phase April 6, 2017 ccNSO2 ccNSO2 Final Report (PDF)
GNSO #1 Complete March 30, 2007 November 3, 2008 GNSO1 GNSO1 Final Report (PDF)
GNSO #2 Complete January 1, 2014 January 27, 2019 GNSO2 GNSO2 Final Report (PDF)
GNSO2 Implementation Final Report (PDF)
NomCom #1 Complete March 30, 2007 March 1, 2012 NomCom1 NomCom1 Final Report of Independent Examiner (PDF)
NomCom1 Finalization WG Final Report (PDF)
NomCom1 Implementation Final Report (PDF)
NomCom #2 Complete September 13, 2016 December 21, 2020 NomCom2 NomCom2 Final Report (PDF)
NomCom2 Implementation Status Report (PDF)
RSSAC #1 Complete June 26, 2008 December 1, 2010 RSSAC1 RSSAC1 Final Report (PDF)
RSSAC1 Implementation Report (PDF)
RSSAC #2 Complete April 19, 2017 December 9, 2020 RSSAC2 RSSAC2 Final Report
RSSAC2 Implementation Progress Report (PDF)
SSAC #1 Complete June 26, 2008 June 25, 2010 SSAC1 SSAC1 Final Report (PDF)
SSAC #2 Complete May 18, 2017 March 25, 2021 SSAC2 SSAC2 Final Report (PDF)
SSAC2 Final Implementation Report (PDF)

Efforts to Improve & Streamline the Review Process

Both the ICANN Board and ICANN staff have recently been engaged in efforts to improve the review process for both specific and organizational reviews. In 2019, the Board issued new Operating Standards for Specific Reviews[16] [17] In addition, ICANN staff drafted a process proposal for streamlining organizational reviews in April 2019.[18] Public comments on the proposal addressed a much broader range of challenges and difficulties than the proposed streamlining measures.[19]

The Board and staff of ICANN continue to address the issues raised during public comment processes, public meetings, and other communications related to the efficiency and timing of reviews.[20] In November 2019, Lars Hoffman presented at ICANN 66 on the topic of improving the effectiveness of review recommendations and their implementation.[21]

References