ICANN bans closed generics for the foreseeable
There will be no applications for closed generic gTLDs in the 2026 application round, ICANN has confirmed.
While the Org has yet to publish the results of last weekend’s board meeting, chair Tripti Sinha has written to community leaders to let them know that companies won’t be able to apply for exclusive-use, non-trademark strings for the foreseeable future.
The ban follows years of talks that failed to find a consensus on whether closed generics should be permitted, and subsequent advice from the Governmental Advisory Committee, backed up by the At-Large Advisory Committee, that they should not.
Apparently quoting board output from its January 21 meeting, Sinha wrote (pdf):
the Board has considered the GAC Advice and has determined that closed generic gTLD applications will not be permitted until such time as there is an approved methodology and criteria to evaluate whether or not a proposed closed domain is in the public interest.
Closed generics were permitted — or at least not explicitly outlawed — in the 2012 application round, but were retroactively banned by ICANN following GAC advice in 2013, stymying the plans of dozens of applicants.
Ironically, it was the clumsy wording of the 2013 advice that saw the debate re-open a few years ago, with the initiation of a closed-doors, Chatham House Rules “facilitated dialogue” between the pro- and anti- camps, which also failed to reach a consensus.
By drawing a line under the issue now, ICANN has finally officially removed closed generics as a potential delaying factor on the next gTLD application round, which is already 13 years late.
Closed generics ban likely to remain after another policy group failure
Closed generic gTLDs are likely off the table for ICANN’s next application round, after a secretive policy development working group failed to reach a consensus on how they could be permitted.
The chairs of the ALAC-GAC-GNSO Facilitated Dialogue on Closed Generic gTLDs have put their names to a draft letter that essentially throws in the towel and recommends ICANN sticks to the status quo in which closed generics are not permitted.
The chairs of the three committees write that they “believe that it is not necessary to resolve the question of closed generic gTLDs as a dependency for the next round of new gTLDs, and we plan to inform the ICANN Board accordingly.”
In other words, whatever latency related to needing a closed generics policy that was built in to ICANN’s recent April 2026 target for opening the next application round could be eliminated from the timeline.
The three chairs added (emphasis in original PDF):
We agree with the ICANN Board (in its original invitation to the GAC and the GNSO to engage in a facilitated dialogue) that this topic is one for community policy work, rather than a decision for the Board. As such and based on our collective belief that there is neither the need nor the community bandwidth to conduct additional work at this stage, we also plan to ask that, for the next round, the Board maintain the position that, unless and until there is a community-developed consensus policy in place, any applications seeking to impose exclusive registry access for “generic strings” to a single person or entity and/or that person’s or entity’s Affiliates (as defined in Section 2.9(c) of the Registry Agreement) should not proceed. Finally, we also plan to inform the Board that any future community policy work on this topic should be based on the good work that has been done to date in this facilitated dialogue.
But that position — still a draft — is already facing some push-back from community members who disagree about what the current status quo actually is.
The 2012 application round opened up with the assumption that closed generics were A-okay, and it received hundreds of such applications.
But the governments of the GAC, no doubt stirred by competition concerns, balked when they saw big companies had applied for gTLD strings that could enable them to dominate their markets.
The GAC demanded that closed generics must service the public interest if they were to be permitted, so ICANN Org — in what would turn out to be an Original Sin injected into the destiny of future rounds — retroactively changed the rules, essentially banning closed generics but allowing applicants to withdraw for a refund or open up their proposed registration policies.
The third option was to defer their applications to a future application round, by which point it was assumed the community would have established a closed generics policy. No applicant took that option.
But making that policy was the job of a committee called SubPro, but when turned its attention to the issue, entrenched positions among volunteers took hold and no consensus could be found. It couldn’t even agree what the status quo was. The group wound up punting the issue to the ICANN board.
The discussion moved on last year when ICANN decided to launch the “Facilitated Dialogue”, forcing the GAC and the GNSO to the negotiating table in last-ditch attempt to put the issue to bed for good.
Ironically, it was the 2013 GAC advice — made at time when the governments drafted their advice in secret and were deliberately ambiguous in their output — that killed off closed generics for a decade that ICANN used to reopen the issue. The GAC hadn’t wanted a blanket ban, after all, it just wanted to mandate a “public interest” benefit.
The assumption was that the Facilitated Dialogue would come up with something in-between a ban and a free-for-all, but what it actually seems to have come up with is a return to the status quo and disagreement about what the status quo even is.
It really is one of those situations where ICANN, in its broadest definition, can’t see to find its ass with two hands and a flashlight (and — if you’ll indulge me — a map, GPS coordinates, and a Sherpa).
Next round of gTLDs could come much sooner than expected
ICANN’s next new gTLDs application round may be closer than we thought, after a policy working group dramatically reduced the timetable for completing its work.
The Internationalized Domain Names Expedited Policy Development Process team has managed to shave a whopping 13 months off its schedule, potentially leading to a similar period being shaved off the runway to the next application window.
The IDNs EPDP had expected to deliver its final deliverables — policy recommendations on how IDNs are handled in gTLD applications — in November 2025, meaning the earliest they could be adopted by the ICANN board would be March 2026.
Because the IDNs policy is seen as a critical gating factor to the next round commencing, the date ICANN penciled in for the next application window was May 2026.
But now the IDNs EPDP group has revised its deadline down to October 2024, member Donna Austin told the GNSO Council last Thursday. This could mean the board could approve its work in early 2025.
The new target means that IDNs are no longer the biggest delaying factor on the critical path to the next window — that honor now falls on the “closed generics” problem, which a “small team” of the GNSO and Governmental Advisory Committee have been working on in private all year.
The latest thinking on closed generics is that another EPDP would be formed with an estimated run-time of 96 weeks (22 months) — a mid-2025 end date, in other words.
But there are even question marks over that optimal timeline now, following a less than supportive informal public comment period that closed last week. The closed generics small team has apparently taken a week off to ask itself some fundamental questions.
One possibility that has been suggested to speed things up is to take closed generics out of the critical path by retaining the current de facto ban for the next round.
If that were to happen, we could be looking at an application window in 2025.
But nobody ever won money betting on ICANN hitting deadlines, so take this speculation with a pinch of salt big enough to give an elephant hypertension.
Closed generics and IDNs debates are big drag on new gTLDs
As ICANN 77 officially kicks off in Washington DC today, the issues of closed generics and IDNs have already emerged as big drag factors on the launch of the next new gTLD application round.
During a day-long “day zero” session yesterday, the community heard that the absolute fastest the GNSO will be able to make policy on closed generics is 96 weeks — over 22 months — using its “expedited” Policy Development Process.
Meanwhile, making policy on internationalized domain names — mainly, how to handle string similarity conflicts in non-Latin scripts — is not expected to be done until March 2026 at the earliest. And that’s through an “expedited” PDP that has already been running for over two years.
The predicted closed generics timetable (on page 16 of this PDF presentation) is actually relatively aggressive compared to the two previous EPDPs (on post-GDPR Whois policy) that the GNSO has previously completed.
It only calls for 36 weeks — about eight months — for the actual working group deliberations, for example, compared to the 48 weeks the equally controversial Whois EPDP took a few years ago.
But the expected duration prompted some criticism yesterday from those wondering why, for example, a “call for volunteers” needs to take as long as three months to carry out.
The timetable was written up prior to the publication over the weekend of a draft framework for closed generics (pdf), which lays out a few dozen principles that should be taken into account in subsequent EPDP work.
With what looks like a certain amount of wheel-reinvention, the document describes a points-based system for determining whether an applicant is worthy of a closed generic. It seems to be based quite a lot on the process used to assess “Community” applications in the 2012 round.
The framework was created in private over the last six months by a cross-community group of 14 people from the GNSO and Governmental Advisory Committee. Chatham House rules applied, so we don’t know exactly whose opinions made it into the final draft. But it exists now, and at first glance it looks like a decent starting point for a closed generics policy.
The major issue is that the work, at its core, is about predicting and preemptively shutting down all the ways devious corporate marketing people might try to blag themselves a closed generic for competitive or defensive purposes, rather than for the public interest, and I’m not sure that’s possible.
Discussion on closed generics will continue this week at ICANN 77, including a session that starts around about the same time I’m hitting publish on this article.
Governments backtracking on closed generics ban
ICANN’s Governmental Advisory Committee appears to be backpedaling on its commitment to permitting so-called “closed generic” gTLDs in the next application round.
The GAC’s output from ICANN 76, which took place in Cancun last week, contains a paragraph that suggests that governments are reverting to their decade-old position that maybe closed generics are not a good idea.
The GAC, GNSO and At-Large have been engaging in a “facilitated dialogue” for the past few months in an attempt to figure out whether closed generics should be allowed and under what terms.
The GAC is now saying “no policy option, including the prohibition of Closed Generics, should be excluded if no satisfactory solution is found”. It had agreed to the dialogue on the condition that prohibition would not be an outcome.
A closed generic is a single-registrant gTLD matching a dictionary word that is not a trademark. Think McDonald’s controlling all the names in .burger or Jack Daniels controlling the whole .whiskey zone.
These types of TLDs had not been banned in the 2012 application round, resulting over 180 gTLD applications, including the likes of L’Oreal applying for .makeup and Symantec’s .antivirus.
But the GAC took a disliking to these applications, issuing advice in 2013 that stated: “For strings representing generic terms, exclusive registry access should serve a public interest goal.”
This caused ICANN to implement what amounted to a retroactive ban on closed generics. Many applicants withdrew their bids; other tried to fudge their way around the issue or simply sat on their gTLDs defensively.
When the GNSO came around to developing policy in 2020 for the next new gTLD round, it failed to come to a consensus on whether closed generics should be allowed. It couldn’t even agree on what the default, status quo position was — the 2012 round by policy permitted them, but in practice did not. The matter was punted to ICANN.
A year ago, ICANN said the GAC and GNSO should get their heads together in a small group, the “facilitated dialogue”, to resolve the matter, but the framing paper outlining the rules of engagement for the talks explicitly ruled out two “edge outcomes” that, ICANN said, were “unlikely to achieve consensus”.
Those outcomes were:
1. allowing closed generics without restrictions or limitations OR
2. prohibiting closed generics under any circumstance.
The GAC explicitly agreed to these terms, with then-chair Manal Ismail (who vacated the seat last week) writing (pdf):
The GAC generally agrees with the proposed parameters for dialogue, noting that discussion should focus on a compromise to allow closed generics only if they serve a public interest goal and that the two “edge outcomes” (i.e. allowing closed generics without restrictions/limitations, and prohibiting closed generics under any circumstance) are unlikely to achieve consensus, and should therefore be considered out of scope for this dialogue.
Now, after days of closed-door facilitated dialogue have so far failed to reach a consensus on stuff like what the “public interest” is, the GAC has evidently had a change of heart.
Its new Cancun communique states:
In view of the initial outputs from the facilitated dialogue group on closed generics, involving representatives from the GAC, GNSO and At-Large, the GAC acknowledges the importance of this work, which needs to address multiple challenges. While the GAC continues to be committed to the facilitated dialogue, no policy option, including the prohibition of Closed Generics, should be excluded if no satisfactory solution is found. In any event, any potential solution would be subject to the GAC’s consensus agreement.
In other words, the GAC is going back on its word and explicitly ruling-in one of the two edge outcomes it less than a year ago had explicitly ruled out.
It’s noteworthy — and was noted by several governments during the drafting of the communique — that the other edge outcome, allowing closed generics without restriction, is not mentioned.
It’s tempting to read this as a negotiating tactic — the GAC publicly indicating that a failure to reach a deal with the GNSO will mean a closed generics ban by default, but since the facilitated dialogue is being held entirely in secret it’s impossible to know for sure.
ICANN to approve next new gTLD round next month (kinda)
ICANN’s board of directors is sending mixed signals about the new gTLD program, but it seems it is ready to start approving the next round when the community meets for its 76th public meeting in Mexico next month.
It seems the board will approve the GNSO’s policy recommendations in a piecemeal fashion. There are some undisclosed sticking points that will have to be approved at a later date.
Chair Tripti Sinha wrote this week that the board “anticipates making incremental decisions leading up to the final decision on opening a new application window for new gTLDs”.
While “many” recommendations will be approved at ICANN 76, the board “will defer a small, but important, subset of the recommendations for future consideration”.
The good news is that the board is erring towards the so-called “Option 2” sketched out in Org’s Operational Design Assessment, which would be much quicker and cheaper than the five-year slog the ODA primarily envisaged.
Sinha wrote:
the Board has asked ICANN Org to provide more detail on the financing of the steps envisioned in the ODA, and to develop a variation of the proposed Option 2 that ensures adequate time and resources to reduce the need for manual processing and takes into account the need to resolve critical policy issues, such as closed generics.
The closed generics issue — where companies can keep all the domains in a generic-term gTLD all to themselves — did not have a community consensus recommendation, and the GNSO Council and Governmental Advisory Committee have been holding bilateral talks to resolve the impasse.
There’s been an informal agreement that some closed generics should be allowed, but only if they serve the global public interest.
A recent two-day GAC-GNSO discussion failed to find agreement on what “generic” and “global public interest” actually mean, so the talks could be slow going. The group intends to file an update before ICANN 76.
ICANN staffer to referee closed generics fight
An ICANN policy staffer seems set to chair discussions between governments and the gTLD community over how to regulate “closed generic” domains in the next round of new gTLD applications.
ICANN has put forward its own conflict resolution specialist Melissa Peters Allgood to facilitate the talks, and the Governmental Advisory Committee and GNSO Council have apparently concurred, according to recent correspondence.
“We are of the view that Ms. Allgood’s experience, qualifications, and neutrality in the matter meets the suggested criteria from the GAC and the GNSO Council,” ICANN chair Maarten Botterman told his GAC and GNSO counterparts.
The talks will attempt to reach a consensus on how closed generics can be permitted, but limited to applications that “serve a public interest goal”.
A closed generic is a dictionary-word gTLD that the applicant hopes to operate as a dot-brand even though it does not own a matching trademark. Think Nike operating .sneakers and excluding Adidas and Reebok from registering names there.
While the GNSO community was unable to come to consensus on whether they should be permitted in subsequent rounds, the nine-year-old “public interest goal” GAC advice is still applicable.
The GAC and GNSO have agreed that the talks will exclude the propositions that closed generics should be unrestricted or banned outright.
Once both parties have formally agreed to Allgood’s appointment, and to the size and makeup of the discussion group, Allgood will prepare more paperwork outlining the problem at hand before talks start to happen, according to Botterman.
The slow crawl to closed generics at ICANN 74
Last Monday saw the 10th anniversary of Reveal Day, the event in London where ICANN officially revealed the 1,930 new gTLD applications submitted earlier in 2012 to a crowd of excited applicants and media.
Dozens of those applications were for closed generics — where the registry operator is the sole registrant, but the string isn’t a trademark — but now, a decade later, the ICANN community still hasn’t decided what to do about that type of gTLD.
At ICANN 74 last week, the Generic Names Supporting Organization and Governmental Advisory Committee inched closer to agreeing the rules of engagement for forthcoming talks on how closed generics should be regulated.
The GNSO’s working group on new gTLDs — known as SubPro — had failed to come to a consensus on whether closed generics should even be allowed, failing even to agree on whether the status quo was the thousand-year-old earlier GNSO policy recommendations that permitted them or the later GAC-influenced ICANN retconning that banned them.
But ever since SubPro delivered its final report, the GAC has been reminding ICANN of its 2013 Beijing communique advice, which stated: “For strings representing generic terms, exclusive registry access should serve a public interest goal.”
At the time, this amounted to an effective ban, but today it’s become an enabler.
ICANN has for the last several months been coaxing the GNSO and the GAC to the negotiating table to help bring the SubPro stalemate into line with the Beijing communique, and the rules of engagement pretty much guarantee that closed generics will be permitted, as least in principle, in the next application round.
GAC chair Manal Ismail told ICANN (pdf) back in April:
discussion should focus on a compromise to allow closed generics only if they serve a public interest goal and that the two “edge outcomes” (i.e. allowing closed generics without restrictions/limitations, and prohibiting closed generics under any circumstance) are unlikely to achieve consensus, and should therefore be considered out of scope for this dialogue.
Remarkably, the GNSO agreed to these terms with little complaint, essentially allowing the GAC to set at least the fundamentals of the policy.
Last week, talks centered on how these bilateral negotiations — or trilateral, as the At-Large Advisory Committee is now also getting a seat at the table — will be proceed.
The rules of engagement were framed by ICANN (pdf) back in March, with the idea that talks would begin before ICANN 74, a deadline that has clearly been missed.
The GNSO convened a small team of members to consider ICANN’s proposals and issued its report (pdf) last week, which now seems to have been agreed upon by the Council.
Both GNSO and GAC are keen that the talks will be facilitated by an independent, non-conflicted, knowledgeable expert, and have conceded that they may have to hire a professional facilitator from outside the community.
That person hasn’t been picked yet, and until he/she has taken their seat no talks are going to happen.
ICANN said a few months ago that it did not expect the closed generics issue to delay the SubPro Operational Design Phase, which is scheduled to wind up in October, but the longer the GAC, GNSO and ICANN dawdle, the more likely that becomes.
All that has to happen is for a group of 14-16 community members to agree on what “public interest” means, and that should be easy, right? Right?
More friction over closed generics
ICANN’s Generic Names Supporting Organization and Governmental Advisory Committee seem to be headed to bilateral talks on the thorny issue of whether “closed generic” gTLDs should be allowed, but not without discontent.
The GNSO’s Non-Commercial Stakeholder Group last week opposed these talks, suggesting that the GAC is trying to acquire more policy-making power and take a second bite at the apple on a issue it has already advised on.
The NCSG wrote (pdf) to the GNSO Council last Thursday to oppose GAC talks, which are being encouraged by ICANN management and board.
Closed generics are dictionary-word gTLDs that do not match the registry’s trademarks but which nevertheless act as though they are a dot-brand, where only the registry may register domains.
There aren’t any right now, because ICANN, acting in 2014 in response to 2013 GAC advice, retroactively banned them from the 2012 application round, even though they were initially permitted.
It’s such a divisive issue that the GNSO working group (known as SubPro) that made the policy recommendations for the next round was, I believe uniquely, unable to come up with a even a fudged recommendation.
The GAC is sticking to its view that closed generics are potentially harmful, and since the GNSO couldn’t make its mind up, ICANN has suggested an informal dialogue between the two parties, to encourage a solution both deem acceptable that could then be thrown back at the GNSO for formal ratification.
The NCSG objected to this idea because it appears, NCSG said, that a new policy process is being created that increases the GAC’s powers to intervene in policy-making when it sees something it doesn’t like.
But the constituency appeared to stand alone during a GNSO Council meeting last Thursday, where the prevailing opinion seemed to be that dialogue is always a good thing and it would be bad optics to refuse to talk.
The Council has formed a small team of four to decide whether to talk to the GAC, which is in favor of the move.
Closed generic gTLDs likely to be allowed, as governments clash with ICANN
So-called “closed generics” seem to be on a path to being permitted in the next new gTLD application round.
The issue reconfirmed itself at ICANN 73 last week as a major point of disagreement between governments and ICANN, and a major barrier to the next round of new gTLDs going ahead.
But a way forward was proposed that seems likely to to permit closed generics in some form in the next round, resolving an argument that has lasted the better part of a decade.
It seems ICANN now expects that closed generics WILL be permitted, but restricted in some yet-to-be-decided way.
A closed generic is a gTLD representing a dictionary word that is not also a brand, operated by a registry that declines to sell domains to anyone other than itself and its close affiliates.
Imagine McDonald’s operating .burgers, but no other fast food chain, cow-masher, or burger afficionado is allowed to register a .burgers domain.
ICANN’s 2012 application round implicitly allowed applications for such gTLDs — at least, it did not disallow them — which prompted outrage from the governments.
The GAC’s Beijing communique (pdf), from April 2013, urged ICANN to retroactively ban these applications unless they “serve a public interest goal”.
The GAC identified 186 applications from the 2012 round that appeared to be for closed generics.
ICANN, taking the GAC’s lead, gave these applicants a choice to either convert their application to an open generic, withdraw for a refund, or maintain their closed generic status and defer their applications to the next round.
Most opted to switch to an open model. Some of those hacked their way around the problem by making registrations prohibitively restrictive or expensive, or simply sitting on their unlaunched gTLDs indefinitely.
The GNSO policy for the next round is inconclusive on whether closed generics should be permitted. The working group contained two or three competing camps, and nobody conceded enough ground for a consensus recommendation to be made.
It’s one of those wedge issues that highlights the limitations of the multistakeholder model.
The working group couldn’t even fall back on the status quo since they couldn’t agree, in light of ICANN’s specific request for a clear policy, what the status quo even was.
Policy-makers are often also those who stand to financially benefit from selling shovels to new gTLD applicants in the next round. The fewer restrictions, the wider the pool of potential clients and the more attractive the sales pitch.
The working group ended up recommending (big pdf) further policy work by disinterested economics and competition law experts, which hasn’t happened, and the GNSO Council asked the ICANN board for guidance, which it refused to provide.
The GAC has continued to press ICANN on the issue, reinforcing its Beijing advice, for the last year or so. It seems to see the disagreement on closed generics as a problem that highlights the ambiguity of its role within the multistakeholder process.
So ICANN, refusing to create policy in a top-down fashion, is forcing the GAC and the GNSO to the table in bilateral talks in an attempt to create community consensus, but the way the Org is framing the issue may prove instructive.
A framework for these discussions (pdf) prepared by ICANN last week suggests that, when it comes to closed generics, an outright-ban policy and an open-door policy would both be ruled out from the outset.
The paper says:
It is evident from the PDP deliberations and the community’s discussions and feedback that either of the two “edge outcomes” are unlikely to achieve consensus; i.e.:
- 1. allowing closed generics without restrictions or limitations OR
- 2. prohibiting closed generics under any circumstance.
As such, the goal could be to focus the dialogue on how to achieve a balanced outcome that does not represent either of these two scenarios. The space to be explored in this dialogue is identifying circumstances where closed generics could be allowed (e.g., when they serve the public interest, as noted by the GAC Advice). This will likely require discussions as to the types of possible safeguards that could apply to closed generics, identifiable public interest goals for that gTLD and how that goal is to be served, with potential consequences if this turns out not to be the case.
It sounds quite prescriptive, but does it amount to top-down policy making? Insert shrugging emoji here. It seems there’s still scope for the GAC and GNSO to set their own ground rules, even if that does mean relitigating entrenched positions.
The GAC, in its ICANN 73 communique (pdf) said yesterday that it welcomes these talks, and the GNSO Council has already started to put together a small team of councillors (so far also former PDP WG members) to review ICANN’s proposal.
ICANN expects the GNSO-GAC group to begin its work, under an ICANN-supplied facilitator, on one or more Zoom calls before ICANN 74 in June.
Recent Comments