Line 4: |
Line 4: |
| <br> | | <br> |
| [[ICANN]] uses CIR invitations to gain more information about the new registry including: points of contact, proof of a continued operations instrument ([[COI]]), disclosure of cross-ownership interests, and any modifications to data in previous applications.<ref>[http://newgtlds.icann.org/en/applicants/agb/cir-guidance-21jun13-en.pdf Contracting Information Request Guidance. ICANN.]</ref> | | [[ICANN]] uses CIR invitations to gain more information about the new registry including: points of contact, proof of a continued operations instrument ([[COI]]), disclosure of cross-ownership interests, and any modifications to data in previous applications.<ref>[http://newgtlds.icann.org/en/applicants/agb/cir-guidance-21jun13-en.pdf Contracting Information Request Guidance. ICANN.]</ref> |
− | In order for an application to be considered eligible for a CIR, it must meet specific criteria, such as being active.<ref name="Contracting"> [http://buenosaires48.icann.org/en/schedule/wed-contracting/presentation-contracting-20nov13-en.pdf Nguyen, Trang. Contracting.]</ref> An applicant will not receive a CIR if the new [[gTLD]] is under objection, in contention, or has received a [[GAC]] early warning.<ref name="Contracting"></ref> Additionally, if the gTLD is considered at high risk for [[name collision]] or has active changes pending, it will not qualify for a CIR invitation.<ref name="Contracting"></ref> | + | In order for an application to be considered eligible for a CIR, it must meet specific criteria, such as being active.<ref name="Contracting"> [http://buenosaires48.icann.org/en/schedule/wed-contracting/presentation-contracting-20nov13-en.pdf Nguyen, Trang. Contracting.]</ref> In particular it must: |
| + | |
| + | # Have passed Initial Evaluation; |
| + | # Not currently be in a contention set; |
| + | # Not have an unresolved objection filed against them; |
| + | # Not be a string for which issues raised in the [[GAC|Governmental Advisory Committee]]’s Beijing Communiqué <ref name="Contracting"></ref> or Durban Communiqué remain unresolved; |
| + | # Not be currently subject to a change request for which ICANN has not yet approved or denied the requested changes; and |
| + | # Not be listed as “High Risk” on the Staff [[name collision|Name Collision]] Risk Mitigation Proposal. |
| + | |
| + | An applicant will not qualify to receive a CIR <ref name="Contracting"></ref> otherwise. |
| + | |
| During the CIR process, registries may apply for a Code of Conduct (COC) exemption. In order to qualify, a registry operator must show: | | During the CIR process, registries may apply for a Code of Conduct (COC) exemption. In order to qualify, a registry operator must show: |
| + | |
| *(i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for the exclusive use of Registry Operator or its Affiliates, | | *(i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for the exclusive use of Registry Operator or its Affiliates, |
| *(ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and | | *(ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and |