Skip to main content

Announcements

Final Proposed Draft v. 2.0 of the IDN Guidelines

The final proposed draft version 2.0 of the Guidelines for implementation of Internationalized...

Nominating Committee Announces Final Selections for Key Leadership Positions within ICANN

After a thorough period of outreach, consultation, recruitment, and evaluation, the Nominating...

IDN Guideline Revision Update

The members of the TLD registries working group for the revision of the IDN Guidelines wish to...

Generic Names Supporting Organization (GNSO) Review - DRAFT Terms of Reference

Following the ICANN Luxembourg Resolution, the GNSO Council has, with the support of the ICANN...

ICANN and VeriSign Announce End to Long-Standing Dispute

Press Release

ICANN today announced that it has reached an proposed agreement to end all pending...

ICANN Marks Anniversary of Passing of Jon Postel

Oct 16, 2005 marks the seventh anniversary of Jon Postel's death. It very nearly coincides with...

ICANN Announces New Staff Appointments

ICANN is pleased to announce the following new staff appointments:

Finance Team

ICANN wishes...

ICANN Announces New Staff Appointments in IANA

ICANN is pleased to announce the following new staff appointments:

General Manager IANA

David...

ICANN Posts Proposed Amendment to .NET Registry Agreement for Public Comment

ICANN and VeriSign, the .NET Registry Operator, in consultation with representatives from...

Summary of Consultations on Proposed Amendment to .NET Registry Agreement

The amended .NET agreements resulted from a series of consultations involving VeriSign, ICANN...

Draft Revised IDN Guidelines: Public Comment Period

ICANN has opened a 30-day public comment period on a draft revised version of the Guidelines for...

Implementation of Internationalized Top Level Domains

A full-day IDN workshop will be held during the ICANN meeting in Vancouver. This workshop will...

Global Policy for IPv6 - Background Report for Early Awareness of a Policy Proposal

The development of Global Internet Number Resource Policies is the subject of an MoU between...

.NET Agreement Update

Following the request-for-proposal process and re-bid set out in the expired .NET agreement,...

Comment Period 2 of ccPDP Commences

The ccNSO Council initiated a country code Policy Development Process to consider recommending...

Registry Services Changes - Final Report

Procedure for use by ICANN in considering requests for consent and related contractual...

ICANN Concludes 23rd International Meeting with Action on Domain Name Security and Global Addressing Policy

July 15 2005, Luxembourg City, Luxembourg – Over 900 delegates from 55 countries gathered in...

ICANN Ombudsman Releases First Annual Report

In accordance with Bylaw V the ICANN Ombudsman, Frank Fowlie, today presented the ICANN Board of...

ICANN Publishes Latest Newsletter

In conjunction with its meetings in Luxembourg, ICANN has published it latest newsletter-...

Statement Concerning London Bombings and ICANN Meeting in Luxembourg

Friends and Colleagues,

There have been multiple bomb blasts in London this morning. At the time...

ICANN Posts New gTLD Questions Paper

In September 2004 ICANN published a strategy for the implementation of new top-level domains...

ICANN Nominating Committee Extends Deadline for Submissions to 20 July 2005

ICANN's Nominating Committee (NomCom) announced today that it has extended its deadline for...

ICANN Board Designates VeriSign to Retain Control of .NET Registry

Marina del Rey, CA – 8 June 2005 – ICANN’s Board has named VeriSign, Inc. as the designated...

ICANN Vice President to head up major European Project 'Galileo' unit

ICANN's Vice President for Policy Support, Paul Verhoef, currently on secondment to the ICANN...

ICANN Publishes Proposed Agreement on .MOBI

ICANN has completed negotiations with the Applicant for .MOBI sponsored top-level domain. The...

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