Skip to main content

Fellowships Committee

ICANN Fellowship Program

Superseded by

20 November 2007

The Fellowships Committee (FC) will be responsible for selecting which applicants will receive fellowships to the ICANN International public meetings, utilizing the vetted applications garnered through the online application system. The Committee will also advise ICANN staff on how the programme could be improved.

Terms of Reference

  1. Objectives

    The objectives of the FC are:

    1. To select fellows from among the applicants based on their conformity with the criteria outlined in the application and the evaluation process outlined in this document.
    2. To act as a resource to the ICANN Board and staff by providing information and feedback on the planning, implementation and evaluation of the fellowships programme.
    3. To conduct outreach in support of the fellowships program and to create a pool of potential future members of the selection committee.
  2. Membership

    1. The FC shall be made up of no less than 4 and no more than five (5) representatives of the public with a strong history of experience with technical Internet issues, developing countries and/or Internet related development work, fellowships programmes and/or non profit experience.
    2. Membership shall strive to include representatives from each of the ICANN regions.
    3. In the event that the FC determines that its membership or terms of reference are not appropriate it shall have the power to recommend to ICANN staff amendments to these Terms of Reference.
    4. Membership is at the invitation of ICANN staff.
    5. An ICANN staff member will act as the FC committee Secretariat.
  3. Terms of Service

    1. Members will serve for a minimum of three ICANN meetings and for a maximum of three years.
    2. Members may resign at any time.
    3. Members will transition off of the committee by one member at a time.
  4. Administration

    1. The FC may ask ICANN staff to investigate specific issues and to report back to the Committee.
  5. Reporting

    1. At the close of each ICANN International public meeting, the FC Secretariat will provide a summary report containing statistical information on its activities to the Fellowship Selection committee for their review. Once approved by the committee, this report will be provided to the Board and ICANN staff, as well as being posted on the ICANN website.
  6. Quorum

    1. A quorum for the meetings of the FC consists of a majority (50% plus 1 of all members).
    2. If any members of the FC cannot attend a meeting or conference call, they will be provided the notes for the Secretariat to provide additional input and approval.
  7. Process

    1. Meetings of the FC shall be held via conference call during the evaluation period of the fellowships application process.
    2. An agenda for each meeting shall be sent to the FC prior to the meeting.
    3. Minutes will be kept by ICANN staff and submitted for approval following each meeting of the FC.
    4. The FC will meet in person at an ICANN meeting once per year, preferably at the second meeting of each calendar year.
    5. Members of the FC will be encouraged to contribute to the agenda.
    6. The FC will be required to rank applicants within regions in order of preference. The number of fellowships available will vary dependant on the location of meeting, region of applicant and budgetary constraints.
  8. Application Assessment and Decision Making Process

Round One – First Order Decision Making

Each FC member reviews the dossiers of each applicant against the questions set out in the application form:

  • Why they want to attend
  • Why they feel participation in ICANN is important
  • Interest in participation in the Fellowship programme
  • Knowledge of field
  • Previous attendance: priority given to those who have not attended a meeting before or have only attended once
  • Willingness to complete feedback materials
  • Willingness to actively participate in ICANN meetings and the fellowship alumni network
  • In addition, beginning with ICANN meeting #31, ICANN Regional Managers comments will be available to the committee.

FC members will individually review each dossier and assign a grade of either 3 (definite yes) 2 (maybe) or 1 (definite no). They will then send that individual scoring information to ICANN, which is summarized within the application database.

If there are four voting FC members, the highest ranked applications will get a 12, the lowest a 4, and everyone will fall somewhere on the scale between 12 and 4.

If there are five voting FC members, the highest ranked applications will get a 15, the lowest a 5 and everyone will fall some where on the scale between 15 and 5.

The staff will then fill the slots from each region with the highest ranking applications according to the scores from the FC membership. If there are more admitted applicants with the same score than there are slots available for a region (i.e. "ties") then the FC must go to a second order of decision making.

Round Two – Second Order Decision Making

In the event of ties – too many applicants with the same score from the same region that exceeds the number of fellowships available for that region there will be a discussion about whether to have multiple attendees from a single country or to spread the slots out over many countries in a region. Questions that will be asked include:

  • Has this country ever been represented at ICANN meetings before?
  • Has the applicant ever been to a meeting before?
  • Is the applicant in a position to influence or teach others at home about ICANN?
  • Is the applicant from a department that makes it possible for them to influence Internet policy at home or in their region?

The FC will make a determination on how to prioritise individuals and countries based on their experience and then convey that determination to staff.

This file was last modified 20-Nov-2007

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."