Skip to main content
Resources

Nominating Committee | Open Leadership Positions 2008

7 December 2007

Candidates for all positions should be women and men with a high level of qualifications and experience with an international outlook including some familiarity with the Internet. They should be prepared to contribute to the collective decision-making process among ICANN's constituencies, supporting organizations, and advisory committees.

About ICANN

The Internet Corporation for Assigned Names and Numbers (ICANN) is a not-for-profit public benefit California corporation having responsibility for the security and stability of the Internet through the management of the Internet's assigned names and numbers. Created in 1998 by a joint initiative of the Internet's business, technical, academic, and user communities, ICANN has been gradually assuming the responsibility for a set of technical functions previously performed by the Internet Assigned Numbers Authority (IANA) and other groups. Under contract from the U.S. Department of Commerce, ICANN includes the IANA function that since the inception of the Internet has managed the Internet's naming and numbering functions.

ICANN's mission is: to coordinate, at the overall level, the global Internet's systems of unique identifiers, and in particular to ensure the stable and secure operation of the Internet's unique identifier systems. In particular, ICANN:

  1. Coordinates the allocation and assignment of the three sets of unique identifiers for the Internet, which are:
    1. Domain names (forming a system referred to as "DNS");
    2. Internet protocol ("IP") addresses and autonomous system ("AS") numbers; and
    3. Protocol port and parameter numbers.
  2. Coordinates the operation and evolution of the DNS root name server system
  3. Coordinates policy development reasonably and appropriately related to these technical functions.<http://www.icann.org/general/bylaws.htm#I>

ICANN is dedicated to preserving the operational stability of the Internet; to promoting competition; to achieving broad representation of global Internet communities; and to developing policy appropriate to its mission through bottom-up consensus-based processes.

Criteria and time commitments applicable to all positions

The Nom Com will use the Criteria for Selection of ICANN Directors contained in the ICANN Bylaws for all four sets of positions it will fill. These Criteria are:

  1. Accomplished persons of integrity, objectivity, and intelligence, with reputations for sound judgment and open minds, and a demonstrated capacity for thoughtful group decision-making;
  2. Persons with an understanding of ICANN's mission and the potential impact of ICANN decisions on the global Internet community, and committed to the success of ICANN;
  3. Persons who will produce the broadest cultural and geographic diversity on the Board consistent with meeting the other criteria set forth in this Section;
  4. Persons who, in the aggregate, have personal familiarity with the operation of gTLD registries and registrars; with ccTLD registries; with IP address registries; with Internet technical standards and protocols; with policy-development procedures, legal traditions, and the public interest; and with the broad range of business, individual, academic, and non-commercial users of the Internet;
  5. Persons who are willing to serve as volunteers, without compensation other than the reimbursement of certain expenses; and
  6. Persons who are able to work and communicate in written and spoken English.

Given ICANN's Mission and Core Values, appointees engage in discussions on the technical functions coordinated by ICANN and their impact on the global Internet operation, such as its stability and integrity, or the effect on the users of the Internet. Appointees interact in a diverse environment, involving ICANN Board, ICANN Supporting Organizations and Constituencies, or Advisory Committees, as well as the broad Internet community, by means of a continuous, transparent and informed dialogue, as it corresponds to the ICANN multi-stakeholder concept.

Appointees will be part of groups which function better in a collegial and cooperative manner but in which individuals must also be prepared for intense debate in which tolerance and reasoning are necessary to accommodate and synthesize conflicting views. Careful consideration of the issues, depth of study of the precedents and environment, and the ability to deal clearly with conflict, including potentially conflict of interest, are predictors of successful contributions to ICANN.

The Nom Com welcomes and encourages participation from all members of the global Internet community. Although Candidates should be able to both work and communicate well in English, there is no requirement that English be the candidate's first language.

The time commitments identified below are a basic requirement and the Nom Com anticipates that in most cases people will spend more time rather than less. All appointees should expect to spend an additional significant amount of time when joining ICANN on training and learning about the organization, its mission, history and mode of operation.

