Skip to main content

2016 ICANN Nominating Committee

Background | Timeline | Members | 360 Reviews | Committee Documents | Report Cards | Conflicts


NomCom 360 Reviews

Committee Documents

Board and Community Recommendations to NomCom


  • Interview with ICANN's NomCom Leadership at ICANN 55 in Marrakech
  • Interview with ICANN's NomCom Leadership at ICANN 54 in Dublin

Reporting Conflicts or Misconduct

The 2016 NomCom agreed to implement NC15 Recommendation 1 which states:

  1. "NC15 Recommends a Whistleblower email for the 2016 NomCom to use if members need to report misconduct. The system should allow conflicts to be declared even if it is the Chair that is suspected of being in conflict. The system should also be designed to be useable by the community and as such, the email should be published and advertised on the NomCom2016 website. NomCom Staff should be the administrators of the mailbox and share information with ICANN Legal for further review."

The community and NomCom members may report misconduct or suspected conflict of NomCom mmebers by sending an email to

Application Period Closed – updated 21 April 2016

Apply Now for ICANN Leadership Positions: Deadline is 20 March 2016

Date: 17 December 2015

The Internet Corporation for Assigned Names and Numbers' (ICANN) Nominating Committee (NomCom) invites interested individuals to submit applications and/or to recommend candidates for ICANN's key leadership positions. Applications in 2016 are invited for the following positions:

  • Three members of the ICANN Board of Directors*
  • Two At-Large Advisory Committee (ALAC) representatives (one each from the Europe and North America regions)
  • One member of the Council of the Generic Names Supporting Organization (GNSO)
  • One member of the Council of the Country-Code Names Supporting Organization (ccNSO)

*Per Article VI, Section 5 of the ICANN Bylaws, ". . . at all times each Geographic Region shall have at least one Director, and at all times no region shall have more than five Directors on the Board (not including the President). As used in these Bylaws, each of the following is considered to be a 'Geographic Region': Europe; Asia/Australia/Pacific; Latin America/Caribbean islands; Africa; and North America." For additional information see Board Geographic Diversity section below.

Open Leadership Positions - To be filled by the 2016 NomCom

Individuals selected by the NomCom will have a unique opportunity to work with accomplished colleagues from around the globe and help shape the Internet's technical coordination and policy development.

Those selected will also gain valuable insights and experience from working across boundaries of knowledge, responsibility, culture and geography. They will be making a valuable public service contribution towards the functioning and evolution of this essential global resource. Guided by the broad public interest, those selected will work to fulfill ICANN's mission to coordinate the global Internet's systems of unique identifiers, and in particular to ensure its stable and secure operation.

Fluency in English is a requirement for all positions.

These positions require regular participation in teleconferences and may involve significant international travel, including travel to ICANN's three annual Public Meetings. Recent ICANN Public Meetings were held in Singapore, Buenos Aires, and Dublin. Meetings during 2016 will be held in Marrakech (5 – 10 March 2016), Helsinki and Hyderabad.

Reasonable direct expenses incurred in the course of service will be reimbursed.

