Skip to main content

Update – .NET RFP Process

The anticipated response from Telcordia to the applicant's written comments as noted in ICANN.s Update dated 20 April 2005 has been delayed.

To date, we have not received the response from Telcordia but expect this response later this week. Accordingly, we are not yet certain about the timing of the posting but will continue to post updates as the information becomes available. We have attached ICANN's previous public update below.

Update – .NET RFP Process

20 April 2005

On 28 March 2005, ICANN published the "ICANN .net RFP Evaluation Final Report" prepared by Telcordia. The report indicated that VeriSign was the top-ranked applicant.

ICANN has since taken the following steps, as prescribed by the process and in an effort to ensure fairness and equal treatment to all of the applicants:

  1. ICANN posted on its website a request for comments from the public and from the Internet Community;
  2. ICANN invited the applicants to provide comments to the report in writing; and
  3. ICANN entered into intensive and speedy negotiations with VeriSign, the top-ranked applicant, based upon the previously posted form of agreement. ICANN and VeriSign have reached agreement in principle on all substantive terms.

ICANN has received written comments from all five applicants regarding the Telcordia report. ICANN published the applicants' correspondence, and forwarded it to Telcordia for review and further comment. ICANN anticipates a response from Telcordia on or before 25 April 2005.

Pursuant to the adopted RFP process, the ICANN Board will consider the following at its next meeting:

  1. the Telcordia report;
  2. the Applicants' written comments on the Telcordia report;
  3. any response from Telcordia to the Applicants' written comments;
  4. any and all public or Internet Community comments received by ICANN on its website; and
  5. the proposed .NET Registry Agreement negotiated between ICANN and VeriSign.

For additional information on the .NET RFP Process, please visit <>. A public comment forum has been established for receiving feedback from the applicants and the Internet community on the RFP process and the Telcordia report at <>. (All applicants are reminded that the terms of the RFP prohibit any other forms of communication with ICANN employees or directors concerning the RFP process.)

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