icannwiki

First GNSO Organizational Review

Revision as of 18:51, 11 June 2021 by JP (talk | contribs) (→Board Action)

The First GNSO Organizational Review (GNSO1) was initiated in 2008, with implementation of improvements continuing throughout 2012.[1]

Background edit

Article 4.4 of the ICANN Bylaws requires periodic review of all supporting organizations and advisory committees, as well as the Nominating Committee.[2] The bylaws state three objectives for the review:

  1. to determine whether that organization, council or committee has a continuing purpose in the ICANN structure;
  2. if so, whether any change in structure or operations is desirable to improve its effectiveness; and
  3. whether that organization, council or committee is accountable to its constituencies, stakeholder groups, organizations and other stakeholders.[2]

Organizational reviews are conducted by independent examiners, selected through a competitive bidding process.[2] The independent examiner works in consultation with a working group assembled by the board, who will act as implementation shepherds once the final report of the independent examiner is submitted.[3] The review parameters are set by the ICANN Board, and those parameters as well as other avenues of inquiry are typically included in the request for proposals (RFP) for independent examiners.[2][3] Reviews can take anywhere from three to five years to complete. The full review process includes seven phases, including the implementation of recommendations from the review.[3] Reviews must be conducted at least every five years, measuring from the date that the final report of the previous review was accepted by the ICANN Board.[3] The Generic Names Supporting Organization (GNSO) is one of the supporting organizations subject to Article 4.4 review.

It is notable that the GNSO1 review began with a review of reviews: the GNSO had previously been reviewed by the London School of Economics Public Policy Group in 2006, and by Patrick Sharry in 2004.[1] These prior reviews were incorporated into the work process of the GNSO1 Review working group.[1]

Initiation edit

The board assembled a GNSO Review Working Group of the Board Governance Committee, and approved its charter, in March 2007[4] The working group was charged to answer the traditional Article 4.4 (as amended at the time) questions: does the GNSO have a continuing purpose within the ICANN structure; and if so, what can be done to improve its effectiveness? The charter document goes further, tasking the working group to develop a "comprehensive proposal" to improve the effectiveness of the GNSO.[5]

Review of Prior Assessments edit

The working group focused on three previous reviews in its information-gathering process: the Patrick Sharry review of 2004; the GNSO Council's own self-assessment, performed as part of the preliminary work to commission Sharry's report; and the review prepared by the London School of Economics Public Policy Group in 2006.[5]

GNSO Council Self-Assessment edit

The GNSO Council, in preparing the Terms of Reference for its 2004 review, conducted a self-review process. The self-review described a number of policy development successes, including updates to the transfer policy, WHOIS, and deletion policy.[6] The GNSO made three categories of recommendations:

  1. Recommendations re: the ICANN Bylaws: maintain GNSO Council compostion of 3 representatives from each constituency; amend the policy development process bylaws to state that PDP timelines are flexible, and may be set and revised by the GNSO Council to reflect the work being considered and status updates from the working group.
  2. Recommendations re: staff support: multiple requests for staff support around the policy development process, task forces, and work of the GNSO Council; make legal staff available to the GNSO Council, task forces, and subcommittees, and in particular for review of policy recommendations and other policy statement for compliance with bylaws and contractual obligations; and create monitoring, compliance, and complaint policies related to gTLDs.
  3. Actions required of the GNSO Council: Ensure that legal advice from ICANN staff is in writing and allow registrars or registries to submit the opinion of their counsel; ensure that policies are ready to be implemented upon approval; establish key metrics for measuring the success of a given party; encourage community-wide participation in the policy development process.[6]

2004 Review by Patrick Sharry edit

Sharry, a strategic planning and change management consultant,[7] reviewed the GNSO Council specifically, without reference to the self-assessment described above, using interviews with GNSO Council members and others, as well as a review of policy and process documentation prepared by the GNSO for that purpose.[8] The report reached many of the same conclusions as the GNSO's self-assessment. Sharry found, in particular, that ICANN staff support of GNSO activities fell "well short of the standards outlined in the bylaws."[8] The review also found substantial gaps between the adoption of policy proposals and the implementation of those policies, with minimal attention devoted to compliance or tracking of the success of the implementation.[8] Sharry provided recommendations for improving the GNSO's core functions, but was also complementary of both the Council's commitment and dedication, as well as its leadership.[8]

As part of its background documentation for the broader community, the improvements implementation team summarized the similarities between the GNSO's self assessment and Sharry's report:

These reviews shared a common approach in certain respects: (i) allowing for more flexibility in the PDP process; (ii) ensuring strong Staff support for policy development; and (iii) developing better mechanisms for public participation and discussion.[5]

