Skip to main content

Announcements

GNSO Council Report to the ICANN Board

ICANN is posting - for information - the GNSO report to the ICANN Board (PDF) on the GNSO's...

Preliminary Task Force Report on the Purpose of Whois and of the Whois Contacts

The "Preliminary Task Force Report on the Purpose of Whois and of the Whois Contacts" has been...

Call for papers -- Policy Development for introduction of new gTLDs

The GNSO Council has voted to launch a Policy Development Process on new gTLDs and to establish...

ICANN Opens Public Comments on ccNSO Recommendations for Proposed Bylaws Changes

Introduction:

On 26 June 2003, the ICANN Board at its public meeting in Montreal, Canada,...

ICANN Posts .aero, .coop, and .museum Renewal Proposals for Public Comment

ICANN is posting for public comment Renewal Proposals submitted by the current .aero, .coop,...

Request for Proposals for Independent Evaluator for GNSO Review

(revised 19 December 2005)

1. Introduction

1.1. This document should be read in conjunction...

Paul Twomey's Presentation on the Proposed Verisign Settlement | Vancouver Meeting, ICANN Public Forum, Part 1

On 02 December 2005, Paul Twomey, CEO of ICANN, gave a presentation concerning the Proposed...

Public Comment Forum for Terms of Reference for New gTLDs

Updated 22 December 2005

The ICANN bylaws require a public comment period of 20 days following...

Next Steps on Proposed .com Settlement

On 24 October 2005, ICANN announced proposed settlement terms between ICANN and VeriSign,...

ICANN Lawsuit Update: Judge Rules in ICANN's Favor and Denies Application for Temporary Restraining Order

A US Federal Judge has ruled in ICANN's favor and denied an application for a Temporary...

ICANN posts briefing on open 2005-06 budget items

The ICANN Board adopted the fiscal year 2005-06 budget at the Luxembourg meeting with the...

Proposed Change to ICANN Bylaws Regarding "At-Large Structure" Certification -- Public Comment Forum Reminder

Background:

The At-Large Advisory Committee (ALAC) is recommending that the Board amend the...

ICANN Announces New Staff Appointments

ICANN is pleased to announce the following new staff appointments:

ICANN Registrar Liaison...

ICANN President's Advisory Committee for IDNs

ICANN is pleased to announce the formation of the President’s Advisory Committee for IDNs. The...

ICANN Welcomes WSIS Tunis Declaration | Support for multi-stakeholder model ensures stability and integrity of DNS for over one billion Internet users

Tunis, November 18, 2005: ICANN has welcomed the Tunis Declaration adopted during the second...

Information on Proposed VeriSign Settlement and New .COM Agreement

On 24 October 2005, ICANN and VeriSign announced that they had reached a proposed agreement to...

Implementation of Internationalized Top Level Domains

As previously announced, an IDN workshop will be held during the ICANN Vancouver meeting....

IDN Guidelines Version 2.0 Finalized

The Guidelines for Implementation of Internationalized Domain Names, version 2.0 is now posted...

Comment Period Extended on VeriSign Settlement Agreement

As part of ICANN's ongoing effort to support community dialogue and consultation regarding the ...

Letter from ICANN Chairman Vint Cerf to GAC Chairman Mohamed Sharil Tarmizi

ICANN Chairman Vint Cerf has written to the Chairman of the ICANN's Government Advisory Committee...

Strategic Planning Update

In accordance with its plan for consultation and writing the next version of the ICANN's...

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

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