Skip to main content

Application Assessment Process

The following attributes or qualifications will be considered by the ICANN Fellowship Selection Committee in assessing each application. The Selection Committee members will assess each application individually, determining a score of “0-did not meet criteria”; “1-met some part of criteria”; “2-met all parts of criteria” for each factor on the table below, based on how well each applicant matches the posted Applicant Selection Criteria. The first 3 factors listed weigh more than other factors in the final score. The applications will then be ranked with respect to sum value of all individual scores combined.

Applicant expresses financial hardship
Applicant states that they are a member of an underserved or underrepresented community. Specifically applicants who have been hindered by social, economic and environmental factors such as poverty, race, ethnicity, age, gender, physical disabilities and/or living in a war torn environment
New Applicant receives positive feedback from ICANN Regional or Policy Staff, supporting need to fill a gap in diversity, gender, expertise that exists in region or ICANN Community group; Returning Fellow (Alumni) receives positive feedback from ICANN Regional or Policy Staff and/or Community Leader regarding their current engagement and activities in support of ICANN
A new Applicant makes a strong case (provides specifics) on what they wish to learn from this ICANN experience; a returning Fellow or someone who has attended an ICANN Meeting provides specific Meeting objectives, document why and how they will contribute to the work of ICANN’s Multistakeholder community and/or will use their Fellowship for significant regional engagement and/or sector engagement and/or global Internet governance work
First-time applicant documents global and/or regional training or engagement activities inside or outside of ICANN that could be applicable to ICANN work
Returning Fellow (Alumni) documents global and/or regional awareness of and /or engagement in activities that are a direct result of the Fellowship and ICANN experience
Applicant is:
  • a member of a Civil Society organization and engaged in studies or activities related to internet issues that reflect regional strategies or current work in ICANN
  • a member of Academic institution with ties to Internet governance through management of ccTLD or related Internet curriculum
  • a business minded individual with involvement in internet issues that reflect regional strategies or current work in ICANN
  • a Gov’t or ccTLD representative who did not receive travel funding from respective ICANN community and is from an underserved or underrepresented region or entity
  • experienced in Technical issues and/or belongs to Technical Societies related to ICANN’s work
  • an End User with specific interests in regional work and / or global Internet Governance
Applicant establishes they are currently a working member of an ICANN SO/AC/SG or Constituency
Applicant has tried to receive financial support through other means (other than ICANN Fellowship ) to attend the meeting but has been unsuccessful in receiving all or part of the funds
Applicant has previously applied and not been selected, but is showing more awareness of ICANN topics and/or has now attended an ICANN Meeting and seeking further engagement

The independent Selection Committee, through the assessment process will continue to take into account comments from ICANN’s Global Regional Engagement teams as well as members of ICANN’s Policy staff who understand the needs and current work of each region and community group in ICANN’s Multistakeholder model. ICANN Fellowship staff will remain in their oversight role to ensure that diversity is maintained within each selected Fellowship round in terms of gender, region, ethnicity, expertise, and sector. This process reflects the Program’s continued commitment to building capacity within ICANN, in order to bring new and diverse voices as well as needed expertise and experience from all ICANN regions and represented sectors.

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