2006 Review by the London School of Economics edit

In 2006, ICANN commissioned the Public Policy Group of the London School of Economics (LSE) to review the GNSO and its operations.[9] The questions were again drawn from Article 4 of the bylaws (as they existed at the time): did the GNSO still serve a purpose, and if so, what improvements could be made to its process and operations?[9]

The LSE report shared some common findings with Sharry's review and the GNSO Council self-assessment. Once again, the established timelines for policy development processes were deemed to be unreasonable given the nature and complexity of the work involved. The LSE echoed Sharry's report regarding the lack of impact assessment or formal metrics for judging the success of implemented policies. Although the LSE found that ICANN staff support of the GNSO had grown in meaningful ways, further capacity-building and tool training could be accomplished to further strengthen trust, clarity, and efficiency in interactions between staff and GNSO teams.[9]

In focusing on the entirety of the supporting organization, rather than the GNSO Council only, the LSE report diverged from the 2004 assessments in its attention to the overall structure, composition, and representativeness of the GNSO and its constituencies. In the executive summary of the report, the team described its concerns about the current constituency model:

The current pattern of Constituencies is relatively complex and no longer seems well-adapted to the needs of all stakeholders in the rapidly changing Internet community. Although the Constituency structure does provide a potential home for almost all types of interest, there are signs that the current structures tend to reflect a snapshot of interests that were present at the beginning of this decade and lack internal flexibility to incorporate new types of stakeholders from commercial and civil society. There is consequently much scope to grow and diversify membership of the GNSO, and to adapt structures in such a way that they are flexible and agile enough to respond to new policy development issues.[9]

The team also noted "worrying signs of dominance of some constituencies" by a small group of people, and low participation rates in policy development work by members of constituencies.[9]

The report offered a number of recommendations that focused on structural flexibility, representation, and growing the GNSO's ability to shift with the ever-shifting environment of the Internet. The report identified four key principles that should guide recommendations for change: increasing visibility and transparency of operations; increasing the representativeness of the GNSO Council and its Constituencies; increasing structural adaptability; and improving mechanisms for reaching "genuinely consensus opinions."[9]

Through this lens, the LSE team found cause to recommend substantial reforms. Among the report's twenty-four recommendations, several significant changes were proposed:

  • Reduce the number of constituencies to three: registration interests, business users, and civil society.
  • Establish a "direct membership" in ICANN for firms, other organizations, and individuals. Guide newly-joined members into relevant constituencies, and provide staff support at the constituency level to sustain their activities and outreach work.
  • Create "radically improved ICANN and GNSO websites" that can effectively represent the GNSO to the Internet community.
  • Abolish weighted voting for registration interests. Give registration interests and business users an effective veto over non-consensus change. Raise the threshold for "consensus policy" from 66 to 75 per cent agreement.
  • Reduce teleconference and remote meetings and shift to increased face-to-face meetings of the Council. Reimburse the travel expenses of councilors to enable this.
  • Expand the use of task forces with independent outside expertise, to broaden the involvement of interests from outside ICANN and to speed up policy development.
  • Leverage staff expertise to speed up policy development and help focus the Council's attention on key issues and decisions.
  • Establish term limits for GNSO Councilors. Create stronger protections against the non-disclosure of interests.[9]

The LSE Report was published for public comment in autumn 2006, and received a total of six comments.[10] The comments were largely complementary of the LSE's efforts but varied widely in their support or non-support of particular recommendations.[10]

Working Group Drafts and Public Comment edit

The Working Group summarized its work synthesizing the three reviews and listed an initial set of recommendations in a "Draft Working Document," released in advance of ICANN 29 in San Juan.[11] The working document presented findings and (in the case of the LSE Review) summaries of public comments received, and produced a series of preliminary recommendations on the issues of constituency structure, the GNCO Council, the GNSO's policy development process, the adoption of a working group model, and staff/cross-community outreach and interaction. It also listed questions for discussion at ICANN 29 regarding each of those issues.[11]

The working document was the subject of a public forum at ICANN 29,[12] and also received written public comments.[10] Participants at the public forum expressed support for "certain, but not all" of the recommendations contained in the working document. The working group's summary of forum comments identified three points of agreement:

  1. Both constituency operations and restructuring can benefit from improvements, but changes in operations should precede changes in the structure.
  2. Formalizing a working group model as the focal point for policy development could enhance the policy development process by making it more inclusive and representative and – ultimately – more effective and efficient.
  3. The GNSO Council should move away from being a legislative body focused on voting and become a more strategic entity with strengthened management and oversight of the policy development process.[13]

