First NomCom Organizational Review

From ICANNWiki
Jump to navigation Jump to search

The First NomCom Organizational Review was initiated in 2007 and concluded in 2010, with the implementation of improvements continuing through 2012.[1]


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 Nominating Committee is one of the organizations subject to the review requirements of Article 4.4.[3]

Multiple other review and reform processes, including the 2002 Evolution and Reform Process and the ATRT1 review, have impacted the Nominating Committee's structure and composition over the history of ICANN. This review marked the first effort to focus specifically on the operation of the NomCom on its own account.


ICANN posted a proposed Terms of Reference (ToR) for NomCom1 on December 12, 2006 for public comment.[4] The proposed ToR included forty-seven questions within seven broad categories - key questions, committee composition, transparency, selection criteria, outreach, effectiveness, and miscellaneous other questions.[4]

Three public comments were received on the proposed ToR, two of which were past the deadline for comment.[5] Thomas Roessler proposed several refinements to questions, from editorial corrections to changes that ensured that a question was not making assumptions that the review process might overturn.[6] Lesley Cowley, on behalf of Nominet (and one day past the submission deadline), expressed concerns that the level of detail and nature of the questions might constrain the reviewers, limit the scope or direction of review, or pre-dispose the reviewers to adapt the structure of their process to ensure that the totality of the questions are addressed.[7] In another late submission, Chris Disspain on behalf of AuDA echoed Nominet's concerns regarding the structural and investigative determinism implied in some of the questions. He also commented that the purpose of the NomCom should not be presumed to be known:

I acknowledge that the draft terms of reference set out to achieve the scope of the review as defined by the bylaws. However, it is critical, in my view, that the review also consider what purpose in the ICANN structure the NomCom is supposed to fulfil [sic]. The current purpose of the NomCom is far from clear and I am not aware of a definitive explanation of it. The draft Terms of Reference evidence this by stating that the purpose 'has been described as follows'.[8]

The ToR was re-drafted in response to the public comments, and the final version was posted on March 15, 2007,[9] alongside ICANN's announcement of a Request for Proposals (RFP).[10] The finalized ToR contained forty questions, organized beneath the core questions of Article 4.4 reviews:

  • Part I: Does the NomCom have a continuing purpose in the ICANN structure?
  1. What is the purpose of the NomCom?
  2. To what extent has the NomCom process been able to select persons who place the broad public interest of the global Internet community ahead of any particular interests?
  3. Should this goal remain the primary goal in filling positions, or are there other elements that are also important to consider?
  4. Of those persons selected by the NomCom process since 2003, do any particular qualifications predominate?
  5. Do people selected by the NomCom appear to play a greater, comparable or lesser role in decision-making within their respective bodies, in comparison to those persons selected by other means?
  6. What should be the purpose of the NomCom going forward?
  7. What other methods of selection for leadership positions might be considered?
  8. What are the benefits, drawbacks and costs of such options?
  • Part II: Is there any change in structure or operations that could improve the NomCom's effectiveness?
    • NomCom Composition (size, diversity of members, source of members, inclusion of necessary skills)
    • Internal Procedures (transparency, continuity & institutional memory, compliance with procedure, managing conflicts of interest)
    • Selection Process (are the selection criteria appropriate, what has the process been like, how might it be improved)
    • Outreach (history and effectiveness of past efforts, goals and metrics for successful outreach, potential barriers for non-English speakers)
    • Overall (how well has the NomCom performed, how can it do better, is there adequate support, or might more resources be needed to increase effectiveness)[9]

On March 30, the ICANN board selected the initial members of the NomCom1 Review Working Group (WG): Alejandro Pisanty; Peter Dengate Thrush, Njeri Rionge, Mouhamet Diop, Jonathan Cohen, and Steve Goldstein.[11]

Independent Examiner Findings & Recommendations

The board selected Interisle Consulting Group for the independent review of the NomCom in July 2007.[12]


