Skip to main content

Report on Improving Institutional Confidence Plan

Open: 12 March 09
Closed: 11 May 09

Explanation: In ICANN’s submission to the Midterm Review by the National Telecommunications and Information Administration in February 2008 of the Joint Project Agreement between ICANN and the United States government, ICANN’s chairman, Peter Dengate Thrush, identified the PSC as the group to facilitate discussions with the community about issues raised regarding ICANN’s transition to the private sector. The PSC was asked to outline a plan for developing such a transition framework. The report is the President’s Strategy Committee’s proposed framework for the continuation of ICANN’s work following the conclusion of the Joint Project Agreement.

The draft Implementation Plan for Improving Institutional Confidence [PDF, 332 KB] was produced by the President’s Strategy Committee and submitted to the Board at ICANN’s Mexico City meeting. It was publicly discussed at a workshop and public forums during the ICANN meeting in Mexico City (1-6 March 2009). On 6 March 2009, the Board accepted the report and decided to post it for 60 days public comment. The Board also directed staff to evaluate implementation of the proposals and report their findings to the Board.

The draft document builds on extensive research, analysis, deliberation and consultation with the global Internet community, including two previous rounds of public comment (16 June - 31 July 2008 and 19 September ­ 20 October 2008), and a series of 9 public international meetings held between June and December, 2008.

About the PSC:

The PSC’s role is to give advice to the President and the Board on strategic issues facing ICANN. Since 2006, the PSC’s focus has been on ICANN’s legal status and identity, and regional presence.

Related links:

The draft Implementation Plan for Improving Institutional Confidence [PDF, 332 KB]

The March 2009 Board resolution accepting the report and directing further action is posted at

The President’s Strategy Committee homepages:

Staff member responsible: Maria Farrell

Announcement | Comments | Summary/analysis of comments

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