Generic Top-Level Domain (gTLD) Registry Agreements

gTLD Registry Agreements establish the rights, duties, liabilities, and obligations ICANN requires of registry operators to run gTLDs.

Amendment No. 1 to the .CAT Registry Agreement

ICANN | Amendment No. 1 to the .CAT Registry Agreement
  ICANN Logo

Amendment No. 1 to the .CAT Registry Agreement

(24 June 2010)


ICANN and Fundacio puntCAT agree that the following modifications are made to the .CAT Registry Agreement dated 23 September 2005:

  1. The Parties agree to the following modifications to Section 3.1(c)(i) Agreement:

[Old Text]

3.1 (c)(i) Data Escrow. Registry shall establish at its expense a data escrow or mirror site policy for the Registry Data compiled by Registry Operator. Registry Data, as used in this Agreement, shall mean the following: (1) data for domains sponsored by all registrars, consisting of domain name, server name for each nameserver, registrar id, updated date, creation date, expiration date, status information, and DNSSEC-related key material; (2) data for nameservers sponsored by all registrars consisting of server name, each IP address, registrar id, updated date, creation date, expiration date, and status information; (3) data for registrars sponsoring registered domains and nameservers, consisting of registrar id, registrar address, registrar telephone number, registrar e-mail address, whois server, referral URL, updated date and the name, telephone number, and e-mail address of all the registrar's administrative, billing, and technical contacts; (4) domain name registrant data collected by the Registry from registrars as part of or following registration of a domain name; and (5) the DNSSEC-related material necessary to sign the TLD zone (e.g., public and private portions of TLD zone key-signing keys and zone-signing keys). The escrow agent or mirror-site manager, and the obligations thereof, shall be mutually agreed upon by ICANN and Registry on commercially reasonable standards that are technically and practically sufficient to allow a successor registry operator to assume management of the TLD. To this end, Registry shall periodically deposit into escrow all Registry Data on a schedule (not more frequently than weekly for a complete set of Registry Data, and daily for incremental updates) and in an electronic format mutually approved from time to time by Registry and ICANN, such approval not to be unreasonably withheld by either party. In addition, Registry will deposit into escrow that data collected from registrars as part of offering Registry Services introduced after the Effective Date of this Agreement. The escrow shall be maintained, at Registry's expense, by a reputable escrow agent mutually approved by Registry and ICANN, such approval also not to be unreasonably withheld by either party. The schedule, content, format, and procedure for escrow deposits shall be as reasonably established by ICANN from time to time, and as set forth in Appendix 1 hereto. Changes to the schedule, content, format, and procedure may be made only with the mutual written consent of ICANN and Registry (which neither party shall unreasonably withhold) or through the establishment of a Consensus Policy as outlined in Section 3.1(b) above. The escrow shall be held under an agreement, substantially in the form of Appendix 2, as the same may be revised from time to time, among ICANN, Registry, and the escrow agent. The escrow will contain DNSSEC-related material only after Registry implements it in the future.

[New Text]

3.1 (c)(i) Data Escrow. Registry shall establish at its expense a data escrow or mirror site policy for the Registry Data compiled by Registry Operator. Registry Data, as used in this Agreement, shall mean the following: (1) data for domains sponsored by all registrars, consisting of domain name, server name for each nameserver, registrar id, updated date, creation date, expiration date, status information, DNSSEC DS and DNSKEY Data; (2) data for nameservers sponsored by all registrars consisting of server name, each IP address, registrar id, updated date, creation date, expiration date, and status information; (3) data for registrars sponsoring registered domains and nameservers, consisting of registrar id, registrar address, registrar telephone number, registrar e-mail address, whois server, referral URL, updated date and the name, telephone number, and e-mail address of all the registrar's administrative, billing, and technical contacts; and (4) domain name registrant data collected by the Registry from registrars as part of or following registration of a domain name. The escrow agent or mirror-site manager, and the obligations thereof, shall be mutually agreed upon by ICANN and Registry on commercially reasonable standards that are technically and practically sufficient to allow a successor registry operator to assume management of the TLD. To this end, Registry shall periodically deposit into escrow all Registry Data on a schedule (not more frequently than weekly for a complete set of Registry Data, and daily for incremental updates) and in an electronic format mutually approved from time to time by Registry and ICANN, such approval not to be unreasonably withheld by either party. In addition, Registry will deposit into escrow that data collected from registrars as part of offering Registry Services introduced after the Effective Date of this Agreement. The escrow shall be maintained, at Registry's expense, by a reputable escrow agent mutually approved by Registry and ICANN, such approval also not to be unreasonably withheld by either party. The schedule, content, format, and procedure for escrow deposits shall be as reasonably established by ICANN from time to time, and as set forth in Appendix 1 hereto. Changes to the schedule, content, format, and procedure may be made only with the mutual written consent of ICANN and Registry (which neither party shall unreasonably withhold) or through the establishment of a Consensus Policy as outlined in Section 3.1(b) above. The escrow shall be held under an agreement, substantially in the form of Appendix 2, as the same may be revised from time to time, among ICANN, Registry, and the escrow agent. The escrow will contain DNSSEC-related material only after Registry implements it in the future.

II. The Parties agree that Appendix 1 to the Agreement is hereby deleted in its entirety and replaced with a new Appendix 1, in the form attached hereto.

The parties have duly executed this Amendment as of the date first written below.

THE INTERNET CORPORATION FOR ASSIGNED NAMES AND NUMBERS FUNDACIO PUNTCAT

By:_______________________________
Name: Kurt Pritz
Title: Senior Vice President, Services
Date:_______________________________


By:_______________________________
Name:
Title:
Date:_______________________________


 


Comments concerning the layout, construction and functionality of this site
should be sent to webmaster@icann.org.

Page Updated 29-Jun-2010

© 2010   The Internet Corporation for Assigned Names and Numbers. All rights reserved.