Common use of Specification 13 Clause in Contracts

Specification 13. Effective as of the Amendment No. 1 Effective Date, Specification 13 of the Agreement shall be deleted in its entirety. From and following the Amendment No. 1 Effective Date, (i) Specification 13 of the Agreement shall be of no further force and effect and (ii) Registry Operator shall comply with all terms of the Agreement as if the Agreement did not contain Specification 13, including compliance with Specification 7 (including the Trademark Clearinghouse Rights Protection Mechanism Requirements (“TMCH Requirements”)), Specification 9, and the provisions of Section 2.9(a) and Section 4.5 (as no longer modified by Specification 13 to the Agreement). Registry Operator represents and warrants to ICANN that, except as permitted by Section 2.2.4 of the TMCH Requirements, Registry Operator has not Allocated (as defined in the TMCH Requirements) or registered any registration in the TLD prior to the Amendment No. 1 Effective Date.

Specification 13. Effective as of the Amendment No. 1 2 Effective Date, Specification 13 of the Agreement shall be deleted in its entirety. From and following the Amendment No. 1 2 Effective Date, (i) Specification 13 of the Agreement shall be of no further force and effect and (ii) Registry Operator shall comply with all terms of the Agreement as if the Agreement did not contain Specification 13, including compliance with Specification 7 (including the Trademark Clearinghouse Rights Protection Mechanism Requirements (“TMCH Requirements”)), Specification 9, and the provisions of Section 2.9(a) and Section 4.5 (as no longer modified by Specification 13 to the Agreement). Registry Operator represents and warrants to ICANN that, except as permitted by Section 2.2.4 of the TMCH Requirements, Registry Operator has not Allocated (as defined in the TMCH Requirements) or registered any registration in the TLD prior to the Amendment No. 1 2 Effective Date.

Specification 13. Effective as of the Amendment No. 1 Effective Date, Specification 13 of the Agreement shall be deleted in its entirety. From and following the Amendment No. 1 Effective Date, (i) Specification 13 of the Agreement shall be of no further force and effect and (ii) Registry Operator shall comply with all terms of the Agreement as if the Agreement did not contain Specification 13, including compliance with the provisions of Section 2.9(a), Section 4.5, Specification 7 (including the Trademark Clearinghouse Rights Protection Mechanism Requirements (“TMCH Requirements”)), and Specification 9, 9 and the provisions of Section 2.9(a) and Section 4.5 (as no longer modified by Specification 13 to the Agreement). Registry Operator represents and warrants to ICANN that, except as permitted by Section 2.2.4 of the TMCH Requirements, Registry Operator has not Allocated (as defined in the TMCH Requirements) or registered any registration in the TLD prior to the Amendment No. 1 Effective Date.

Specification 13. Effective as of the Amendment No. 1 Effective Date, Specification 13 of the Agreement shall be deleted in its entirety. From and following the Amendment No. 1 Effective Date, (i) Specification 13 of the Agreement shall be of no further force and effect and (ii) Registry Operator shall comply with all terms of the Agreement as if the Agreement did not contain Specification 13, including compliance with Specification 7 (including the Trademark Clearinghouse Rights Protection Mechanism Requirements (“TMCH Requirements”)), Specification 9, and the provisions of Section 2.9(a) and Section 4.5 (as no longer modified by Specification 13 to the Agreement). Registry Operator represents and warrants to ICANN that, except as permitted by Section 2.2.4 of the TMCH Requirements, Registry Operator has not Allocated (as defined in the TMCH Requirements) or registered any registration in the TLD prior to the Amendment No. 1 Effective DateEffectiveDate.