Name Collision Report Handling Sample Clauses

Name Collision Report Handling. 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS. 6.3.2 Registry Operator shall develop an internal process for handling in an expedited manner reports received pursuant to subsection 6.3.1 under which Registry Operator may, to the extent necessary and appropriate, remove a recently activated name from the TLD zone for a period of up to two years in order to allow the affected party to make changes to its systems.
Sample 1Sample 2Sample 3See All (2k)
AutoNDA by SimpleDocs
Name Collision Report Handling. During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS.
Sample 1Sample 2Sample 3See All (1k)
Name Collision Report Handling. 6.3.1 During the first two years after delegation of the TLD, Registry 6.3.2 Registry Operator shall develop an internal process for handling in an expedited manner reports received pursuant to subsection 6.3.1 under which Registry Operator may, to the extent necessary and appropriate, remove a recently activated name from the TLD zone for a period of up to two years in order to allow the affected party to make changes to its systems.
Sample 1Sample 2
Name Collision Report Handling. 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be
Sample 1
Name Collision Report Handling. 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS. 6.3.2 Registry Operator shall develop an internal process for handling in an expedited manner reports received pursuant to subsection 6.3.1 under which Registry Operator may, to the extent necessary and appropriate, remove a recently activated name from the TLD zone for a period of up to two years in order to allow the affected party to make changes to its systems. 1. 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.
Sample 1

Related to Name Collision Report Handling

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-­‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-­‐and-­‐ media/announcement-­‐2-­‐17nov13-­‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-­‐OARC) <xxxxx://xxx.xxx-­‐xxxx.xxx/xxxx/xxxx/xxxx>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-­‐ new-­‐gtld-­‐annex-­‐1-­‐07oct13-­‐en.pdf>.

  • Name Collision Occurrence Management 6.1. No-­‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-­‐Activation Period ends.

  • Office of Supplier Diversity The State of Florida supports its diverse business community by creating opportunities for woman-, veteran-, and minority-owned small business enterprises to participate in procurements and contracts. The Department encourages supplier diversity through certification of woman-, veteran-, and minority-owned small business enterprises and provides advocacy, outreach, and networking through regional business events. For additional information, please contact the Office of Supplier Diversity (OSD) at xxxxxxx@xxx.xxxxxxxxx.xxx.

  • Recovery Schedule If the initial schedule or any current updates fail to reflect the Work’s actual plan or method of operation, or a contractual milestone date is more than fifteen (15) days behind, Owner may require that a recovery schedule for completion of the remaining Work be submitted. The Recovery Schedule must be submitted within seven (7) calendar days of Owner’s request. The Recovery Schedule shall describe in detail Construction Contractor’s plan to complete the remaining Work by the required Contract milestone date. The Recovery Schedule submitted shall meet the same requirements as the original Construction Schedule. The narrative submitted with the Recovery Schedule should describe in detail all changes that have been made to meet the Contract milestone dates.

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