ICANN holds three meetings per year. These meetings typically last for one week and are where the ICANN community gathers to discuss and develop policy and conduct ICANN's business. Meeting locations rotate across ICANN's five geographic regions, for example the first meeting of 2008 will be held in Asia (New Delhi, India), the second meeting will be held in Europe (Paris, France), and the third meeting in the African region (country and city to be announced). Subsequent meetings will be held in the Latin America and Caribbean region and North American regions (due to movement of the Asia/Pacific/Australia meeting to Los Angeles in November 2007, the next meeting in the North American region is scheduled for October 2010). All NomCom appointees are expected to travel and participate in ICANN meetings. Reasonable expenses incurred in attending meetings will be reimbursed.

Position and Roles, Eligibility Factors, and Time Commitments

Position: Board of Directors (http://www.icann.org/general/board.html)

Number of Seats: 2

Start of Term: Conclusion of Annual Meeting 2008

End of Term: Conclusion of Annual Meeting 2011

ICANN's Directors, as a group, are responsible for exercising the powers of ICANN, controlling its property, and conducting or directing its business and affairs, except as otherwise provided in the ICANN Articles of Incorporation or Bylaws. Directors serve as individuals who have the duty to act in what they reasonably believe are the best interests of ICANN and not as representatives of the entity that selected them, their employers, or any other organizations or constituencies.

Directors are expected to support the ICANN mission and the implementation of ICANN's Core Values.

The Nominating Committee will use the Selection Criteria for Directors, set forth in the Bylaws, for these positions.

ICANN Directors shall receive no compensation for their services as Directors. The Board may, however, authorize the reimbursement of actual and necessary reasonable expenses incurred by Directors performing their duties as Directors. [Bylaws Article VI, Section 22, see http://www.icann.org/general/bylaws.htm#VI-22]

Board Eligibility Factors

  1. No person who serves on the Nominating Committee in any capacity is eligible for selection by any means to any position on the Board or any other ICANN body having one or more membership positions that the Nominating Committee is responsible for filling, until the conclusion of an ICANN annual meeting that coincides with, or is after, the conclusion of that person's service on the Nominating Committee. [Bylaws, Article VII, Section 8, see http://www.icann.org/general/bylaws.htm#VII-8]
  2. Nominating Committee shall seek to ensure that the ICANN Board is composed of members who in the aggregate display diversity in geography, culture, skills, experience, and perspective, by applying the criteria set forth above in this document. [Bylaws, Article VI, Section 2(2), see http://www.icann.org/general/bylaws.htm#VI-2.2]
  3. At no time shall the Nominating Committee select a Director to fill any vacancy or expired term whose selection would cause the total number of Directors (not including the President) who are citizens of countries in any one Geographic Region to exceed five; and the Nominating Committee shall ensure through its selections that at all times the Board includes at least one Director who is a citizen of a country in each ICANN Geographic Region. [Bylaws, Article VI, Section 2(2), see http://www.icann.org/general/bylaws.htm#VI-2.2]
  4. No official of a national government or a multinational entity established by treaty or other agreement between national governments may serve as a Director. [Bylaws, Article VI, Section 4(1), see http://www.icann.org/general/bylaws.htm#VI-4.1]
  5. No person who serves in any capacity (including as a liaison) on any Supporting Organization Council shall simultaneously serve as a Director or liaison to the Board. [Bylaws, Article VI, Section 4(2), see http://www.icann.org/general/bylaws.htm#VI-4.2]
  6. Term limits: Vinton G. Cerf, appointed as a Director by the NomCom in 2004, has served three terms on the board and is not eligible for consideration by the 2007 NomCom. Other ICANN Directors appointed by the NomCom whose terms expire at the ICANN General Meeting of 2007 have not exceeded the three term limit as defined in the Bylaws.

The current composition of the Board of Directors is available here http://www.icann.org/general/board.html

Time Commitment and Working Practice

The basic responsibilities of an ICANN Director require a minimum commitment of time which when averaged out over the year is roughly equivalent to 20-24 hours each week. This includes participation in three ICANN meetings/year, two Board retreats/year and work on Board Committees. The time spent in these basic responsibilities is typically clustered around Board meetings and monthly teleconferences, but there is a constant flow of information requiring attention on a near daily basis.

Directors are expected to attend three ICANN meetings per year and depending on the location and including travel time and preparation this could be a commitment of up to ten (10) days per meeting. In addition the board occasionally holds shorter face-to-face meetings such as retreats.

Directors spend additional time in connection with their work on Board Committees, a commitment that varies in relation to the number of Committees on which they serve, the scope of the Committee's responsibilities, and their role as Chair or Member of the Committee.

Position: GNSO Council

Number of Seats: 1

Start of Term: Conclusion of Annual Meeting 2008

End of Term: Conclusion of Annual Meeting 2010

The Generic Names Supporting Organization (GNSO) is a policy-development body responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. The GNSO consists of various Constituencies representing defined groups of stakeholders and a GNSO Council, responsible for managing the policy development and administrative processes of the GNSO. The GNSO Constituencies choose the majority of the Council members; Nominating Committee chooses three Council members with staggered terms. The GNSO also includes a liaison from the ALAC and the Governmental Advisory Committee. Liaison activities from the ASO and ccNSO are under development.

GNSO Council Members receive no compensation for their services as GNSO Council Members. ICANN provides administrative and operational support necessary for the GNSO to carry out its responsibilities through the GNSO Secretariat. ICANN also provides staff support for policy development. As stated in the ICANN Bylaws, such support shall not include an obligation for ICANN to fund travel expenses incurred by GNSO participants for travel to any meeting of the GNSO or for any other purpose. However, ICANN has customarily furnished travel expenses for Nominating Committee appointed Council members to ICANN meetings. This custom is planned to continue, but is subject to the Bylaw statement. [Bylaws Article X, Section 4, see http://www.icann.org/general/bylaws.htm#X-4]

Nominating Committee will use the Criteria for Selection of ICANN Directors (see above) in choosing Selected Nominees for the GNSO Council. GNSO Council members are expected to support the ICANN mission and the implementation of ICANN's Core Values.

Role of the Nomcom Appointee

As discussed above the majority of the councillors are appointed by the constituencies and represent those constituencies in the council. Nom Com appointees, on the other hand, are not the representatives of any specific group, though they may choose to represent the interests of groups that are not currently represented in council. Most importantly Nom Com appointees should be people chosen, often from outside the GNSO constituencies and sometime from outside ICANN, who bring a fresh perspective into the council and who accept the responsibility to do their best to support ICANN in its mission and core values. Appointees should be people who can help the GNSO council to perform its duties; sometimes this may involve filling gaps in the skill set, at other times it may involve addressing a diversity or other demographic balance or may involve bringing a necessary perspective into the council that is not already present. Generally an appointee needs to fulfil several of these needs at the same time.

The Nominating Committee will also take into account the following eligibility factors and additional considerations.

GNSO Council Eligibility Factors

No person who serves on the Nominating Committee in any capacity is eligible for selection by any means to any position on the Board or any other ICANN body having one or more membership positions that the Nominating Committee is responsible for filling, until the conclusion of an ICANN annual meeting that coincides with, or is after, the conclusion of that person's service on the Nominating Committee. [Bylaws, Article VII, Section 8, see http://www.icann.org/general/bylaws.htm#VII-8]

No more than one officer, director, or employee of any particular corporation or other organization (including its subsidiaries and affiliates) shall serve on the GNSO Council at any given time. [Bylaws, Article X, Section 3(5), see http://www.icann.org/general/bylaws.htm#X-3.5]

Additional Considerations

For the GNSO Council position, specific experience related to the scope of the GNSO's work with the Domain Name System would be advantageous.

The current composition of the GNSO Council is available here http://gnso.icann.org/council/members.shtml

The Bylaws do not state a limit on the number of terms GNSO Council members may serve, although it is possible that term limits may be considered in future.

Time Commitment

The basic responsibilities of a GNSO Council member involve a minimum of 20 hours per month on Council related activities, with those chairing or participating in committees or task forces spending up to 60 hours a month or more. Depending on work load, for example during the weeks before the 3 face to face meeting, this can sometimes escalate to as much as 20 hours per week or more. The commitment for the 3 face to face meetings generally run about 7 days with council members having sometimes extensive responsibilities on most days. For those involved in Task forces or Working Groups, there may occasionally be additional face to face interim meetings

Task force members and councilors are not compensated for either time or teleconference costs though ICANN makes toll free numbers available whenever practical.

Additional GNSO criteria:

There are various criteria that should be considered when judging GNSO candidates. The first set of criteria are general and should be present in anyone appointed to the GNSO Council, while the second set of criteria reflect a diversity of skills that may be necessary. Depending on the composition of the sitting council, these skill based criteria will vary from year to year. Criteria that are considered especially important for the 2008 appointment are marked with (2008).

Baseline Criteria for anyone selected as a nomcom appointee:

  • Demonstrated experience working effectively in collaborative environments involving diverse interests.
  • Ability to chair, or otherwise assist, a multi-stakeholder group in reaching consensus
  • Basic knowledge of DNS systems and industry structure - registries, registrars. The goal is not to find technical DNS experts, but a minimal understanding of the DNS is needed to effectively function on the Council. For example appointees should understand something along the lines of "do you know what happens in the DNS when you send an email, or access a webpage". This requires an understanding of the general process of name resolution without requiring a precise technical description.

Variable Criteria that are useful to the GNSO

Part of the role of Nom Com appointees is to fill in gaps in the skill set of the Council. Some, but not all, of the skills that are highly useful in the process of GNSO Council work are listed below. The gap skills will vary year by year. Criteria that are especially important for the 2008 selection are marked with (2008)

  • Knowledge of
    • International Law (2008)
    • Competition law
    • Anti-trust law
    • Public interest
    • Consumer rights
    • Human rights
    • Economics especially market analysis (2008)
  • Intergovernmental expertise (2008)
  • Understanding of the special needs of financial services businesses
  • IDN expertise (2008)
  • DNS security expertise (2008)
  • Setting up of dispute and objection processes
  • Enforcement procedures and processes
  • Application software development - e.g multi-lingual support
  • Online collaborative work and consensus building technologies - wiki's etc
  • Statistics and survey analysis
  • Project management and document control processes

Additionally consideration may be given to Nom Com appointees who can help with the geographical or gender balance on the council as needed, as long as other necessary attributes and skills are also present.

Position: ccNSO Council

Number of Seats: 1
Start of Term: Conclusion of Annual Meeting 2008 End of Term: Conclusion of Annual Meeting 2011

The Country Code Names Supporting Organization (ccNSO) is a policy-development body which is responsible for developing and recommending to the Board global policies relating to country-code top-level domains (ccTLDs), nurturing consensus across the ccNSO's community, including the name-related activities of ccTLDs; and coordinating with other ICANN Supporting Organizations, committees, and constituencies under ICANN.

In addition to the above core responsibilities, the ccNSO may also engage in other activities authorized by its members, including: seeking to develop voluntary best practices for ccTLD managers, assisting in skills building within the global community of ccTLD managers, and enhancing operational and technical cooperation among ccTLD managers. The ccNSO consists of ccTLD managers that have agreed in writing to be members of the ccNSO, and a ccNSO Council responsible for managing the policy-development process of the ccNSO. Some ccNSO Council members are chosen by the ccNSO members within each of ICANN's Geographic Regions; Nominating Committee chooses three members with staggered terms.

ccNSO Council members receive no compensation for their services as ccNSO Council Members. Upon request of the ccNSO Council, ICANN shall provide administrative and operational support necessary for the ccNSO to carry out its responsibilities. As stated in the ICANN Bylaws, such support shall not include an obligation for ICANN to fund travel expenses incurred by ccNSO participants for travel to any meeting of the ccNSO or for any other purpose. However, ICANN has customarily furnished travel expenses for Nominating Committee appointed Council members to ICANN meetings. This custom is planned to continue, but is subject to the Bylaw statement. [Bylaws Article IX, Section 7, see http://www.icann.org/general/bylaws.htm#IX-7]

Nominating Committee will use the Criteria for Selection of ICANN Directors in choosing Selected Nominees for the ccNSO Council. CCNSO Council members are expected to support the ICANN mission and the implementation of the ICANN Core Values. Nominating Committee will also take into account the following eligibility factors and additional considerations.

ccNSO Eligibility Factors

1. No person who serves on the Nominating Committee in any capacity is eligible for selection by any means to any position on the Board or any other ICANN body having one or more membership positions that the Nominating Committee is responsible for filling, until the conclusion of an ICANN annual meeting that coincides with, or is after, the conclusion of that person's service on the Nominating Committee. [Bylaws, Article VII, Section 8, see http://www.icann.org/general/bylaws.htm#VII-8]

Additional Considerations

For the ccNSO Council positions, while no specific considerations are reflected in the Bylaws, experience or knowledge of ccTLDs and issues of importance to the global Internet, would be advantageous. Additionally, familiarity with the global environment in which ICANN operates and perspectives not otherwise reflected in the ccTLD community would be advantageous. Experience in international organizations and in developing new organizations is likewise valuable for these positions.

Time Commitment

An average ccNSO Council member would spend at least 12 hours per month on Council related activities, with those chairing committees or task forces spending at least 30 hours a month. (The commitment involves a minimum of 6 hours per month based on an average of 1.5 two-hour teleconferences (or physical meetings) per month plus about two hours of preparation for each meeting for reading task force reports and potentially discussing with the community. Participation in committees of the council and/or task forces could easily double that minimum time commitment.)

The Nom Com had some discussion about what "basic of knowledge of DNS" meant and it was something along the lines of "do you know what happens in the DNS when you send an email, or access a webpage". This is not a precise technical description, but an understanding of concepts of resolution.

Position: At-Large Advisory Committee (ALAC)

Number of Seats: 2

1 (Europe)
1 (North America)
Start of Term: Conclusion of Annual Meeting 2008 End of Term: Conclusion of Annual Meeting 2010

(for a definition of ICANN's geographic regions see http://www.icann.org/montreal/geo-regions-topic.htm)

The role of the At-Large Advisory Committee (ALAC) is to finalize the establishment of a mechanism for individual user participation in ICANN, through the accreditation of user organizations as At-Large Structures (ALS) and the creation of Regional At Large Organizations (RALOs). The ALAC also performs a role to consider and provide advice on the activities of ICANN, insofar as they relate to the interests of individual Internet users. Individual users may be consumers, non-for-profit or profit or business users but the key term is that they are 'individuals'.

ALAC Committee members, like the members of ICANN's other Advisory Committees, receive no compensation for their services as a member of a committee. The Board may, however, authorize the reimbursement of the actual and necessary expenses incurred by Advisory Committee members performing their duties as Advisory Committee members. [Bylaws Article XI, Section 6, see http://www.icann.org/general/bylaws.htm#XI-6]

Nominating Committee will use the Criteria for Selection of ICANN Directors (see above) in choosing Selected Nominees for ALAC. ALAC members are expected to support the ICANN mission and the implementation of the ICANN Core Values. Nominating Committee will also take into account the following eligibility factors and additional considerations.

ALAC Eligibility Factors

  1. No person who serves on the Nominating Committee in any capacity is eligible for selection by any means to any position on the Board or any other ICANN body having one or more membership positions that the Nominating Committee is responsible for filling, until the conclusion of an ICANN annual meeting that coincides with, or is after, the conclusion of that person's service on the Nominating Committee. [Bylaws, Article VII, Section 8, see http://www.icann.org/general/bylaws.htm#VII-8]
  2. The five members of the ALAC selected by the Nominating Committee shall include one citizen of a country within each of the five Geographic Regions (Europe; Asia/Australia/Pacific; Latin America/Caribbean Islands; Africa; and North America) established according to Bylaws Article VI, Section 5, see http://www.icann.org/general/bylaws.htm#VI-5. Only Citizens of the European and North American regions as defined in ICANN's definition of geographic regions http://www.icann.org/montreal/geo-regions-topic.htm are eligible for ALAC vacancies in 2008.

Additional Considerations

For the ALAC positions, experience and skills that bear on gathering, understanding, and communicating the interests of individual users would be advantageous. Perspectives not otherwise reflected in the existing ALAC membership would be advantageous. Nominating Committee's selections for ALAC are intended to diversify the skill and experience sets of the ALAC, including in such areas as group decision-making.

Current composition of the ALAC is available at http://www.icann.org/committees/alac/

The Bylaws do not state a limit on the number of terms ALAC members may serve.

Time Commitment

The basic responsibilities of a member of the ALAC is approximately 18 hours each month. This includes participating in online (e-mail) discussions, commenting on/contributing to documents/proposed actions (drafted in English), participating in monthly ALAC telephone conferences (in English), and meeting with/making presentations to, local and regional organizations. ALAC members serving as liaisons to other Supporting Organizations and to the Board can expect to spend more than this basic 18 hours per month.

ICANN has traditionally reimbursed expenses incurred by ALAC members for attending ICANN meetings.

The Nom Com had some discussion about what "basic of knowledge of DNS" meant and it was something along the lines of "do you know what happens in the DNS when you send an email, or access a webpage". This is not a precise technical description, but an understanding of concepts of resolution.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."