Common use of Rights Protection Mechanisms Clause in Contracts

Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registry-Registrar Agreement entered into by ICANN-accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.

Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registry-Registrar Agreement entered into by ICANN-accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.

Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registry-Registrar Registry‐Registrar Agreement entered into by ICANN-accredited ICANN‐accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch‐requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated ICANN‐designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Registry‐Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Registry‐Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Registry‐Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Registry‐Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.

Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registry-Registrar Agreement entered into by ICANN-accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements xxxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.

Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registry-Registrar Agreement entered into by ICANN-accredited registrars authorized to register names in the TLD.” Specification 8 The terms of Specification 8 shall be of no force or effect. Registry Operator shall implement Specification 9, § 1(b) The terms of Section 1(b) of Specification 9 are hereby amended and restated in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse their entirety as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements (the follows: “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may reserve names from registration pursuant to Section 2.6 of the Agreement;” This Addendum shall constitute an integral part of the Registry Agreement. Notwithstanding Section 7.10 of the Registry Agreement, the Registry Agreement (including those specifications and documents incorporated by reference to URL locations which form a part of it) and this Addendum constitute the entire agreement of the parties hereto pertaining to the operation of the TLD and supersedes all prior agreements, understandings, negotiations and discussions, whether oral or written, between the parties on that subject. The Registry Agreement and this Addendum shall at all times be read together. Except as follows: a. if specifically provided for in this Addendum, all of the terms of the Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined Agreement shall remain unchanged and in the Trademark Clearinghouse Requirements)full force and effect, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Programand, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date extent applicable, such terms shall apply to this Addendum as if it formed part of the Sunrise Period Registry Agreement. This Addendum may be executed and delivered (as defined including by electronic transmission) in any number of counterparts, and by the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains different parties hereto in separate counterparts, each of which when executed shall be deemed to be an original but all of which taken together shall constitute a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9single instrument.

Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registryregistry-registrar agreementRegistry-Registrar Agreement entered into by ICANN-accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.

Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registry-Registrar Agreement entered into by ICANN-accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements xxxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.

