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 in writing by ICANN to Registry Operator. 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) <https://www.dns-‐oarc.net/oarc/data/ditl>. 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.
Appears in 2 contracts
Samples: Registry Agreement, Registry Agreement
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 second-level domain name, or (B) block those second-‐level 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 second-level domain names identified in writing by ICANN to Registry Operator. 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-‐OARCDNS-OARC) <https://www.dns-‐oarc.net/oarc/data/ditlxxxxx://xxx.xxx-xxxx.xxx/oarc/data/ditl>.
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.
Appears in 2 contracts
Samples: Registry Agreement, Registry Agreement
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 second-level domain name, or (B) block those second-‐level 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 second-level domain names identified in writing by ICANN and set forth at <xxxxx://xxxxxxxx.xxxxx.xxx/en/announcements-and-media/ announcement-2-17nov13-en> as such list may be modified by ICANN from time to Registry Operatortime. 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-‐OARCDNS-OARC) <https://www.dns-‐oarc.net/oarc/data/ditlxxxxx://xxx.xxx-xxxx.xxx/oarc/data/ditl>.
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.
Appears in 1 contract
Samples: Registry Agreement
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 second‐level domain name, or (B) block those second-‐level 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 second‐level domain names identified in writing by ICANN to Registry Operator. 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-‐OARCDNS‐OARC) <https://www.dns-‐oarc.net/oarc/data/ditlxxxxx://xxx.xxx‐xxxx.xxx/oarc/data/ditl>.
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.
Appears in 1 contract
Samples: Registry Agreement