The working group issued a draft final report in October 2007,[14] and held a workshop on the draft report at ICANN 30 in Los Angeles.[15] The draft report refined recommendations related to the broad topics of adopting a working group model, reforming the policy development process, improvements in process for the GNSO Council, and altering the structure of constituencies and participation within constituencies. Staff and cross-community interaction and outreach were also adressed. The workshop was well-attended and drew a number of comments on the recommendations being proposed, as well as the overall process of the working group.[16] There was also a public comment period for the draft report, with eight comments submitted.[17]

Final Report edit

The working group's final report was submitted to the board in February 2008.[1] The report concludes:

Our deliberations have achieved near consensus on a comprehensive set of recommendations that addresses five main areas:

  • Formalizing a working group model to become the focal point for policy development and enhance the PDP by making it more inclusive and representative, and – ultimately – more effective and efficient.
  • Revising the PDP to make it more effective and responsive to ICANN’s policy development needs, bringing it in-line with the time and effort actually required to develop policy, and making it consistent with ICANN’s existing contracts (including, but not limited to, clarifying the appropriate scope of GNSO “consensus policy” development).
  • Moving the GNSO Council away from being a legislative body heavily focused on voting towards becoming a smaller, more focused strategic entity, composed of four broad stakeholder groups, with strengthened management and oversight of the policy development process, the elimination of weighted voting and the imposition of term limits.
  • Enhancing constituency procedures and operations to become more transparent, accountable and accessible; and
  • Improving GNSO coordination with other ICANN bodies.[18]

The report contained a total of nineteen action items within these five categories.[18] As the working group was a committee of the board, the action items were mainly board directives to the GNSO Council or delegations of tasks to ICANN staff. Some of the directives involved an eventual return to the board for action - for example, amendments to the ICANN Bylaws.

On February 15, 2008, the board accepted the report and approved its recommendations, subject to a final public comment period.[19] During the passing of the public comment period, the board directed ICANN staff to "draft a detailed implementation plan in consultation with the GNSO, begin implementation of the non-contentious recommendations, and return to the Board and community for further consideration of the implementation plan."[19]

The public comment period on the final report received thirty-one comments. The summary report of public comments characterized ten of those comments as not germane to the specific topics contained in the final report, and noted that four of them merely requested an extension of time for the public comment period.[20] There were extensive comments on the recommendations. A collective of user constituencies (ALAC, the Commercial and Business Users Constituency, the Intellectual Property Constituency, the Internet Service and Connection Providers Constituency, and the Non-Commercial Users Constituency) presented a joint proposal for restructuring the council.[21] From the summary report:

The finalized UC [joint proposal] contribution expresses support for the effort to create a better representational balance on the GNSO Council, but the UC says the BGC WG’s recommendations have three defects that 'contradict the goals of improving policy development and maximizing stakeholder participation.' The UC says the defects include (1) over-representation of contract parties; (2) insufficient stakeholder participation; and (3) external credibility issues.[22]

The joint proposal offered this alternative to Council composition:

  • create a "a parity triangle of equal representation to represent all stakeholders." - 6 seats each for contractual interests (registries and registrars), commercial interests, and non-commercial interests;
  • consider using NomCom appointments to the GNSO Council to provide specific expertise to working groups; and
  • regardless of decisions about the specific number of seats, the Council totals should create equal, unweighted votes for the three interest groups described above.[23]

The joint proposal generated discussion among commenters as the public comment period progressed. In their comments, the ALAC, the Noncommercial User's Group, and the Internet Commerce Association expressed support for the joint proposal, as well as making other comments about the final report. Two individuals - Chuck Gomes and Jeff Neuman, specifically objected to the joint proposal.[22] The majority of other comments expressed support for most of the recommendations, although some constituencies objected to specific action items, or warned against utilizing structural changes to "fix" human behaviors.[22]

Implementation edit

Implementation Planning edit

GNSO activity regarding implementation was ongoing in parallel with the board review of the GNSO Improvements working group recommendations. The GNSO1 dashboard reports that the GNSO Improvement Planning Team (IPT) was formed on March 1, 2008[1], although the dashboard refers to a board resolution from ICANN 37 in Nairobi from March 12 that makes no reference to the GNSO review. [24] The GNSO's community reference on GNSO1 states that the GNSO Council created the IPT.[5] The IPT circulated a draft of a "Top Level Plan" in May 2008 to the GNSO Council and community for feedback.[25] After review and feedback, a second draft was published in June.[26] The revised plan proposed two standing committees for improvements work - a process committee and an operations committee - and proposed charters for each committee.[26]

