Skip to main content
Resources

ICANN Meeting Fellowships

The ICANN Meeting Fellowship program is one example of how ICANN is supporting the next generation of community members, as part of the work of ICANN's Development and Public Responsibility Department.  In order to continue in its mission to build capacity within the ICANN Multistakeholder Model, this program seeks to create a broader and more diverse base of knowledgeable constituents with priority given to candidates currently living in underserved and underrepresented communities around the world, those who represent diversity of gender, sector, region, experience, and expertise, and/or have established financial need.  Participation in the program at an ICANN Meeting is a "fast track" experience of engagement into that community model, with presentations designed to facilitate understanding of the many pieces and parts of ICANN while providing opportunities to network and promoting interaction with ICANN Community and Staff.

Each candidate selected into the program through the online application and assessment process is provided a grant of support that covers the cost of economy class airfare, hotel and a stipend.  Fellowship recipients are expected to engage prior to, during and after the ICANN meeting with the ICANN Fellowship office, Program Alumni, Newcomer Coaches and their selected peers, as well as begin to actively contribute to ICANN processes upon completion of the Program.

For more information please see the Program's Process and Terms

Who may apply for and be awarded a fellowship?

Candidates from all regions and sectors are welcome to apply to the ICANN Fellowship Program. The Program is targeted at individuals who: show awareness of, but are either new to the ICANN environment; are familiar with ICANN but have yet to attend a face-to-face meeting; have started participating in ICANN through the program or by other means but are in need of travel support and/or an additional fellowship opportunity in order to broaden their knowledge and deepen their engagement.  Candidate backgrounds are diverse: government, the ccTLD community, civil society, academic, technical, and security, commercial and non-commercial sectors.  These individuals must NOT be involved in or associated with other ICANN supported travel programs at time of selection.

Successful applicants will have demonstrated:

  • Desire and ability to utilize the experiences gained from the fellowship to become an active member of the next generation of ICANN's volunteer community
  • A role or interest in the Internet space, specifically as it relates to the work of ICANN
  • An interest in contributing to:
    • ICANN policy development processes
    • The ICANN Fellowship Alumni network
    • ICANN outreach in their sector, community and region
    • An ICANN supporting organization, advisory committee, stakeholder group or constituency
  • A returning fellow (Alumni) who can provide documented support from community leaders and/or ICANN Regional staff as to their continued engagement and work related to their fellowship and ICANN experiences, as well as articulate specific goals for a particular Meeting which may include Newcomer Coach
Click here for information about Applicant Criteria

How are the fellowships awarded?

Fellowships are assessed by an independent selection committee based on the ability of the individual applicant to meet the Applicant criteria, and ranked through a scoring process that prioritizes those applicants who not only meet the criteria but also show: diversity in gender, sector, experience, expertise; that they are a member of an underrepresented or underserved community; with consideration given to financial need. Applicant experience and references also may affect final selection.

ICANN Fellowship Selection Committee

Fellowship Application Assessment Process

Current Program Status

The following individuals successfully participated in ICANN57 held 3-10 November 2016 in Hyderabad, India:

  • Abdalmonem Galila – Arab Republic of Egypt – ccTLD Operations
  • Adela Goberna – Argentina – Business
  • Amal Ramzi Al-Saqqaf – Yemen – Academic
  • Anivar Ammanath Aravind – India – Civil Society
  • Ashish Agarwal – India – Government
  • Bart Morgan – Barbados – Internet End User
  • Buddhadeb Halder – India – Civil Society
  • Dessalegn Yehuala – Ethiopia – Academic
  • Edowaye Makanjuola – Nigeria – Government
  • Fadi Salem – Syrian Arab Republic – Academic
  • Fotjon Kosta – Albania – Government
  • Gazi Zehadul Kabir – Bangladesh – Technical
  • Houda Belkassem – Morocco – Academic
  • Huthaifa Mohammad Ahmad Albustanji – Jordan – Intellectual Property
  • Ines Hfaiedh – Tunisia – Academic
  • James Bidal – South Sudan – Civil Society
  • Jason Hynds – Barbados – Technical
  • John Sushil Chand – Fiji – Technical
  • Kasek Galgal – Papua New Guinea – Academic
  • Khalid Samara – Jordan – Security
  • Lucas de Moura – Brazil – Security
  • Manmeet Pal Singh – India – Internet End User
  • Maryan Rizinski – Bulgaria – Business
  • Matilda Pamao – Papua New Guinea – Academic
  • Monica Gastelú Céspedes – Bolivia – Academic
  • Monica Romero Chacon – Costa Rica – Government
  • Mubashir Hassan – Pakistan – Civil Society
  • Nadira AlAraj – State of Palestine – Civil Society
  • Narine Khachatryan – Armenia – Civil Society
  • Nasrat Khalid – Afghanistan – Civil Society
  • Naveen Lakshman – India – Technical
  • Paul Muchene – Kenya – Technical
  • Pitinan Kooarmornpatana – Thailand – Business
  • Radha Parvatee Ramphul – Mauritius – Technical
  • Raitme Osvaldo Citterio Alvarado – Bolivarian Republic of Venezuela – Civil Society
  • Renata Aquino Ribeiro – Brazil – Civil Society
  • Ricardo Holmquist – Bolivarian Republic of Venezuela – Civil Society
  • Rim Hayat Chaif – Algeria – Civil Society
  • Royden Thato Mfikwe – South Africa – Civil Society
  • Sanjay Bahadoor Singh – Trinidad and Tobago – Academic
  • Sarata Omane – Ghana – Academic
  • Shavkat Sabirov – Kazakhstan – Civil Society
  • Waqqas Ahmad Mir – Pakistan – Business
  • Wayne Reiher – Kiribati – Government

ICANN58 (Meeting A) in Copenhagen, Denmark to be held 11-16 March 2017

  • Application Round open: 12 September 2016 at 23:59 UTC
  • Application Round close: 21 October 2016 at 23:59 UTC
  • Selected Fellows announcement: 16 December 2016

ICANN59 (Meeting B / Policy Forum) in Johannesburg, South Africa to be held 26 - 29 June 2017

  • Application Round open: 23 December 2016 at 23:59 UTC
  • Application Round close: 3 February 2017 at 23:59 UTC
  • Selected Fellows announcement: 24 March 2017

*Mtg B Application Round will be a program for Alumni of the ICANN Fellowship Program only, therefore only those who have successfully completed an ICANN Fellowship are eligible to apply for this particular round.

ICANN60 (Meeting C) in Abu Dhabi, United Arab Emirates to be held 28 October - 3 November 2017

  • Application Round open: 21 April 2017 at 23:59 UTC
  • Application Round close: 2 June 2017 at 23:59 UTC
  • Selected Fellows announcement: 28 July 2017

ICANN61 (Meeting A) in TBD location in North America to be held 10 - 15 March 2018

  • Application Round open: 1 September 2017 at 23:59 UTC
  • Application Round close: 13 October 2017 at 23:59 UTC
  • Selected Fellows announcement: 8 December 2017

Previous Fellowship Participants

Online Application

FAQ

 

For more information: fellowships@icann.org

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""icann.org"" is not an IDN."