Skip to main content

Summary of Consultations on Proposed Amendment to .NET Registry Agreement

The amended .NET agreements resulted from a series of consultations involving VeriSign, ICANN and the registrar constituency representatives.

Following the request-for-proposal process and re-bid set out in the expired .NET agreement, which included an independent evaluation of applications for the operation the .NET registry (see, <>) and subsequent negotiations, the ICANN Board approved a Registry Agreement executed by ICANN and VeriSign. The registrar community, along with other members of the ICANN community, voiced complaints concerning the content of the .NET agreement at the Luxembourg meetings and in postings thereafter. VeriSign issued a statement agreeing to renegotiate terms relating to the wholesale price of names to registrars and the terms Registry-Registrar agreement (RRA). Subsequent to that, VeriSign extended the period for the submission of comments concerning those contract terms.

After the close of the Luxembourg meeting the GNSO Registrars' Constituency appointed Jonathon Nevett to lead the negotiations on their behalf. The following generally summarizes the consultations the were held July — September 2005 to discuss proposed amendments to the agreement. There were exchanges of email and phone discussions that supplemented this discourse throughout this period.

  • 28 Jul 2005 - ICANN and registrar representatives held a conference call to establish the plan for going forward in the negotiations. The issues were generally discussed. The registrar representatives committed to furnishing a written amendment proposal.
  • 18 Aug 2005 - The registrar representatives furnished a proposal covering the price of names for the term of the agreement and amendments to the RRA. ICANN reviewed the proposal, contacted VeriSign to describe and forward the document for review.
  • 25 Aug 2005 - ICANN received a written response from VeriSign, responding to the registrar proposal. The document was forwarded on to the registrar representatives.
  • 1 Sep 2005 - ICANN staff met with registrar representatives in Washington, DC to discuss the VeriSign response regarding outstanding issues in the name price and terms of the RRA. ICANN took notes of the registrar position on each of the outstanding issues.
  • 5 Sep 2005 - The topics raised during the Washington, DC meeting with the registrar representatives were described in a conference call with VeriSign.
  • 8 Sep 2005 - ICANN received a written response from VeriSign regarding the remaining issues that were raised in the Washington, DC meeting. That information was forwarded to the registrar representatives.
  • 14 Sep 2005 - ICANN received a new version of the RRA from the registrar representatives, annotated to describe the remaining issues.
  • 19 Sep 2005 - After receiving verbal and written feedback on the remaining issues from VeriSign, ICANN and the registrar representatives held a conference call to discuss the outstanding issues.
  • 22 Sep 2005 - Additional consultations were held individually with both registrar representatives and VeriSign.

During the consultations, considerable progress was made toward a mutual agreement.

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