Interisle solicited public comment on the NomCom and its processes, with a broad request for feedback or commentary.[12] It used these comments to guide its interview process, conducting interviews with forty-seven individuals who were connected to or interacted with the NomCom in some way. It also engaged in documentary review from a variety of sources, including board records, email communications, and formal and informal presentations from ICANN meetings and beyond.[13]


The report listed a series of "observations" based on the documentary evidence, interviews, and written feedback. Because the RFP and ToR encouraged a focus on both what was standard practice (written or unwritten) in the NomCom as it was, as well as findings that could reveal potentials for improvement in the future, the observations range from descriptive to prescriptive.[13] The findings are listed below - bold text has been added to findings that were particularly relevant to the recommendations that followed.

  1. The central purpose of the NomCom is to find genuinely independent and unaffiliated Board, Council, and ALAC members.
  2. The responsibility for achieving and maintaining cultural and geographic diversity on the bodies to which it appoints makes it difficult for the NomCom to pursue its central purpose.
  3. A nominating committee is a good way to find and appoint independent people to some of ICANN’s leadership positions, but the current NomCom could be substantially improved.
  4. Direct elections are not a desirable alternative to the NomCom in the absence of a well-defined and adequately engaged electorate.
  5. The At-Large Advisory Committee is not currently a viable alternative to the NomCom.
  6. NomCom members do not consistently understand the overall role and responsibilities of the NomCom or agree on the details.
  7. NomCom members do not consistently understand ICANN or its constituent bodies well enough to interpret and apply the criteria and qualifications for appointments.
  8. Recruiting and selecting candidates for the ICANN Board is fundamentally different from recruiting and selecting candidates for the SOs and ALAC.
  9. The rationale for NomCom appointments to the Board is stronger than the rationale for NomCom appointments to the SOs or ALAC.
  10. The NomCom lacks representation from the Board, but otherwise adequately represents the different parts of the ICANN community.
  11. The representative composition of the NomCom encourages members to think of themselves (and act) as constituency representatives rather than as individuals.
  12. New NomCom members are not always well prepared to participate effectively.
  13. When some members are much better prepared than others, the NomCom appears to be controlled by “insiders.”
  14. NomCom’s one-year term of service with one-year renewal strikes the right balance between continuity and productive turnover.
  15. NomCom lacks a practical mechanism for removing and replacing underperforming members.
  16. NomCom is “too small” for effective recruitment and outreach and “too large” for efficient deliberation and selection after candidates have been identified.
  17. The success of the NomCom’s efforts depends heavily on the skills of the Chair.
  18. The demands of the NomCom Chair’s job exceed what can reasonably be expected of a volunteer, part-time position.
  19. The unrealistic level of effort expected of the Chair inhibits regular turnover and planned orderly succession.
  20. The rules governing the relationship between the NomCom and ICANN staff are not clearly documented or understood.
  21. Lack of clarity concerning what does and does not constitute “interference” by staff in NomCom deliberations inhibits communication and encourages suspicion.
  22. Broader awareness of ICANN and its mission would help NomCom recruit qualified volunteers.
  23. As ICANN’s most visible outward-facing activity, the NomCom has a significant effect on the way in which ICANN is perceived in the world at large.
  24. The way in which the NomCom operates is not well understood outside of the NomCom itself.
  25. The NomCom lacks specific requirements for its annual Board, SO, and ALAC appointments, and it is not clear how those requirements should be established (or by whom).
  26. The NomCom “application” model for recruitment deters some potentially well qualified candidates who are accustomed to and more comfortable with the traditional corporate “invitation” model.
  27. Recruitment and selection follow different procedures, call for different skills and aptititudes, and place different demands on NomCom resources.
  28. Annual NomCom outreach generates information about motivated potential ICANN volunteers that is not available either to subsequent NomComs or to other parts of ICANN.
  29. Candidates want better and more timely information about the status of their candidacy and the progress of the NomCom process.
  30. Some successful candidates consider the background check to be unreasonably intrusive.
  31. The rules that govern the way in which candidate qualifications are evaluated and selections are made are not well-documented or understood.
  32. Lack of internal agreement on the way in which deliberation and selection should be conducted makes it difficult for the NomCom to resolve conflicting criteria for evaluating candidates.
  33. NomCom lacks information about the past performance of incumbent candidates for re-appointment.
  34. In practice, the importance of its obligation to maintain absolute candidate confidentiality has led the NomCom to be secretive about other aspects of its operation as well.
  35. Secrecy beyond what is required to preserve candidate confidentiality shields the NomCom from outside pressure and influence but also damages its credibility.
  36. Members properly disclose their financial and other relationships in accordance with the NomCom’s conflict of interest policy, and also properly recuse themselves from discussions when called for by the policy.
  37. On the whole the NomCom has appointed well-qualified, independent, and effective people to the Board, SO Councils, and ALAC.
  38. The NomCom’s multi-stakeholder process is inherently biased in favor of appointments that are uncontroversial and broadly acceptable.
  39. Some NomCom appointees need more help “getting up to speed” in their new jobs; with better and more timely information about selected candidates, staff could fill this role.


