New TLD contracting: Difference between revisions

Line 241:

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

==References==

@@ Line 241: / Line 241: @@
 *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.
 ==References==
 {{reflist}}