Contracting Invitation Requests: Difference between revisions
No edit summary |
|||
Line 10: | Line 10: | ||
==Sample CIR== | ==Sample CIR== | ||
The CIR requires the following information: | |||
# '''Signatory Information''' - Name, Contact info | |||
# '''Point of Contact Information''' - Name, Contact info | |||
# '''File Attachments''' - includes Redlines of Registry Agreement, and COI | |||
# '''Special Circumstances''' | |||
## Cross Ownership Relations - Disclosure of applicant's involvement with any registrar, reseller | |||
## Spec. 9, Code of Conduct - Indicate if a Spec. 9 Code of Conduct Exemption is desired, if so, attach relevant request | |||
## Unique Designations - Indicate whether the applicant is a Governmental/IGO applicant and/or a Community Priority Applicant | |||
## Changes of Registry Agreement - Indicate whether you are submitting changes to the Registry Agreement, and, if so, whether these changes are based on a prior agreement with ICANN | |||
# '''Contracting Point of Contact''' - Name, Contact info | |||
# '''Additional Information''' | |||
## Indicate whether the Contracting POC is the same as Primary contact | |||
## Confirm that authorized signatory was named in Question 11 of the original application | |||
## Indicate Notices POC, to receive all general notices from ICANN | |||
## Indicate whether or not you intend to provide additional Registry Services - Those services are to be identified in Exhibit A of the Registry Agreement, any addition services to be offered must align with responses in your application, such as the response to question 23. | |||
## Confirm that your COI is in compliance with Spec. 8 of the Registry Agreement | |||
## Indicate if there are changes to applicant data that have no been previously communicated to ICANN. If so, follow the official Change Request Process. | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} |
Revision as of 00:04, 5 December 2013
Contracting Invitation Requests or CIR are invitations sent to new TLD applicants that have passed initial evaluation (IE) and are ready to continue the process of registering a new gTLD. ICANN uses CIR invitations to gain more information about the 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.[1] In order for an application to be considered eligible for a CIR, it must meet specific criteria, such as being active.[2] An applicant will not receive a CIR if the new gTLD is under objection, in contention, or has received a GAC early warning.[2] 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.[2] 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,
- (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
- (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest."[3]
CIR Review[edit | edit source]
After the CIR is submitted, it is checked for completeness and subject to a substantive review. Although ICANN processes CIRs by their priority number, any problems or errors found will result in a more lengthy CIR process and follow up procedure.[2]
Sample CIR[edit | edit source]
The CIR requires the following information:
- Signatory Information - Name, Contact info
- Point of Contact Information - Name, Contact info
- File Attachments - includes Redlines of Registry Agreement, and COI
- Special Circumstances
- Cross Ownership Relations - Disclosure of applicant's involvement with any registrar, reseller
- Spec. 9, Code of Conduct - Indicate if a Spec. 9 Code of Conduct Exemption is desired, if so, attach relevant request
- Unique Designations - Indicate whether the applicant is a Governmental/IGO applicant and/or a Community Priority Applicant
- Changes of Registry Agreement - Indicate whether you are submitting changes to the Registry Agreement, and, if so, whether these changes are based on a prior agreement with ICANN
- Contracting Point of Contact - Name, Contact info
- Additional Information
- Indicate whether the Contracting POC is the same as Primary contact
- Confirm that authorized signatory was named in Question 11 of the original application
- Indicate Notices POC, to receive all general notices from ICANN
- Indicate whether or not you intend to provide additional Registry Services - Those services are to be identified in Exhibit A of the Registry Agreement, any addition services to be offered must align with responses in your application, such as the response to question 23.
- Confirm that your COI is in compliance with Spec. 8 of the Registry Agreement
- Indicate if there are changes to applicant data that have no been previously communicated to ICANN. If so, follow the official Change Request Process.