Difference between revisions of "2002 Evolution and Reform Process"

From ICANNWiki
Jump to navigation Jump to search
Line 34: Line 34:
  
 
==Committee Work and Reports==
 
==Committee Work and Reports==
The Evolution and Reform Committee (ERC) began work in the spring of 2002.<ref>[https://archive.icann.org/en/committees/evol-reform/ ICANN.org Archive - Evolution & Reform Committee Workspace]</ref> The ERC presented an interim report on progress to the Board in April 2002, stating that it was making strides in gathering public opinion across a variety of fora, including personal communications to committee members.<ref name="apint">[https://archive.icann.org/en/committees/evol-reform/report-29apr02.htm ECR Workspace - Interim Report], April 29, 2002.</ref> The report provided an "idiosyncratic" overview of the public input received around many of the features and talking points of Stuart Lynn's proposals for reform. The Committee chair, [[Alejandro Pisanty]], emphasized that none of the community input and discussions could be characterized as conclusive.<ref name="apint" />
+
The Evolution and Reform Committee (ERC) began work in the spring of 2002.<ref name="workspace">[https://archive.icann.org/en/committees/evol-reform/ ICANN.org Archive - Evolution & Reform Committee Workspace]</ref> The ERC presented an interim report on progress to the Board in April 2002, stating that it was making strides in gathering public opinion across a variety of fora, including personal communications to committee members.<ref name="apint">[https://archive.icann.org/en/committees/evol-reform/report-29apr02.htm ERC Workspace - Interim Report], April 29, 2002.</ref> The report provided an "idiosyncratic" overview of the public input received around many of the features and talking points of Stuart Lynn's proposals for reform. The Committee chair, [[Alejandro Pisanty]], emphasized that none of the community input and discussions could be characterized as conclusive.<ref name="apint" />
 +
===Working Papers===
 +
In May 2002, the ERC released a series of working papers on ICANN's mission & values, its policy development process, and its structure & the nominating committee concept.<ref name="workspace" /> The papers were intended to capture the current state of ICANN and its written and unwritten rules, and to spark community contributions and discussion on each of the issue areas being addressed by the ERC.<ref name="workspace" />
 +
 
 +
====ICANN Mission====
 +
At the time of the ERC's work, neither ICANN's mission nor the organization's values were described in the bylaws.<ref name="feb02bl">[https://www.icann.org/resources/unthemed-pages/bylaws-2002-02-12-en ICANN Bylaws], as amended February 12, 2002</ref> The ERC created a draft mission statement and core values based on a wide variety of documents and agreements, most importantly the [[White Paper]], the 1998 Memorandum of Understanding with the Department of Commerce, the [[IANA Contract]], and the Memorandum of Understanding between ICANN and the IETF.<ref name="missionwp">[https://archive.icann.org/en/committees/evol-reform/working-paper-mission-06may02.htm Working Paper on ICANN's Mission and Core Values], May 6, 2002</ref>
  
 
==References==
 
==References==
 
{{reflist}}
 
{{reflist}}

Revision as of 21:58, 11 June 2021

The 2002 Evolution and Reform Process was a board-led reform process that resulted in the adoption of substantial reform in the bylaws, structure, and operation of ICANN.

Background

ICANN was incorporated in 1998, and entered into a Memorandum of Understanding with the Department of Commerce in November of that year to begin a joint project to manage the domain name system in a way that promoted the principles of stability, competition, private, bottom-up coordination, and representation of all views among the global and diverse community of Internet users and functions.[1]

Initial Structure and Growth

In March 1999, ICANN amended its bylaws to establish a new supporting organization, the Domain Names Supporting Organization (DNSO).[2] As amended, the bylaws contemplated the following structure of ICANN and its SOs and ACs:

  • Three Supporting Organizations: Address Supporting Organization (ASO); Domain Name Supporting Organization (DNSO); and Protocol Supporting Organization (PSO).
  • Four Advisory Committees: Governmental Advisory Committee (GAC); Root Server System Advisory Committee (RSSAC); an Advisory Committee on Membership (until such time as the board established rules for At-Large director seats on the board); and an Advisory Committee on Independent Review (until such time as the board adopted procedures for independent review).

In the March 1999 amended bylaws, only the DNSO had defined procedures established for its operation. The ASO and the PSO sections of the bylaws were reserved.[2] ICANN and the PSO signed a Memorandum of Understanding in July 1999,[3] amended bylaws of August 26, 1999, included procedural and operational guidelines for the PSO.[4] In October 1999, the three existing regional internet registries - RIPE NCC, APNIC, and ARIN - entered into a Memorandum of Understanding with ICANN as well, resulting in the creation of the ASO.[5] The addition of the ASO to the bylaws occurred at the end of October.[6]

Perceived Need for Reform

In November 2001, the ICANN Board created a Committee on Restructuring to investigate possible reforms to ICANN's structure and operations.[7] The resolution forming the committee also instructed the ICANN President (at the time, M. Stuart Lynn) "to take such steps as he deems appropriate to bring to the Board for its review and approval recommendations for how best to reaffirm and clarify the nature and scope of ICANN's limited mission."[7] The board cited "ongoing considerable discussion in the ICANN community, including a number of the DNSO constituencies, about the desirability of possible changes in the structure of ICANN, including consideration of possible new Supporting Organizations and changes in the composition of the ICANN Board;" as well as the fact that "ongoing evaluation of the ALSC Final Report also implicates issues of ICANN structure and Board composition" as factors in taking these actions.[7]

In February 2002, Lynn published his report and proposal for comprehensive reforms of the ICANN structure, board, and operations.[8] Prior to publication, the reform report and proposal was presented to the ICANN Board during its retreat in Washington D.C.[8] The report makes the case for "deep, meaningful, structural reform, based on a clearheaded understanding of the successes and failures of the last three years."[8] Lynn's proposals included:

  • Reformation of the ICANN Board.
  • Reform of ICANN's Policy Development Structure and Process:
    • Three Policy Councils - Address & Numbering, Generic TLDs, and Geographic TLDs;
    • Two Advisory Committees - Technical and Governmental;
    • Two additional Standing Committees - Security Committee, and Root Server System Operations Committee; and
    • Participation in Councils by self-organized forums, including possibly an At-Large organization for internet users.
  • Transparency and Accountability reforms: creation of the Ombudsman's office, and a "Manager of Public Participation" role.
  • Funding reforms - dramatically increase funding from governmental and non-governmental sources, including contributions for core functions and fees for services.

In response to Lynn's report, the board made a number of resolutions at its meeting at ICANN 12 in Accra, Ghana:

  • the Committee on Restructuring was renamed the Committee on Evolution and Reform;
  • the committee was tasked to provide a report to the board outlining a "framework for the structure and functioning of a reformed ICANN, and a timetable for implementing that framework" in time for the ICANN 13 meeting in Bucharest;
  • the committee was to ensure that they addressed and recommended resolutions for a broad range of issues, including both structural and operational considerations for the proposed reformed structure, transition of existing structural components, and ensuring adherence to ICANN's core mission and objectives;
  • the board strongly encouraged public comment on reform proposals as well as all activities and recommendations of the committee; and
  • the committee was instructed to work with Lynn and ICANN staff to develop its recommendations for reform.[9]

These actions kicked off what would come to be known as the Evolution and Reform Process. The board expressed a desire to engage in deliberations on a set of proposals for reform at ICANN 13 in Bucharest, and that any materials to be presented at that meeting should be published for public comment no later than May 31, 2002.[9]

Committee Work and Reports

The Evolution and Reform Committee (ERC) began work in the spring of 2002.[10] The ERC presented an interim report on progress to the Board in April 2002, stating that it was making strides in gathering public opinion across a variety of fora, including personal communications to committee members.[11] The report provided an "idiosyncratic" overview of the public input received around many of the features and talking points of Stuart Lynn's proposals for reform. The Committee chair, Alejandro Pisanty, emphasized that none of the community input and discussions could be characterized as conclusive.[11]

Working Papers

In May 2002, the ERC released a series of working papers on ICANN's mission & values, its policy development process, and its structure & the nominating committee concept.[10] The papers were intended to capture the current state of ICANN and its written and unwritten rules, and to spark community contributions and discussion on each of the issue areas being addressed by the ERC.[10]

ICANN Mission

At the time of the ERC's work, neither ICANN's mission nor the organization's values were described in the bylaws.[12] The ERC created a draft mission statement and core values based on a wide variety of documents and agreements, most importantly the White Paper, the 1998 Memorandum of Understanding with the Department of Commerce, the IANA Contract, and the Memorandum of Understanding between ICANN and the IETF.[13]

References