First Competition, Consumer Trust, and Consumer Choice Review

Revision as of 23:37, 9 July 2021 by JP (talk | contribs)

The First Competition, Consumer Trust, and Consumer Choice Review was initiated in October 2015, after the launch of the New gTLD Program, pursuant to amendments to the ICANN Bylaws.[1] The CCT Review was one of the new processes designed to ensure the transparency and fairness of the New gTLD Program.[2]

Background edit

Origin and Purpose of Specific Reviews edit

The Affirmation of Commitments, an agreement between ICANN and the United States Department of Commerce, establishes ICANN's obligations to perform its duties with specific commitments in mind. All of the commitments bear on public and consumer trust of the organization. ICANN is to perform its functions in a manner that:

  • ensures accountability and transparency of decision-making;
  • preserves the security, stability, and resiliency of the DNS;
  • promotes competition, consumer trust, and consumer choice; and
  • enables access to registration data.

ICANN is also charged to periodically review and assess its performance through the lens of each of the above commitments.[3]

ICANN's board enshrined these commitments (and the associated reviews) in its Bylaws in Article 1 (Mission, Commitments, and Core Values)[4] and in Article 4 (Accountability and Review).[5] Article 4.6 deals with "Specific Reviews," each of which are tied to one of the commitments in the Affirmation of Commitments.[6]

The Organizational Effectiveness Committee of the board oversees the conduct of specific reviews.[7]

CCT Review Team edit

The CCT Review Team was comprised of members from a variety of geographical regions and areas of expertise. The group consisted of six members endorsed by the GNSO, two members endorsed by the ALAC, two from the ccNSO, two from the GAC, one representing ICANN's CEO, and four independent experts.

Members Representing ICANN SOs or ACs edit

Members Serving as Independent Experts edit

Interrelationship with SUBPRO edit

The recommendations contained in the review team's Final Report often address issues or programs that are also the subject of the Policy Development Process for New gTLD Subsequent Procedures (SUBPRO). As a result, the ICANN Board passed many of the recommendations to the SUBPRO Working Group for deliberation and action within that policy development process.[8]

Final Report edit

The review team issued its Final Report and Recommendations on October 10, 2018.[9] The Final Report contained 37 recommendations for the ICANN Board to consider.[10] Twenty-four of the recommendations were either identified as prerequisites to a new round of gTLD applications, or as "high priority" recommendations that "must be implemented with 18 months of the issuance of the Final Report."[10]

Public Comment edit

The Final Report received a total of nine public comments during the public comment period. Comments largely came from ICANN bodies and stakeholder constituencies: comments were received from the ALAC and the GAC, as well as from the Business Constituency, IP Constituency, gTLD Registries Stakeholders Group, and Noncommercial Stakeholders Group. Comments were also received from the International Trademark Association, the National Association of Boards of Pharmacy, and John Poole.[11]

ICANN Staff found substantial differences of opinion in the comments regarding the scope, commitment of resources, and relative importance of the recommendations. There were divergent opinions on many of the specific recommendations, and few instances of full consensus.[11]

Board Reception and March 2019 Recommendation Scorecard edit

The ICANN Board provided extensive detail on its decision-making process in its resolution adopting the Final Report.[12] The Board accepted six of the report's recommendations for implementation, delegated or directed some recommendations to the relevant supporting organization or working group, and placed seventeen of the recommendations into "pending" status, pending further research and price estimation regarding those recommendations.[12] The Board summarized its actions in a recommendation scorecard attached to the resolution.[8]

The six recommendations that were accepted tended toward broad outlines of policy guidance, rather than specific policies:

  • Recommendation 1: Formalize and promote ongoing data collection.
  • Recommendation 17: ICANN should collect data about and publicize the chain of parties responsible for gTLD domain name registrations.
  • Recommendation 21: Include more detailed information on the subject matter of complaints in ICANN publicly available compliance reports.
  • Recommendation 22: Initiate engagement with relevant stakeholders to determine what best practices are being implemented to offer reasonable and appropriate security measures commensurate with the offering of services that involve the gathering of sensitive health and financial information.
  • Recommendation 30: Expand and improve outreach into the Global South.
  • Recommendation 31: The ICANN organization to coordinate the pro bono assistance program.*[8]

*Contingent upon the SUBPRO working group deciding to maintain the pro bono assistance program in subsequent rounds

In explaining its decision making rationales, the Board identified three common themes in the recommendations:

One theme is the need for different and additional data that is highlighted across many of the 35 recommendations. The Board appreciates and understands the concerns raised by the CCT-RT about the need for data to inform future CCT-RT's work. The Board finds it important that ICANN continues to be appropriately involved with data collection to inform the community and its work...

The second theme relates to recommendations directed to the Board that are not within the Board's power to do, and recommendations that the Board actually cannot direct the outcome of, such as recommendations to policy development working groups, or relating to contractual terms that are subjected to contractual negotiations...

Another theme is that there are recommendations that require significant resources to implement. The Board's fiduciary obligations mean that it cannot commit the organization to start work on these recommendations until it understands the full cost and resource impact.[12]

Of the themes identified, the Board seemed to find the resource allocation issue to be paramount. Noting that other specific reviews as well as other substantial policy deliberations were ongoing, the Board stated that it was obliged to balance the needs of the stakeholder community as well as the core mission of stability and security of the DNS.[12]

October 2020 Scorecard on Pending Recommendations edit

In October 2020, the Board took action on eleven of the seventeen pending recommendations.[13] The Board issued another scorecard to identify and discuss the approved recommendations.[14] The majority of the approved recommendations involved data collection or analysis. In many cases, the Board acknowledged that data collection suggested by the recommendations was already occurring. In other cases, the Board instructed ICANN staff to initiate studies or analysis related to the recommendations.[14] The Board instructed ICANN staff to continue work regarding the six remaining pending recommendations.</ref name="octbres" />

Implementation edit

March 2019 Accepted Recommendations edit

The Review Team published its implementation plan for the six recommendations that were originally approved in September 2019 for public comment.[15] [16] Public comments on the proposed plan tended toward consensus that the recommendations were valid, but in some cases, opinions differed as to the usefulness of the proposed implementation of those recommendations.[17]

The Board approved the implementation plan in January 2020.[18] Updates on the implementation of those recommendations were provided by Maarten Botterman on the ICANN Blog in August 2020[19]

October 2020 Accepted Recommendations edit

As of May 2021, there is not a proposed implementation plan for the recommendations approved in the October 2020 board resolution.[20]

References edit