Changes

   <!-- Sorry, very rough start! -->

   <!-- Sorry, very rough start! -->

== Application ==

== Application ==

The TLD Application System ([[TAS]]) is ICANN’s online application system for registering new gTLDs. Applicants were required to register and submit their completed applications within the designated time frame in order to be considered. <ref>gTLD Applicant Guidebook, pdf version 2012-06-04, pp. 1-4 </ref>  

The TLD Application System ([[TAS]]) is ICANN’s online application system for registering new gTLDs. Applicants were required to register and submit their completed applications within the designated time frame in order to be considered.<ref>gTLD Applicant Guidebook, pdf version 2012-06-04, pp. 1-4 </ref>  

== Contracting Information Request ==

== Contracting Information Request ==

Contracting Information Request ([[CIR]]) invitations are sent to 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. <ref>[http://newgtlds.icann.org/en/applicants/agb/cir-guidance-21jun13-en.pdf Contracting Information Request Guidance. ICANN.]</ref>

Contracting Information Request ([[CIR]]) invitations are sent to 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.<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>  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>

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  

*(iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest." <ref name="Registry Agreement">[http://newgtlds.icann.org/en/applicants/agb/base-agreement-contracting Base Registry Agreement, pdf, p. 81.]</ref>

*(iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest."<ref name="Registry Agreement">[http://newgtlds.icann.org/en/applicants/agb/base-agreement-contracting Base Registry Agreement, pdf, p. 81.]</ref>

== CIR Review ==

== CIR Review ==

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. <ref name="Contracting"></ref>

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.<ref name="Contracting"></ref>

== Registry Agreement (with Code of Conduct Exemptions) ==  

== Registry Agreement (with Code of Conduct Exemptions) ==  

== Pre-Delegation Testing ==

== Pre-Delegation Testing ==

The Pre-Delegation Testing ([[PDT]]) process allows ICANN to determine if registries meet specific “technical and operational requirements” <ref>[http://newgtlds.icann.org/en/announcements-and-media/announcement-26aug13-en Milestone: First of the Contracted Registries Pass Pre-Delegation Testing]</ref> deemed necessary to maintain a new gTLD.

The Pre-Delegation Testing ([[PDT]]) process allows ICANN to determine if registries meet specific “technical and operational requirements”<ref>[http://newgtlds.icann.org/en/announcements-and-media/announcement-26aug13-en Milestone: First of the Contracted Registries Pass Pre-Delegation Testing]</ref> deemed necessary to maintain a new gTLD.

==Post-Delegation Processes==  

==Post-Delegation Processes==  

=== Sunrise Period ===

=== Sunrise Period ===

The [[Sunrise Period]] gives trademark holders a minimum of 30 days to register domain names that match their trademarks before these names become publicly accessible. <ref name="FAQ">[http://newgtlds.icann.org/en/about/trademark-clearinghouse/faqs FAQs: Trademark Clearinghouse]</ref> Additionally, notice must be given to all trademark holders in the clearinghouse when new gTLDs enter this process. <ref> gTLD Applicant Guidebook, pdf version 2012-06-04, p. 296 </ref>

The [[Sunrise Period]] gives trademark holders a minimum of 30 days to register domain names that match their trademarks before these names become publicly accessible.<ref name="FAQ">[http://newgtlds.icann.org/en/about/trademark-clearinghouse/faqs FAQs: Trademark Clearinghouse]</ref> Additionally, notice must be given to all trademark holders in the clearinghouse when new gTLDs enter this process. <ref> gTLD Applicant Guidebook, pdf version 2012-06-04, p. 296 </ref>

=== Trademark Clearinghouse ===

=== Trademark Clearinghouse ===

Registries are required to submit new gTLDs to the [[Trademark Clearinghouse]] (TMC or TMCH), which was established in order to protect intellectual and trademarked property. Attempts to register a mark that is already within the system will lead to notification. <ref name="FAQ"></ref>

Registries are required to submit new gTLDs to the [[Trademark Clearinghouse]] (TMC or TMCH), which was established in order to protect intellectual and trademarked property. Attempts to register a mark that is already within the system will lead to notification.<ref name="FAQ"></ref>

== Registry Onboarding ==

== Registry Onboarding ==