Skip to main content
Resources

Community Travel Support

ICANN relies in part on the face-to-face interaction of community members to advance policy development and other work. In addition, ICANN is committed to facilitating the participation of those members not yet fully engaged with ICANN. Outside ICANN Public Meetings, much of ICANN's work is done over the Internet and through conference calls. Community members should consider using authorized tools and methods to participate remotely in ICANN Public Meetings and other approved ICANN events. Even with these options for remote participation, meeting face-to-face continues to be an important part of the ICANN process.

Currently, ICANN supports more than 300 community members to attend each ICANN Public Meeting and spends considerable resources on travel support for community members. The ICANN Organization Travel Support team is dedicated to ensuring that support is implemented fairly, consistently, economically, and with administrative efficiency for all supported travelers and for ICANN. Consistent with ICANN's commitment to accountability and transparency, these Community Travel Support Guidelines set forth the process and scope of support that ICANN provides to community travelers.

ICANN Travel Support updates these guidelines periodically based on community feedback gathered from:

  • Public Comment processes
  • Open sessions at ICANN Public Meetings
  • Formal consultation with Supporting Organizations, Advisory Committees, stakeholder groups, and constituencies
  • Individual community members

Community Travel Support Guidelines

Notice: The revised Guidelines are in effect as of 1 July 2020. However, the publication of the revised Guidelines does not reverse the existing travel guidance in light of the COVID-19 pandemic. ICANN org will update its travel guidance as global public health conditions permit.

  1. Community Travel Support Guidelines as of 1 July 2020 [PDF, 516 KB]
  2. Redline Version [PDF, 691 KB]
  3. Draft Community Travel Support Guidelines [LINK: https://www.icann.org/public-comments/community-travel-guidelines-2020-02-13-en]

Archives

Travel Summary

Additional Travel Summary can be found here: https://community.icann.org/display/trvlconstit/Travel+Summary

2014

51 – Los Angeles Meeting:

50 – London Meeting:

49 – Singapore Meeting:

2013

48 – Buenos Aires Meeting:

47 – Durban Meeting:

46 – Beijing Meeting:

2012

45 – Toronto Meeting:

44 – Prague Meeting:

43 – Costa Rica Meeting:

2011

42 – Dakar Meeting:

41 – Singapore Meeting:

40 – Silicon Valley in San Francisco Meeting:

Travel Summary for Silicon Valley in San Francisco (untranslated):

2010

39 – Cartagena Meeting:

37 – Nairobi Meeting:

2009

36 – Seoul Meeting:

35 – Sydney Meeting:

Community Travel Questions and Answers: http://www.icann.org/en/news/in-focus/travel-support/community-travel-procedure-add-info-21aug08-en.htm

Travel Support Reports

Additional Travel Support Reports can be found here: https://community.icann.org/display/trvlconstit/Travel+Report

2013

47 – Durban Meeting:

46 – Beijing Meeting:

2012

45 – Toronto Meeting:

44 – Prague Meeting:

43 – Costa Rica Meeting:

2011

42 – Dakar Meeting:

41 – Singapore Meeting:

40 – Silicon Valley Meeting:

2010

39 – Cartagena Meeting:

38 – Brussels Meeting:

37 – Nairobi Meeting:

2009

36 – Seoul Meeting:

35 – Sydney Meeting:

34 – Mexico City Meeting:

2008

33 – Cairo Meeting:

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