Jump to content

New TLD contracting: Difference between revisions

From ICANNWiki
← Older editNewer edit →
VisualWikitext
Elise (talk | contribs)
231 edits
Elise (talk | contribs)
231 edits
No edit summary
Line 32: Line 32:
* 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>
* Some Post RA provisioning can be done simultaneous to other phases, see [[#Registry Onboarding|Registry Onboarding]].
 
== Registry Onboarding Overview ==
*ICANN suggested timeline: 6 weeks, simultaneous with 6 week PDT <ref name="Program Update"></ref>
* Applicant timeline examples: ____ days
*Registry Onboarding takes place in steps throughout the contracting process. Therefore, allotting 6 weeks at PDT may not be a very helpful way to think of this process, especially as it can be started as early as after the RA is signed. 
 
===Registry Onboarding Step 1===
*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>


== Pre-Delegation Testing ==
== Pre-Delegation Testing ==
Line 81: Line 94:
*ensuring that whois is located at whois.nic.tld  
*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>
*and hosting the whois server at a different location during the delegation process<ref name="dotShabaka"></ref>
== Registry Onboarding ==
*ICANN suggested timeline: 6 weeks, simultaneous with 6 week PDT <ref name="Program Update"></ref>
**In a previous ICANN 48 presentation, 30+ days were allotted for the Onboarding Process <ref name="Onboarding"></ref>
* Applicant timeline examples: ____ days
*Much of the registry onboarding can be done concurrently with PDT, Delegation, and Sunrise. <ref name="Onboarding"></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.
** 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]


==Delegation==
==Delegation==

Revision as of 18:31, 16 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]

  1. CIR
    1. approx. 4-6 weeks from CIR invitation to RA provisioning
  2. Sign Registry Agreement
  3. Registry Onboarding: Step 1
  4. Pre-Delegation Testing (approx. 6 weeks)
  5. Registry Onboarding
    1. approx. 6 weeks, to be completed simultaneous with PDT & IANA transition
  6. Transition to IANA (approx. 4-6 weeks)
  7. Delegation
    1. TMCH
    2. Sunrise (min. 60 days)

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

Registry Agreement[edit | edit source]

  • Download Base Agreement, supplement
  • ICANN suggested timeline: 7 days, based on the following weekly schedule [3]
    • 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.
  • 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. [2]

Registry Onboarding Overview[edit | edit source]

  • ICANN suggested timeline: 6 weeks, simultaneous with 6 week PDT [1]
  • Applicant timeline examples: ____ days
  • Registry Onboarding takes place in steps throughout the contracting process. Therefore, allotting 6 weeks at PDT may not be a very helpful way to think of this process, especially as it can be started as early as after the RA is signed.

Registry Onboarding Step 1[edit | edit source]

  • 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.” [4]
    • 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. [4]

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.[2]
  • Registries also must submit individual paperwork for each new gTLD.[2]

Pre-Delegation Testing[edit | edit source]

  • See Pre-Delegation Testing for summary
  • ICANN suggested timeline: 6 weeks [5]
    • 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. [3]
  • 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.[6]
    • 24 days, Nov. 4-Nov. 28; Dot Chinese Online and Dot Chinese Website [7] [8]
    • 17 days, Nov. 25-Dec. 12; for Donuts Inc.'s .holiday [2]
      • This is the fastest time frame for PDT Donuts Inc. has experienced. [2]
    • 24 days; for Donuts Inc. [2]
  • ICANN's Self-Test Tools

Transition to IANA and Delegation[edit | edit source]

Transition to Delegation sequence, including the status of registries in the Delegation Process as of Nov. 18, 2013
  • 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, an update of the slide presentation from Buenos Aires shows that this estimate has since been lengthened. [3]
  • Applicant timeline example from the end of PDT to delegation:
    • 21 days, Oct. 17-Nov. 6; for Donuts Inc.'s .singles [2]
  • Applicant timeline examples from date of ICANN's invitation to delegation:
    • 5 days, Oct. 19-24; dotShabaka. [6]
    • 5 days, Nov. 1-Nov. 6; for Donuts Inc.'s .singles [2]

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 [9]

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:
    • 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" [6]

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[6]

Delegation[edit | edit source]

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. [3]
  • An update from the TMCH indicates that it will continue to provide notice 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. [11]

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. [6]

  • 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. [13]

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

Expected timeline[14] [8]:

  • 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]

  • Be sure your TLD is on the PSL so that it works smoothly with major browsers

References[edit | edit source]

  1. ↑ 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. ↑ 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 Ondo, Crystal. Personal Communication
  3. ↑ 3.0 3.1 3.2 3.3 Papac, Krista. Registry Onboarding. PDF download:
  4. ↑ 4.0 4.1 http://buenosaires48.icann.org/en/schedule/mon-new-gtld/transcript-new-gtld-18nov13-en PDT Papac, Krista.
  5. ↑ PDT FAQ v.2.2, ICANN
  6. ↑ 6.0 6.1 6.2 6.3 6.4 Omer, Yasmin. dotShabaka Registry – Delegation & Beyond, ICANN 48 Presentation
  7. ↑ 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
  8. ↑ 8.0 8.1 http://edm.illuminantpartners.com/t/r-1391716757ABD0662540EF23F30FEDED TLD Registry Newsletter, Dec. 2013 issue
  9. ↑ http://newgtlds.icann.org/en/applicants/customer-service/user-guide-transition-delegation-05sep13-en.pdf PDF Customer Portal User Guide: Transition to Delegation
  10. ↑ PDF http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements-faqs-12nov13-en.pdf Trademark Clearinghouse Rights Protection Mechanism Requirements Frequently Asked Questions
  11. ↑ http://domainnamewire.com/2013/12/13/a-little-bit-more-about-the-trademark-clearinghouses-extended-alert-service/ Allemann, Andrew. Retrieved on 13 Dec. 2013
  12. ↑ 12.0 12.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
  13. ↑ http://www.dotshabaka.com/register-en.php
  14. ↑ 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" (.中文网)
Retrieved from "https://icannwiki.org/index.php?title=New_TLD_contracting&oldid=84496"