Trademark Clearinghouse Sample Clauses

Trademark Clearinghouse. 4.1 Notwithstanding the requirements of Section 2.8 of the Agreement, Section 1 of Specification 7 to the Agreement and Section 2 of the Trademark Clearinghouse Rights Protection Mechanism Requirements (the “TMCH Requirements”), Registry Operator is not required to provide a Sunrise Period (as defined in the TMCH Requirements) or, except as set forth herein, otherwise comply with the obligations set forth in Section 2 of the TMCH Requirements (collectively, the “Sunrise Requirements”) so long as the TLD continues to be qualified as a .Brand TLD by ICANN.
AutoNDA by SimpleDocs
Trademark Clearinghouse. 4.1 Notwithstanding the requirements of Section 2.8 of the Agreement, Section 1 of Specification 7 to the Agreement and Section 2 of the Trademark Clearinghouse Rights Protection Mechanism Requirements (the “TMCH Requirements”), Registry Operator is not required to provide a Sunrise Period (as defined in the TMCH Requirements) or, except as set forth herein, otherwise comply with the obligations set forth in Section 2 of the TMCH Requirements (collectively, the “Sunrise Requirements”) so long as the TLD continues to be qualified as a .Brand TLD by ICANN. 4.2 Registry Operator must comply with all other provisions of the TMCH Requirements, including completing the Integration Testing required by Section 1 of the TMCH Requirements and providing the Claims Services required by Section 3 of the TMCH Requirements. Registry Operator will provide ICANN (i) confirmation of completion of Integration Testing and (ii) notice of the start date (the “Claims Commencement Date”) and end date for the Claims Period (as defined in the TMCH Requirements) for the TLD, in each case via the customer services portal at xxxx://xxxxxxx.xxxxxx.xxxxx.xxx/. Registry Operator may not Allocate (as defined in the TMCH Requirements) or register a domain name in the TLD (except for “NIC” and self-­‐allocation or registration to itself of domain names pursuant to Section 3.2 of Specification 5) prior to the Claims Commencement Date. 4.3 Registry Operator must comply with the Sunrise Requirements effective as of the Disqualification Date and commence a Sunrise Period within 60 calendar days of the Disqualification Date. If, at the Disqualification Date, the Trademark Clearinghouse or any successor or alternative trademark validation authority appointed by ICANN is not in operation, Registry Operator must implement the Sunrise Requirements through an alternative mechanism developed by Registry Operator that is reasonably acceptable to ICANN. As of the Disqualification Date, Registry Operator may not Allocate or register any additional domain names to third parties prior to the Allocation or registration of all Sunrise Period registrations except as permitted by Section 2.2.4 of the TMCH Requirements. In the event ICANN develops an alternative version of the TMCH Requirements specifically for .Brand TLDs or former .Brand TLDs, Registry Operator agrees to comply with such alternative requirements if such requirements are similar to the TMCH Requirements in effect as of the date hereof as modif...
Trademark Clearinghouse. 4.1 Notwithstandingtherequirements of Section 2.8 ofthe Agreement, Section 1 of Specification 7 to the Agreement and Section 2 of the Trademark Clearinghouse Rights Protection Mechanism Requirements(the“TMCH Requirements”), Registry Operator is not required to provide a Sunrise Period (as defined in the TMCH Requirements) or, except as set forth herein, otherwise comply with the obligations set forth in Section 2 of the TMCHRequirements(collectively,the“SunriseRequirements”)solongas the TLD continues to be qualified as a .Brand TLD by ICANN. 4.2 Registry Operator must comply with all other provisions of the TMCH Requirements, including completing the Integration Testing required by Section 1 of the TMCH Requirements and providing the Claims Services required by Section 3 of the TMCH Requirements. Registry Operator will provide ICANN (i) confirmation of completion of Integration Testing and
Trademark Clearinghouse. 14.1. Customer may choose to offer its Users access to the Trademark Clearinghouse as described in section 14.

Related to Trademark Clearinghouse

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

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD

  • Internationalized Domain Names (IDNs) Registry Operator may offer registration of IDNs at the second and lower levels provided that Registry Operator complies with the following requirements:

  • Anti-Boycott Verification To the extent this Agreement constitutes a contract for goods or services within the meaning of Section 2270.002 of the Texas Government Code, as amended, solely for purposes of compliance with Chapter 2270 of the Texas Government Code, and subject to applicable Federal law, the Developer represents that neither the Developer nor any wholly owned subsidiary, majority-owned subsidiary, parent company or affiliate of Developer (i) boycotts Israel or (ii) will boycott Israel through the term of this Agreement. The terms “boycotts Israel” and “boycott Israel” as used in this paragraph have the meanings assigned to the term “boycott Israel” in Section 808.001 of the Texas Government Code, as amended.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • wire Unbundled ISDN Digital Loops These will be provisioned according to industry standards for 2-Wire Basic Rate ISDN services and will come standard with a test point, OC, and a DLR. NewPhone will be responsible for providing BellSouth with a Service Profile Identifier (SPID) associated with a particular ISDN-capable Loop and customer. With the SPID, BellSouth will be able to adequately test the circuit and ensure that it properly supports ISDN service.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!