Changes

*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: 3-4 weeks

*ICANN suggested timeline: 3-4 weeks

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

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

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

**In an ICANN 49 presentation, it was stated that an applicant would normally receive a delegation token about a week or so after the successful completion of PDT.<ref name="fortynine">http://singapore49.icann.org/en/schedule/mon-launch-onboarding Lentz, Karen and Krista Papac. ''TLD Launch Process Experiences and Registry Onboarding''</ref>  

**In an ICANN 49 presentation, it was stated that an applicant would normally receive a delegation token about a week or so after the successful completion of PDT.<ref name="fortynine">http://singapore49.icann.org/en/schedule/mon-launch-onboarding Lentz, Karen and Krista Papac. ''TLD Launch Process Experiences and Registry 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>

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

==References==

==References==

{{reflist}}

{{reflist}}</div>