Skip to main content

ICANN Fellowship Coaching

ICANN Fellowship Program

About | Eligibility | Selection Criteria | Apply | Important Links


The ICANN Fellowship Coaching process is aimed at helping fellows (new or alumni) to prepare themselves for the ICANN Fellowship experience. This is an effort to maintain consistency of the Fellowship Program and strengthen the relationship between fellows and the ICANN community.

Through the coaching process, ICANN provides travel assistance to Fellowship alumni to attend an ICANN Public Meeting as a Fellowship coach. Receiving an Fellowship Coaching award does not count as a second or third fellowship.

The coaching process was developed from a need to provide mentorship to the ICANN Fellows in order to help them have a more fruitful experience during ICANN Meetings. The coaching process started as a pilot in 2014 during ICANN49 and was properly launched for ICANN52.

The main role of a Fellowship coach is to support up to three ICANN Fellows and help them learn about ICANN and how to take full advantage of the ICANN Fellowship opportunities. For more information about the role of a coach, see ICANN Fellowship Coaching Guidelines [PDF, 495 KB].


A Fellowship alumni is qualified to serve in the role of a coach if he/she fulfills the following criteria:

  1. Already has attended at least two ICANN Meetings, of which one of the meetings must have been attended as an ICANN Fellow. Depending on the situation at hand, the capability of the fellow and his/her conformance of points 2 to 8 below, this requirement can be set to one meeting only;
  2. Receives strong support from an ICANN community member and/or regional ICANN staff and/or global Internet leader;
  3. Possesses sound understanding of ICANN, its mission, model and processes;
  4. Demonstrates active engagement in at least one of the ICANN communities;
  5. Applied via the Fellowship Program online application and clearly explained why he/she wants to be a coach and what achievements demonstrate his/her leadership skills;
  6. Able to dedicate time for coaching and possess a good bandwidth to perform the duties;
  7. Has the understanding that the coaching process requires continuous engagement with a group of mentees that begins two months prior to the ICANN Meeting, continues during the duration of the meeting and ends after guiding the mentees into drafting and submitting the post-meeting report;
  8. Possesses good communication and interpersonal skills.
  9. Applicant must NOT be involved in or associated with other ICANN supported travel programs at time of selection.

Selection Criteria

  • Overall knowledge of ICANN mission and multistakeholder model; overall awareness of Internet governance related work in Internet ecosystem.
  • Be engaged within ICANN and /or the Internet community.
  • Feedback from ICANN's regional stakeholder engagement team and/or ICANN community leaders.
  • Previous experiences in the Fellowship Program that show aptitude for mentorship role;
  • Current role in the ICANN community, if applicable.
  • Rationale for particular meeting attendance and how coaching will be beneficial for you and the newcomers.

If a coach candidate is not selected to perform that role; he/she may or may not be selected as a Fellowship participant. See Fellowship Program Eligibility and Selection Criteria.


Applications for the Fellowship Coaching program must be submitted via the Fellowship Program Application system. Check out Application Dates & Deadlines on the ICANN Fellowship Program page.

Results will be published with the ICANN Fellowship Program announcement.

Important Links

Fellowship Program
More information about the ICANN Fellowship Program
Apply to become a Fellowship Coach
Submit an application during open rounds
Upcoming Application Dates
Planned launch dates for future application round
Terms & Conditions
More information on the Program's Terms & Conditions
List of Fellowship Participants
See list of Fellowship Program participants and coaches for each ICANN meeting
Fellowship Post-Meeting Report
Submit post-meeting report
Check out FAQs about the Fellowship Program

For more information, please contact

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