Jump to content

New TLD contracting: Difference between revisions

From ICANNWiki
← Older edit
VisualWikitext
Elise (talk | contribs)
231 edits
No edit summary
Elise (talk | contribs)
231 edits
 
(189 intermediate revisions by 7 users not shown)
Line 1: Line 1:
The following is an outline of the Contracting process as defined by ICANN, it is our goal to supplement this with actual contracting timelines and action items that are encountered by new TLD applicants. Information can be edited directly, or contact [[Andrew Merriam]],  andrew[at]tldesign.co
The following is an outline of the Contracting process for New gTLD applicants as defined by [[ICANN]]. It is our goal to supplement this with actual contracting timelines and action items that are encountered by new [[TLD]] applicants. Information can be edited directly, or contact [[Elise Ferguson]],  elise[at]tldesign.co


==Steps & Timeline==  
==Steps & Timeline==  
[[File:Registry Onboarding Timeline.png|thumb]]
[[File:Registry Onboarding Timeline.png|thumb]]
# [[CIR]] (approx. 8 days)
# [[CIR]]  
## CIR Review
## approx. 4-6 weeks from CIR invitation to RA provisioning
# Sign Registry Agreement
# Sign [[Registry Agreement]]
# [[Pre-Delegation Testing]] (approx. 6 weeks)
##ICANN estimates it will take 60 days from signing the RA to Delegation if there are no delays<ref name="sing">http://singapore49.icann.org/en/schedule/mon-new-gtld PDF Download. Willett, Christine. Singapore New gTLD Program Update</ref>
# Transition to Delegation (approx. 2 weeks)
# Registry Onboarding: Step 1
# [[TMDB]] Integration Testing
# [[Pre-Delegation Testing]] (approx. 3-4 weeks)
# Transition to [[IANA]] (approx. 4-6 weeks)
# Delegation
# Delegation
# Registry Onboarding
#Registry Onboarding: Step 2
#Registry Onboarding: Step 3
##TLD Startup Information
##TMCH
## Sunrise (min. 60 days)
## Sunrise (min. 60 days)


== Contracting Information Request ==
== Contracting Information Request (CIR) ==
* See [[CIR|Contracting Information Request]] summary and example.  
*'''UPDATE''': as of February 18, 2014, ICANN has released a new CIR form that is designed to be more user friendly. Guidelines addressing the new CIR have been posted on ICANN's website. This new form should not affect any applicant who has already successfully submitted the CIR. However, for those currently filling out the CIR, their data should be transferred onto the new CIR form.<ref name="apweb">http://newgtlds.icann.org/en/announcements-and-media/webinars PDF download Applicant Update Webinar, February 21, 2014.</ref>
** ICANN's [http://newgtlds.icann.org/en/applicants/agb/base-agreement-contracting#cir CIR Guide, with examples]
**The main changes to the CIR include: removing the COI section and Exhibit A section.<ref name="apweb"></ref> Although these sections are no longer included in the CIR, COI information and any declarations of cross ownership must still be provided through cases in the CSC portal in order for the overall contracting process to move forward.<ref name="apweb"></ref>
* ICANN suggested timeline: 8 days
**The one element that seems to be added to the new CIR is a Billing Point of Contact section.<ref name="apweb"></ref>
* Applicant timeline examples: _ days
*See [[CIR|Contracting Information Request]] summary and example.  
** ICANN's [http://newgtlds.icann.org/en/applicants/agb/base-agreement-contracting#cir CIR Guide, with examples & Sample Disclosures of Cross Ownership Interests and Irrevocable Standby Letters of Credit]
**CIR invitations go out on Wednesdays.<ref name="webinar">http://newgtlds.icann.org/en/announcements-and-media/webinars New gTLD Applicant Webinar, Jan. 22</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>
**New information from ICANN Singapore suggests that the time between filling out the CIR and executing the RA could take as little as 3 weeks.<ref name="sing"></ref> However, as many as 61% of applicants "are processed within 41 calendar days."<ref name="sing"></ref>
* Applicant timeline examples:  
**28 days, Oct. 16-Nov. 14; Donuts Inc.'s .network<ref name="Ondo">Ondo, Crystal. Personal Communication.</ref>
**29 days, Nov. 6-Dec. 14; Donuts Inc.'s .report<ref name="Ondo"></ref>


