Skip to main content

Regional Newcomers Fellowship Pilot

ICANN Fellowship Program

About | Eligibility | Selection Criteria


The Regional Newcomers Fellowship Pilot started at the ICANN59 Policy Forum in Johannesburg. The pilot aims to strengthen regional engagement by providing an opportunity for newcomers who can contribute to ICANN's policy work to participate at an ICANN Public Meeting in their own region.

Selectees are integrated with the rest of Fellowship Program participants for the duration of the ICANN meeting. The 15 slots count against the total number of annual Fellowship Program slots.


To be eligible for the Regional Newcomers Fellowship Pilot, an applicant must:

  • Be a Newcomer (never attended an ICANN Public Meeting in the past).
  • Be a national from a region where the ICANN Policy Forum takes place.
  • Be currently involved or have the potential to contribute to ICANN's policy work.
  • NOT be involved in or associated with other ICANN supported travel programs at the time of selection.
  • If selected, be able to attend the ICANN Policy Forum and required activities. Participant is expected to be engaged prior to the meeting through coaching process, participate in ICANN Fellowship sessions during the ICANN meeting, network and interact with program alumni and community members.
  • If selected, submit a post-meeting report.
  • If selected, participant is encouraged to actively contribute to ICANN policy development processes and Fellowship alumni network upon completion of the Regional Newcomers Fellowship Pilot.

Selection Criteria

Application and selection processes are carried out by ICANN's Global Stakeholder Engagement team from the region in which the meeting takes place. The number of selected candidates is 15 for each Policy Forum round.

Applications for the ICANN62 Policy Forum in Panama are now closed. Results will be published with the ICANN Fellowship Program announcement.

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