Optical fiber

The next round of gTLDs is around the corner

The next round is around the corner.

ICANN has been working on adding generic extensions to the internet for many years, and the next round will, in fact, be the 5th round of gTLD expansion.


In the 1980s, seven gTLDs were created: .com, .edu, .gov, .int, .mil, .net, and .org. Under three of these (.com, .net, and .org) internet users were able to freely register domain names not tied to a country code.

Twenty years later, the 2000 round introduced the concept of applying to obtain the control of internet extensions. It was a so-called “proof of concept round” during which the ICANN Board selected the following seven applications biz, .info, .name, .pro, .aero, .coop, and .museum to be launched.

In 2003, another round of TLD applications took place and the following extensions were launched .asia, .cat, .jobs, .mobi, .tel and .travel.

After the successful results of the 2000 and 2003 expansions, ICANN initiated in 2005 a Policy Development Process to prepare and regulate the introduction of additional new gTLDs.

In 2008, ICANN released the first draft of the new gTLD Applicant Guidebook for public comment. The document specified the operational, financial, and legal commitments for applying and operating a new gTLD. For three years, the internet community and the public provided their input on this document, which led to its current version. Despite the intellectual property and business constituencies’ doubts regarding the protectiveness of the program towards their members’ rights, the ICANN Board launched the New gTLD Program in June 2011.

2012 Round results

It is important to note that the Applicant Guidebook was intended to govern “the first round of what is to be an ongoing process for the introduction of new gTLDs” and that “ICANN’s goal [was] to launch subsequent gTLD application rounds as quickly as possible. “While this program was admittedly far from perfect, its results made it somewhat successful, despite the complexity of its structure and the multi-stakeholder model on which ICANN is functioning. Indeed, the 338 pages of the Applicant Guidebook and its underlying policies – most of them pre-existing – could have resulted in a massive crash, but clearly did not. Out of the 1930 applications received, 1232 were successful and were added to the internet root servers. Aside from the fringe cases of Amazon, which is currently battling the governments of Peru, Colombia, Ecuador and Bolivia over the delegation of .amazon and the internecine war between Merck & Co and Merck Group over .merck, every brand owner successfully obtained the extensions they applied for. Furthermore, every new extension was subject to specific rights protection mechanisms including especially a “sunrise period” which allowed Intellectual Property rights owners to register their marks before the general public. Also, a notification system was implemented, informing them immediately when a third party registered a domain name corresponding to their trademarks.

Nonetheless, the fact that the program was launched successfully did not mean that a thorough review could be avoided. To this end, ICANN initiated two policy development initiatives:

  • one to Review New gTLD Subsequent Procedures; and
  • the other to Review of All Rights Protection Mechanisms in All gTLDs

New gTLD Subsequent Procedures PDP

This working group started its work in January 2016. After completing deliberations on a set of six overarching and foundational subjects, the working group established the following five separate work tracks to address the remaining items:

  1. Issues related to the overall process, support, and outreach;
  2. Legal and regulatory issues;
  3. Matters related to string contention, objections, and disputes;
  4. Internationalized Domain Names and technical and operational problems;
  5. Geographic names at the top-level issues.

The working group sought community input through two comment periods. In July 2018, the working group published its Initial Report and later in October 2018 it released Supplemental Initial Report, focused on the more complex and controversial protection of Geographic Names at the Top-Level.

As of the writing of this post, the working group has completed its initial review of public comments for both the Initial Report and its Supplemental Initial Report. Every sub-group is currently looking into how the public input might affect the final recommendations. The current open issues concern:

  • geographic features and “culturally significant terms related to geography (such as the name of a river, mountain, lake, etc.) which are not considered protected terms in the applicant guidebook;
  • the creation of a repository containing every protected term in every language;
  • the protection of translated forms of protected geographical names in every language;
  • the contention resolution process for geographic names to give priority to the application which will use the extension for its geographic meaning, and
  • the prioritization of concurrent applications by cities sharing the same name.

To resolve those issues, the Work Track 5 sub-group will have to amend its report so that greater protection be granted to geographic names without hindering legitimate applicants’ interests. The subgroup is aiming to send a full review to the rest of the working group by August-September 2019. The working group will then incorporate it into its final report, which is due for the end of 2019. The recommendations contained in the final report will then be used to amend the applicant guidebook.

Review of All Rights Protection Mechanisms in All gTLDs

