Skip to main content

Public Comment Solicitation for FY13 Community Travel Support Guidelines

Comment/Reply Periods (*) Important Information Links
Comment Open: 1 June 2012
Comment Close: 22 June 2012
Close Time (UTC): 23:59 UTC Public Comment Announcement
Reply Open: 23 June 2012 To Submit Your Comments (Forum)
Reply Close: 13 July 2012 View Comments Submitted
Close Time (UTC): 23:59 UTC Report of Public Comments
Brief Overview
Originating Organization: ICANN Travel Support
Categories/Tags: Operations-Finances
Purpose (Brief): Purpose to provide community members with the opportunity to review and comment upon proposed FY13 community travel support guidelines.
Current Status: Pending review and comments. Changes in guidelines this year include: (1) New proposed booking and reimbursement procedures; and (2) Inclusion of data on FY13 special SO/AC budget requests approved (one time approvals, not ongoing support).
Next Steps: There will be a Constituency Travel meeting on 26-June-2012 during the Prague meeting to further discuss proposed procedural changes for future travel bookings and reimbursements.
Staff Contact: Steve Antonoff Email:
Detailed Information
Section I: Description, Explanation, and Purpose
The proposed travel guidelines are posted each year for community review and comment prior to the next fiscal year. The purpose is to invite comments and questions specifically from the SO/AC community.
Section II: Background
Every year during planning for the next fiscal year budget, the community member travel support guidelines are posted for public review and comment.
Section III: Document and Resource Links
Proposed FY13 Community Travel Support Guidelines [PDF, 316 KB]
Section IV: Additional Information
One addition to this year guidelines is discussion of SO/AC Special Requests for FY13. In addition, a number of modifications to travel policy are proposed.

(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.

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