Skip to main content

ICANN Nominating Committee (NomCom) Operating Procedures 2020


  1. Modifications to NomCom Operating Procedures
  2. Obligations of NomCom Members
  3. Vacancies and Removal from NomCom
  4. Handling of Sensitive Information
  5. Terminology
  6. Internal Communications and Relations
  7. External Communications and Relations
  8. Criteria for Selection for ICANN Directors, PTI Directors GNSO Council Members, ALAC Members, and ccNSO Council Members
  9. Eligibility Factors for ICANN Directors, PTI Directors, GNSO Council Members, ALAC Members, ccNSO Council Members
  10. Review and Evaluation of Candidates
  11. Miscellaneous aspects related to logistics and planning
  1. Modifications to NomCom Operating Procedures

    Considerable care has been taken in developing the NomCom Operating Procedures (Procedures). In setting and publicizing its Procedures, the NomCom reserves the right to modify them in the course of its work in order to ensure efficiency and effectiveness in fulfilling its responsibilities. If the NomCom concludes that modification of these Procedures is necessary, the NomCom will post the changes on the NomCom web page.

  2. Obligations of NomCom Members

    Notwithstanding their being a delegate of their sending Organization, Group or Committee, members of the NomCom have an obligation to act independently and in the larger public interest and not act as representatives of, or lobby or advance the interest of, any particular Organization, Group or Committee, in particular with respect to the assessment and selection of Candidates.

    NomCom members are expected to engage in outreach, recruitment, and information gathering; to read the submitted and gathered information about each Candidate under consideration; to participate in both deliberations about individual Candidates and construction of slates of Candidates that will fulfill the requirements for each of the ICANN bodies for which the NomCom selects leadership members; to participate in NomCom teleconferences; to work diligently with NomCom colleagues toward an overall consensus on the best possible group of Candidates to be selected; and to adhere to the Participation Agreement.

    NomCom members are strongly encouraged to travel to face-to-face meetings; and in joining the NomCom, all members make a commitment to attend the selection meeting; however, provisions for participation via teleconference will be arranged for members unable to attend in person.

  3. Vacancies and Removal from NomCom

    Vacancies that may occur in the NomCom may be filled for the remainder of the term by the same means through which the position was initially filled. In the event that a NomCom member is removed for any reason, he/she is obligated to delete all NomCom-related material. In the event that a member of the ICANN organization staff supporting the NomCom is removed for any reason, he/she is obligated to arrange for secure transfer of all NomCom-related material to a NomCom designated person, and then to delete all NomCom-related material from his/her own records in any form.

    Where a NomCom member is in breach of:

    • 3.1. The Participation Agreement for not properly dealing with a Conflict of Interest by failing to report it appropriately or failing to abide by the decision of the Conflicts of Interest Sub-Committee;
    • 3.2. Any requirement related to handling of Sensitive Information or Confidentiality;
    • 3.3. The Participation Agreement by furthering or attempting to further the interests or goals other than those that are the obligation of the NomCom with respect to any Candidate(s) (such as the obligation not to promote the interests of any Advisory Committee (AC) or Supporting Organization (SO), or other group, over that of the NomCom's objective assessment and selection of Candidates as required by the ICANN Bylaws, the Participation Agreement and these Procedures); or
    • 3.4. The ICANN Bylaws, the Participation Agreement, these Procedures, any obligations agreed to by the member or any applicable rule or legal requirement, following notice to the NomCom member and, if selected by an SO constituency or AC, following notice to that SO constituency or AC, that NomCom member may be removed by a majority vote of all NomCom members entitled to vote. In such a scenario, the member who is the subject of the removal action shall not be entitled to vote on such an action or be counted as a voting member of the NomCom when calculating the required majority vote. Each vote to remove a NomCom member shall be a separate vote on the sole question of the removal of that particular member.

    In the event that an allegation is made to the NomCom Chair or Chair-Elect about a member of the NomCom having breached the NomCom Participation Agreement, the rules of confidentiality set out in the ICANN Bylaws, ICANN's Expected Standards of Behavior or these Procedures, the NomCom member alleged to have breached any of the above shall be privately notified of the allegation and asked for an explanation/response.

    1. If NomCom leadership and the person alleging the breach(es) are satisfied with the explanation then the matter shall be considered concluded.
    2. If NomCom leadership and the person alleging the breach(es) are not satisfied with the explanation the procedure below shall be followed:

      1. NomCom leadership shall task the NomCom Conflicts Committee to investigate the allegation(s).
      2. The NomCom Conflicts Committee shall interview all persons available who have relevant knowledge of the alleged improper conduct.
      3. The NomCom Conflicts Committee shall then ask the member who is the subject of the allegation(s) to meet with the Conflicts Committee.
      4. The NomCom Conflicts Committee shall give the member who is the subject of the allegation(s) full disclosure of the allegations and the information provided to the committee during its investigation.
      5. The member who is the subject of the allegation(s) shall be given full opportunity to respond to the allegations during an interview with the NomCom Conflicts Committee.
      6. The NomCom Conflicts Committee shall write up a full report of its work in addressing the allegation(s) and provide that report to NomCom leadership for distribution to the whole NomCom for review.
      7. The NomCom, after its review of the report, shall discuss the report of the NomCom Conflicts Committee at a meeting scheduled for that purpose and shall then vote on whether to remove the member who is the subject of the allegation(s) or take any other action deemed appropriate.

    A member of the ICANN organization staff supporting the NomCom may be removed by the Chair of the NomCom, following notice to the ICANN President and CEO.

  4. Handling of Sensitive Information

    The nature of the NomCom functions and activities requires confidentiality for some information (such as deliberations) and openness for other information (such as these Procedures).

    Any information that relates to an individual and can be used to identify the individual by name or can be used in context with other information to lead to identifying such person will be marked "Confidential: NomCom Sensitive" whether the information is in physical or electronic form. A designation that anonymizes a Candidate's identifying information, with a number or in another commonly accepted manner, will not be considered NomCom Sensitive. However, any "Key List" that connects a Candidate's name to an anonymized designation will be considered NomCom Sensitive.

    NomCom members agree to keep all NomCom Sensitive information confidential.

    Access to NomCom Sensitive information shall be restricted only to NomCom members and ICANN organization staff supporting the NomCom who have signed the NomCom Participation Agreement. NomCom members' confidentiality obligations shall be continuing and will survive a member's resignation or termination from the NomCom.

    To the greatest extent practical, NomCom Sensitive information will be stored only in a non-public central repository, which members can access on a read-only basis. Access controls and security safeguards protecting this information must comply with highest standards used by ICANN for protecting user authentication, confidentiality, and data integrity. Mechanisms must be in place that provide for the ability to identify and distinguish between NomCom Sensitive information and non-sensitive information. This will enable NomCom Sensitive information to be destroyed or otherwise disposed of after the conclusion of the NomCom deliberations each year without risking the loss of files that are needed for archival purposes.

    NomCom members agree to take all reasonable steps to dispose of any NomCom Sensitive information in their possession, custody or control after the conclusion of the NomCom deliberations each year.

  5. Terminology

    The term "Candidate" will be reserved for those individuals who agree to be considered by the NomCom and for whom all required information in the Application has been received.

    The term "Selected Nominee" is reserved to refer to a Candidate selected by the NomCom for a position for which it is charged to fill.

  6. Internal Communications and Relations

    • 6.1. Communications and Meetings

      The NomCom will conduct its business in English.

      The NomCom will carry out its work primarily through teleconferences and email. When proposed for immediate decisions, draft materials for the NomCom's work should normally be distributed at least five working days in advance of the meetings.

      The Chair will seek to facilitate confidential communications in a way that makes the most sense for the NomCom members.

    • 6.2. Quorum

      At any meeting of the NomCom a minimum 10 of the total number of current NomCom voting members shall constitute a quorum for the transaction of business. The act of a majority (more than 50%) of the voting members present at any meeting at which there is a quorum shall be the act of the NomCom. Every vote will require a minimum of 10 votes to be cast.

      Provided that any vote undertaken for the purposes of the ICANN Bylaws or as provided in these procedures shall require a majority (over 50%) of the total number of current NomCom voting members to be present to constitute a quorum for the transaction of business related to a vote. The act through a vote of a majority (more than 50%) of current NomCom voting members when at any meeting at which there is a quorum to conduct a vote for the purposes of the ICANN Bylaws or as provided in these procedures shall be the act of the NomCom.

      If a quorum shall not be satisfied at any meeting of the NomCom, the members present at that meeting may discuss any matters but not take any decisions or may adjourn the meeting to another place, time or date. If the meeting is adjourned for more than twenty-four (24) hours, notice shall be given to those members not at the meeting at the time of the adjournment.

    • 6.3. Volunteer Service and Expense Reimbursement

      NomCom members serve as volunteers, without compensation. This contribution is respected and appreciated. Reimbursement of reasonable, documented and necessary expenses will be available for travel to face-to-face meetings and to outreach events as approved by the NomCom Chair, in accordance with applicable terms of ICANN's travel reimbursement policy. Reimbursement will not be made for any expenditure without prior approval from the Chair. Provisions will be made to alleviate any financial burden placed on individual NomCom members resulting from teleconference participation, such as long distance telephone charges when alternatives are not available.

    • 6.4. Voting

      Voting in all matters within the NomCom shall be conducted in accordance with the ICANN Bylaws. Whenever the Chair calls for a vote on any matter, votes of NomCom members designated as voting members under ICANN Bylaws shall be counted. [Reference: ICANN Bylaws Article 8, Section 8.2]

      Matters that constitute the act or decisions of the NomCom in particular, which are outcome determinative with respect to the selection or non-selection of any Candidate within the process of assessments or selections by the NomCom shall be deemed to be a vote.

      All NomCom members (including non-voting members) may participate in all discussions and deliberations (unless a conflict of interest has been determined to be present).

    • 6.5. Access to Information

      The NomCom Chair will maintain a non-public central repository of information about Candidates under consideration, including available background, professional information, and all other gathered information. All NomCom members will have access to the information in the non-public central repository. The non-public central repository is confidential to NomCom members and ICANN organization staff supporting the NomCom, and to any and all outside consultants who may be retained by the NomCom to assist with any phase of its work, as is appropriate with respect to the terms of their engagement.

      At the conclusion of the NomCom process, the Chair will seek the consent of unsuccessful Candidates for retention of their Application for the next NomCom's consideration and will only retain that information if such consent is granted. The Chair will also retain the Application of Candidates who wish to be considered for any interim vacancies that may occur. No information for other individual Candidates will be retained.

      Concerning the internal communications, the rules described in point 3.c of the Participation Agreement apply.

  7. External Communications and Relations

    • 7.1. Transparency

      In balancing the requirements of transparency and confidentiality, the NomCom will follow the principle that process is transparent and data (i.e., information relating to Candidates) is kept confidential. The NomCom will publish these Procedures, Participation Agreement and other relevant documents on its webpage on the ICANN website. The Chair, in consultation with the other NomCom members, will establish and publicize milestones, deadlines and updates, including the public call for suggestions for Candidates, so as to keep the public duly informed and to allow the NomCom to complete its work in a timely way.

      The NomCom will hold a public meeting session at ICANN67 Cancún.

      The NomCom Chair will serve as the official spokesperson for the NomCom.

    • 7.2. Recruitment Consultations

      The NomCom will engage proactively in consultations with the various elements of the ICANN community in its recruitment efforts. Contacts will include the Internet Engineering Task Force (IETF), the Security and Stability Advisory Group (SSAC), the Root Server System Advisory Committee (RSSAC), the Regional Internet Registries (RIRs), the Address Council, the generic top level domain (gTLD) and the country code top level domain (ccTLD) registries and registrars, the technical liaison group, the Council (constituencies and stakeholder groups) of the Generic Names Supporting Organization (GNSO), the Council and constituencies of the country code Names Supporting Organization (ccNSO), and the At-Large Advisory Committee (ALAC). Focused consultations will be held with the bodies that the NomCom partly populates, in order to inform and update the NomCom about desired skill sets.

      The success of the NomCom will depend in no small measure on the willingness and ability of NomCom members to engage in affirmative recruitment of excellent Candidates. The NomCom will use all readily available means to publicize and otherwise inform about the call for Candidate Applications.

      In order to encourage NomCom members to do their best to identify and recruit outstanding Candidates, each NomCom member will be asked to share and present action plans on identifying Candidates for the bodies to be populated in part by the NomCom.

    • 7.3. Public Input

      The NomCom will call publicly for Candidate Applications from, inter alia, across the global Internet community to find the talent and experience needed for the positions it fills, to inform the community of the NomCom's progress and decisions, and to generate the confidence and respect of the community for those positions that the NomCom selects.

      The NomCom will actively seek suggestions for potential Candidates to enlarge and enhance the pool of Candidates. A suggestion, however, is not a requirement for consideration by the NomCom, for which a subsequent self-nomination is essential.

      The NomCom Chair will provide a minimum of 60 days notice for interested parties to submit an Application.

      Because the NomCom will conduct its work in English, all submissions to the NomCom must be provided in English.

      All Applications will be acknowledged in a timely fashion, using the contact information provided by the submitter.

      The NomCom will provide a one-way communication mechanism (email or web-based) through which the public can easily provide input to assist the NomCom in its work.

    • 7.4. Confidentiality and Privacy

      All NomCom members and ICANN organization staff supporting the NomCom will safeguard all internal NomCom Sensitive information and treat it as strictly private, confidential, and for the use of immediate committee members and organization staff supporting the NomCom only.

      Communications within the NomCom are limited to the NomCom members and ICANN organization staff supporting the NomCom. Members may not designate alternates or include assistants or other associates.

      NomCom members will not disclose outside of the NomCom any of the discussions, deliberations, communications, record and notes about the Candidates. Further, NomCom members and ICANN organization staff supporting the NomCom will not disclose outside of the NomCom the identities of the Candidates under consideration by the NomCom, unless the NomCom as a whole has decided to do so and the explicit consent of the Candidate(s) in question has been obtained. The NomCom can agree to make justified exceptions to this rule for specific purposes, such as Candidate assessment by an external consultancy, due diligence process, and Candidate travel support for face-to-face interviews. Confidentiality of Candidate identities shall be assured in such exceptional cases.

      Note that because the NomCom will need to check references and consult with selected third-party sources on a confidential basis before making its selections, those wishing to be considered as Candidates are required to confirm their understanding of the confidentiality arrangements when they submit an Application.

      When the NomCom has completed its selection of Nominees for the positions that it is charged to fill, including a due diligence verification of Nominee credentials, the NomCom will publish the identities of the Selected Nominees.

      The processes that the NomCom may implement and follow, and any statistical information that does not identify individual Candidates (for example, information about the size and nature of the Candidate pool) may be published.

  8. Criteria for Selection for ICANN Directors, PTI Directors, GNSO Council Members, ALAC Members, and ccNSO Council Members

    The NomCom will apply the criteria for selection and terms of eligibility, as defined in the applicable ICANN Bylaws, to identify a strong pool of qualified Candidates that meet the highest standards of integrity and capability.

    To select from this pool of qualified Candidates, the NomCom will take into account relevant and additional considerations related to the roles to be filled as the selection process progresses, with particular regard to the ICANN Bylaws requirements and desired skill sets as identified through written communication with relevant ICANN bodies.

    By doing so, the NomCom seeks to ensure that ICANN can benefit from individuals who place the public interest of the global Internet community ahead of any particular special interests, but who nevertheless are, or commit themselves to becoming, knowledgeable about the environment in which ICANN operates. The NomCom also seeks those Candidates who will reflect the functional, geographic, and cultural diversity of the Internet community at all levels of policy development and decision-making. [Reference: ICANN Bylaws Article 1, Section1.2(b)(ii); Article 7, Section 7.2(b); and Article 8, Section 8.4]

    In the following, general information is provided about the roles of the positions to be filled. For a more detailed description relating to the most current year, see the documents "Open Leadership Positions." In consultation with the ICANN community, these selection criteria will be updated each year to reflect the needs of ICANN, the Supporting Organizations and Advisory Councils.

    • 8.1. Roles of the Positions to Be Filled

      The NomCom will be selecting its Nominees with careful consideration of the roles they fill:

      1. ICANN 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. [ICANN Bylaws Article 2, Section 2.1 and Article 7, Section 7.7]
      2. PTI Directors as mandated by the PTI Bylaws [Bylaws of Public Technical Identifiers Article 5].
      3. The GNSO Council is responsible for managing the policy development process of the GNSO. [ICANN Bylaws Article 11, Section 11.3(d)]
      4. The ALAC is to consider and provide advice on the activities of ICANN, insofar as they relate to the interests of individual users. [ICANN Bylaws Article 12, Section 12.2(d)]
      5. The ccNSO Council is responsible for managing the policy-development process of the ccNSO. [ICANN Bylaws Article 10, Section 10.3(h)]
      6. For all these positions, the NomCom will apply the selection criteria in the ICANN Bylaws for ICANN Directors [see below]. The NomCom may use additional considerations for the GNSO Council, ALAC, and ccNSO Council positions to support the specific roles of these entities [see below].
    • In the following, general information is provided about the criteria for the positions to be filled. For a detailed description relating to the most current year, see the document "Open Leadership Positions."

    • 8.2. Criteria for Selection of ICANN Directors [ICANN Bylaws, Article 7, Section 7.3]

      ICANN Directors shall be:

      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 7.3;
      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; and
      5. Persons who are able to work and communicate in written and spoken English.
    • 8.3. Additional Considerations for PTI, GNSO, ALAC and ccNSO Positions

      The criteria for selection for PTI Board shall be as per PTI Bylaws.

      The criteria for selection of the GNSO Council, ccNSO Council, and At Large Advisory Committee members are less specifically defined in the ICANN Bylaws, but the NomCom notes the "Legislative History" behind the decision for the NomCom to select some individuals to the above committees. [ICANN: A Blueprint for Reform, Section 3 (20 June 2002) and Final Implementation Report and Recommendations, Section 3(C) (2 October 2002)]

      The NomCom is looking for individuals who have demonstrated the maturity, experience, knowledge and skills to handle the tasks and make the judgments involved in fulfilling the roles of GNSO Council Members, ccNSO Council Members, and ALAC Members.

      1. Additional Considerations for the GNSO Council Positions

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

      2. Additional Considerations for the ALAC Positions

        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. The NomCom's selections for ALAC are intended to diversify the skill and experience sets of the ALAC, including in such areas as group decision-making. Over time these NomCom selections present an opportunity to connect with the interests of individual users from all categories.

      3. Additional Considerations for the ccNSO Council Positions

        For the ccNSO Council positions, while no specific considerations are reflected in the ICANN 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 likewise be advantageous.

  9. Eligibility Factors for ICANN Directors, PTI Directors, GNSO Council Members, ALAC Members, ccNSO Council Members

    • 9.1. Eligibility Factors for ICANN Directors

      1. In carrying out its responsibilities to nominate the Directors for Seats 1 through 8 for designation by the EC, the Nominating Committee shall ensure that the Board is composed of Directors who, in the aggregate, display diversity in geography, culture, skills, experience, and perspective, by applying the criteria set forth in Section 7.3, Section 7.4 and Section 7.5. At no time when it makes its nomination shall the Nominating Committee nominate a Director to fill any vacancy or expired term whose designation would cause the total number of Directors (not including the President) from countries in any one Geographic Region to exceed five; and the Nominating Committee shall ensure when it makes its nominations that the Board includes at least one Director who is from a country in each ICANN Geographic Region ("Diversity Calculation"). For purposes of this Section 7.2(b), if any candidate for director maintains citizenship of more than one country, or has been domiciled for more than five years in a country of which the candidate does not maintain citizenship ("Domicile"), that candidate may be deemed to be from either country and must select in his or her Statement of Interest the country of citizenship or Domicile that he or she wants the Nominating Committee to use for Diversity Calculation purposes. For purposes of this Section 7.2(b), a person can only have one Domicile, which shall be determined by where the candidate has a permanent residence and place of habitation. [Article 7, Section 7.2(b)]
      2. Notwithstanding anything herein to the contrary, no official of a national government or a multinational entity established by treaty or other agreement between national governments may serve as a Director. As used herein, the term "official" means a person (i) who holds an elective governmental office or (ii) who is employed by such government or multinational entity and whose primary function with such government or entity is to develop or influence governmental or public policies. [Article 7, Section 7.4(a)]
      3. 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. If such a person is identified by, or presents themselves to, the Supporting Organization Council or the At-Large Community for consideration for nomination to serve as a Director, the person shall not thereafter participate in any discussion of, or vote by, the Supporting Organization Council or the committee designated by the At-Large Community relating to the nomination of Directors by the Council or At-Large Community, until the Council or committee(s) specified by the At-Large Community has nominated the full complement of Directors it is responsible for nominating. In the event that a person serving in any capacity on a Supporting Organization Council is considered for nomination to serve as a Director, the constituency group or other group or entity that selected the person may select a replacement for purposes of the Council's nomination process. In the event that a person serving in any capacity on the At-Large Advisory Committee is identified as or accepts a nomination to be considered for nomination by the At-Large Community as a Director, the Regional At-Large Organization or other group or entity that selected the person may select a replacement for purposes of the At-Large Community's nomination process. [Article 7, Section 7.4(b)]
      4. Persons serving in any capacity on the Nominating Committee shall be ineligible for nomination or designation to positions on the Board as provided by Section 8.8. [Article 7, Section 7.4(c)]
      5. No person who serves on the EC Administration while serving in that capacity shall be considered for nomination or designated to the Board, nor serve simultaneously on the EC Administration and as a Director or Liaison to the Board. [ICANN Bylaws Article 7, Section 7.4(d)]
    • 9.2. Eligibility Factors for PTI Directors shall be as per the PTI Bylaws.

    • 9.3. Eligibility Factors for GNSO Council Members

      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. [ICANN Bylaws Article 11, Section 11.3(e)]

    • 9.4. Eligibility Factors for ALAC Members

      The five members of ALAC selected by the NomCom shall include one citizen of a country within each of the five Geographic Region (Europe; Asia/Australia/Pacific Islands; Latin America/Caribbean Islands; Africa; and North America) established according to ICANN Bylaws Article 7, Section 7.5. [ICANN Bylaws Article 12, Section 12.2(d)(ii)]

    • 9.5. Eligibility Factors for ccNSO Council Members

      There are no additional Bylaw eligibility considerations for ccNSO Council Members selected by the NomCom.

  10. Review and Evaluation of Candidates

    While the NomCom process differs from an election, the goal is the same —a thorough process leading to the selection of very well-qualified individuals to fulfill the specific roles of the envisaged positions.

    The NomCom will post on the NomCom webpage a timeline with identified activities and milestones. The NomCom reserves the right to adjust its timeline within the boundaries of the Bylaws requirements. Adjustments of the NomCom's timeline will be posted on the NomCom webpage.

    Additional information on the NomCom process will be included in the Formal Call for Candidates, and in subsequent updates, which will be posted on the NomCom webpage.

    The NomCom will begin its review of Candidate information contained in the completed Application as soon as it has received all required information.

    The NomCom will evaluate Candidates in a fair and consistent manner, considering the Application, references and, as needed, interviews, consultations, and third-party information sources. While doing so, it will adhere to its Participation Agreement. At all times, NomCom members and staff shall treat all Candidates in a respectful and considerate manner.

    The NomCom will need to carry out due diligence, as appropriate, regarding Candidates it wishes to consider. For this purpose, the NomCom will arrange (with the consent of these Candidates as noted in the Application Form) to verify credentials and consult with others not named by the Candidate on a confidential basis.

    The NomCom will provide Candidates with updates as appropriate on progress of the selection process.

    See also Section 8 above which describes the criteria and additional considerations that will be taken into account in the NomCom selections. Section 9 describes the eligibility factors. The NomCom will also take into account the continuing membership of the Board (and other such bodies) to ensure that the persons it nominates to serve as Director and selects shall, to the extent feasible and consistent with other criteria required to be applied by ICANN Bylaws Article 8, Section 8.4 and guided by the ICANN Bylaws Article 1, Section 1.2(b)(ii).

    Note that endorsements by organizations or groups and lists of signatories are not appropriate and will not be influential in the NomCom's selections. The NomCom will not accept unsolicited comments about a Candidate from any third party.

    Approximately two months before the commencement of each ICANN Annual Meeting, the NomCom shall give the EC Administration (with a copy to the Decisional Participants and Secretary) written notice of its nomination of Directors for seats with terms beginning at the conclusion of the annual meeting, and the EC Administration shall promptly provide the Secretary (with a copy to the Decisional Participants with written notice of the designation of those Directors. All such notices shall be posted promptly to the Website. [ICANN Bylaws Article 7, Section 7.8(c)].

  11. Miscellaneous aspects related to logistics and planning

    The NomCom will meet face to face on four occasions through its cycle:

    • At the three ICANN meetings scheduled in 2019–20 at or around the same time as the ICANN meetings scheduled in Montréal (kick-off meeting), Cancún (assessment meeting) and Kuala Lumpur (final selection meeting).
    • The NomCom will also meet in person at one intercessional.

    With respect to any of its face-to-face meetings the NomCom may nominate one primary and one alternate (in case the primary venue/accommodation is unavailable) venue and/or accommodation and submit them to ICANN along with specified dates for its face-to-face meetings 90 days prior to the meeting. ICANN shall confirm the availability of the venue/ accommodation within 14 business days thereafter.

    ICANN organization shall ensure IT and Tech Support and normal meeting support to be provided at the venue and accommodation throughout the period of the stay of the NomCom members at the venue and accommodation.

    The Leadership may instruct ICANN organization staff supporting the NomCom to work with ICANN organization staff to contract resources for any purposes such as recruitment, vetting, due diligence, training or other vendor services, such as consultants, trainers or courses/informational materials either throughout the year or at the face-to-face meetings of 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."