The report offered eighteen broad-brush recommendations, with additional specific recommendations or steps beneath some:

  • Balance confidentiality and transparency;
  • Treat candidates more respectfully;
  • Recruit and select based on requirements (specifically, explicitly identify required skills and use that profile to guide the NomCom's process);
  • Separate recruiting from selection;
  • Focus NomCom on its core mission (i.e., find independent and unaffiliated directors for the ICANN Board);
  • Restructure the NomCom leadership roles - hire a "NomCom Administrative Director" (NomCom AD) to lessen the burdens on the Chair, and incorporate succession planning for Chairpersons (multiple options);
  • Reduce NomCom membership;
  • Enforce participation rules;
  • Explicitly design and document NomCom processes;
  • Seek candidate information from many sources beyond their submitted Statement of Interest and references;
  • Boost awareness of ICANN and the NomCom;
  • Hold NomCom appointees accountable (establish metrics for performance and base re-appointment or recall decisions on those metrics);
  • Audit the NomCom process annually, and publish the results;
  • Assign the management of outreach and recruitment to the NomCom AD - maintain relationships with and connections to a roster of ICANN volunteers who would be likely candidates for substantive policy work, as well as service on the NomCom;
  • Select NomCom members by lottery;
  • Distinguish between the "fiduciary" and "policy" roles of the ICANN Board;
  • Nominate "policy" directors to the board from a slate of candidates drawn objectively from the NomCom AD's roster. ALAC selects two "policy" directors using its own mechanisms and processes. "Fiduciary" directors are recruited and selected through an independent process;
  • Select SO and AC council members from the NomCom AD's roster; but
  • Devlolve responsibility for selection of ALAC members - "It is no longer necessary or advisable for the NomCom to be involved in the selection of ALAC members."

Public Comment

Interisle presented on their report at ICANN 30 in Los Angeles, and solicited feedback on the report and its recommendations.[14] In addition, six written comments were submitted during the public comment period on Interisle's report.[15] Public comment ranged from positive to highly critical.[15] Elisabeth Porteneuve presented without comment a statistical breakdown of home nation and native tongue of Interisle's interviewees. The statistics showed that the overwhelming majority of interviewees were English speakers, with over half of the interviewees coming from the United States.[16] Avri Doria found fault with the report's division of "fiduciary" and "policy" roles, even as a thought exercise: "These responsibilities cannot be seperated and should not be separated in the considerations that form the nomcom or that shape the nomcom's decisions."[17] Thomas Roessler strongly objected to a number of the recommendations, citing the "miracle" that is performed by the NomCom each year:

At the core of my disagreement is the review's tendency to consider the nominating committee's complex social process in a somewhat mechanistic way. The nominating committees perform a small miracle each year by achieving agreement on appointees in a group that is as diverse as the ICANN community overall. Great care should be taken to not endanger the committee's ability to perform this miracle. A significant part of the secret sauce that makes this success possible is the nomcom's secrecy and, yes, the unaccountabilty of individual members. Changes to these points are extremely risky, and should only be made with utmost care.[18]

Philip Sheppard commented specifically to argue that there was no longer a need for the NomCom to appoint members to the GNSO Council.[19]

Delay and Update Process

Following the closing of the public comment period in April 2008, the plan was for the WG to submit a draft report to the Board Governance Committee regarding the recommendations and proposing implementation for improvements.[20] The WG drafted that report; however, "[t]he BGC considered that recommendations from the NomCom review process had to be analysed in coordination with the findings of other reviews [including the ICANN Board Review and the First ALAC Organizational Review] that at the time of delivery of the report were ongoing. Consequently, the NomCom review WG report was not published for public comments."[21]

New Draft Report

During the delay in action on the WG's final report, the Structural Improvements Committee (as it was then known) assumed responsibility for the oversight of Article 4.4 organizational reviews.[21] In June 2009, anticipating a need for updates to the original final report, the SIC presented a re-composed working group to the board for approval and appointment. The following month Thomas Roessler (Chair), Alejandro Pisanty, Jonathan Cohen, Steve Goldstein, and "all nominated Members accepted to serve in this role" were appointed by resolution of the board.[22] As work wrapped up on the other reviews, the SIC asked the recomposed WG to update and consolidate the draft report to reflect new data and input from the intervening years. The Interisle report was primarily based on data running up to and including 2006.[13] As such, there was an opportunity to refresh the organization's understanding of the NomCom's operation and processes. The WG "reviewed relevant documents, and consulted intensively with NomCom Chairs of the period of 2006 to 2009 and with supporting staff" to update its draft report.[21]

Public Comment

The updated draft report was published for public comment in October 2009, with the intention to gather public input and substantially refine the draft at ICANN 36 in Seoul.[21]

ICANN 36 Workshop

At ICANN 36, Thomas Roessler and Marco Lorenzi presented the WG's updated report,[23] while members of the ICANN Board Review working group were also on hand to provide input related to the recommendations of that review.[24] Much discussion was focused on support, backup, and succession planning for the chairperson. There was concern expressed about the proposal for the chair-elect to serve as a non-voting member in the year prior to his term, because of the potential risk of burnout or unforeseen circumstances causing the "trained and ready" chairperson to abandon the post. Roessler defended the plan as an improvement over the current system, which still carried the risk of the loss of an experienced chair.[24] Tricia Drakes, who by custom was transitioning into the role of Advisor to the NomCom after stepping down from the chair, countered that risk management argues in favor of retaining the past chair for an advisory, support role, rather than training up a new chair.[24] Wolfgang Kleinwächter, the incoming chair for the 2010 NomCom, proposed a number of methods to help ensure prepared and experienced chairpersons: for example, the Bylaws could require prior experience on the NomCom to be nominated chair. Kleinwächter preferred the "troika" method, with the prior chair becoming an advisor to the NomCom, and the Chair-elect serving in a learning role for a year.[24] Jonathon Cohen proposed possibly transitioning the Advisor role into an on-demand consultation role, so that the former chair is not obligated to attend.[24]

The Seoul session also approached the challenge of Interisle's observation 16: that the NomCom was both "too small" and "too large" to fulfill each of its functions. Roessler outlined the drivers for change, and provided some background on the current state of the ICANN Bylaws related to NomCom composition. The status quo composition of the NomCom at the time was:

  • Voting Seats
    • 7 GNSO seats (1 RySG, 1 RrSG, 2x BC (small business & large business ), 1 ISPPC, 1 IPC, and a delegate selected by the NCUC);
    • 5 ALAC seats (selected according to ALAC rules);
    • 1 ccNSO seat;
    • 1 ASO seat,
    • 1 "academic" seat (chosen by an institution selected by the ICANN Board);
    • 1 IETF seat; and
    • 1 TLG seat.
  • Nonvoting Seats
    • Chair
    • Past Chair
    • RSSAC
    • SSAC
    • GAC (at the time, not exercising its option to attend)

The status quo, assuming full participation, was 22 total seats, 17 voting and 5 non-voting. The WG proposed two strawman structures - one smaller and one larger:

  1. Smaller, stakeholder-based model: 1 GNSO seat from each stakeholder group in the GNSO, 3 selected by the ALAC, remove the "academic" representative and keep the rest of the composition the same. 16 total seats, 11 voting and 5 non-voting.
  2. Larger, stakeholder-based model: 1 GNSO seat from each SG in the CPH, 2 seats for each SG in the NCPH, 3 seats selected by the ALAC, remove the "academic" representative, and keep the rest of the composition the same. 20 total seats, 15 voting and 5 non-voting.

Both proposals represented a reduction in the number of seats, although the larger model was close to the same composition. Wolfgang Kleinwächter stated that caution should be exercised whenever the ICANN community "shrinks" (or is perceived to shrink) representation and participation. Adam Peake agreed, stating in particular that decreased ALAC participation might diminish global representation, and generally stating that a large committee, while unmanageable, was preferable because of the goal of maximum representation and participation. Subsequent commenters agreed that a large composition, though unwieldy, was preferable. George Sandusky noted the "violent agreement" on the issue of size, and added his voice. Marilyn Cade agreed with the general consensus that too much change, too quickly, was ill-advised, and stated that it "may be premature" to know when the time was for structural modifications. Mike Roberts, however, noted that ICANN Staff management was struggling with "an out-of-control travel budget," and that the incoming NomCom would not be able to attend the full ICANN meeting unless they paid their own travel expenses. While still preferring a large committee, he stated that there were already trade-offs as regards budget.[24] The session briefly touched on issues of recall and replacement of NomCom appointees, but there was little time for substantive discussion. The general consensus was that the recall of appointees would likely not fall to the NomCom but to the SO or AC that had the issue. Replacement processes, however, as Adam Peake commented, might be of value for the review team to evaluate or propose.[24]

Written Comments

Most written comments, as requested by the WG, were submitted in advance of ICANN 36. The RySG submitted a consensus comment in November 2009 that largely agreed with the public comments gathered at the meeting.[25]

Working Group Final Report

The WG's final report was submitted to the SIC in January 2010.[1][26] The report incorporated feedback from the Seoul session as well as written comments. In the eyes of the WG, some of Interisle's recommendations were rendered moot by refinements and improvements to the NomCom's process in the intervening years.[26]

Recommendations and WG Response

Note: The Finalization Working Group ordered Interisle's recommendations by topic cluster, so the order is slightly revised from Interisle's Final Report

Recommendation Working Group Comment WG Implementation Opinion/Proposal
1. Create a full‐time Administrative Director position "...the tasks that reviewers originally proposed to delegate to an Administrative Director are now regularly carried out either by NomCom Members or by supporting staff." Should not implement
2. Treat candidates more respectfully "...the objective to fully respect the candidates shall be considered as a core value for the NomCom, and –as such‐ included in the set of core binding values governing the NomCom, suggested in the WG comments to Recommendation 16." Incorporate into value statement; no further implementation needed re: transparency of process
3. Recruit and select based on requirements Agree with ICANN Board Review Working Group that communication between the board and NomCom regarding requirements should be formalized (current practice is informal communication regarding needs)
"The WG recommends that future Nominating Committees target their recruiting process according to specific profiles (including gender3, outside executive and board experience, and other goals), devise success metrics for their outreach activity, and share information about how these metrics were attained in public. We also recommend that Nominating Committees develop and refine their outreach strategy over the course of several years, and encourage more detailed information sharing on the success of various outreach mechanisms across Nominating Committees."
4. Separate recruitment from selection Agree; NomCom has evolved to divide these processes No further implementation needed. "Candidate pool" concept might require opt-in mechanism - one is proposed in Recommendation 14 that could be expanded to include interest in applying for open roles
5. Seek candidates' information from multiple sources Agree; already in practice No further implementation needed
6. Boost awareness of ICANN and NomCom "However, recent awareness building campaigns seem not to have influenced the number of SoIs received by recent Nominating Committees. We re‐iterate our advice on recommendation 3, that the awareness building and recruiting process used by the Nominating Committee should be evaluated based on requirements and specific metrics, and should be refined systematically." ICANN should continue to increase its awareness-building and outreach activities
7. Select "policy" directors from volunteer pool; give ALAC two seats on the board Outside of scope; ALAC issue superseded by board action to give ALAC a voting seat; No further implementation needed
8. SOs to select their Council Members from ICANN volunteer pool, based on qualifications needed, to be documented by SOs Disagree - "in the interest of objectivity and avoidance of capture the NomCom should remain responsible for the selection of these positions." Should not implement
9. ALAC to select its At‐large Committee Members Out of remit Should not implement
10. Reduce NomCom membership "The comments that have been received almost unanimously discourage the suggestion to reduce the size of the NomCom and differently represent communities in its composition." Review again in three years' time
11. Select NomCom members by lottery from a list of volunteers "The WG does not support this recommendation; its adoption would introduce risks of unbalanced representation into the process of selection of NomCom Members." Should not implement
12. Focus NomCom on its core mission to seek independent, unaffiliated directors for the board Independence from outside interests is "very hard - if not impossible - to achieve in the current ICANN environment." "The WG endorses the recommendation that the NomCom process 'not simply offer an alternative path to a leadership position for people who have been unsuccessful reaching that position through a constituency appointment process,' but notes that this is eventually a question within each Nominating Committee’s judgment, and not a hard, bylaw‐level requirement."
13. Restructure NomCom leadership rules, providing balance of continuity and fresh perspectives "The current NomCom practice – as codified in the ICANN bylaws ‐ provides for the participation of the previous year’s Chair in the work of each Nominating Committee; while not a voting member, the previous chair serves as an advisor to the active chairman of the committee. The reviewers proposed to flip this arrangement: the chair would be appointed a year in advance, and would participate as a non‐voting 'incoming chair,' before taking full responsibility in the next year." WG endorses the recommendation and refers to the ICANN Board for amendment of bylaws
14. Balance confidentiality and transparency: maintain core confidentiality of candidates' data and eliminate secrecy everywhere else WG agrees with prior WG statement: "Support, but need to foresee an opt‐in mechanism for non selected candidates for subsequent recruitment rounds."
Document and formalize an opt-in procedure for future appointment rounds - consider expanding opt-in to include appointment to board or council seats
15. Enforce participation rules & create a removal process for non-participating members Performance expectations should be baked into the NomCom operating principles (see Rec. 16)
Referral to board: "We recommend that the following guiding principles be integrated in Art.7 of Bylaws:
A NomCom member may be removed by the Chair based on objective criteria, following notice to the member, and due consideration of the member's response to the notice;
Removal of a member is to be adopted by a two‐thirds majority of the voting NomCom Members;
Preliminary notice is given to the entity that has appointed the member."
16. Design and document NomCom key processes Agree, but needs to be minimally structured and flexible "On balance, the WG recommends identifying and documenting – based on the efforts made by previous Nominating Committees – a small set of core working values and procedures, to be formally adopted by the Board as a binding guidance.
Any instance of the NomCom should be then left free to adopt and to adapt further working practices that are deemed necessary for its functioning, in respect and application of the established core principles."
17. Audit yearly NomCom effectiveness, and publish the results Disagree with the term "audit" - all organizations already expected to evaluate performance Future NomComs should consider: 1) publishing formal outreach goals and outcomes; 2) polling members at the end of their term regarding committee effectiveness and integrity, effectiveness and performance of the chair, and suggestions for improvement, with polling results submitted to the board for review & implementation of improvements; and 3) experiment with more explicit performance goals and metrics, and with self-evaluations of those metrics, with any evaluations to feed into the next organizational review

