Skip to main content

ICANN Newsletter | Week ending 29 June 2007

A weekly electronic newsletter from the Internet Corporation for Assigned Names and Numbers

Announcements This Week

Top-Level Domains, Internationalized Domain Names, and Address Space Discussions Make Progress in San Juan

29 June 2007 | Refinement of policies means new domain names on track for mid-2008, possible live evaluation of IDNs.

ICANN Posts Approved Version of the Proposed Fiscal Year 2008 Budget

29 June 2007 | The ICANN Board has approved the as-amended, proposed Fiscal Year 2008 Budget [PDF, 429 KB], dated 29 June, 2007.

Proposed .NAME Renewal Registry Agreement Posted for Public Comment

29 June 2007 | The proposed .NAME renewal registry agreement is posted for public comment and can be viewed at [PDF, 97 KB] and appendices at /tlds/agreements/name/appendices-renewal-proposed-final-07.pdf [PDF, 305 KB].

ICANN Commences Development of July 2008 - June 2011 Strategic Plan

28 June 2007 | In accordance with its annual planning calendar, ICANN is seeking community input on key questions that will inform the development of the July 2008 – June 2011 Strategic Plan.

IANA Wants Public Input on New Website

28 June 2007 | Redesign goal to make information easier to find.

ICANN Formalizes Relationships with ccTLD Managers for Puerto Rico and Fiji

26 June 2007 | ICANN has signed accountability frameworks with the country code top level domain (ccTLD) managers for .pr-- Puerto Rico, Gauss Research Laboratory Inc. and .fj-- Fiji, University of the South Pacific, Information Technology Services.

Global Participation Gets a Boost at ICANN

26 June 2007 | Fellowship program helps get 33 participants to 29th public meeting.

Protecting Registrants Focus of ICANN Workshop

25 June 2007 | Strengthening the protection of registrants and their domain names was the focus of a key workshop at the 29th International Public Meeting of the Internet Corporation for Assigned Names and Numbers (ICANN) in San Juan, Puerto Rico.

New: ICANN Maps

25 June 2007 | In further improvements to transparency and accountability, ICANN has commenced the process of illustrating some basic data in geographical maps.

ICANN's 29th International Meeting Opens Monday in San Juan

25 June 2007 | The San Juan meeting is the second of the three public ICANN meetings in 2007. These meetings are crucial because ICANN's polices are created through a bottom-up, transparent process involving Internet Community.

ICANN Featured Individual: Anne-Rachel Inné, Regional Liaison for Africa

Anne-Rachel is part of the Global Partnership department at ICANN that has a network of seven regional liaisons so far. It was established in response to Internet community demand and in implementation of ICANN's publicly agreed strategic plan. Her responsibilities include outreach, support to and engagement with respective regions and stakeholders, civil society, business and governments; partnering with respective organizations; delivering against an action plan consistent with ICANN's operations and strategic plans.

Anne-Rachel was first a translator, then a sales manager for UTA/Air France for the Niger office and then an ICT for development practices consultant. She has a Master of Arts in English/Translation from the University of Paris XII, and graduated in 1997 from the University of Illinois at Urbana Champaign with an MBA in International Management. Prior to working for ICANN, she worked as a consultant on local, regional and international projects for the UNDP/UNOPS, UNCTAD, the French Ministry of Foreign Affairs, the IICD, the Francophonie, etc.

She is a member/board member of several African and international organizations that work with/for the private sector with a focus on ICTs. She is the god mother of youth community radios, cyber centers and is a long time member of the Rotary. She practices sports in general.


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

Operating Plan (Draft) Fiscal Year 2007 - 2008

Adopted Budget Fiscal Year 2007 - 2008 [PDF, 426 KB]

To unsubscribe from this mailing list, please visit

If you have questions or comments about this mailing list, send an email 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"""" is not an IDN."