Skip to main content

Revised Community Travel Support Guidelines

Today, the ICANN organization published revised Community Travel Support Guidelines. The ICANN org began the process of updating the guidelines last year. The goal of this process was to improve the guidelines for supported travelers, as the last revisions were made in 2013; provide clarity for supported travelers and community groups; and separate matters of funding from the guidelines. The revisions do not address specific requests for changing levels of support. This approach ensures discussions of resource allocation remain part of the budget planning process.

The guidelines reflect the initial input received from the community consultation conducted between September 2017 and January 2018, as well as the subsequent submissions received as part of the public comment proceeding conducted from May to July 2018. The ICANN org appreciates the contributions of the community to this process, and the guidelines build on community experiences and capture observations made by ICANN Travel Support.

Over the past few years, several community groups have experimented with increased levels of funding through the Additional Budget Request process. In a number of cases, increased travel support was later incorporated into the budget and operating plan. The ICANN org recognizes the significant value that the community's work provides in the furtherance of its mission. Likewise, the ICANN org recognizes that individual community group requests to increase travel support levels are important, requiring consideration as part of the budget planning process.

The long-term sustainability of travel support requires strategic consideration by the community. Demands are growing over time, driven by many factors. This includes increasing cross-community work, robust policy development and implementation, growth in working groups, and the expansion of reviews. Currently, ICANN supports more than 300 community members to attend each ICANN Public Meeting, and spends considerable resources on travel support for approved ICANN events.

The Global Stakeholder Engagement and Policy Development Support departments led the revision process and collaboration with the community. The Communications, Finance, Legal, and Travel Services departments offered guidance as well. Moving forward, ICANN welcomes feedback from the community on how well the guidelines are meeting its needs and expectations. The ICANN org commits to a regular review of the guidelines after a sufficient period of working with the revised guidelines.


    Anthony Constantinou  03:58 UTC on 28 November 2019

    Thanks for updating the information. Guidelines are essential to work on right path.

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