Board Action on Recommendations edit

On March 28, at ICANN 32 in Paris, the board acknowledged the work of the IPT, as well as receipt of the final GNSO Improvements report.[27] It endorsed all the recommendations in the final report, with the exception of the recommendation regarding Council restructuing. On that topic, it instructed the GNSO Council to convene a working group, including at least one member from each constituency, one member from among the NomCom appointees to the Council, and one member from each of the Council liaison-appointing ACs who wished to appoint a member.[27] The group was instructed to develop and present a Council restructuring recommendation "by no later than 25 July 2008 for consideration by the ICANN Board as soon as possible, but no later than the Board meeting in August 2008."[27]

Working Group on Council Restructuring edit

The working group on GNSO Council restructuring presented its final report on July 25.[28] The report was also distributed to the GNSO Council.[29] The working group was able to achieve consensus on the following general principles:

  • No single stakeholder group should have a veto for any policy vote.
  • Council recommendations of policy requiring 2/3 board vote to reject should have at least one vote of support from at least 3 of the 4 stakeholder groups
  • Equal number of votes between registries and registrars.
  • Equal number of votes between commercial and non-commercial users.

The report recommended a "two houses" GNSO structure, with the Council divided into a contracted party house, and a non-contracted party house, and bicameral voting processes. Within this two-house system, multiple details were hammered out regarding composition of the houses, voting thresholds for various GNSO actions and processes, and NomCom appointees to the Council.[28] There were some specifics that did not achieve consensus, largely because of a fundamental disagreement regarding a reduction of the number of NomCom appointees between the Business Constituency representative and the NomCom-appointed representative.[28]

Separate Statements and Commentary edit

The working group's report included separate statements from many of the working group members. In those statements, there was a general expression of appreciation (and sometimes surprise) regarding the level of consensus and compromise that was achieved in a short time.[28] However, specific group members called out the relative flexibility of the various parties. The IP Constituency appointee Steve Metalitz, writing in his own capacity, gave a frank assessment of the process of "consensus-building" within the working group:

It is obvious from the documents which interests moved the farthest and were most willing to compromise in search of consensus. The work product of the group far more closely resembles the Board Governance Committee proposal than it does the Joint Users Group proposal that was before the Board. The bicameral approach, which originated from the registrar constituency representative, was a useful and productive effort to reframe the discussion, but it did not fundamentally alter the recurring dynamic: We did not reach full consensus because a few participants drew red lines very close to their initial preferred position, or, in one case, very close to the status quo. Notably, throughout the six meetings of our group, and hundreds of e-mail exchanges, the recurrent pattern was that representatives of the GNSO constituencies were far more willing to make compromises than were the participants not representing constituencies. I believe that the constituency representatives, on their own, might well have achieved consensus.[28]

At ICANN 70, Bertrand de la Chapelle participated in an ALAC session on "Reimagining ICANN’s Role; Responding to National Pressures."[30] During a conversation about silos and their impact on the multistakeholder model, de la Chapelle recalled the introduction of the two houses approach and offered this critique of the mindset of the working group participants:

...I participated in one of the calls that led to the restructuring of the GNSO and the creation of the two houses. If I can give a very frank assessment from the outside, I immediately felt that the main objective of the different entities and the different soon-to-become houses was to make sure one thing: that the other halves could not impose anything on them, period. Nothing was about how can we make it better so that we can solve problems together? I’m caricaturing a little bit, but I can tell you this was the feeling that I had exactly at the moment the proposal was made on the call. And I feel that it has remained a little bit in this way.[31]

Board Action edit

At a special meeting of the board on July 31, 2008, the board discussed the working group's report and the issues and proposals submitted by the working group.[32] After discussion of the issues, the board resolved to accept the report, and instructed staff "to perform an analysis of the potential consequences and implementation issues presented by the proposals in the report, and to report one week before the August Board meeting with the recommended steps that can be adopted during the August Board Meeting."[32]

On August 28, 2008, the board held another special meeting to discuss the staff recommendations and proposed resolutions for the board to adopt.[33] Denise Michael presented a summary of staff recommendations:

