Skip to main content

Letter from Tina Dam to Bruce Beckwith

By Postal Mail

Los Angeles, 7 August 2003

Mr Bruce W. Beckwith
Vice President, Operations

Public Interest Registry
1775 Wiehle Avenue, Suite 102A
Reston, VA 20190

Dear Mr. Beckwith,

Thank you for informing ICANN that Public Interest Registry currently is experiencing problems regarding EPP/"thick" data items such as "registrant email" and "registrant phone number", during the RRP to EPP conversion.

I understand that the current .org registry RRP to EPP Transition Plan requires that registrars collect these two data elements, and also that the Whois specification calls for the registry to display these two data elements, which registrars were not previously required to collect or display.

ICANN wishes to afford PIR and affected registrars all appropriate flexibility to go forward with the transition despite this problem. Accordingly, ICANN has no objection to PIR allowing registrars to insert and maintain temporary "placeholder" data in the fields in question for a reasonable period of time post cut-over to EPP. ICANN consider up to the end of 2003 to be a reasonable period of time. Should additional time be necessary, please contact us to discuss further arrangements.

For the registrant telephone number, examples of appropriate"placeholder" data include the phone number of the admin contact, or the registrar's own telephone number. For the registrant e-mail address, examples of appropriate "placeholder" data include the current value ( or the e-mail address of the admin contact. (In the alternative, a registrar might want to use an email such as configured with an auto-reply stating "This domain record has been transitioned to Public Interest Registry; however, the registrant's email and phone number have not yet been updated. Please contact the registrar at if you require further assistance.")

Thank you for consulting ICANN concerning this issue. Hopefully the approach outlined above will be satisfactory. Please feel free to contact me if you have questions or if I can be of any other assistance.

Best Regards,

Tina Dam
Chief gTLD Registry Liaison

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