Each Board Member has the option to receive compensation in accordance with the resolution passed by the Board on 30 July 2014, but is not required to do so. (See

Leadership Positions Information

The following documents provide detailed information (descriptions, criteria and time commitment) about the key Leadership Positions.


Please submit applications for the positions described above through the on-line application request form at ( or by emailing

All applications are confidential and should be received by 20 March 2016 (23:59 UTC) for full consideration. Selections will be announced in August or September 2016. Successful candidates will take up their positions following ICANN's Annual Meeting in October 2016.

Candidate Recommendations

Candidate recommendations are encouraged and can be submitted through an on-line form at

Board Geographic Diversity

Open Leadership Positions - To be filled by the 2016 NomCom

Current NomCom-selected Board members include: Cherine Chalaby, Steve Crocker, Asha Hemrajani, Rafael Litto Ibarra, Bruno Lanvin, Erika Mann, George Sadowsky and Lousewies Van der Laan


2016 NomCom Timetable

How the NomCom Works: a walk-through of the main steps in the NomCom process

Outreach/Application Phase

  • 23 – 24 Oct 2015: 2016 NomCom convened in Dublin, Ireland
    • Outreach opportunities discussed and planned
  • 17 Dec 2015 – 20 Mar 2016: Candidate Application Period
    • Interested individuals complete and submit the online Candidate Application Request Form to begin the application process. NomCom staff (Joette Youkhanna and Jia Kimoto) sends an email acknowledging that the Application Request Form was received.
    • Individual candidate applications are created in the RESTRICTED NomCom wiki platform for those that have submitted a Candidate Application Request Form. Each candidate is notified of their unique login credentials needed to access their application forms and information about the application process
    • NomCom staff monitors candidate applications for completeness during the application period. Applications in which candidates have indicated their application is complete are reviewed by NomCom staff and acknowledges the forms are complete or if information is missing.
    • As the end of the application process approaches, NomCom staff sends reminders to candidates that have not completed their applications
  • 20 March 2016 at 23:59 UTC: Application Period Ends
    • The online Application Request Form is disabled.
  • 20 – 28 Mar 2016: Wiki Application Grace Period
    • Grace period for candidates to complete their personalized application forms on the NomCom’s RESTRICTED wiki platform. Candidate applications that are incomplete will not be considered.
  • 29 March 2016: Wiki Applications Restricted
    • Candidates are notified the application period has ended and the NomCom wiki is restricted to only NomCom members.

Assessment Phase

  • 29 March to early-June 2016: Review, Evaluation and Shortlisting of Candidates
    • Candidate references are contacted requesting they provide a reference
    • NomCom members review Candidate information, deliberate and agree on shortlisted candidates.
    • Assessment consultant performs interviews and provides NomCom with Scorecard (assessment summary) of each candidate interviewed.
    • NomCom ‘Deep Dive’ teams formed and perform more in depth assessment of shortlisted candidates which may include phone interviews.
    • Shortlisted Board candidates are advised of the Board retreat in Istanbul, Turkey from 15 – 17 September 2016 and invited to participate if selected.
    • SO/AC shortlisted candidates will be advised of dates of on-boarding/training sessions that they should plan to attend.

Selection Phase

  • 26 – 30 June 2016: Interviews with Shortlisted Board Candidates (during ICANN56 Meeting) in Helsinki, Finland
  • 1 – 2 July 2016: NomCom Selection Meeting in Helsinki, Finland
  • Early July 2016: Selected Nominees Notified
    • Selected nominees are notified individually by email they have been and due diligence begins
  • Early July 2016: The Secretary of ICANN Notified of Selected Nominees
    • given written notice of the NomCom’s selected nominees (Board, GNSO, ALAC and ccNSO)
  • Early July – early September: Due Diligence of Selected Nominees
  • September 2016: Selected Nominees Announced
    • NomCom publicly announces the 2016 NomCom selected nominees
  • 15 – 17 September: Board Retreat in Istanbul
    • Board selected nominees attend the Board Retreat in Istanbul, Turkey
  • 29 October – 4 November 2016: ICANN57 in Hyderabad, India
    • Selected Nominees attend ICANN57 meeting and take their positions at the conclusion of the ICANN Annual General Meeting.

Outreach Opportunities

2016 NomCom Outreach Opportunities by Region

Members | Bios | Organizational Chart – (Group Photo)

Leadership Team: Stephane Van Gelder, Chair; Hans Petter Holen, Chair Elect; Wolfgang Kleinwächter, Associate Chair

Committee Members: Alejandro Acosta (RSSAC), Thomas Barrett (GNSO/Registrars SG), Steve Coates (GNSO/CBUC-Large), Eduardo Diaz (ALAC-NA), William Drake (GNSO/NCUC), Hartmut Glaser (ASO-AC), Zahid Jamil (GNSO/CBUC-Small), Dave Kissoondoyal (ALAC-AF), Yrjo Lansipuro (ALAC-EU), Sylvia Herlein Leite (ALAC-LAC), Osvaldo Novoa (GNSO/ISPCP), Amir Qayyum (ALAC-AP), Jörg Schweiger (ccNSO), Mark Seiden (SSAC), Ellen Shankman (until April 2016), Damon Ashcraft (GNSO-IPC), Ken Stubbs (GNSO/Registries SG) and Tim Wicinski (IAB for IETF)

Nominating Committee Member Biographies

Committee Organization Chart [PDF, 235 KB]

NomCom Staff Support: Joette Youkhanna (Senior Project Manager) and Jia Kimoto (Project Manager)


The Nominating Committee (NomCom) is an independent committee tasked with selecting eight members of the Board of Directors and other key positions within ICANN's structure.

It is designed to function independently from the ICANN Board, Supporting Organizations, and Advisory Committees. NomCom members act only on behalf of the interests of the global Internet community and within the scope of the ICANN mission and responsibilities assigned to it by the ICANN Bylaws.

NomCom members contribute understanding of the broad interests of the Internet community as a whole, and knowledge and experience of specific Internet constituencies who have appointed them.

The challenge for the NomCom is to integrate these perspectives and derive consensus in its selections. Although appointed by Supporting Organizations and other ICANN bodies, individual NomCom members are not accountable to their appointing bodies.

NomCom members are accountable for adherence to the ICANN Bylaws and for compliance with the rules and procedures established by the NomCom.

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"""" is not an IDN."