Policy Development Process for New gTLD Subsequent Procedures: Difference between revisions

← Older edit

VisualWikitext

@@ Line 16: / Line 16: @@
 ICANN stated the intention to introduce new application rounds of gTLDs on an ongoing basis after the first round.<ref name="agb" /> The AGB explains that the timing of future application rounds would be based on the “experience gained and changes required” after the completion of the first round.<ref name="agb" /> After the application period closed, the GNSO created a Discussion Group (DG) to evaluate the first round of applications and use experiences to identify potential areas for policy development for subsequent rounds.<ref>[https://community.icann.org/display/DGNGSR Discussion Group on New gTLD Subsequent Rounds], Archived Wiki, ICANN.org</ref> The DG submitted its Final Issue Report in December 2015<ref>[https://gnso.icann.org/en/issues/new-gtlds/subsequent-procedures-final-issue-04dec15-en.pdf Final Issue Report on New gTLD Subsequent Procedures], December 4, 2015 (PDF)</ref> After review, the GNSO Council initiated the New gTLD Subsequent Procedures Policy Development Process Working Group in January 2016.<ref>[https://community.icann.org/display/NGSPP/New+gTLD+Subsequent+Procedures+PDP+Home New GTLD Subsequent Procedures PDP Workspace]</ref>
+During [[ICANN 76]], the [[ICANN Board]] adopted 98 recommendations contained in the [[SUBPRO|New gTLD Subsequent Procedures Policy Development Process Final Report]], setting in motion the implementation process for the next round of [[New gTLD Program|new generic top-level domains]].<ref>[https://www.icann.org/en/announcements/details/icann-board-moves-to-begin-preparations-for-the-next-round-of-new-gtlds-16-03-2023-en ICANN Board Moves to Begin Preparations for the next round of nTLDs, ICANN Announcements]</ref>
 {|align=right
@@ Line 348: / Line 350: @@
 During the meeting, the ODP team hosted a session to engage stakeholders and receive feedback on specific work areas in progress.<ref name="74odp">[https://74.schedule.icann.org/meetings/Q5k7NyhhFhLwmbkgY ICANN 74 Archive - Plenary Session: New gTLD Subsequent Procedures - Working Together], May 13, 2022</ref>
+==ODA==
+ICANN spent $6.8 million on the ODP to generate and deliver the Operational Design Assessment in mid-December 2022. This amount fell under the low-end of the $7 million to $9 million the ICANN board approved for its budget. Fifteen full-time equivalents, mostly [[:Category:ICANN staff|ICANN Staff]], spent over 27,000 hours in making the ODA report.<ref>[https://domainincite.com/28594-new-gtlds-report-came-in-under-budget nTLD ODA Report Under Budget, Domain Incite]</ref>
 ===Key Take-Aways from the ODA ===
 ICANN Org
@@ Line 359: / Line 363: @@
 *proposed a Business Process Design (Appendix 6) outlining the key components of how the next round could be implemented, from foundational concepts to post-contracting, with the aim of supporting the Implementation Review Team (IRT) and found that the overall implementation cost for the next round of the New TLD Program would be significantly higher than the 2012 round.<ref>[https://www.icann.org/en/system/files/files/subpro-oda-12dec22-en.pdf SubPro ODA, Executive Summary] </ref>
+====Application Period Options====
 *presented two options for the application process: a single application submission period per round (the assumed route) or cyclical application submission periods (the alternative; Appendix 19).
 ::'''Option 1''' may take at least five years from the Board directing ICANN org to begin implementation to the opening of the application submission window, cost approximately USD $457 million, involve 18 system services and 125 full-time equivalents, and incur the risk of material financial losses if demand is low.<ref>[https://www.icann.org/en/system/files/files/subpro-oda-12dec22-en.pdf SubPro ODA, Executive Summary], Pgs 12-14</ref>
-::'''Option 2''' would split the immediate next round into four annual application submission periods, create predictability for the New TLD Program,  moderate the influx of applications in the first cycle, rely on a processing capacity limit of 450 applications per cycle, offer flexibility to potential applicants, and may be beneficial to new entrants who may need to invest more time and resources. However, this option contains the risks of limited space leading to competition and giving an advantage to applicants already engaged in the current DNS ecosystem.
+::'''Option 2''' would take 18 months to begin implementing, split the immediate next round into four annual application submission periods, create predictability for the New TLD Program,  moderate the influx of applications in the first cycle, rely on a processing capacity limit of 450 applications per cycle, offer flexibility to potential applicants, and may be beneficial to new entrants who may need to invest more time and resources. However, this option contains the risks of
+::#limited space leading to competition,
+::#giving an advantage to applicants already engaged in the current DNS ecosystem, and
+::#being less efficient than the processing of portfolio applications available with option 1.<ref>[https://www.icann.org/en/system/files/files/subpro-oda-12dec22-en.pdf SubPro ODA, Executive Summary], Pg 17</ref>
+===Reactions to the ODA===
+On January 20, 2023, the GNSO Council provided feedback to the ICANN Board about the SubPro ODA. The Council encouraged the ICANN Board to adopt the New gTLD Subsequent Procedures Final Report ASAP. In particular, the Small Team:
+*explained that it couldn’t differentiate Options 1 and 2 and their impacts on the overall new gTLD program;
+*believed that the bulk of the applications would come in the first cycle, regardless of what ICANN org internally designs;
+*suggested that the next round should not be more complex or time and resource intensive than is necessary;
+*requested that the org use existing know-how and lessons learned (and the general approach of outsourcing or buying in and adapting systems);
+*distinguished between what is necessary to support the program and what is a wish list; and
+*felt that the design could be simplified to minimize the risks identified by using customizable existing software and platforms instead of building in-house and from scratch.<ref>[https://www.icann.org/en/system/files/correspondence/ducos-to-sinha-20jan23-en.pdf Ducos to Sinha Jan 20, 2023, Correspondence, ICANN Files]</ref>
+==Implementation Planning Phase==
+At [[ICANN 76]], the [[GNSO Council]] agreed to form a small team of councilors to review the pending recommendations and suggest how to address the underlying concerns. The Council SubPro Small Team completed an initial run-through of the issues chart and proposed paths forward for each pending recommendation to be presented in the Council's dialogue with the ICANN Board on May 22, 2023.<ref>[https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2023-05-25 Final Proposed Agenda for 05/25/2023, GNSO Council Meetings]</ref>
 ==References==