Skip to main content

Amending the New gTLD Registry Agreement

Amending new gtld registry agreement 725x400 31may16 en

Today, ICANN announced that it has posted for public comment a proposed amendment to the base New gTLD Registry Agreement.

Why Change the Registry Agreement?

Like other business contracts, the New gTLD Registry Agreement will need to be modified occasionally to clarify responsibilities and update terms. The process for making amendments is defined in Section 7.7 of the base agreement.

The Amendment Process

According to Section 7.7, the amendment process is initiated when either ICANN or the Registries Stakeholder Group (RySG) notifies the other party that it wishes to propose changes to the agreement. This process cannot be initiated more than once per year. Thereafter, ICANN representatives and a working group representing the RySG review any modifications proposed by the other party. Once these representatives arrive at mutually acceptable terms, a proposed amendment can be presented for public comment.

Proposed Changes

After nearly 18 months of discussions, the revisions proposed by the RySG that ICANN agreed to have been made available to the community for comment today. Read a summary of the proposed changes [PDF, 242 KB].

Comment on the Proposed Amendment

ICANN has notified all registry operators that the public comment period for the proposed amendment is now open. In addition, all members of the ICANN community are invited and encouraged to provide feedback. The full set of documentation related to the proposed amendment, including a redline version of the base New gTLD Registry Agreement that provides full text revisions illustrating how the amendment will affect the New gTLD Registry Agreement, is available on the public comment page. The comment period ends 13 July 2016.

Comment now!

Next Steps

The amendment process defined in Section 7.7 of the base New gTLD Registry Agreement requires that a proposal be published for comment for no fewer than 30 days. ICANN will accept public comment on this amendment for 43 days. Following the conclusion of the public comment period, ICANN representatives and the RySG working group will consider comments and then submit a final proposal to all registry operators and the ICANN board. Registry operators and the ICANN board will vote on whether to approve or reject the proposal. If these approvals are obtained, the amendment will become effective upon 60 days notice from ICANN to the registry operators.

ICANN plans to hold a webinar in June 2016 to review the proposed changes in detail and provide an opportunity for community members to ask questions. Stay tuned for an announcement with more information.

Comments

    황은주  21:32 UTC on 31 May 2016

    안녕하세요.

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