Difference between revisions of "New TLD contracting"
Jump to navigation
Jump to search
| Line 68: | Line 68: | ||
** 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 Claims Periods] | ||
=== Trademark Clearinghouse === | === Trademark Clearinghouse === | ||
Revision as of 23:09, 5 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. 8 days)
- CIR Review
- Sign Registry Agreement
- Pre-Delegation Testing (approx. 6 weeks)
- Transition to Delegation (approx. 2 weeks)
- Delegation
- Registry Onboarding
- Sunrise (min. 60 days)
Contracting Information Request[edit | edit source]
- See Contracting Information Request summary and example.
- ICANN's CIR Guide, with examples
- ICANN suggested timeline: 8 days
- Applicant timeline examples: _ days
Registry Agreement[edit | edit source]
- See Summary and Examples on Signing Registry Agreement
- ICANN suggested timeline: 7 days
- Applicant timeline examples:
- 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 [1]
- 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:
- 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.[3]
- ICANN's Self-Test Tools
Transition to Delegation[edit | edit source]
- ICANN suggested timeline: 2 weeks [2]
- Applicant timeline examples:
Delegation[edit | edit source]
- ICANN suggested timeline: within 30 business days [4]
- Applicant timeline examples: 5 days, Oct. 19-24; dotShabaka. [3]
Delegation Process[edit | edit source]
See Delegation for more information and examples.
Overview[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" [3]
Tips[edit | edit source]
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. [3]
Registry Onboarding[edit | edit source]
- ICANN suggested timeline: 30+ days [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.
Sunrise Period[edit | edit source]
- See Sunrise Period summary, (min. 60 days)
- ICANN's current list of Sunrise and Claims Periods
Trademark Clearinghouse[edit | edit source]
Applicant Examples[edit | edit source]
Applicant Timelines[edit | edit source]
This timeline shows the experience of dotShakaba, beginning with the execution of their registry agreement. [3]
Applicant tips[edit | edit source]
References[edit | edit source]
- ↑ PDT FAQ v.2.2, ICANN
- ↑ 2.0 2.1 2.2 2.3 Papac, Krista. Registry Onboarding. PDF download
- ↑ 3.0 3.1 3.2 3.3 3.4 Omer, Yasmin. dotShabaka Registry – Delegation & Beyond, ICANN 48 Presentation
- ↑ http://www.iana.org/reviews/kpis-gtld-delegation-201301 Consultation on gTLD Delegation and Redelegation Performance Standards
- ↑ 5.0 5.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