Skip to main content

ICANN Newsletter | Week ending 15 August 2008

News from the Internet Corporation for Assigned Names and Numbers

Announcements This Week

The Future of ICANN: A Series of Regional Consultative Meetings

15 August 2008 | A series of regional consultative meetings about crucial changes to ICANN will take place over the next three months in an effort to reach out to and involve the organization's global stakeholders.

Bulk Transfer of gTLD Names Formerly Managed by De-Accredited Registrar DotForce Corp.

14 August 2008 | As a result of the de-accreditation of registrar DotForce Corp., ICANN initiated a process to identify a gaining registrar to receive the gTLD names that had been formerly managed by DotForce Corp.

Draft Terms of Reference for the Upcoming SSAC Review Posted for Public Comment

13 August 2008 | As part of ICANN's commitment to its ongoing improvement, the Board approved a comprehensive plan for independent review of ICANN's structures, as well as of the Board itself. The reviews are intended to ensure an independent examination of the role and operation of key elements of ICANN.

ALAC Review: Translations of Final Report by Independent Evaluator Released

13 August 2008 | The final report of the Independent Review of the ALAC submitted by Westlake Consulting has been posted.

ICANN Posts Revised Community Travel Support Procedure for FY09

13 August 2008 | The revised Community Travel Support Procedure for FY09 document strives to accommodate the community feedback.

Upcoming Events

2 - 7 November 2008: 33rd International Public ICANN Meeting - Cairo, Egypt


ICANN Bylaws

Our bylaws are very important to us. They capture our mission of security, stability and accessibility, and compel the organization to be open and transparent. Learn more at

Strategic Plan, July 2007 - June 2010

Adopted FY09 Operating Plan and Budget [PDF, 489 KB]

Sign up for ICANN's Monthly Magazine

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