Changes

# Registry Onboarding: Step 1  

# Registry Onboarding: Step 1  

# [[TMDB]] Integration Testing

# [[TMDB]] Integration Testing

# [[Pre-Delegation Testing]] (approx. 6 weeks)

# [[Pre-Delegation Testing]] (approx. 3-4 weeks)

# Transition to [[IANA]] (approx. 4-6 weeks)

# Transition to [[IANA]] (approx. 4-6 weeks)

# Delegation

# Delegation

* ICANN suggested timeline between the CIR and RA: 4-6 weeks <ref name="Program Update">http://buenosaires48.icann.org/en/schedule/mon-new-gtld PDF New gTLD Program Update from ICANN 48 Buenos Aires Presentation</ref>

* ICANN suggested timeline between the CIR and RA: 4-6 weeks <ref name="Program Update">http://buenosaires48.icann.org/en/schedule/mon-new-gtld PDF New gTLD Program Update from ICANN 48 Buenos Aires Presentation</ref>

**An applicant will have 9 months after receiving the initial CIR invitation to enter into a Registry Agreement with ICANN. Applicants may also request an extension of this period through the Customer Service Portal (CSC).<ref name="webinar"></ref> Applicants who have already received CIR invitations will start their official 9 month period on Wednesday January 29, 2014.<ref name="webinar"></ref>

**An applicant will have 9 months after receiving the initial CIR invitation to enter into a Registry Agreement with ICANN. Applicants may also request an extension of this period through the Customer Service Portal (CSC).<ref name="webinar"></ref> Applicants who have already received CIR invitations will start their official 9 month period on Wednesday January 29, 2014.<ref name="webinar"></ref>

* Applicant timeline examples:  

* Applicant timeline examples:  

**28 days, Oct. 16-Nov. 14; Donuts Inc.'s .network<ref name="Ondo">Ondo, Crystal. Personal Communication.</ref>  

**28 days, Oct. 16-Nov. 14; Donuts Inc.'s .network<ref name="Ondo">Ondo, Crystal. Personal Communication.</ref>  

== Registry Agreement ==

== Registry Agreement ==