== Registry Agreement ==
== Registry Agreement ==
* See Summary and Examples on Signing [[Registry Agreement]]
* [http://newgtlds.icann.org/en/applicants/agb/base-agreement-contracting#cir Download Base Agreement], supplement
* ICANN suggested timeline: 7 days
* 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>
* Applicant timeline examples:
**Thursday-Monday: draft [[RA]]s
**Tuesday-Wednesday: send the RA out for signature
**Thursday: execute 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. 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
**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>


=== Post RA Provisioning ===
==Registry Onboarding: Step 1==
* [[Contact Sheet]] - Establishes appropriate contacts for various contingencies.
*ICANN suggested timeline: 6 weeks, simultaneous with 6 week PDT <ref name="Program Update"></ref>
* [[Delegation Info]] - Can be established concurrently with PDT, but must be completed prior to Delegation. Includes information on Zone File Access; Bulk Thin Registration Data Access; Data Escrow Registry Reporting; URS; EPP; IDN Tables; SLA Monitoring.
* Applicant timeline examples: ____ days
*Registry Onboarding takes place in steps throughout the contracting process.
*The first step of Registry Onboarding can take place after the execution of the RA, and it includes gathering contact information and verifying  “credentialing and operational support.” <ref name="transcript">http://buenosaires48.icann.org/en/schedule/mon-new-gtld/transcript-new-gtld-18nov13-en PDT Papac, Krista.</ref>
** [[Contact Sheet]] - Establishes appropriate contacts for various contingencies.
** [[Onboarding Information Request]] (ONB-IR) - Can be established concurrently with PDT, but must be completed prior to Delegation. Includes information on Zone File Access; Bulk Thin Registration Data Access; Data Escrow Registry Reporting; URS; EPP; IDN Tables; SLA Monitoring.
*Without completing this step, one cannot move on to delegation. <ref name="transcript"></ref>
===Applicant Tips and Experience===
*The ONB-IR is sent out as a text file and must be submitted as a text file, unlike other documents ICANN asks registries to submit.<ref name="Ondo"></ref>
*Registries also must submit individual paperwork for each new gTLD.<ref name="Ondo"></ref>
*New information given in a recent Applicant Update Webinar stated that while step 1 of Registry Onboarding was expected to be completed simultaneously with PDT, many applicants are not ready to submit or have not already submitted the ONB-IR information by the end of PDT.<ref name="apweb"></ref> This may increase the time it takes to reach delegation.


==TMDB Integration Testing==
*Integration Testing can start after the RA or RAA is signed, though a registry operator or registrar can request a registration token via email prior to signing if they have an active gTLD application. <ref name="TMDB"> http://newgtlds.icann.org/en/about/trademark-clearinghouse/scsvcs PDF TMDB Registration and Platform Access Process Document </ref>
*ICANN suggested timeline: Integration Testing must be completed before TLD Startup Information can be submitted. It does not need to be completed before PDT.
*Applicant timeline examples:___
*Certification that one has passed TMDB Integration Testing is a necessary component of the TLD Startup Information.
*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:
**Download a SMD Revocation List.
**Download a DNL list.
**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>
***If the connection to download the CNIS appears to be hanging check your source IP matches the ACL IP in the CNIS TMDB Test Profile.
*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===
*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.
*Exemption for additional TLDs can be applied for after three (3) certification passes, see [http://newgtlds.icann.org/en/about/trademark-clearinghouse/scsvcs/certification-exemption-request-template-10feb14-en.doc] for the template, populate section 1 only and email the .doc file to IBM.
== Pre-Delegation Testing ==
== Pre-Delegation Testing ==
*See [[Pre-Delegation Testing]] for summary
*See [[Pre-Delegation Testing]] for summary
*ICANN suggested timeline: 2-3 weeks <ref>[http://newgtlds.icann.org/en/applicants/pdt#resources PDT FAQ v.2.2, ICANN]</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>
** 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">[http://buenosaires48.icann.org/en/schedule/wed-contracting  Papac, Krista. Registry Onboarding. PDF download]</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>
*Applicant timeline examples:  
*ICANN suggested timeline: 3-4 weeks
** 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>
**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>
* [http://newgtlds.icann.org/en/applicants/pdt#resources ICANN's Self-Test Tools]
*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>
** 24 days, Nov. 4-Nov. 28; Dot Chinese Online and Dot Chinese Website <ref>http://internetregistry.info/pre-delegation-testing-start-date-announced-dot-chinese-online-%E5%9C%A8%E7%BA%BF-dot-chinese-website-%E4%B8%AD%E6%96%87%E7%BD%91/ TLD Registry: The Essential New Chinese TLDs</ref> <ref name="Newsletter">http://edm.illuminantpartners.com/t/r-1391716757ABD0662540EF23F30FEDED TLD Registry Newsletter, Dec. 2013 issue </ref>
** 17 days, Nov. 25-Dec. 12; for Donuts Inc.'s .holiday <ref name="Ondo"></ref>
***This is the fastest time frame for PDT Donuts Inc. has experienced. <ref name="Ondo"></ref>
** 24 days; for Donuts Inc. <ref name="Ondo"></ref>
** 18 days, Nov. 4-21; for DotStrategy's .buzz<ref name="buzz">Doshier, Bill. Personal Communication.</ref>
** 39 days, Jan. 13-Feb. 20; for Top Level Design's .ink.
===Tips & Resources===
*Changes to the PDT Process may be made by ICANN, possibly regarding data escrow, in the coming months; those applicants who have already completed PDT will not be held accountable for new or differing requirements.<ref name="webinar"></ref>
*Be prepared to complete any additional ONB-IR requests during PDT.<ref name="buzz"></ref>
*Applicants need to use a specific PDT encryption key for testing Data Escrow services.<ref>Kuhl, Rubens. Personal Communication</ref>
**See the [https://pdt.iis.se/files/pdtescrow.pub PDT encryption key]
*[http://newgtlds.icann.org/en/applicants/pdt#resources ICANN's Self-Test Tools]


==Transition to Delegation==
==Transition to IANA and Delegation==
* ICANN suggested timeline: 2 weeks <ref name="Onboarding"></ref>  
[[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.]]
* Applicant timeline examples:
*[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>
**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>
*Generally, Delegation POC requests are sent out on Tuesdays and Delegation Tokens are sent on Thursdays.<ref name="timeline"></ref>
*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>
**20 days; for Top Level Design's .ink
*Applicant timeline examples from date of ICANN's invitation to delegation:
**5 days, Oct. 19-24; dotShabaka. <ref name="dotShabaka"></ref>
**5 days, Nov. 1-Nov. 6; for Donuts Inc.'s .singles <ref name="Ondo"></ref>
*Applicant timeline example from receiving delegation token to delegation:
**6 days, Dec. 12-18; for DotStrategy's .buzz<ref name="buzz"></ref>
**14 days, Feb. 27-Mar. 12; for Top Level Design's .ink
===Transition to IANA===
Below is a brief overview of the transition process provided by ICANN:
*Open the Transition to IANA Case in the Customer Portal
*Provide Delegation [[POC]]
*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.
====Tips====
At ICANN 49, an IANA representative offered some advice to applicants to help their transition to IANA go more smoothly:<ref name="fortynine"></ref>
*Know that every contact provided by the registry to IANA will be contacted and must respond from each email account listed, even if the accounts belong to the same person.
*Make sure the appointed delegation POC is prepared to receive the pin via email.
*IANA will ask for the name of the organization, the name provided by the delegation POC must exactly match the name on the RA; if it does not, it will fail IANA's verification mechanisms.
*If you receive a notice from IANA regarding a technical failure on the part of the registry or its credentials, there may not be a need to panic. IANA's verification and checks are designed to be conservative and may result in false positives. If you are notified of this kind of failure, contact IANA.


==Delegation==
*ICANN suggested timeline: within 30 business days <ref>http://www.iana.org/reviews/kpis-gtld-delegation-201301 Consultation on gTLD Delegation and Redelegation Performance Standards</ref>
*Applicant timeline examples:
===Delegation Process===
===Delegation Process===
See [[Delegation]] for more information and examples.
 
====Overview====
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
* Delegation PIN sent to Delegation POC
* Delegation PIN sent to Delegation POC
* Token and pin entered into RZM system to initiate process
* Token and pin entered into [[RZM]] system to initiate process
* Following information entered:
* Following information entered:
** Manager: also know as the "Registry" or "Sponsoring Organization"
** Manager: also know as the "Registry" or "Sponsoring Organization"
Line 56: Line 136:
** Authoritative Name servers maintained to serve the TLD
** Authoritative Name servers maintained to serve the TLD
** Registration Information: additional information including location of whois server" <ref name="dotShabaka"></ref>
** Registration Information: additional information including location of whois server" <ref name="dotShabaka"></ref>
====Tips====
===Tips===
dotShabaka also had some recommendations and tips for the delegation process,  such as making sure that the Delegation POC and Primary Contact are the same and ensuring that whois is located at whois.nic.tld. Additionally, the whois server needs to be established to continue through the RZM system, which can become an issue. Hosting the whois server at a different location during the process can solve this problem. <ref name="dotShabaka"></ref>
*dotShabaka also had some recommendations for the delegation process,  such as:
#making sure that the Delegation POC and Primary Contact are the same
#ensuring that whois is located at whois.nic.tld  
#and hosting the whois server at a different location during the delegation process<ref name="dotShabaka"></ref>
*Some applicants have found it helpful to have TLD Startup Information prepared and ready to be submitted directly after the new gTLD is delegated.
*The quick 5-6 day turn around seems to be fairly consistent for delegation. Plan accordingly, and be prepared with plans for the new gTLD's website, nic.newtld.<ref name="buzz"></ref>
*A recent webinar clarified that it is not required for the applicant to have a website at nic.newtld but that at delegation whois.nic.newtld should be set up.<ref name="webinar"></ref>
*When listing your name servers for IANA during the delegation process, make sure you enter both the IPv4 and IPv6 addresses separated by a space.
*Make sure both Delegation POC and Primary Contact are responsive.
 
==Delegation==
==Registry Onboarding: Step 2==
*Step 2 of Registry Onboarding starts at delegation.
*It mainly involves using the information provided in Step 1 to institute service infrastructures.<ref name="transcript"></ref>
*See ICANN 48's [http://buenosaires48.icann.org/en/schedule/wed-contracting/presentation-contracting-20nov13-en Contracting and Registry Onboarding Presentation] for an overview of the complete list of infrastructures set up during Step 2.
 
==Registry Onboarding: Step 3==
*Step 3 can begin "as early as delegation." <ref name="transcript"></ref>
===TLD Startup Information===
*'''TLD Startup Information Form''': outlines the Sunrise, Claims, and other registration periods for the new TLD, in addition to describing the registry's policies, such as any specific restrictions on registration during the Sunrise and Claims Periods. <ref>PDF http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements-faqs-12nov13-en.pdf Trademark Clearinghouse Rights Protection Mechanism Requirements Frequently Asked Questions</ref> It should also include certification that the registry has passed TMCH Integration Testing. <ref name="Onboarding"></ref>
**Blank [http://newgtlds.icann.org/en/about/trademark-clearinghouse/scsvcs/startup-info-form-17nov13-en.pdf TLD Startup Information Form]
**A sample (pdf) of Donuts Inc.'s [http://www.icann.org/sites/default/files/tlds/gallery/gallery-startup-info-17nov13-en.pdf Trademark Clearinghouse TLD Startup Information Form for .gallery]
** A sample (.docx) of dotShabaka's [http://www.icann.org/en/about/agreements/registries/xn--ngbc5azd Trademark Clearinghouse TLD Startup Information Form]
 
*Launch Program Application: can be completed anytime after the contracting process has begun and needs to be submitted to ICANN before the Sunrise Period starts.<ref>http://newgtlds.icann.org/en/about/trademark-clearinghouse PDF Trademark Clearinghouse Rights Protection Mechanism Requirements: Approved Launch Program Application Process </ref>
**[http://newgtlds.icann.org/en/about/trademark-clearinghouse/launch-application-process-12nov13-en.pdf Launch Program Application (PDF)] provided by ICANN.
***A sample (pdf) of dotShabaka's [http://www.icann.org/sites/default/files/tlds/xn--ngbc5azd/xn--ngbc5azd-launch-policy-23oct13-en.pdf Launch Policy]
**New information on Qualified Launch Plans (QLPs) is expected to be released by ICANN. There is currently a draft that is open to public comment that addresses if and how registries could allocate some of their 100 reserved names to 3rd parties for the promotion of new gTLDs.<ref name="apweb"></ref>  QLPs could allow applicants to give names to 3rd parties as long as the name is not on the TMCH list (unless it will be allocated to the rights holder or public authorities).<ref name="apweb"></ref>
====Tips & Additional Information====
*It is not necessary to provide gTLD prices or pricing strategies in Startup Documents.<ref>http://newgtlds.icann.org/en/announcements-and-media/webinars, 22 January 2014; Additional Questions and Answers PDF</ref>


=== Trademark Clearinghouse ===
*After the 7 day window ICANN uses to process the TLD Startup Information, it then will schedule dates that fit the TMCH requirements with IBM for the claims period. Both the registry and IBM will then confirm the dates. <ref name="Onboarding"></ref>


*An update from the TMCH indicates that it will continue to provide Notice of Registered Names (NORN) to trademark holders if an individual registers domains matching their TMCH stored trademark after the 90 day period required in the new gTLD program ends. <ref>http://domainnamewire.com/2013/12/13/a-little-bit-more-about-the-trademark-clearinghouses-extended-alert-service/ Allemann, Andrew. Retrieved on 13 Dec. 2013</ref>


=== Registry Onboarding ===
=== Sunrise Period ===
=== Sunrise Period ===
* See [[Sunrise Period]] summary, (min. 60 days)
* See [[Sunrise Period]] summary, (min. 60 days)
** ICANN mandated timeline for Start Date Sunrise: 30 day notice period with a minimum of 30 days running <ref name="First">Murphy, Kevin. First Come, First-Served Sunrise Periods on the Cards. http://domainincite.com/14627-first-come-first-served-sunrise-periods-on-the-cards</ref>
** ICANN mandated timeline for Start Date Sunrise: 30 day notice period with a minimum of 30 days running <ref name="First">Murphy, Kevin. First Come, First-Served Sunrise Periods on the Cards. http://domainincite.com/14627-first-come-first-served-sunrise-periods-on-the-cards</ref>
** ICANN mandated timeline for End Date Sunrise: no notice period, minimum of 60 days running <ref name="First"></ref>
** ICANN mandated timeline for End Date Sunrise: no notice period, minimum of 60 days running <ref name="First"></ref>
*ICANN's current list of [http://newgtlds.icann.org/en/program-status/sunrise-claims-periods Sunrise and Trademark Claims Periods]
** A sample (pdf) of [[Donuts]] Inc.'s [http://www.icann.org/sites/default/files/tlds/guru/guru-sunrise-overview-12nov13-en.pdf Complete Registry Policy for .guru]
** A sample (pdf) of [[.shabaka|dotShabaka's]] [http://www.icann.org/sites/default/files/tlds/xn--ngbc5azd/xn--ngbc5azd-sdrp-18oct13-en.pdf Sunrise Dispute Resolution Policy]
** A sample (pdf) of .buzz's [http://newgtlds.icann.org/en/node/17509 Sunrise Policy and Sunrise Dispute Resolution Policy]


=== Trademark Clearinghouse ===
== Applicant Examples ==
== Applicant Examples ==
===Applicant Timelines===
===Applicant Timelines===
[[file:dotShabakaRegistryTimeline.png|thumb]] This timeline shows the experience of dotShakaba, beginning with the execution of their registry agreement. <ref name="dotShabaka"></ref>
====dotShabaka====
===Applicant tips===
[[file:dotShabakaRegistryTimeline.png|thumb]] This image shows the experience of [[dotShabaka]], beginning with the execution of their registry agreement. <ref name="dotShabaka"></ref>
*NOTE: dotShabaka's 30 day Landrush Period is scheduled to begin on Jan. 2 and to conclude on Jan. 31, 2014. It's General Availability (GA) date is set for Feb. 4, 2014. <ref>http://www.dotshabaka.com/register-en.php</ref>
 
====Dot Chinese Online and Dot Chinese Website====
Expected timeline<ref>http://internetregistry.info/go-live-dates-dot-chinese-online-%E5%9C%A8%E7%BA%BF-dot-chinese-website-%E4%B8%AD%E6%96%87%E7%BD%91/ Isokoski, Arto. "Go-Live Dates for Dot Chinese Online (.在线) & Dot Chinese Website" (.中文网)</ref> <ref name="Newsletter"></ref>:
*[[PDT]] begins-Monday Nov. 4, 2013
*PDT ends-Thursday Nov. 28, 2013
*[[Sunrise]] begins-Friday Jan. 17, 2014
*Sunrise ends-Monday Mar. 17, 2014
*2 day quiet period
*Landrush begins-Thursday Mar. 20, 2014
*Landrush ends-Thursday Apr. 24, 2014
*3 day quiet period
*GA begins-Monday Apr. 28, 2014
 
====DotStrategy's .Buzz Timeline====
.Buzz's timeline:<ref name="buzz"></ref>
*CIR Form-Wednesday Sept. 11, 2013
*RA Executed-Wednesday Oct. 2, 2013<ref>http://www.icann.org/en/about/agreements/registries/buzz</ref>
*PDT Eligibility Notice-Friday Oct. 4, 2013
*Additional ONB-IR Q38 and Q39-Monday Nov. 4, 2013
*PDT begins-Monday Nov. 4, 2013
*PDT ends-Thursday Nov. 21, 2013
*Transition to IANA: POC Request-Friday Dec. 6, 2013
*Transition to IANA: Token-Thursday Dec. 12, 2013
*Delegated-Wednesday Dec. 18, 2013
*Start-Up Information Submitted to ICANN-Friday Dec. 20, 2013
*Launch Dates confirmed-Monday Dec. 23, 2013
*Sunrise begins-Wednesday Jan. 15, 2014
*Sunrise ends-Tuesday Mar. 18, 2014
*Landrush begins-Thursday Mar. 20, 2014
*Landrush ends-Thursday Apr. 10, 2014
*5 day quite period
*GA begins-Tuesday Apr. 15, 2014
 
====Top Level Design's .wiki====
.wiki is currently going through the new gTLD contracting program and will update its timeline as it hits important landmarks in the process.
*Signed RA-Thursday Nov. 7, 2013
*PDT begins-Monday Jan. 6, 2014
*PDT passed-Thursday Jan. 30, 2014
*Transition to IANA: POC Request-Tuesday Feb. 4, 2014
*Transition to IANA: Token-Thursday Feb. 7, 2014
*Transition to IANA: Information Sent-Monday Feb. 10, 2014
*Delegation: Wednesday Feb. 19, 2014
*Submitted Start-up Information: Thursday Feb. 20, 2014
*ICANN Confirms Launch Dates: Wednesday Feb. 26, 2014
**Sunrise Begins: Monday Mar. 3, 2014
**Sunrise Ends: Monday May 5, 2014
**Quiet Period 1: May 6-7, 2014
**Land Rush Begins: Thursday May 8, 2014
**Land Rush Ends: Thursday May 22, 2014
**Quiet Period 2: May 23-25, 2014
**General Availability: Tuesday May 27, 2014
 
====Top Level Design's .ink====
.ink is currently going through the new gTLD contracting program and will update its timeline as it hits important landmarks in the process.
*Signed RA-Thursday, December 5
*PDT Begins-Thursday, Jan 30
*PDT Ends-Thursday, Feb 20
**Note: This 39 day period in PDT seems to be longer than the averages suggested by other applicants.
*Transition to IANA: POC Request-Tuesday, Feb 25, 2014
*Transition to IANA: Token-Thursday, Feb 27, 2014
*Transition to IANA: Information Sent-Friday, Feb 28, 2014
*Delegation: Wednesday March 12, 2014
**Note: 13 days seems to be longer than average amount of time to reach delegation based on the other timeline examples.
*Submitted Start-up Information: Friday March 14, 2014
*ICANN Confirms Launch Dates: Thursday March 20, 2014
**Sunrise Begins: Monday, March 31
**Sunrise Ends: Monday, June 2
**Quiet Periods 1: June 3-4
**Land Rush Begins: Thursday, June 5
**Land Rush Ends: Thursday, June 19
**Quiet Period 2: June 20-22
**General Availability: Monday, June 23
 
===Applicant Tips===
 
* Be sure your TLD is on the [[PSL]] so that it works smoothly with major browsers.
*Applicants found ICANN's customer service responses to questions to be helpful and timely.<ref name="Ondo"></ref><ref name="buzz"></ref> Contact ICANN through the Customer Service Portal or by emailing questions to newgltd@ICANN.org.
*Be prepared for important documents or notices to be sent out for completion by ICANN on Fridays.<ref name="buzz"></ref>
*While .buzz initially received priority #746, it was the 54th string delegated.<ref name="buzz"></ref> Having a higher priority number, then, may not necessarily slow down the delegation process at this point in the new gTLD program.
*The February Applicant Update Webinar released these statistics: applicants who signed RAs in November or December were able to reach delegation in 60 days on average as opposed to 75 days which was the average for applicants who signed RAs before November.<ref name="apweb"></ref> ICANN representatives identified the decrease in time as a result of applicant responsiveness and readiness.<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.
**Statements made at ICANN Singapore suggest that strings that have already been delegated will not be affected by any new proposal adopted but will use the previously agreed upon name collision mitigation techniques.<ref name="sing"></ref>
 
==References==
==References==
{{reflist}}
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
{{reflist}}</div>


__NOTOC__
[[Category:New gTLD Program]]

Latest revision as of 22:22, 20 March 2015

The following is an outline of the Contracting process for New gTLD applicants as defined by ICANN. It is our goal to supplement this with actual contracting timelines and action items that are encountered by new TLD applicants. Information can be edited directly, or contact Elise Ferguson, elise[at]tldesign.co

Steps & Timeline[edit | edit source]

  1. CIR
    1. approx. 4-6 weeks from CIR invitation to RA provisioning
  2. Sign Registry Agreement
    1. ICANN estimates it will take 60 days from signing the RA to Delegation if there are no delays[1]
  3. Registry Onboarding: Step 1
  4. TMDB Integration Testing
  5. Pre-Delegation Testing (approx. 3-4 weeks)
  6. Transition to IANA (approx. 4-6 weeks)
  7. Delegation
  8. Registry Onboarding: Step 2
  9. Registry Onboarding: Step 3
    1. TLD Startup Information
    2. TMCH
    3. Sunrise (min. 60 days)

Contracting Information Request (CIR)[edit | edit source]

  • UPDATE: as of February 18, 2014, ICANN has released a new CIR form that is designed to be more user friendly. Guidelines addressing the new CIR have been posted on ICANN's website. This new form should not affect any applicant who has already successfully submitted the CIR. However, for those currently filling out the CIR, their data should be transferred onto the new CIR form.[2]
    • The main changes to the CIR include: removing the COI section and Exhibit A section.[2] Although these sections are no longer included in the CIR, COI information and any declarations of cross ownership must still be provided through cases in the CSC portal in order for the overall contracting process to move forward.[2]
    • The one element that seems to be added to the new CIR is a Billing Point of Contact section.[2]
  • See Contracting Information Request summary and example.
  • ICANN suggested timeline between the CIR and RA: 4-6 weeks [4]
    • 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).[3] Applicants who have already received CIR invitations will start their official 9 month period on Wednesday January 29, 2014.[3]
    • New information from ICANN Singapore suggests that the time between filling out the CIR and executing the RA could take as little as 3 weeks.[1] However, as many as 61% of applicants "are processed within 41 calendar days."[1]
  • Applicant timeline examples:
    • 28 days, Oct. 16-Nov. 14; Donuts Inc.'s .network[5]
    • 29 days, Nov. 6-Dec. 14; Donuts Inc.'s .report[5]

Registry Agreement[edit | edit source]

  • Download Base Agreement, supplement
  • ICANN suggested timeline: 7 days, based on the following weekly schedule. [6]
    • Thursday-Monday: draft RAs
    • Tuesday-Wednesday: send the RA out for signature
    • Thursday: execute 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. 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.[1]
  • 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. [5]

Registry Onboarding: Step 1[edit | edit source]

  • ICANN suggested timeline: 6 weeks, simultaneous with 6 week PDT [4]
  • Applicant timeline examples: ____ days
  • Registry Onboarding takes place in steps throughout the contracting process.
  • The first step of Registry Onboarding can take place after the execution of the RA, and it includes gathering contact information and verifying “credentialing and operational support.” [7]
    • Contact Sheet - Establishes appropriate contacts for various contingencies.
    • Onboarding Information Request (ONB-IR) - Can be established concurrently with PDT, but must be completed prior to Delegation. Includes information on Zone File Access; Bulk Thin Registration Data Access; Data Escrow Registry Reporting; URS; EPP; IDN Tables; SLA Monitoring.
  • Without completing this step, one cannot move on to delegation. [7]

Applicant Tips and Experience[edit | edit source]

  • The ONB-IR is sent out as a text file and must be submitted as a text file, unlike other documents ICANN asks registries to submit.[5]
  • Registries also must submit individual paperwork for each new gTLD.[5]
  • New information given in a recent Applicant Update Webinar stated that while step 1 of Registry Onboarding was expected to be completed simultaneously with PDT, many applicants are not ready to submit or have not already submitted the ONB-IR information by the end of PDT.[2] This may increase the time it takes to reach delegation.

TMDB Integration Testing[edit | edit source]

  • Integration Testing can start after the RA or RAA is signed, though a registry operator or registrar can request a registration token via email prior to signing if they have an active gTLD application. [8]
  • ICANN suggested timeline: Integration Testing must be completed before TLD Startup Information can be submitted. It does not need to be completed before PDT.
  • Applicant timeline examples:___
  • Certification that one has passed TMDB Integration Testing is a necessary component of the TLD Startup Information.
  • To begin TMDB Integration Testing process, use the new gTLD name and registration token to register on TMDB's website.
  • TMDB Integration Testing for registries will include the following tests:
    • Download a SMD Revocation List.
    • Download a DNL list.
    • 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." [8]
      • If the connection to download the CNIS appears to be hanging check your source IP matches the ACL IP in the CNIS TMDB Test Profile.
  • For step by step instruction on TMDB Integration Testing, see ICANN's TMDB Registration and Platform Access Process Document or the Registry User Manual Version 2.3.

Tips[edit | edit source]

  • Reading the Terms and Conditions of the TMDB, located here, ahead of time can be helpful. [9]
  • TMDB Integration Testing does not have to be completed before PDT; it only needs to be completed before submitting TLD Startup Information.
  • Exemption for additional TLDs can be applied for after three (3) certification passes, see [1] for the template, populate section 1 only and email the .doc file to IBM.

Pre-Delegation Testing[edit | edit source]

  • 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.[3]
  • PDT invitations go out on Fridays, appointments are confirmed on Tuesdays, and results are released on Thursdays.[10]
  • 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.[11][12]
  • 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.[9]
    • 24 days, Nov. 4-Nov. 28; Dot Chinese Online and Dot Chinese Website [13] [14]
    • 17 days, Nov. 25-Dec. 12; for Donuts Inc.'s .holiday [5]
      • This is the fastest time frame for PDT Donuts Inc. has experienced. [5]
    • 24 days; for Donuts Inc. [5]
    • 18 days, Nov. 4-21; for DotStrategy's .buzz[15]
    • 39 days, Jan. 13-Feb. 20; for Top Level Design's .ink.

Tips & Resources[edit | edit source]

  • Changes to the PDT Process may be made by ICANN, possibly regarding data escrow, in the coming months; those applicants who have already completed PDT will not be held accountable for new or differing requirements.[3]
  • Be prepared to complete any additional ONB-IR requests during PDT.[15]
  • Applicants need to use a specific PDT encryption key for testing Data Escrow services.[16]
  • ICANN's Self-Test Tools

Transition to IANA and Delegation[edit | edit source]

Transition to Delegation sequence, including the statuses of registries in the Delegation Process as of March 2014 presented at ICANN 49 in Singapore.
  • ICANN's list of delegated strings
  • ICANN suggested timeline: 4-6 weeks [4]
    • 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. [6]
    • 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.[17]
  • Generally, Delegation POC requests are sent out on Tuesdays and Delegation Tokens are sent on Thursdays.[10]
  • Applicant timeline example from the end of PDT to delegation:
    • 21 days, Oct. 17-Nov. 6; for Donuts Inc.'s .singles [5]
    • 20 days; for Top Level Design's .ink
  • Applicant timeline examples from date of ICANN's invitation to delegation:
    • 5 days, Oct. 19-24; dotShabaka. [9]
    • 5 days, Nov. 1-Nov. 6; for Donuts Inc.'s .singles [5]
  • Applicant timeline example from receiving delegation token to delegation:
    • 6 days, Dec. 12-18; for DotStrategy's .buzz[15]
    • 14 days, Feb. 27-Mar. 12; for Top Level Design's .ink

Transition to IANA[edit | edit source]

Below is a brief overview of the transition process provided by ICANN:

  • Open the Transition to IANA Case in the Customer Portal
  • Provide Delegation POC
  • After ICANN validates the delegation POC, obtain IANA token later used to start delegation [18]

See ICANN's Customer Portal User Guide: Transition to Delegation PDF for specific instructions.

Tips[edit | edit source]

At ICANN 49, an IANA representative offered some advice to applicants to help their transition to IANA go more smoothly:[17]

  • Know that every contact provided by the registry to IANA will be contacted and must respond from each email account listed, even if the accounts belong to the same person.
  • Make sure the appointed delegation POC is prepared to receive the pin via email.
  • IANA will ask for the name of the organization, the name provided by the delegation POC must exactly match the name on the RA; if it does not, it will fail IANA's verification mechanisms.
  • If you receive a notice from IANA regarding a technical failure on the part of the registry or its credentials, there may not be a need to panic. IANA's verification and checks are designed to be conservative and may result in false positives. If you are notified of this kind of failure, contact IANA.

Delegation Process[edit | edit source]

Below is an overview provided by the dotShabaka Registry:

  • Notification of eligibility for Alternate Path to delegation and report
  • Request for Delegation POC
  • Delegation token sent through CSC portal
  • Delegation PIN sent to Delegation POC
  • Token and pin entered into RZM system to initiate process
  • Following information entered:
    • Manager: also know as the "Registry" or "Sponsoring Organization"
    • Administrative and Technical Contacts
    • Authoritative Name servers maintained to serve the TLD
    • Registration Information: additional information including location of whois server" [9]

Tips[edit | edit source]

  • dotShabaka also had some recommendations for the delegation process, such as:
  1. making sure that the Delegation POC and Primary Contact are the same
  2. ensuring that whois is located at whois.nic.tld
  3. and hosting the whois server at a different location during the delegation process[9]
  • Some applicants have found it helpful to have TLD Startup Information prepared and ready to be submitted directly after the new gTLD is delegated.
  • The quick 5-6 day turn around seems to be fairly consistent for delegation. Plan accordingly, and be prepared with plans for the new gTLD's website, nic.newtld.[15]
  • A recent webinar clarified that it is not required for the applicant to have a website at nic.newtld but that at delegation whois.nic.newtld should be set up.[3]
  • When listing your name servers for IANA during the delegation process, make sure you enter both the IPv4 and IPv6 addresses separated by a space.
  • Make sure both Delegation POC and Primary Contact are responsive.

Delegation[edit | edit source]

Registry Onboarding: Step 2[edit | edit source]

  • Step 2 of Registry Onboarding starts at delegation.
  • It mainly involves using the information provided in Step 1 to institute service infrastructures.[7]
  • See ICANN 48's Contracting and Registry Onboarding Presentation for an overview of the complete list of infrastructures set up during Step 2.

Registry Onboarding: Step 3[edit | edit source]

  • Step 3 can begin "as early as delegation." [7]

TLD Startup Information[edit | edit source]

  • Launch Program Application: can be completed anytime after the contracting process has begun and needs to be submitted to ICANN before the Sunrise Period starts.[20]
    • Launch Program Application (PDF) provided by ICANN.
    • New information on Qualified Launch Plans (QLPs) is expected to be released by ICANN. There is currently a draft that is open to public comment that addresses if and how registries could allocate some of their 100 reserved names to 3rd parties for the promotion of new gTLDs.[2] QLPs could allow applicants to give names to 3rd parties as long as the name is not on the TMCH list (unless it will be allocated to the rights holder or public authorities).[2]

Tips & Additional Information[edit | edit source]

  • It is not necessary to provide gTLD prices or pricing strategies in Startup Documents.[21]

Trademark Clearinghouse[edit | edit source]

  • After the 7 day window ICANN uses to process the TLD Startup Information, it then will schedule dates that fit the TMCH requirements with IBM for the claims period. Both the registry and IBM will then confirm the dates. [6]
  • An update from the TMCH indicates that it will continue to provide Notice of Registered Names (NORN) to trademark holders if an individual registers domains matching their TMCH stored trademark after the 90 day period required in the new gTLD program ends. [22]

Sunrise Period[edit | edit source]

Applicant Examples[edit | edit source]

Applicant Timelines[edit | edit source]

dotShabaka[edit | edit source]

This image shows the experience of dotShabaka, beginning with the execution of their registry agreement. [9]

  • NOTE: dotShabaka's 30 day Landrush Period is scheduled to begin on Jan. 2 and to conclude on Jan. 31, 2014. It's General Availability (GA) date is set for Feb. 4, 2014. [24]

Dot Chinese Online and Dot Chinese Website[edit | edit source]

Expected timeline[25] [14]:

  • PDT begins-Monday Nov. 4, 2013
  • PDT ends-Thursday Nov. 28, 2013
  • Sunrise begins-Friday Jan. 17, 2014
  • Sunrise ends-Monday Mar. 17, 2014
  • 2 day quiet period
  • Landrush begins-Thursday Mar. 20, 2014
  • Landrush ends-Thursday Apr. 24, 2014
  • 3 day quiet period
  • GA begins-Monday Apr. 28, 2014

DotStrategy's .Buzz Timeline[edit | edit source]

.Buzz's timeline:[15]

  • CIR Form-Wednesday Sept. 11, 2013
  • RA Executed-Wednesday Oct. 2, 2013[26]
  • PDT Eligibility Notice-Friday Oct. 4, 2013
  • Additional ONB-IR Q38 and Q39-Monday Nov. 4, 2013
  • PDT begins-Monday Nov. 4, 2013
  • PDT ends-Thursday Nov. 21, 2013
  • Transition to IANA: POC Request-Friday Dec. 6, 2013
  • Transition to IANA: Token-Thursday Dec. 12, 2013
  • Delegated-Wednesday Dec. 18, 2013
  • Start-Up Information Submitted to ICANN-Friday Dec. 20, 2013
  • Launch Dates confirmed-Monday Dec. 23, 2013
  • Sunrise begins-Wednesday Jan. 15, 2014
  • Sunrise ends-Tuesday Mar. 18, 2014
  • Landrush begins-Thursday Mar. 20, 2014
  • Landrush ends-Thursday Apr. 10, 2014
  • 5 day quite period
  • GA begins-Tuesday Apr. 15, 2014

Top Level Design's .wiki[edit | edit source]

.wiki is currently going through the new gTLD contracting program and will update its timeline as it hits important landmarks in the process.

  • Signed RA-Thursday Nov. 7, 2013
  • PDT begins-Monday Jan. 6, 2014
  • PDT passed-Thursday Jan. 30, 2014
  • Transition to IANA: POC Request-Tuesday Feb. 4, 2014
  • Transition to IANA: Token-Thursday Feb. 7, 2014
  • Transition to IANA: Information Sent-Monday Feb. 10, 2014
  • Delegation: Wednesday Feb. 19, 2014
  • Submitted Start-up Information: Thursday Feb. 20, 2014
  • ICANN Confirms Launch Dates: Wednesday Feb. 26, 2014
    • Sunrise Begins: Monday Mar. 3, 2014
    • Sunrise Ends: Monday May 5, 2014
    • Quiet Period 1: May 6-7, 2014
    • Land Rush Begins: Thursday May 8, 2014
    • Land Rush Ends: Thursday May 22, 2014
    • Quiet Period 2: May 23-25, 2014
    • General Availability: Tuesday May 27, 2014

Top Level Design's .ink[edit | edit source]

.ink is currently going through the new gTLD contracting program and will update its timeline as it hits important landmarks in the process.

  • Signed RA-Thursday, December 5
  • PDT Begins-Thursday, Jan 30
  • PDT Ends-Thursday, Feb 20
    • Note: This 39 day period in PDT seems to be longer than the averages suggested by other applicants.
  • Transition to IANA: POC Request-Tuesday, Feb 25, 2014
  • Transition to IANA: Token-Thursday, Feb 27, 2014
  • Transition to IANA: Information Sent-Friday, Feb 28, 2014
  • Delegation: Wednesday March 12, 2014
    • Note: 13 days seems to be longer than average amount of time to reach delegation based on the other timeline examples.
  • Submitted Start-up Information: Friday March 14, 2014
  • ICANN Confirms Launch Dates: Thursday March 20, 2014
    • Sunrise Begins: Monday, March 31
    • Sunrise Ends: Monday, June 2
    • Quiet Periods 1: June 3-4
    • Land Rush Begins: Thursday, June 5
    • Land Rush Ends: Thursday, June 19
    • Quiet Period 2: June 20-22
    • General Availability: Monday, June 23

Applicant Tips[edit | edit source]

  • Be sure your TLD is on the PSL so that it works smoothly with major browsers.
  • Applicants found ICANN's customer service responses to questions to be helpful and timely.[5][15] Contact ICANN through the Customer Service Portal or by emailing questions to newgltd@ICANN.org.
  • Be prepared for important documents or notices to be sent out for completion by ICANN on Fridays.[15]
  • While .buzz initially received priority #746, it was the 54th string delegated.[15] Having a higher priority number, then, may not necessarily slow down the delegation process at this point in the new gTLD program.
  • The February Applicant Update Webinar released these statistics: applicants who signed RAs in November or December were able to reach delegation in 60 days on average as opposed to 75 days which was the average for applicants who signed RAs before November.[2] ICANN representatives identified the decrease in time as a result of applicant responsiveness and readiness.[2]
  • 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.[2] 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.[2]
  • 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 Name Collision Mitigation Report that suggests possible changes to the current new gTLD program. However, the report is still undergoing public comment.
    • Statements made at ICANN Singapore suggest that strings that have already been delegated will not be affected by any new proposal adopted but will use the previously agreed upon name collision mitigation techniques.[1]

References[edit | edit source]

  1. ↑ 1.0 1.1 1.2 1.3 1.4 http://singapore49.icann.org/en/schedule/mon-new-gtld PDF Download. Willett, Christine. Singapore New gTLD Program Update
  2. ↑ 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 http://newgtlds.icann.org/en/announcements-and-media/webinars PDF download Applicant Update Webinar, February 21, 2014.
  3. ↑ 3.0 3.1 3.2 3.3 3.4 3.5 http://newgtlds.icann.org/en/announcements-and-media/webinars New gTLD Applicant Webinar, Jan. 22
  4. ↑ 4.0 4.1 4.2 http://buenosaires48.icann.org/en/schedule/mon-new-gtld PDF New gTLD Program Update from ICANN 48 Buenos Aires Presentation
  5. ↑ 5.00 5.01 5.02 5.03 5.04 5.05 5.06 5.07 5.08 5.09 5.10 Ondo, Crystal. Personal Communication.
  6. ↑ 6.0 6.1 6.2 6.3 Papac, Krista. Registry Onboarding. PDF download
  7. ↑ 7.0 7.1 7.2 7.3 http://buenosaires48.icann.org/en/schedule/mon-new-gtld/transcript-new-gtld-18nov13-en PDT Papac, Krista.
  8. ↑ 8.0 8.1 http://newgtlds.icann.org/en/about/trademark-clearinghouse/scsvcs PDF TMDB Registration and Platform Access Process Document
  9. ↑ 9.0 9.1 9.2 9.3 9.4 9.5 Omer, Yasmin. dotShabaka Registry – Delegation & Beyond, ICANN 48 Presentation
  10. ↑ 10.0 10.1 http://newgtlds.icann.org/en/program-status/timelines
  11. ↑ http://newgtlds.icann.org/en/announcements-and-media/webinars GDD Update Webinar held May 21, 2014
  12. ↑ PDT FAQ v.2.2, ICANN
  13. ↑ http://internetregistry.info/pre-delegation-testing-start-date-announced-dot-chinese-online-%E5%9C%A8%E7%BA%BF-dot-chinese-website-%E4%B8%AD%E6%96%87%E7%BD%91/ TLD Registry: The Essential New Chinese TLDs
  14. ↑ 14.0 14.1 http://edm.illuminantpartners.com/t/r-1391716757ABD0662540EF23F30FEDED TLD Registry Newsletter, Dec. 2013 issue
  15. ↑ 15.0 15.1 15.2 15.3 15.4 15.5 15.6 15.7 Doshier, Bill. Personal Communication.
  16. ↑ Kuhl, Rubens. Personal Communication
  17. ↑ 17.0 17.1 http://singapore49.icann.org/en/schedule/mon-launch-onboarding Lentz, Karen and Krista Papac. TLD Launch Process Experiences and Registry Onboarding
  18. ↑ http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf PDF Customer Portal User Guide: Transition to Delegation
  19. ↑ PDF http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements-faqs-12nov13-en.pdf Trademark Clearinghouse Rights Protection Mechanism Requirements Frequently Asked Questions
  20. ↑ http://newgtlds.icann.org/en/about/trademark-clearinghouse PDF Trademark Clearinghouse Rights Protection Mechanism Requirements: Approved Launch Program Application Process
  21. ↑ http://newgtlds.icann.org/en/announcements-and-media/webinars, 22 January 2014; Additional Questions and Answers PDF
  22. ↑ http://domainnamewire.com/2013/12/13/a-little-bit-more-about-the-trademark-clearinghouses-extended-alert-service/ Allemann, Andrew. Retrieved on 13 Dec. 2013
  23. ↑ 23.0 23.1 Murphy, Kevin. First Come, First-Served Sunrise Periods on the Cards. http://domainincite.com/14627-first-come-first-served-sunrise-periods-on-the-cards
  24. ↑ http://www.dotshabaka.com/register-en.php
  25. ↑ http://internetregistry.info/go-live-dates-dot-chinese-online-%E5%9C%A8%E7%BA%BF-dot-chinese-website-%E4%B8%AD%E6%96%87%E7%BD%91/ Isokoski, Arto. "Go-Live Dates for Dot Chinese Online (.在线) & Dot Chinese Website" (.中文网)
  26. ↑ http://www.icann.org/en/about/agreements/registries/buzz
Retrieved from "https://icannwiki.org/index.php?title=New_TLD_contracting&oldid=98466"