Staff recommended that the Board approve a contracted party house with three reps from Registries and three from Registrars and a Nominating Committee appointee. Staff also recommended a non-contracted party house of six representatives from commercial and six reps from non-commercial plus one voting Nominating Committee representative. Also, Staff recommended additional work with the GNSO to create a transition program from 2009 bringing it in line with Council elections at the end of the calendar year. To assure that the ICANN Bylaw principles of openness, representativeness, transparency and fairness are honored, constituencies should be asked to re-certify themselves and show plans for future recruitment and expansion consistent with the recommendation of the BGC’s Working Group on the GNSO Review, to attract educational, research and individual registrants, and other issues. Staff recommended a goal to have a new council be seated by January 2009. Staff recommended adopting the proposed voting thresholds, and suggested that this should be discussed and considered during the ongoing work on the Nominating Committee Review.
Also, Staff recommended deferring proposal regarding ICANN Bylaws changes to the GNSO Council selection of ICANN Board Member Seats 13 and 14. Staff noted that this should be part of the Board Review process in light of concerns raised by General Counsel regarding approach by WG for selection of Board members.[33]

After extensive discussion, the board approved the proposed resolutions of staff, which effectuated the recommendations described above.[33]

Implementation Plan edit

References edit

  1. ↑ 1.0 1.1 1.2 1.3 1.4 ICANN.org - GNSO1 Review Dashboard, last material update on June 23, 2012
  2. ↑ 2.0 2.1 2.2 2.3 ICANN Bylaws - Article 4.4
  3. ↑ 3.0 3.1 3.2 3.3 ICANN.org - Organizational Reviews
  4. ↑ Resolution of the Board, March 30, 2007
  5. ↑ 5.0 5.1 5.2 5.3 GNSO Community Reference - Background on GNSO Improvements, January 9, 2013
  6. ↑ 6.0 6.1 2004 GNSO Review - Terms of Reference and Self-Assessment, December 22, 2004
  7. ↑ People + Decisions - About Patrick Sharry
  8. ↑ 8.0 8.1 8.2 8.3 GNSO Archive - GNSO Review by Patrick Sharry, December 22, 2004
  9. ↑ 9.0 9.1 9.2 9.3 9.4 9.5 9.6 A Review of the GNSO, September 2006
  10. ↑ 10.0 10.1 10.2 ICANN.org Listserv Archive - GNSO Improvements
  11. ↑ 11.0 11.1 Draft Working Document of the BGC GNSO1 Working Group, June 18, 2007
  12. ↑ ICANN.org Archive - ICANN 29 Public Forum, June 25, 2007
  13. ↑ GNSO Improvements - Summary of Public Forum, July 1, 2007
  14. ↑ GNSO Improvements Draft Report, October 15, 2007
  15. ↑ ICANN 30 Workshop - GNSO Improvements, October 29, 2007
  16. ↑ Summary of BGC Working Group Workshop on GNSO Improvements, October 29, 2017
  17. ↑ GNSO Improvements - Public Comment Proceeding, October 19, 2007
  18. ↑ 18.0 18.1 Final Report of the BGC Working Group on GNSO Improvements, February 3, 2008
  19. ↑ 19.0 19.1 Resolutions the Board, February 15, 2008
  20. ↑ ICANN Listserv Archive - Public Comment Proceeding Summary email from Robert Hoggarth, May 6, 2008
  21. ↑ ICANN.org Listserv Archive - email from Philip Sheppard re: joint users proposal, April 23, 2008
  22. ↑ 22.0 22.1 22.2 Summary Report of Public Comments on GNSO Improvements, May 7, 2008 (Word document)
  23. ↑ Joint Proposal from the User Community for GNSO Council Structural Change, April 23, 2008 (Word document)
  24. ↑ Resolution of the Board, March 12, 2010
  25. ↑ GNSO Improvements Top-Level Plan, May 22, 2008
  26. ↑ 26.0 26.1 GNSO Improvements Top-Level Plan, June 21, 2008
  27. ↑ 27.0 27.1 27.2 Resolution of the Board, June 26, 2008
  28. ↑ 28.0 28.1 28.2 28.3 28.4 Report to the ICANN Board from WG-GCR, July 25, 2008 (Word document)
  29. ↑ GNSO Council Listserv - Rob Hoggarth to list, July 28, 2008
  30. ↑ ICANN 70 Archive: Reimagining ICANN's Role, March 23, 2021 (registration/login required)
  31. ↑ Transcript of "Reimagining ICANN's Role", March 23, 2021 (registration/login required)
  32. ↑ 32.0 32.1 Board Meeting Minutes, July 31, 2008
  33. ↑ 33.0 33.1 33.2 Board Meeting Minutes, August 28, 2008

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

At-Large Advisory Committee. Considers and provides advice on the activities of ICANN related to the interests of individual Internet users (ICANN Bylaws). Not to be confused with the Non-Commercial Stakeholder Group.

Retrieved from "https://icannwiki.org/index.php?title=First_GNSO_Organizational_Review&oldid=1320585"