Skip to main content

NextGen@ICANN Terms and Conditions

  1. Application Process

    The only way to apply for the NextGen@ICANN Program is through the online NextGen Applicant Portal. All information requested in the application must be written in English and submitted in the online form. Each candidate can only be selected and participate in one NextGen@ICANN Program. If you applied for a program round but were not selected, you must re-apply for the next ICANN meeting for which you are eligible.

    Please take careful note of the application closing dates listed at Incomplete applications will NOT be considered once the application period is closed.

    The NextGen@ICANN Program supports approximately 12-15 participants at each ICANN Public Meeting. An independent selection committee reviews all eligible applications. Each Supporting Organization/Advisory Committee (SO/AC) shall nominate one representative to serve on the ICANN NextGen@ICANN Selection Committee, for a total of up to seven members. Selection Committee members rank each application according to the NextGen@ICANN selection criteria. Confidentiality is a crucial component of the selection process. During the review and selection process, the Selection Committee may have access to confidential information, including, but not limited to, your personal information, such as educational history, work product or personal research, and other information you choose to provide in your application. You agree that this information is confidential to ICANN org and will not be shared with anyone during and following the selection process, except as described in the NextGen@ICANN Terms and Conditions, and where the disclosure is required by applicable law.

    Members of the Selection Committee may reside in locations outside of the United States or your country of residence and are committed to protecting and keeping each applicant's personal information confidential and in compliance with ICANN policies and applicable laws.

    All successful candidates are announced on the ICANN website, within approximately eight (8) weeks after the online application process closes; actual dates for all NextGen@ICANN postings are located on the NextGen@ICANN webpage. Successful candidates will receive a follow-up email to the email address provided on their application at the time of the announcement. Selected candidates must confirm their acceptance to participate in the NextGen@ICANN Program within seven (7) days upon receipt of the email.

  2. Program Requirements

    Successful candidates are required to:

    • engage with the NextGen@ICANN Program administrator and selected Program Ambassadors in the months leading up to the relevant ICANN Meeting, to learn about ICANN's mission, work and current topics of discussion
    • create a 5-10 minute presentation based on their studies and related to Internet Governance; this will be submitted prior to the ICANN Meeting and presented to their peers, ICANN staff and community at the ICANN Meeting
    • fully participate in the ICANN Meeting, attending each mandatory scheduled session as well as other ICANN community sessions
    • complete a post Meeting survey, remain connected with the NextGen@ICANN community through various media including Facebook and WhatsApp, work with ICANN's Regional teams and their own communities where possible
  3. Travel and Other Support Once Selected

    Travel will be booked by ICANN org through its designated Travel Management vendor. This method provides the lowest trip cost and allows ICANN Travel Support to ensure the security and well-being of supported travelers.

    ICANN org will not purchase any travel tickets for a NextGen@ICANN participant unless they are in receipt and can show proof of all valid travel documents: passport and required final destination and transit visas.

    ICANN org shall not be liable for any loss or expenses (including airfares) for travel delays incurred by the NextGen@ICANN participant as a result of inaccurate information provided by the NextGen@ICANN participant, delays in submitting the appropriate forms to the relevant authorities or refusals of host or transit country authorities to grant a visa to the NextGen@ICANN participant.

    ICANN org will cover the cost of the lowest available economy airfare at the time of booking based on the NextGen@ICANN participant's approved dates of arrival and departure as provided in a separate email sent by ICANN Travel Support titled "Welcome Email". For the compete travel guidelines on air transportation booking, please refer to the ICANN Community Travel Support Guidelines.  

    ICANN org will book and pay for a standard room (king or queen) on the NextGen@ICANN participant's behalf based on a single occupancy. NextGen@ICANN participants are not allowed to self-book their hotel reservation. Any and all hotel surcharges (e.g., telephone calls, room service, laundry, movies) and other incidental expenses are the responsibility of the NextGen@ICANN participant. The hotel may request a credit card or cash deposit from the fellow to guarantee these expenses.

    For ICANN meetings, a stipend not to exceed USD 500.00 will be provided to offset reasonable individual expenses (such as meals, transport to/from the airport and incidentals). The stipend will be wired to the NextGen@ICANN participants once they have proven that they have received their visa (if necessary) and their flight booking has been completed by ICANN org's Travel Management Company. Therefore, if NextGen@ICANN participants want to guarantee receipt of their stipend prior to the meeting, they must meet both visa and flight requirements 30 days prior to the ICANN Meeting. Anything less than 30 days will mean that NextGen@ICANN participants may not receive their stipend before the meeting. Those NextGen@ICANN participants who satisfactorily complete all aspects of the program will receive a certificate of completion.

    ICANN org will reimburse costs incurred by NextGen@ICANN participant to obtain a visa up to USD 200.00 as allowed in the ICANN Community Travel Support Guidelines.

    NextGen@ICANN participants agree to the abide by the ICANN Community Travel Support Guidelines to determine the level and amount of travel support provided by ICANN org and acknowledge the responsibilities shared with the NextGen@ICANN participants.

  4. Required Travel Documents

    Each selected NextGen@ICANN participant must be holding a valid passport prior to ICANN booking any travel (airfare and hotel).

    Travel documents as required by the NextGen@ICANN participants' country of origin or the country hosting the meeting. Transit visas may be required to connect in certain cities or countries. NextGen@ICANN participant should check with their local consulate agency.

    ICANN is not responsible for obtaining visas for NextGen@ICANN participants, but MAY help with communications regarding the visas, including a Form invitation letter to the ICANN meeting for which the individual has been selected to participate.

    NextGen@ICANN participants should always carry proof of health insurance. Insurance is NOT supplied by ICANN. Acquiring and paying for any and all insurance, including but not limited to travel insurance is the sole and exclusive responsibility of the NextGen@ICANN participant as is any subsequent claim processing.

    All travel documents must be consistent with the name on the selected NextGen@ICANN participant's valid passport.

  5. National laws and legislation

    ICANN is non-profit public benefit corporation incorporated in the State of California, United States and must therefore comply with all of the laws and regulations of California and the United States.

    It is the NextGen@ICANN participant's responsibility to comply with all local laws, regulations and legislation of the country or countries to which he or she will travel to or transit through (including but not limited to laws pertaining to immigration, taxation, customs, employment and foreign exchange control, as well as visas and required vaccinations).

    ICANN will not entertain any claim for work permits or any other costs relating to compliance with the national legislation of any country in the world from a NextGen@ICANN participant or any third party.

  6. Personal Safety and Health

    ICANN is not responsible for the personal health, safety or belongings of the NextGen@ICANN participant; each selected individual is exclusively responsible for maintaining their personal health and safety during the period of the NextGen@ICANN Program.

    ICANN strongly suggests that NextGen@ICANN participants consult and comply with the views of the diplomatic and consular authorities of the country of their nationality in respect of travel conditions and safety of travelers applicable in the countries to be visited under this NextGen@ICANN Program. It is not ICANN's responsibility to inform or provide advice to applicants or NextGen@ICANN participants about travel conditions or safety of travelers.

    ICANN also strongly suggests that NextGen@ICANN participants seek guidance from qualified health personnel concerning potential health risks in the areas to be visited. In preparing for a trip, each supported individual should receive, at their own expense, all required and recommended immunizations and take malaria prophylaxis if traveling to an area where malaria is endemic.

    Be aware that some transit regions may also require certain vaccinations or lapse time in travel due to your region of origin.

  7. Failure to Comply with NextGen Terms and Conditions

    Please note that if a selected participant of the NextGen@ICANN Program fails to comply with any one of the above mentioned terms and conditions, ICANN reserves the right to determine the appropriate course of action including, but not limited to: (i) terminating the selected candidate's participation before a Meeting; (ii) causing the NextGen@ICANN participant's early departure from the program and ICANN meeting; and/or (iii) asking the NextGen participant to cover costs for expenditures.

  8. Data Protection Practices

    ICANN respects the protection and privacy of personal data. ICANN will process each candidate's personal data in accordance with our privacy policy. For more information on ICANN's Data Protection Practices, please refer to

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