Skip to main content
Resources

Global Amendment to the Base New gTLD Registry Agreement

News

7 February 2017, 16:00-17:00 UTC – Webinar – Registry Agreement Amendment Voting Procedures

ICANN Organization held a webinar regarding the Global Amendment to the base New gTLD Registry Agreement. Members of the RySG's Working Group and the ICANN Organization led participants through an overview of the amendment process, summarized the changes, and reviewed the voting procedures and next steps.

9 February 2017 at 23:59 UTC –Voting Period Opens

10 April 2017 at 23:59 UTC – Voting Period Closes

View archived news

Voting Guidelines, Status, and Progress

Voting Guidelines

For information about the voting procedures, please see the Voting Process - Frequently Asked Questions ("FAQ") below and the slides from the webinar on 7 February 2017.

Voting Status

This CSV file is a list of Applicable Registry Operators and whether an Applicable Registry Operator has voted. The file includes the following data: (1) TLD; (2) Registry Operator Name; and (3) voting status where "X" indicates that a vote has been submitted.

Voting Progress

Throughout this vote, ICANN Organization will update this section approximately once every two weeks with progress of the vote towards the two thresholds required to achieve Applicable Registry Operator Approval pursuant to Section 7.6(j)(ii) of the base New gTLD Registry Agreement.

  1. Fee Threshold Chart: represents progress towards "the affirmative approval of the Applicable Registry Operators whose payments to ICANN accounted for two-thirds of the total amount of fees paid, pursuant to the Registry Agreement, the immediately previous calendar year."
    Fee Threshold Chart
    As of 16 Feb 2017
  2. Majority Threshold Chart: represents progress towards "the affirmative approval of a majority of the Applicable Registry Operators at the time such approval is obtained."
    Majority Threshold Chart
    As of 16 Feb 2017

Background

Section 7.7(a) of the base New gTLD Registry Agreement provides a mechanism enabling ICANN or the Registries Stakeholder Group (RySG) to periodically initiate negotiations to discuss revisions to the Registry Agreement. These negotiations may be initiated by either party not more than once per twelve month period and the first notice to initiate negotiations could not be submitted by either party prior to 1 July 2014.

On 16 July 2014, the RySG notified ICANN that it wished to negotiate proposed changes to the Registry Agreement. As required by Section 7.7(b) of the Registry Agreement, ICANN engaged in a "Discussion Period" with the Working Group established by the RySG on the form and substance of proposed contract amendments that were submitted by the Working Group and ICANN.

On 31 May 2016, ICANN posted for public comment the proposed changes to the Registry Agreement. After the close of the public comment period on 20 July 2016, ICANN published the Report of Public Comments [PDF, 404 KB] on 17 August 2016. ICANN and the Working Group then reviewed the public comments and, on 22 December 2016, ICANN published a Reissued Report [PDF, 545 KB] to supplement the initial Report of Public Comments with additional analysis as well as an updated Global Amendment [PDF, 424 KB].

The Global Amendment, posted in relevant resources below, is the result of several months of negotiations between the parties on mutually agreeable text of the proposed amendments. Pursuant to Section 7.7(c) of the Registry Agreement, the Proposed Revisions shall be submitted for Applicable Registry Operator approval (as defined in Section 7.6). Should the Global Amendment achieve Applicable Registry Operator approval, it will then be submitted to the ICANN Board of Directors for approval.

If such approvals are obtained as outlined in Section 7.7(c) of the Registry Agreement, the proposed Global Amendment shall be deemed an Approved Amendment and shall be effected and deemed an amendment to the New gTLD Registry Agreement following a 60-day notice from ICANN Organization to Registry Operators.

Relevant Resources

All capitalized terms and referenced sections used throughout this webpage have the meaning described to them in the base New gTLD Registry Agreement.

News Archive

22 December 2016 –ICANN Published a Reissued Staff Report [PDF, 545 KB] on the Proposed Global Amendment to the Base New gTLD Registry Agreement

17 June 2016 – Session at ICANN56 Announced – Amending the New gTLD Registry Agreement

ICANN held a session at ICANN56 in Helsinki on 28 June 2016 at 07:30 UTC (10:30 EEST) on the proposed amendment to the base New gTLD Registry Agreement. To learn more, read the blog published 31 May 2016.

14 June 2016 – Webinar – Amending the New gTLD Registry Agreement

31 May 2016 – Proposed Amendment to Base New gTLD Registry Agreement

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""icann.org"" is not an IDN."