New gTLD Program: Next Round: Difference between revisions
Christiane (talk | contribs) information update |
Christiane (talk | contribs) information update; general fixes |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
The first New gTLD Program application round opened in January 2012 and resulted in over a thousand new gTLD delegations, including geographic, community, brand, and generic strings. After the close of the 2012 round, ICANN and the community launched a broad series of reviews and studies on topics such as rights protection mechanisms, DNS Abuse, consumer trust, competition, and name collisions. | The first New gTLD Program application round opened in January 2012 and resulted in over a thousand new gTLD delegations, including geographic, community, brand, and generic strings. After the close of the 2012 round, ICANN and the community launched a broad series of reviews and studies on topics such as rights protection mechanisms, DNS Abuse, consumer trust, competition, and name collisions. | ||
In December 2015, the GNSO Council initiated the Policy Development Process on New gTLD Subsequent Procedures (SubPro) to determine whether, and under what conditions, additional application rounds should proceed.<ref name="history-new-gtld">[https://www.icann.org/resources/pages/newgtlds-history-2023-04-05-en ICANN: History of the New gTLD Program] Retrieved December 1, 2025</ref> The GNSO New gTLD Subsequent Procedures (SubPro) Working Group conducted several years of deliberations, including work tracks on overarching issues, application types, geographic names, and technical and operational criteria. Its "Final Report on the new gTLD Subsequent Procedures Policy Development Process" was delivered in February 2021 and organized into a set of affirmations, recommendations, and implementation guidance | In December 2015, the GNSO Council initiated the Policy Development Process on New gTLD Subsequent Procedures (SubPro) to determine whether, and under what conditions, additional application rounds should proceed.<ref name="history-new-gtld">[https://www.icann.org/resources/pages/newgtlds-history-2023-04-05-en ICANN: History of the New gTLD Program] Retrieved December 1, 2025</ref> The GNSO New gTLD Subsequent Procedures (SubPro) Working Group conducted several years of deliberations, including work tracks on overarching issues, application types, geographic names, and technical and operational criteria. Its "Final Report on the new gTLD Subsequent Procedures Policy Development Process" was delivered in February 2021 and organized into a set of affirmations, recommendations, and implementation guidance.<ref name="subpro-final">[https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf ICANN GNSO: Final Report on the new gTLD Subsequent Procedures Policy Development Process] Retrieved December 1, 2025</ref> | ||
On February 18, 2021, the GNSO Council approved all SubPro outputs that achieved "Full Consensus" or "Consensus" and transmitted them to the ICANN Board.<ref name="history-new-gtld" /> | On February 18, 2021, the GNSO Council approved all SubPro outputs that achieved "Full Consensus" or "Consensus" and transmitted them to the ICANN Board.<ref name="history-new-gtld" /> Following receipt of the SubPro Final Report, ICANN org conducted an Operational Design Phase (ODP) to assess the practical, financial, and risk implications of implementing the new policies; the resulting Operational Design Assessment (ODA) was delivered to the Board in December 2022.<ref name="history-new-gtld" /> | ||
On March 16, 2023, the Board adopted the majority of SubPro recommendations and marked a smaller set as pending while it consulted further with the GNSO and the GAC.<ref name="gac-next-round">[https://gac.icann.org/activity/new-gtld-program-next-round ICANN GAC: New gTLD Program Next Round] Retrieved December 1, 2025</ref> The Board also requested an implementation plan from ICANN org describing how a subsequent round could be operationalized, which was delivered on July 31, 2023.<ref name="impl-plan-2023">[https://newgtlds.icann.org/sites/default/files/new-gtld-next-round-implementation-plan-31jul23-en.pdf ICANN: The New gTLD Program Next Round Implementation Plan] Retrieved December 1, 2025</ref> | |||
== Implementation Governance == | |||
=== SubPro Implementation Review Team === | |||
To help ensure fidelity to the policy recommendations, the GNSO Council chartered the [[Subsequent Procedures IRT|SubPro Implementation Review Team (IRT)]]. The IRT consists of community volunteers who review draft implementation proposals, comment on operational details that interpret policy, and receive regular updates on communications, outreach, and systems development.<ref name="impl-plan-2023" /><ref name="next-round-reports" /> | |||
ICANN org provides monthly reports to the IRT on outreach and engagement efforts for the Next Round, and holds regular IRT calls where program timelines, draft [[2026 Round Applicant Guidebook|Applicant Guidebook]] text, and related implementation topics are discussed.<ref name="next-round-reports">[https://newgtldprogram.icann.org/en/reports ICANN: Next Round gTLD Reports] Retrieved December 2, 2025</ref> | |||
=== ICANN Oversight === | |||
The ICANN Board oversees the overall direction of the Next Round, adopting relevant policy recommendations, approving key program documents such as the Applicant Guidebook (AGB), and authorizing the opening of the application window.<ref name="board-agb-2025">[https://www.icann.org/en/announcements/details/icann-board-adopts-next-round-applicant-guidebook-clears-path-to-2026-launch-03-11-2025-en ICANN Announcements: ICANN Board Adopts Next Round Applicant Guidebook; Clears Path to 2026 Launch] Retrieved December 2, 2025</ref> ICANN org is responsible for detailed program design, systems implementation, contracting, and ongoing operations, reporting back to the Board and community through public sessions at ICANN meetings and written updates.<ref name="impl-plan-2023" /> <ref name="q1-2025"></ref> | |||
== Applicant Guidebook and ICANN Board Adoption == | == Applicant Guidebook and ICANN Board Adoption == | ||
| Line 45: | Line 59: | ||
The AGB reflects SubPro's balancing of applicant freedom of expression with safeguards related to legal rights, objection mechanisms, and program integrity. SubPro reaffirmed that the evaluation process should not infringe applicants’ freedom of expression under internationally recognized principles of law, while also requiring respect for enforceable legal rights (including intellectual property rights).<ref name="subpro-final" /><ref name="agb" /> | The AGB reflects SubPro's balancing of applicant freedom of expression with safeguards related to legal rights, objection mechanisms, and program integrity. SubPro reaffirmed that the evaluation process should not infringe applicants’ freedom of expression under internationally recognized principles of law, while also requiring respect for enforceable legal rights (including intellectual property rights).<ref name="subpro-final" /><ref name="agb" /> | ||
=== IDNs and Variants === | === IDNs and Variants === | ||
| Line 68: | Line 68: | ||
If an applicant wishes to apply for a new gTLD in a script that is not yet supported by the RZ-LGR but has common and widespread use, the application will be put on hold until the relevant script community forms a Generation Panel and develops an LGR proposal. That proposal is then reviewed by the Integration Panel and, if approved, integrated into the RZ-LGR under the "Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels".<ref name="next-round-faqs" /><ref name="lgr-procedure">[https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en ICANN: Proposals for Root Zone Label Generation Ruleset], ICANN, retrieved December 3, 2025.</ref> | If an applicant wishes to apply for a new gTLD in a script that is not yet supported by the RZ-LGR but has common and widespread use, the application will be put on hold until the relevant script community forms a Generation Panel and develops an LGR proposal. That proposal is then reviewed by the Integration Panel and, if approved, integrated into the RZ-LGR under the "Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels".<ref name="next-round-faqs" /><ref name="lgr-procedure">[https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en ICANN: Proposals for Root Zone Label Generation Ruleset], ICANN, retrieved December 3, 2025.</ref> | ||
=== Closed Generics | === Closed Generics === | ||
Closed generics were treated as a pending topic during SubPro and the Operational Design Phase, and were the subject of a 2022–2023 Facilitated Dialogue among the GAC, GNSO, and ALAC. After considering the dialogue outcomes and GAC/ALAC advice, the ICANN Board decided in January 2024 that closed generic gTLD applications will not be permitted in the 2026 round unless and until an approved methodology and criteria are developed to assess their compatibility with the public interest.<ref name="gac-next-round" /> | Closed generics are defined as "a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others". They were treated as a pending topic during SubPro and the Operational Design Phase, and were the subject of a 2022–2023 Facilitated Dialogue among the GAC, GNSO, and ALAC. After considering the dialogue outcomes and GAC/ALAC advice, the ICANN Board decided in January 2024 that closed generic gTLD applications will not be permitted in the 2026 round unless and until an approved methodology and criteria are developed to assess their compatibility with the public interest.<ref name="gac-next-round" /> The AGB maintains this position.<ref name="agb" /> | ||
=== IDN Policy Dependencies === | |||
The [[EPDP on Internationalized Domain Names|Expedited Policy Development Process on Internationalized Domain Names (IDNs)]] provides the detailed rules for IDN gTLDs and top-level variants in the Next Round. Phase 1 recommendations, which cover top-level IDN definitions and variant sets, were fully adopted by the ICANN Board in 2024–2025 and are being implemented through an IDN Implementation Review Team as a sub-track of the SubPro IRT. Phase 2 recommendations, focused on second-level variant management, have been approved by the GNSO Council and are currently under ICANN Board consideration following a 2024–2025 public comment proceeding.<ref name="history-new-gtld" /> | The [[EPDP on Internationalized Domain Names|Expedited Policy Development Process on Internationalized Domain Names (IDNs)]] provides the detailed rules for IDN gTLDs and top-level variants in the Next Round. Phase 1 recommendations, which cover top-level IDN definitions and variant sets, were fully adopted by the ICANN Board in 2024–2025 and are being implemented through an IDN Implementation Review Team as a sub-track of the SubPro IRT. Phase 2 recommendations, focused on second-level variant management, have been approved by the GNSO Council and are currently under ICANN Board consideration following a 2024–2025 public comment proceeding.<ref name="history-new-gtld" /> | ||
== | == Applicant Support Program == | ||
SubPro recommends an expanded and better resourced Applicant Support Program targeted at eligible applicants with limited financial means, particularly from underserved regions and communities. The policy framework envisages reduced fees, non-financial support such as pro bono services, and carefully structured mechanisms (including possible bid credits in contention resolution) designed to improve the chances that supported applicants can successfully obtain and operate a gTLD.<ref name="subpro-final" /> | |||
== Registry Service Provider Evaluation Program == | |||
The Registry Service Provider (RSP) Evaluation Program pre-evaluates entities that provide back-end registry services to ensure that Registry Service Providers meet the technical requirements to run a TLD back-end. This enables RSPs to be evaluated just once, no matter how many TLDs they may support. The AGB and program documentation describe this as a mechanism to reduce duplicative technical review by separating assessment of registry technical operations from the gTLD string application.<ref name="agb" /><ref name="rsp-page">[https://newgtldprogram.icann.org/en/application-rounds/round2/rsp ''Registry Service Provider Evaluation Program''], ICANN New gTLD Program website, retrieved January 30, 2026.</ref> <ref name="introvideoone">[https://icann.zoom.us/rec/play/U5KqJzPA6hn7Gw2YNcoDpsoPFMi3TBMZa_lYy-g9XY6roINkZzyBZoDIvll77gd1Z1aya2tWtqAzM0-R.W1RJmCOidXPWcbBR?eagerLoadZvaPages=sidemenu.billing.plan_management&accessLevel=meeting&canPlayFromShare=true&from=share_recording_detail&continueMode=true&componentName=rec-play&originRequestUrl=https%3A%2F%2Ficann.zoom.us%2Frec%2Fshare%2F-6gDqW0GyDlxscoQuyfPTY7Czs8V9iSIfmipWNSSG3TVVFHIwOFu_pVoGRp7fhQj.MxTJyhSDYk2zcqs3 ''Introduction to the 2026 Round''] ICANN, retrived February 2, 2026</ref> | |||
= | The program had a pre-evaluation period from November 19, 2024 to May 20, 2025. An initial list of organizations participating in the Registry Service Provider (RSP) Evaluation Program was published by ICANN on January 30, 2026. The list includes organizations that have cleared both technical screening and technical testing, as well as those that have cleared technical screening but are still in the process of clearing technical testing. Remaining RSP, IDN Services, and additional Registry Services applications are expected to be published in early March 2026.<ref name="rsp">[https://www.icann.org/en/announcements/details/icann-publishes-initial-list-of-evaluated-rsps-for-2026-round-30-01-2026-en '''ICANN Publishes Initial List of Evaluated RSPs for 2026 Round'''] ICANN.org, retrived February 2, 2026</ref> | ||
RSPs that did not apply in the pre-evaluation window will be able to apply in parallel to the opening of the gTLD application window expected to open on April 30, 2026.<ref name="introvideoone"></ref> | |||
The List of Evaluated RSPs will be updated on an ongoing basis as ICANN continues to test and qualify providers.<ref name="rsp"></ref> | |||
The | |||
== Outreach and Communications == | == Outreach and Communications == | ||
| Line 131: | Line 105: | ||
The Applicant Support Program (ASP) provides financial and non-financial assistance to eligible applicants, particularly those from underserved regions or with limited resources.<ref name="asp-page">[https://newgtldprogram.icann.org/en/application-rounds/round2/asp ICANN New gTLD Program Next Round: Applicant Support Program] Retrieved December 2, 2025.</ref> Qualifying supported applicants may receive reduced evaluation fees, access to pro bono professional services, and preferential treatment in any ICANN Auction of Last Resort within defined parameters.<ref name="status-2024" /> | The Applicant Support Program (ASP) provides financial and non-financial assistance to eligible applicants, particularly those from underserved regions or with limited resources.<ref name="asp-page">[https://newgtldprogram.icann.org/en/application-rounds/round2/asp ICANN New gTLD Program Next Round: Applicant Support Program] Retrieved December 2, 2025.</ref> Qualifying supported applicants may receive reduced evaluation fees, access to pro bono professional services, and preferential treatment in any ICANN Auction of Last Resort within defined parameters.<ref name="status-2024" /> | ||
The ASP opened | The ASP application submission period opened on November 19, 2024 and closed for complete applications on December 19, 2025 (following a deadline extension for applicants who had entered organizational information by 19 November 2025).<ref name="asp" /><ref name="asp-extension">[https://www.icann.org/en/announcements/details/icann-extends-deadline-for-applicant-support-program-06-10-2025-en ''ICANN Extends Deadline for Applicant Support Program''], ICANN, published 6 October 2025, retrieved 30 January 2026 | ||
=== IDNs and Applicant Support === | === IDNs and Applicant Support === | ||
| Line 146: | Line 120: | ||
The program includes two evaluation periods: an initial pre-application period from November 19, 2024 to May 20, 2025, and a second period aligned with the 2026 application window.<ref name="rsp-program" /><ref name="update-2025" /> RSPs that successfully complete evaluation are listed on a dedicated page for use by prospective applicants.<ref name="rsp-program" /> Through the program, RSPs may only need to be evaluated once for the 2026 Round regardless of the number of gTLDs they support.<ref name="agb" /> | The program includes two evaluation periods: an initial pre-application period from November 19, 2024 to May 20, 2025, and a second period aligned with the 2026 application window.<ref name="rsp-program" /><ref name="update-2025" /> RSPs that successfully complete evaluation are listed on a dedicated page for use by prospective applicants.<ref name="rsp-program" /> Through the program, RSPs may only need to be evaluated once for the 2026 Round regardless of the number of gTLDs they support.<ref name="agb" /> | ||
== Systems and Tools == | |||
ICANN is deploying a new "TLD Application Management System (TAMS)" to replace the 2012 TAS platform. TAMS is designed to support application submission, document management, evaluation workflows, communications between ICANN and applicants, and publication of application data.<ref name="impl-plan-2023" /> | |||
Additional tools include portals for the Applicant Support Program, the RSP Evaluation Program, and public information sites that present timelines, FAQs, and outreach materials for potential applicants.<ref name="next-round-landing">[https://newgtldprogram.icann.org/en/application-rounds/round2 ICANN: New gTLD Program: Next Round] Retrieved December 2, 2025.</ref> <ref name="next-round-faqs" /> | |||
== Applicant Journey == | == Applicant Journey == | ||
=== Pre- | === Pre-Submission === | ||
In the pre- | In the pre-submission phase, prospective applicants are expected to review the Applicant Guidebook, evaluate business cases for operating a gTLD, and identify potential strings and registry service providers. ICANN supports this phase with information materials, webinars, regional engagement activities, and an outreach “toolkit” aimed at organizations that can promote awareness of the Next Round in their communities.<ref name="next-round-landing" /><ref name="next-round-reports" /> | ||
Applicants requiring financial or capacity support are encouraged to apply to the Applicant Support Program sufficiently in advance of the main application window.<ref name="asp-page" /><ref name="q1-2025" /> | Applicants requiring financial or capacity support are encouraged to apply to the Applicant Support Program sufficiently in advance of the main application window.<ref name="asp-page" /><ref name="q1-2025" /> | ||
| Line 157: | Line 137: | ||
=== Application Submission === | === Application Submission === | ||
During the 2026 application window, applicants submit their gTLD applications through TAMS. Each application must provide detailed information about the applicant entity, the proposed string, registry services, technical and operational plans, financial capabilities, and policies for abuse mitigation and rights protection.<ref name="next-round-faqs" /><ref name="impl-plan-2023" /> | During the 2026 application window, applicants submit their gTLD applications through TAMS. Each application must provide detailed information about the applicant entity, the proposed string, registry services, technical and operational plans, financial capabilities, and policies for abuse mitigation and rights protection.<ref name="next-round-faqs" /><ref name="impl-plan-2023" /> Applicants will be able to enter their string in TAMS to check whether there is a match. If a string fails one of the validations or a match is found, the applicant will receive an error or warning message in TAMS explaining the detected issues and will not be allowed to proceed and submit its application or will have to provide additional documentation.<ref name="agb" /> | ||
=== Evaluation === | === Evaluation === | ||