Business Magazine

ICANN Publishes “Changes to Registry Agreement for New gTLDs”

Posted on the 02 April 2013 by Worldwide @thedomains

ICANN has just posted the  Revised Registry Agreement for Review

“In the interest of transparency and accountability ICANN is providing the latest revision of the previously posted “Revised New gTLD Registry Agreement” for the community’s information and review.”

“This revision reflects the inputs and comments received from our stakeholders and other members of the community.”

“We have carefully considered the feedback on the revised Agreement and many suggestions have now been implemented in the new version of the Agreement. Community discussions will continue at ICANN’s Public Meetings in Beijing (7-11 April 2013).”

Here are the Summary of Changes to the Registry Agreement for New gTLD’s:


Summary of Changes to Registry Agreement for New gTLDs

The table below sets out the proposed changes to the draft base registry agreement for new gTLDs. Additions are reflected in bold double underline and deletions are reflected in strike through. These changes were made in response to comments received from the community on the February 2013 discussion draft base agreement for new gTLDs (the “Agreement”) and further review of the contractual needs of the new gTLD program. Note that non-substantive, purely technical and stylistic changes to the draft base agreement for new gTLDs are not reflected in the below table. To review all changes to the agreement, please see the full redline comparison posted with this summary.

Summary of Proposed Changes to Base gTLD Agreement

Summary of Changes


Change to Text

Comments and Rationale


Reserved Names. Except to the extent that ICANN otherwise expressly authorizes in writing, Registry Operator shall comply with the restrictions on registration of character strings set forth in Specification 5 attached hereto (“Specification 5”). Registry Operator may establish policies concerning Registry Operator’s ability to reserve (i.e., not register to third parties, delegate, use, or otherwise make available) or block additional character strings within the TLD at its discretion. If Registry Operator is the registrant for any domain names in the registry TLD (other than the second-level reservations for Registry Operator’s use pursuant to Section 4 of Specification 5), such registrations must be through an ICANN accredited registrar. Any such registrations will be considered Transactions (as defined in Section 6.1) for purposes of calculating the Registry-level transaction fee to be paid to ICANN by Registry Operator pursuant to Section 6.1; provided that Registry Operator may register names in its own name without the use of an ICANN accredited registrar in order to withholdreserve or block such names from delegation or use in accordance with this Section 2.6, and such registrations will not be considered Transactions.

Back to Featured Articles on Logo Paperblog