Rights Protection Mechanisms. Registry Operator shall may develop and implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs RPMS required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registryregistry-Registrar Agreement registrar agreement entered into by ICANN-accredited registrars authorized to register names in the TLD. Dispute Resolution Mechanisms. Registry Operator shall implement in accordance will comply with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse following dispute resolution mechanisms as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements (the “Trademark Clearinghouse Requirements”), which they may be revised in immaterial respects by ICANN from time to time: the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) and the Registration Restriction Dispute Resolution Procedure (RRDRP) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/pddrp and xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, respectively). Registry Operator shall not mandate that agrees to implement and adhere to any owner remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of applicable intellectual property rights use any other trademark information aggregationdoubt, notification, or validation service in addition to or instead the termination of the ICANN-designated Trademark ClearinghouseRegistry Agreement pursuant to Section 6.1(c) of the Agreement) following a determination by any PDDRP panel or RRDRP and to be bound by any such determination; and the Uniform Rapid Suspension system (“URS”) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/urs), including the implementation of determinations issued by URS examiners. If there [INTENTIONALLY OMITTED] REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a conflict between the “Registry Related Party”), to: directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) subject to substantially similar conditions; register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may reserve names from registration pursuant to Section 3.1(c)(i)(B) of the Agreement; register names in the TLD or sub-domains of the TLD based upon proprietary access to information about searches or resolution requests by consumers for domain names not yet registered (commonly known as, “front-running”); or allow any Affiliated registrar to disclose Personal Data about registrants to Registry Operator or any Registry Related Party, except as follows: a. reasonably necessary for the management and operations of the TLD, unless all unrelated third parties (including other registry operators) are given equivalent access to such user data on substantially similar terms and subject to substantially similar conditions. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will, or will cause such Registry Related Party to, ensure that such services are offered through a legal entity separate from Registry Operator, and maintain separate books of accounts with respect to its registrar or registrar-reseller operations. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to an address to be provided by ICANN. (ICANN may specify in the future the form and contents of such reports or that the reports be delivered by other reasonable means.) Registry Operator agrees that ICANN may publicly post such results and certification. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct. Nothing set forth herein shall limit the ability of Registry Operator or any Registry Related Party, to enter into arms-length transactions in the ordinary course of business with a registrar or reseller with respect to products and services unrelated in all respects to the TLD. Registry Operator may request an exemption to this Code of Conduct, and such exemption may be granted by ICANN in ICANN’s reasonable discretion, if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN demonstrates to conduct an Approved Launch Program ICANN’s reasonable satisfaction that (as those terms are defined i) all domain name registrations in the Trademark Clearinghouse Requirements)TLD are registered to, and maintained by, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program for the exclusive use of Registry Operator or Approved Launch Programits Affiliates, as applicable; b. if (ii) Registry Operator does not conduct a Qualified Launch Program sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date Affiliate of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(aand (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest. REGISTRY PERFORMANCE SPECIFICATIONS DNS. Refers to the Domain Name System as specified in RFCs 1034, 1035, and Specification 9related RFCs. DNSSEC proper resolution. There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.

Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registryregistry- registrar agreementRegistry-Registrar Agreement entered into by ICANN-accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch- requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall Capitalizing “Registry-Registrar Agreement” reflects the use of the defined term. Revisions also clarify that Registry Operator must enter into a Registry- Registrar Agreement with at least one ICANN accredited registrar, and specify the timing related thereto. Section Change to Text Comments and Rationale control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: : a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; ; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Section Change to Text Comments and Rationale Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.

Rights Protection Mechanisms. Registry Operator shall may develop and implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registryregistry-Registrar Agreement registrar agreement entered into by ICANN-accredited registrars authorized to register names in the TLD. Dispute Resolution Mechanisms. Registry Operator shall implement in accordance will comply with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse following dispute resolution mechanisms as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements (the “Trademark Clearinghouse Requirements”), which they may be revised in immaterial respects by ICANN from time to time: the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/pddrp). Registry Operator shall not mandate that agrees to implement and adhere to any owner remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of applicable intellectual property rights use any other trademark information aggregationdoubt, notification, or validation service in addition to or instead the termination of the ICANN-designated Trademark ClearinghouseRegistry Agreement pursuant to Section 6.1(c) of the Agreement) following a determination by any PDDRP panel and to be bound by any such determination; and the Uniform Rapid Suspension system (“URS”) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/urs), including the implementation of determinations issued by URS examiners. If there [INTENTIONALLY OMITTED] REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a conflict between the “Registry Related Party”), to: directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) subject to substantially similar conditions; register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may reserve names from registration pursuant to Section 3.1(c)(i)(B) of the Agreement; register names in the TLD or sub-domains of the TLD based upon proprietary access to information about searches or resolution requests by consumers for domain names not yet registered (commonly known as, “front-running”); or allow any Affiliated registrar to disclose Personal Data about registrants to Registry Operator or any Registry Related Party, except as follows: a. reasonably necessary for the management and operations of the TLD, unless all unrelated third parties (including other registry operators) are given equivalent access to such user data on substantially similar terms and subject to substantially similar conditions. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will, or will cause such Registry Related Party to, ensure that such services are offered through a legal entity separate from Registry Operator, and maintain separate books of accounts with respect to its registrar or registrar-reseller operations. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to an address to be provided by ICANN. (ICANN may specify in the future the form and contents of such reports or that the reports be delivered by other reasonable means.) Registry Operator agrees that ICANN may publicly post such results and certification. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct. Nothing set forth herein shall limit the ability of Registry Operator or any Registry Related Party, to enter into arms-length transactions in the ordinary course of business with a registrar or reseller with respect to products and services unrelated in all respects to the TLD. Registry Operator may request an exemption to this Code of Conduct, and such exemption may be granted by ICANN in ICANN’s reasonable discretion, if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN demonstrates to conduct an Approved Launch Program ICANN’s reasonable satisfaction that (as those terms are defined i) all domain name registrations in the Trademark Clearinghouse Requirements)TLD are registered to, and maintained by, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program for the exclusive use of Registry Operator or Approved Launch Programits Affiliates, as applicable; b. if (ii) Registry Operator does not conduct a Qualified Launch Program sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date Affiliate of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(aand (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest. REGISTRY PERFORMANCE SPECIFICATIONS DNS. Refers to the Domain Name System as specified in RFCs 1034, 1035, and Specification 9related RFCs. DNSSEC proper resolution. There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.

Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registry-Registrar Agreement entered into by ICANN-accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch- requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-ICANN- designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registry- Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.

Rights Protection Mechanisms. Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the Registry-Registrar Agreement entered into by ICANN-accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-requirements xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch- requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-ICANN- designated Trademark Clearinghouse. If there is a conflict between the terms and conditions of this Agreement and the Trademark Clearinghouse Requirements, the terms and conditions of this Agreement shall control. Registry Operator must enter into a binding and enforceable Registry-Registry- Registrar Agreement with at least one ICANN accredited registrar authorizing such registrar(s) to register domain names in the TLD as follows: a. if Registry Operator conducts a Qualified Launch Program or is authorized by ICANN to conduct an Approved Launch Program (as those terms are defined in the Trademark Clearinghouse Requirements), Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to allocating any domain names pursuant to such Qualified Launch Program or Approved Launch Program, as applicable; b. if Registry Operator does not conduct a Qualified Launch Program or is not authorized by ICANN to conduct an Approved Launch Program, Registry Operator must enter into a binding and enforceable Registry-Registry- Registrar Agreement with at least one ICANN accredited registrar at least thirty (30) calendar days prior to the expiration date of the Sunrise Period (as defined in the Trademark Clearinghouse Requirements) for the TLD; or c. if this Agreement contains a Specification 13, Registry Operator must enter into a binding and enforceable Registry-Registrar Agreement with at least one ICANN accredited registrar prior to the Claims Commencement Date (as defined in Specification 13). Nothing in this Specification 7 shall limit or waive any other obligations or requirements of this Agreement applicable to Registry Operator, including Section 2.9(a) and Specification 9.