This working group kicked off in February 2016 to review all Rights Protection Mechanisms  (“RPMs”) in two phases. In phase one, which is currently ongoing, the working group is reviewing all the RPMs specifically developed for the 2012 round of applications.


  • International nongovernmental organizations (INGO) Claims Notification
    INGOs are provided 90-days claims notifications service under every new gTLD.
  • Public Interest Commitment Dispute Resolution Procedure (PICDRP)
    The PICDRP addresses complaints that a registry may not be compliant with the Public Interest Commitment(s) in its Registry Agreement.
  • Registration Restrictions Dispute Resolution Procedure (RRDRP)
    The RRDRP is intended to address circumstances in which a community-based registry deviates from the registration restrictions outlined in its Registry Agreement.
  • Trademark Clearinghouse (TMCH)
    The TMCH is a repository for trademark data supporting rights protection services offered by new gTLD registries. The purpose of the TMCH is to facilitate the sunrise services and trademark claims services.
  • Trademark Clearinghouse (TMCH) Requirements
    The TMCH requirements are the rights protection mechanisms related to the Trademark Clearinghouse specified in the Registry Agreement between ICANN and the registries.
  • Trademark Post-Delegation Dispute Resolution Procedure (PDDRP)
    The PDDRP is intended to cover general trademark post-delegation dispute resolution proceedings and addresses registry’s complicity in trademark infringement under its extension.
  • Uniform Rapid Suspension (URS)
    The URS is a rights protection mechanism that complements the existing Uniform Domain-Name Dispute Resolution Policy (UDRP) by offering a lower-cost and faster solution for rights holders experiencing the most clear-cut cases of infringement.

In November 2016, the working group completed its review of the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP).
By October 2018, the working group completed its review of the Uniform Rapid Suspension (URS) dispute resolution procedure. It also completed a data collection exercise that involved the survey of targeted respondent groups. Its goal was to obtain factual data that can assist with the review of Sunrise and Trademark Claims that are offered through the TMCH.
In December 2018, two sub-groups were formed to analyze all Sunrise and Trademark Claims related data. They completed their data analysis in February 2019 and in June 2019 they completed their development of proposed answers and preliminary recommendations.
The working group is now preparing its final report draft which is expected to be published by April 2020. Once this phase is completed and the final report of the working group is adopted by the ICANN Board, its recommendations will be used to amend the relevant parts of the applicant guidebook.

In phase two, the working group will review the UDRP. Although during this phase only one RPM will be discussed, it should prove more complex and lengthier than the previous stage. Indeed, the UDRP was established more than 20 years ago, and 100 000+ arbitration decisions have been taken following its rules.

Thankfully, this phase of the working group does not need to be completed for the next round of extensions to take place. This review will be conducted in parallel, and most probably will continue after the next application round has taken place.

New push

Numerous successful uses of brand extensions such as .sncf, .leclerc, .mma, .total and .bnpparibas in France or .bmw, .audi and .mini in Germany and .mango .lacaixa, .zara and .telefonica in Spain have resulted in a growing interest of brands in claiming their zone of the internet.

Most probably due to this interest and the fact that the review of the application program will soon take longer than the creation of the program itself, ICANN recently published a paper entitled “ICANN Org’s Readiness to Support Future Rounds of New gTLDs.” This paper contains a list of 8 assumptions related to the operational aspect of the next round of new gTLDs. Those can be summarized as follows:

  1. The reports from the Subsequent Procedures and the RPM review Working groups will be used to modify the AGB and other policies where applicable, before the next round.
  2. ICANN believes the next round will have around 2000 applications.
  3. The yearly application window will be of one to three months, and the delegation rate will remain at 1000 extensions per year.
  4. ICANN will establish a dedicated and permanent operational infrastructure that will be in charge of the next and subsequent rounds.
  5. ICANN will invest in systems and tools dedicated to the next rounds. And more importantly, it will thoroughly test the security and stability of those systems.
  6. ICANN will train its staff to follow the operational process defined by/and in accordance with the applicant guidebook.
  7. ICANN will hire new staff and outsource parts of the process which require specific expertise.
  8. The program will operate on a cost-recovery basis. It will be funded by the collected application fees.

Although this document is aimed to obtain feedback from the ICANN community, it also constitutes a clear signal that the next round of applications will take place shortly.
The realistic date for the next round is now the first quarter of 2021. While it may seem far in the future, a whole year might be necessary for applicants to coordinate between their different departments to ensure that the application and its launch will be successful.

Many brand owners, most probably ill-advised, rushed into the 2012 round to realize a few years later that they should not have applied for the delegation of their own extension. As of this date, 50+ brands have decided to terminate their agreement with ICANN and sunset their extensions.
This shows that it is of the uttermost importance to proceed to a full assessment of the opportunity to apply for a branded extension. Not every brand should have its own extension; most of the time appropriate management of a domain name portfolio is sufficient.

If you are interested in proceeding to such assessment, don’t hesitate to contact our specialists at newgtlds@ebrandservices.com. EBRAND has successfully counseled and accompanied a dozen brand owners who are now managing their own internet extension.

Trending Stories

Get in touch

Our experts are ready to provide you with a customized solution. Fill out the contact sheet to connect with us.


Client login

Welcome to the client login portal, where EBRAND users access their solution platforms. Select your solution below:

Not an EBRAND client yet? Sign up
Discover more on our Solutions pages