Skip to main content

ICANN Fellowship Selection Committee

ICANN Fellowship Program

Membership Makeup | Terms of Service | Application Assessment | Committee Members

The ICANN Fellowship Selection Committee is responsible for assessing all vetted applications for the ICANN Fellowship received through the online application system, to determine which applicants have best met the posted Applicant Selection Criteria for the program.

Additionally, committee members are asked to:

  1. Act as a resource to the ICANN Board and staff by providing information and feedback on the planning, implementation and evaluation of the Fellowship Program as needed during their time of service
  2. Conduct outreach in support of the Fellowship Program and to help create a pool of potential future members of the Selection Committee

Fellowship Selection Committee Membership Makeup

  1. The Committee shall be made up of no less than four and no more than five representatives from the global Internet community who have a strong history of experience with some specific sector (s) of the Internet ecosystem including but not limited to technical Internet issues; work in government, academia, commercial or non-commercial work; work with ICANN or other Internet entities; work involving underserved and /or under represented countries and/or Internet related development work, or affiliation/knowledge of other fellowship programs.
  2. Makeup to reflect sector and regional balance
  3. Membership is at the invitation of ICANN staff, who may utilize recommendations from the ICANN communities to canvas for potential candidates

Terms of Service

  1. Members of the Fellowship Selection Committee are asked to serve for a minimum of one year (2 rounds) and a maximum of three years (6 rounds) for ICANN Community Fora and Annual General Meetings
  2. Members may resign at any time if circumstances arise that prevent them from effectively performing their function
  3. Members transition off the Fellowship Committee one member at a time when possible to maintain continuity of experience and information
  4. The Committee will meet in person at an ICANN Public meeting once per year, preferably at either an ICANN Community Forum or Annual General Meeting. If required, additional meetings of the committee shall be held via conference call during the Fellowship application assessment period

Application Assessment and Decision-Making Process

  1. The number of fellowships available will vary dependent on number of qualified candidates, the location of meeting, and budgetary constraints per round
  2. Each Fellowship Committee member assesses the application responses which relate to the posted applicant criteria:
    • Why a new applicant or returning alumni feels participation in ICANN and specifically in the Fellowship Program is important for this particular meeting
    • Has this country where the applicant resides ever been represented at ICANN meetings before; is it considered underserved and/or under represented within ICANN?
    • Has the applicant ever attended an ICANN Public meeting before? If so, what experience has been gained, how was this utilized
    • Has the applicant ever been selected as a Fellow and if so, how was that experience utilized and what are the goals for this meeting based on that experience
    • What is the applicant's knowledge base and level of expertise about ICANN, either from a newcomer or alumni point of view
    • Is the applicant themselves in a position or is the applicant from a group, organization or governmental department that makes it possible for him/her to influence Internet policy at home or in his or her region
    • Has the applicant expressed financial hardship and/or efforts to fund self previously through other means in order to attend an ICANN Public Meeting
    • Is the applicant willing to complete feedback material as well as actively participate in ICANN work, in and away from ICANN meetings as well as remain engaged in the Fellowship alumni network
    • Based on feedback received from ICANN Global Stakeholder Engagement and Policy staff, does this applicant bring needed expertise and experience into a region, sector or community within ICANN
  3. Fellowship Committee members individually assess and score each application using the Applicant Selection Criteria.

ICANN staff will fill the Fellowship Program slots available based on these assessments and scores, mindful of the need for quality candidates from all regions and sectors, including those from underserved and/or under represented communities, along with sectors that still lack diverse representation within ICANN.

Fellowship Selection Committee Members

Current Members

  • Aftab Siddiqui – Asia Pacific: Serving through Summer 2018 (Chief Technologist at Eintellego Networks Pty Ltd, an active member of APNIC, appointed by APNIC to the ASO Advisory Committee, Co-Chair SANOG PC).
  • Sorina Telenau – Europe: Serving through Summer 2019 (Digital Policy Senior Researcher at DIPLO; previously worked as an advisor in the Romanian Parliament, dealing with ICT-related legislation and policies. She also served as the alternate representative of the Romanian Government to ICANN's Governmental Advisory Committee. and is an alumni of the Fellowship Program).
  • Carolina Aguerre – Latin America: Serving through Fall 2019 (General Manager of LACTLD since 2012, engaging in capacity-building for Latin American ccTLDs and representing those ccTLDs in international fora. Carolina has been a member of the ccNSO since 2007 and is also a member of the IGF's MAG.
  • Nadira Al-Araj – Western Asia: Serving through Summer 2020 (Online freelancer in Capacity Building on IG; member of MEAC-SWG; An earlier vice chair of ISOC Palestine and the Chapter representative to ALS APRALO and Chapters Advisory Council of ISOC. Founding member of ISOC Blockchain SIG. Was the Arab MAG 2015 coordinator to the workshops track).
  • Dustin Phillips - North America: Serving through Summer 2020 (Co-Executive Director of ICANNWiki, working on building capacity by providing an accessible, encyclopedic resource on ICANN and Internet governance available in 7+ languages; Dustin is also the Assistant Director of ISOC-DC and an active member of the IGF-USA Steering Committee).

Past Members

  • Nashwa Abel Baki – Western Asia – served 3 years / 9 rounds
  • Christine Arida – Western Asia – served 3 years / 7 rounds
  • Fahd Batayneh – Western Asia – served 3 rounds * now ICANN staff
  • Tatiana Chirev – Eastern Europe - served 3 years / 10 rounds
  • Mouhamet Diop – Africa – served 3 years / 10 rounds
  • Ayman El-Sherbiny – Western Asia – served 1 year / 3 rounds
  • Demi Getschko – Latin American – served 3 years 10 rounds
  • Steven Huter – North America – served 3 years / 9 rounds
  • Erick Iriarte Ahon – Latin America – served 2 ½ years / 8 rounds
  • Gaongalelwe ("Gao") Mosweu – Africa – served 3 years / 7 rounds
  • Pierre Ouédraogo – Africa – served 1 1/2 years / 5 rounds
  • Alejandro Pisanty – Latin America – served 3 years /10 rounds
  • Vanda Scartezini – Latin America – served 3 years / 9 rounds
  • Nelly Stoyanova – Europe – served 3 years / 10 rounds
  • Gaurab Raj Upadhaya – Asia Pacific – served 3 years / 10 rounds
  • Hong Xie – Asia Pacific – served 3 years / 9 rounds
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."