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}} |