* [http://newgtlds.icann.org/en/applicants/agb/base-agreement-contracting#cir Download Base Agreement], supplement

* [http://newgtlds.icann.org/en/applicants/agb/base-agreement-contracting#cir Download Base Agreement], supplement

* ICANN suggested timeline: 7 days, based on the following weekly schedule <ref name="Onboarding">[http://buenosaires48.icann.org/en/schedule/wed-contracting  Papac, Krista. Registry Onboarding. PDF download]:</ref>

* ICANN suggested timeline: 7 days, based on the following weekly schedule. <ref name="Onboarding">[http://buenosaires48.icann.org/en/schedule/wed-contracting  Papac, Krista. Registry Onboarding. PDF download]</ref>  

**Thursday-Monday: draft [[RA]]s

**Thursday-Monday: draft [[RA]]s

**Tuesday-Wednesday: send the RA out for signature

**Tuesday-Wednesday: send the RA out for signature

**Thursday: execute RA

**Thursday: execute RA

**Friday: post RA

**Friday: post RA

**Note: ICANN's estimate of 7 days represents how long it takes ICANN to create and process the RA internally. However, because applications are processed by priority number, this step may take longer.

**Note: ICANN's estimate of 7 days represents how long it takes ICANN to create and process the RA internally. However, because applications are processed by priority number, this step may take longer. Taking this into account, new ICANN data suggests that the average execution time for the RA once it is send to the applicant is 13 days, possibly due to renegotiation and other delays.<ref name="sing"></ref>

* Applicant timeline examples: ____ days

* Applicant timeline examples: ____ days

**Donuts Inc., which has signed RAs for a significant number of applications, generally has received RAs ready for signature on Tuesday with ICANN returning them countersigned by Thursday. <ref name="Ondo"></ref>

**Donuts Inc., which has signed RAs for a significant number of applications, generally has received RAs ready for signature on Tuesday with ICANN returning them countersigned by Thursday. <ref name="Ondo"></ref>

 

==Registry Onboarding: Step 1==

==Registry Onboarding: Step 1==

*ICANN suggested timeline: 6 weeks, simultaneous with 6 week PDT <ref name="Program Update"></ref>

*ICANN suggested timeline: 6 weeks, simultaneous with 6 week PDT <ref name="Program Update"></ref>

*To begin TMDB Integration Testing process, use the new gTLD name and registration token to register on [https://marksdb.org/tmdb/public/ TMDB's website].

*To begin TMDB Integration Testing process, use the new gTLD name and registration token to register on [https://marksdb.org/tmdb/public/ TMDB's website].

*TMDB Integration Testing for registries will include the following tests:

*TMDB Integration Testing for registries will include the following tests:

**"Download a SMD Revocation List.

**Download a SMD Revocation List.

**Download a DNL list.

**Download a DNL list.

**Upload a Sunrise LORDN file with at least three (3) domain names that have been validated using teh "testing SMDs" generated by the Trademark Clearinghouse; retrieve the related LORDN log file.

**Upload a Sunrise LORDN file with at least three (3) domain names that have been validated using the "testing SMDs" generated by the Trademark Clearinghouse; retrieve the related LORDN log file.

**Download a Trademark Notice (CNIS file) using a test 'Lookup Key' obtained by downloading a "sample DNL" file from the TMDB OT&E. Upload a Claims LORDN file with at least three (3) domain names that have been validated using the "testing CNIS files"; retrieve the related LORDN log file." <ref name="TMDB"></ref>

**Download a Trademark Notice (CNIS file) using a test 'Lookup Key' obtained by downloading a "sample DNL" file from the TMDB OT&E. Upload a Claims LORDN file with at least three (3) domain names that have been validated using the "testing CNIS files"; retrieve the related LORDN log file." <ref name="TMDB"></ref>

*For step by step instruction on TMDB Integration Testing, see ICANN's [http://newgtlds.icann.org/en/about/trademark-clearinghouse/scsvcs TMDB Registration and Platform Access Process Document or the Registry User Manual Version 2.3].  

*For step by step instruction on TMDB Integration Testing, see ICANN's [http://newgtlds.icann.org/en/about/trademark-clearinghouse/scsvcs TMDB Registration and Platform Access Process Document or the Registry User Manual Version 2.3].  

===Tips===

===Tips===

*Reading the Terms and Conditions of the TMDB, located [https://marksdb.org/tmdb/public/tandc here], ahead of time can be helpful. <ref name=dotShabaka></ref>

*Reading the Terms and Conditions of the TMDB, located [https://marksdb.org/tmdb/public/tandc here], ahead of time can be helpful. <ref name=dotShabaka></ref>

*TMDB Integration Testing does not have to be completed before PDT; it only needs to be completed before submitting TLD Startup Information.

*TMDB Integration Testing does not have to be completed before PDT; it only needs to be completed before submitting TLD Startup Information.

== Pre-Delegation Testing ==

== Pre-Delegation Testing ==

*See [[Pre-Delegation Testing]] for summary

*See [[Pre-Delegation Testing]] for summary

*The current PDT capacity is 20 testing slots per week. The number of testing slots can be increased if there is advanced notice; however, the PDT system has not yet reached or exceeded weekly capacity.<ref name="webinar"></ref>

*The current PDT capacity is 20 testing slots per week. The number of testing slots can be increased if there is advanced notice; however, the PDT system has not yet reached or exceeded weekly capacity.<ref name="webinar"></ref>

*ICANN suggested timeline: 6 weeks <ref>[http://newgtlds.icann.org/en/applicants/pdt#resources PDT FAQ v.2.2, ICANN]</ref>

*PDT invitations go out on Fridays, appointments are confirmed on Tuesdays, and results are released on Thursdays.<ref name="timeline">http://newgtlds.icann.org/en/program-status/timelines</ref>

** In prior documents, ICANN has broken this down as 2 weeks for testing, and an additional 2-3 weeks for reporting the PDT results. This seems to have been recently conflated and changed to a 6 week process, according to slides from ICANN 48 in Buenos Aires. <ref name="Onboarding"></ref>

**In a recent GDD webinar, ICANN staff estimated that the average length of PDT from starting PDT to receiving results has been 3-4 weeks, as opposed to the previously suggested 6 weeks.<ref name="gdd">http://newgtlds.icann.org/en/announcements-and-media/webinars GDD Update Webinar held May 21, 2014</ref><ref>[http://newgtlds.icann.org/en/applicants/pdt#resources PDT FAQ v.2.2, ICANN]</ref>

*Applicant timeline examples: 17-24 days, with an outlier of 39 days.

*Applicant timeline examples: 17-24 days, with an outlier of 39 days.

** 21 days, Aug. 5-Aug. 26; DotShabaka. Yasmin Omer has explained that as the first applicant to go through PDT, their experience should not be taken as indicative of current ICANN processes.<ref name="dotShabaka">Omer, Yasmin. dotShabaka Registry – Delegation & Beyond, ICANN 48 Presentation</ref>

** 21 days, Aug. 5-Aug. 26; DotShabaka. Yasmin Omer has explained that as the first applicant to go through PDT, their experience should not be taken as indicative of current ICANN processes.<ref name="dotShabaka">Omer, Yasmin. dotShabaka Registry – Delegation & Beyond, ICANN 48 Presentation</ref>

==Transition to IANA and Delegation==

==Transition to IANA and Delegation==

[[File:TransitiontoDelegationSequence.png|thumb| Transition to Delegation sequence, including the statuses of registries in the Delegation Process as of Dec. 17, 2013]]

[[File:TransitiontoDelegationSequence.png|thumb| Transition to Delegation sequence, including the statuses of registries in the Delegation Process as of March 2014 presented at ICANN 49 in Singapore.]]

*[http://newgtlds.icann.org/en/program-status/delegated-strings ICANN's list of delegated strings]

*[http://newgtlds.icann.org/en/program-status/delegated-strings ICANN's list of delegated strings]

*ICANN suggested timeline: 4-6 weeks <ref name="Program Update"></ref>

*ICANN suggested timeline: 4-6 weeks <ref name="Program Update"></ref>

**An initial ICANN 48 presentation stated there was an estimated 2 week period for transitioning to delegation, an update of the slide presentation from Buenos Aires shows that this estimate has since been lengthened. <ref name="Onboarding"></ref>

**An initial ICANN 48 presentation stated there was an estimated 2 week period for transitioning to delegation, an update of the slide presentation from Buenos Aires shows that this estimate has since been lengthened. <ref name="Onboarding"></ref>

*Applicant timeline example from the end of PDT to delegation:

*Applicant timeline example from the end of PDT to delegation:

**21 days, Oct. 17-Nov. 6; for Donuts Inc.'s .singles <ref name="Ondo"></ref>

**21 days, Oct. 17-Nov. 6; for Donuts Inc.'s .singles <ref name="Ondo"></ref>

*After ICANN validates the delegation POC, obtain IANA token later used to start delegation <ref>http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf PDF Customer Portal User Guide: Transition to Delegation</ref>

*After ICANN validates the delegation POC, obtain IANA token later used to start delegation <ref>http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf PDF Customer Portal User Guide: Transition to Delegation</ref>

See ICANN's [http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf Customer Portal User Guide: Transition to Delegation PDF] for specific instructions.

See ICANN's [http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf Customer Portal User Guide: Transition to Delegation PDF] for specific instructions.

===Delegation Process===

===Delegation Process===

Below is an overview provided by the dotShabaka Registry:

Below is an overview provided by the dotShabaka Registry:

*"Notification of eligibility for Alternate Path to delegation and report

*Notification of eligibility for Alternate Path to delegation and report

* Request for Delegation POC

* Request for Delegation POC

* Delegation token sent through CSC portal

* Delegation token sent through CSC portal

**Land Rush Ends: Thursday May 22, 2014

**Land Rush Ends: Thursday May 22, 2014

**Quiet Period 2: May 23-25, 2014

**Quiet Period 2: May 23-25, 2014

**General Availability: Monday May 26, 2014

**General Availability: Tuesday May 27, 2014

====Top Level Design's .ink====

====Top Level Design's .ink====

*Filing a change request can result in a 4-6 week delay depending on the change. Changing POCs can take as little as 1-2 days.<ref name="apweb"></ref> Large "material" changes can result in applicant re-evaluation which can cost up to $10,000 for financial or technical changes and $2,000 for registry services, and take longer to review.<ref name="apweb"></ref>

*Filing a change request can result in a 4-6 week delay depending on the change. Changing POCs can take as little as 1-2 days.<ref name="apweb"></ref> Large "material" changes can result in applicant re-evaluation which can cost up to $10,000 for financial or technical changes and $2,000 for registry services, and take longer to review.<ref name="apweb"></ref>

*Look for possible changes to the contracting process regarding name collision proceedings for delegated vs. not-yet-delegated names as ICANN has just released a new [https://www.icann.org/en/about/staff/security/ssr/name-collision-mitigation-26feb14-en.pdf Name Collision Mitigation Report] that suggests possible changes to the current new gTLD program. However, the report is still undergoing public comment.

*Look for possible changes to the contracting process regarding name collision proceedings for delegated vs. not-yet-delegated names as ICANN has just released a new [https://www.icann.org/en/about/staff/security/ssr/name-collision-mitigation-26feb14-en.pdf Name Collision Mitigation Report] that suggests possible changes to the current new gTLD program. However, the report is still undergoing public comment.

==References==

==References==

{{reflist}}

{{reflist}}</div>