Skip to main content

ICANN Newsletter | Week ending 29 May 2009

News from the Internet Corporation for Assigned Names and Numbers

Announcements This Week

Public Comment: IRT Final Report on Trademark Protection in New gTLDs

29 May 2009 | The Implementation Recommendation Team (IRT) posted its Final Report on Trademark Protection in New gTLDs [PDF, 300 KB]. This Final IRT Report will be posted for a thirty (30) day comment period that closes on 29 June, 2009.

ICANN Expense Analysis: by Stakeholder Interest Area

29 May 2009 | In response to community requests to view ICANN's expenses in reports more aligned with stakeholder interest areas, ICANN has developed a new financial report: Expense Area Group (EAG) reporting (formally known as Cost Analysis Group).

New Registrar Contract Approved by Board

29 May 2009 | A wide range of amendments have been approved to the contract that defines the rules for the retail level of the Internet's domain name system.

Root Server System Root Scaling Study

29 May 2009 | Responding to a request from the ICANN Board, SSAC and RSSAC have commissioned a study of the potential impact on the operation of the root server system of adding IPv6 address records, IDN top level names, other new TLDs, and new records to support DNS security to the root zone.

Ask a Question Direct to the Board in Sydney

28 May 2009 | An online question box where community members can ask questions directly to the ICANN Board and staff has opened.

GAC Responds to Board on Geographic Names

28 May 2009 | On 26 May 2009, the GAC submitted a final letter responding to the ICANN Board's concerns about the ability to implement the provisions of article 2 of the GAC Principles regarding new gTLDs.

Timing of IRT Report

27 May 2009 | The final Implementation Recommendation Team (IRT) report, originally called for by 24 May 2009 will be published on 29 May, 2009.

Public Comment: ccNSO Review (Terms of Reference)

26 May 2009 | The Structural Improvements Committee approved for public comments the proposed Terms of Reference, which detail questions that would guide the independent review of ICANN's ccNSO.

Upcoming Events

21 - 26 June 2009: 35th International Public ICANN Meeting - Sydney, Australia


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