New TLD contracting: Difference between revisions
Appearance
Line 8: | Line 8: | ||
# [[Pre-Delegation Testing]] (approx. 6 weeks) | # [[Pre-Delegation Testing]] (approx. 6 weeks) | ||
# Transition to IANA & Delegation (approx. 4-6 weeks) | # Transition to IANA & Delegation (approx. 4-6 weeks) | ||
# Registry Onboarding | # Registry Onboarding | ||
## approx. 6 weeks, to be completed simultaneous with PDT | |||
## Sunrise (min. 60 days) | ## Sunrise (min. 60 days) | ||
## [[TMCH]] | ## [[TMCH]] |
Revision as of 21:20, 10 December 2013
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
Steps & Timeline[edit | edit source]
- CIR
- approx. 4-6 weeks from CIR invitation to RA provisioning
- Sign Registry Agreement
- Pre-Delegation Testing (approx. 6 weeks)
- Transition to IANA & Delegation (approx. 4-6 weeks)
- Registry Onboarding
- approx. 6 weeks, to be completed simultaneous with PDT
- Sunrise (min. 60 days)
- TMCH
Contracting Information Request[edit | edit source]
- See Contracting Information Request summary and example.
- ICANN's CIR Guide, with examples
- ICANN suggested timeline between the CIR and RA: 4-6 weeks [1]
- Applicant timeline examples: _ days
Registry Agreement[edit | edit source]
- See Summary on Signing Registry Agreement
- ICANN suggested timeline: 7 days, based on the following weekly schedule [2]:
- 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 with additional time added if there are multiple negotiations between ICANN and the registry.
- Applicant timeline examples: ____ days
- Some Post RA provisioning can be done simultaneous to other phases, see Registry Onboarding.
Pre-Delegation Testing[edit | edit source]
- See Pre-Delegation Testing for summary
- ICANN suggested timeline: 2-3 weeks [3]
- 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. [2]
- Applicant timeline examples:
- ICANN's Self-Test Tools
Transition to IANA and Delegation[edit | edit source]
- ICANN's list of delegated strings
- ICANN suggested timeline: 4-6 weeks [1]
- An initial ICANN 48 presentation stated there was an estimated 2 week period for transitioning to delegation.[2]
- Applicant timeline examples:
- 5 days, Oct. 19-24; dotShabaka. [4]
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 [7]
See ICANN's Customer Portal User Guide: Transition to Delegation PDF for specific instructions.
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:
Tips[edit | edit source]
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[4]
Registry Onboarding[edit | edit source]
- ICANN suggested timeline: 6 weeks [1]
- In a previous ICANN 48 presentation, 30+ days were allotted for the Onboarding Process [2]
- Applicant timeline examples: ____ days
- Parts of registry onboarding can be done concurrently with PDT, Delegation, and Sunrise. [2]
- Contact Sheet - Establishes appropriate contacts for various contingencies.
- 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.
- 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. [8]
- Launch Program Application (PDF) provided by ICANN.
- A sample (pdf) of dotShabaka's Launch Policy
Sunrise Period[edit | edit source]
- See Sunrise Period summary, (min. 60 days)
- ICANN's current list of Sunrise and Trademark Claims Periods
- A sample (pdf) of Donuts Inc.'s Complete Registry Policy for .guru
- A sample (pdf) of dotShabaka's Sunrise Dispute Resolution Policy
Trademark Clearinghouse[edit | edit source]
- Registries can send a Trademark Clearinghouse TLD Startup Information Form to ICANN after delegation. This 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. [10] ICANN then will schedule dates that fit the TMCH requirements with IBM. Both the registry and IBM will the confirm the dates. [2]
- A sample (pdf) of Donuts Inc.'s Trademark Clearinghouse TLD Startup Information Form for .gallery
- A sample (.docx) of dotShabaka's Trademark Clearinghouse TLD Startup Information Form
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. [4]
Dot Chinese Online and Dot Chinese Website[edit | edit source]
- PDT begins-Monday Nov. 4
- PDT ends-Thursday Nov. 28
- Sunrise begins-Friday Jan. 17
- Sunrise ends-Monday Mar. 17
- 2 day quiet period
- Landrush begins-Thursday Mar. 20
- Landrush ends-Thursday Apr. 24
- 3 day quiet period
- GA begins-Monday Apr. 28
Applicant Tips[edit | edit source]
References[edit | edit source]
- ↑ 1.0 1.1 1.2 http://buenosaires48.icann.org/en/schedule/mon-new-gtld PDF New gTLD Program Update from ICANN 48 Buenos Aires Presentation
- ↑ 2.0 2.1 2.2 2.3 2.4 2.5 Papac, Krista. Registry Onboarding. PDF download
- ↑ PDT FAQ v.2.2, ICANN
- ↑ 4.0 4.1 4.2 4.3 4.4 Omer, Yasmin. dotShabaka Registry – Delegation & Beyond, ICANN 48 Presentation
- ↑ 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
- ↑ 6.0 6.1 http://edm.illuminantpartners.com/t/r-1391716757ABD0662540EF23F30FEDED TLD Registry Newsletter, Dec. 2013 issue
- ↑ http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf PDF Customer Portal User Guide: Transition to Delegation
- ↑ http://newgtlds.icann.org/en/about/trademark-clearinghouse PDF Trademark Clearinghouse Rights Protection Mechanism Requirements: Approved Launch Program Application Process
- ↑ 9.0 9.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
- ↑ PDF http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements-faqs-12nov13-en.pdf Trademark Clearinghouse Rights Protection Mechanism Requirements Frequently Asked Questions
- ↑ 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" (.中文网)