Board Action

In March 2010 the Board accepted reports from three review working groups, including NomCom1.[27] The board instructed the SIC to generate implementation plans for the recommendations in the final report. In June 2010, the board again addressed the status of implementation planning, and noted that ICANN staff and the SIC had been working together to establish implementation plans. The board resolved for the SIC to finalize their implementation goals and submit the final plans to the board.[28] In November, the final implementation plan was submitted to the board.[29] The board approved the plan at its meeting at ICANN 39 in Cartagena.[30]


Implementation continued through March 2012, at which point an updated implementation plan was published, noting that implementation of all improvements was complete.[31] The publication of the report marked the end of the NomCom1 review.[1]


  1. 1.0 1.1 1.2 - NomCom1 Dashboard
  2. 2.0 2.1 2.2 2.3 ICANN Bylaws - Article 4.4
  3. 3.0 3.1 3.2 3.3 3.4 - Organizational Reviews
  4. 4.0 4.1 Announcements - ICANN Seeks Public Comments on Proposed ToR, December 12, 2006
  5. Listserv Archive - Public Comment on Proposed ToR for NomCom1, December 2006 - January 2007
  6. ICANN Listserv Archive - Comment of Thomas Roessler on NomCom1's Proposed ToR, December 13, 2006
  7. ICANN Listserv Archive - Comment of Nominet on NomCom1's Proposed ToR, January 12, 2007
  8. ICANN Listserv Archive - Comment of AuDA on NomCom1's Proposed ToR, January 29, 2007
  9. 9.0 9.1 Archive - Terms of Reference, NomCom1, March 15, 2007
  10. Archive - Request for Proposals, NomCom1March 15, 2007
  11. Resolutions of the Board, March 30, 2007
  12. 12.0 12.1 Announcement - Independent Evaluator Selected, Seeks Public Input for NomCom1, July 19, 2007
  13. 13.0 13.1 13.2 Interisle Consulting Group - Final Report, Independent Review of the NomCom, October 23, 2007
  14. ICANN 30 Archive: Workshop - Nominating Committee Review, October 31, 2007
  15. 15.0 15.1 Listserv Archive - Public Comment on NomCom1 Independent Evaluator's Report, October 2007 - March 2008
  16. Elisabeth Porteneuve - Public Comment Submission: Some stats on 47 person interviewed, November 2, 2007
  17. Avri Doria - Individual comments on the nomcom report, November 5, 2007
  18. Thomas Roessler - Nomcomm Review Comments, November 12, 2007
  19. Phiilip Sheppard - Nom Com appointees to the GNSO, March 18, 2008
  20. Listserv Archive - Summary of Public Comments, April 14, 2008
  21. 21.0 21.1 21.2 21.3 Announcement - Public Comment sought for draft report of the NomCom Review WG, October 3, 2009
  22. Resolutions of the Board, July 30, 2009
  23. ICANN 36 Archive - NomCom2 Presentation Slides, October 28, 2009
  24. 24.0 24.1 24.2 24.3 24.4 24.5 24.6 ICANN 36 Archive - Review of the Nominating Committee: Presentation of the WG Report, October 28, 2009
  25. RySG Comment on the Draft Report of the NomCom1 Finalization WG, November 21, 2009
  26. 26.0 26.1 NomCom1 Finalization WG Final Report, January 29, 2010
  27. Resolutions of the Board, March 12, 2010
  28. Resolutions of the Board, June 25, 2010
  29. Nominating Committee Improvements - Implementation Plan, November 5, 2010
  30. Resolutions of the Board, December 10, 2010
  31. NomCom1 Improvements - Updated Implementation Plan, March 1, 2012