Single/plural gTLD combos to be BANNED

Singular and plural versions of the same string will be banned at the top level under proposed rule changes for the next round of new gTLDs.

The final set of recommendations of ICANN’s New gTLDs Subsequent Procedures working group (SubPro), which were published after four years of development last week, state:

the Working Group recommends prohibiting plurals and singulars of the same word within the same language/script in order to reduce the risk of consumer confusion. For example, the TLDs .EXAMPLE and .EXAMPLES may not both be delegated because they are considered confusingly similar.

The 2012 round had no hard and fast rule about plurals. There were String Similarity Review and String Confusion Objection procedures, but they produced unpredictable results.

At least 15 single/plural string pairs currently exist in the root, including .fan(s), .accountant(s), .loan(s), .review(s) and .deal(s). Sometimes they’re both part of the same registry’s portfolio, other times they’re owned by competitors.

But others, including .pet and .pets and .sport and .sports, were ruled by independent panels too “confusingly similar” to be allowed to coexist.

The proposed new rule would remove much of the subjectivity from these kinds of decisions, replacing the current system of objections with a flat no-coexistence rule.

If a gTLD that was the plural of an existing gTLD were applied for, the application would be rejected. If the singular and plural variants of the same word were applied for in the same round, the applications would likely end up at auction.

But there would be some wriggle room, with the ban only applying if both applied-for strings truly are singular/plural variations of each other in the same language. The working group wrote:

.SPRING and .SPRINGS could both be allowed if one refers to the season and the other refers to elastic objects, because they are not singular and plural versions of the same word. However, if both are intended to be used in connection with the elastic object, then they will be placed into the same contention set. Similarly, if an existing TLD .SPRING is used in connection with the season and a new application for .SPRINGS is intended to be used in connection with elastic objects, the new application will not be automatically disqualified.

In such situations, both registries would have to agree to binding Public Interest Commitments to only use the gTLDs for their stated, non-conflicting purposes. Registrants would also have to commit to only use .spring to represent the season and .springs for the elastic objects, also.

The ban will substantially eliminate the problem I’ve previously referred to as “tailgating”, where a registry applies for the plural variant of a competitor’s successful, well-marketed gTLD, prices domains slightly lower, then sits back to effortlessly reap the benefits of their rival’s popularity.

One could easily imagine applicants for strings such as .clubs or .sites in the next round, with applicants content to lazily ride the coat-tails of the million-selling singular namespaces.

The rule change will also remove the need for existing registries to defensively apply for the single/plural variants of their current portfolio, and for existing registrants to be compelled to defensively registry domains in yet another TLD.

On the flipside, it means that some potentially useful strings would be forever banned from the DNS.

While it might make sense for a film producer to register a .movie domain to market a single movie, it would not make sense for a review site or movies-related blog, where a .movies domain would be more appropriate. But now that’s never going to be possible.

SubPro’s work is still subject to final approval by SubPro, the GNSO Council and ICANN board of directors before it becomes policy.

The end of the beginning? ICANN releases policies for next round of new gTLDs

Over eight years after ICANN last accepted applications for new gTLDs and more than four years after hundreds of policy wonks first sat around the table to discuss how the program could be improved, the working group has published its draft final, novel-length set of policy recommendations.

Assuming the recommendations are approved, in broad terms the next round will be roughly similar to the 2012 round.

But almost every phase of the application process, from the initial communications program to objections and appeals, is going to get tweaked to a greater or lesser extent.

The recommendations came from the GNSO’s New gTLD Subsequent Procedures working group, known as SubPro. It had over 200 volunteer members and observers and worked for thousands of hours since January 2016 to come up with its Final Draft Report.

Some of the proposed changes mean the cost of an application will likely go down, while others will keep the cost artificially high.

Some changes will streamline the application process, others may complicate it.

Many of the “changes” to policy are in fact mere codifications of practices ICANN brought in unilaterally under the controversial banner of “implementation” in the 2012 round.

Essentially, the GNSO will be giving the nod retroactively to things like Public Interest Commitments, lottery-based queuing, and name collisions mitigation, which had no basis in the original new gTLDs policy.

But other contentious aspects of the last round are still up in the air — SubPro failed to find consensus on highly controversial items such as closed generics.

The report will not tell you when the next round will open or how much it will cost applicants, but the scope of the work ahead should make it possible to make some broad assumptions.

What it will tell you is that the application process will be structurally much the same as it was eight years ago, with a short application window, queued processing, objections, and contention resolution.

SubPro thankfully rejected the idea replacing round-based applications with a first-come, first-served model (which I thought would have been a gaming disaster).

The main beneficiaries of the policy changes appear to be registry service providers and dot-brand applicants, both of which are going to get substantially lowered barriers to entry and likely lower costs.

There are far too many recommendations for me to summarize them eloquently in one blog post, so I’m going to break up my analysis over several articles to be published over the next week or so.

In the meantime, ICANN has opened up the final draft report for public comment. You have until September 30.

The report notes that previously rejected comments will not be considered, so if your line is “New gTLDs suck! .com is King!” you’re likely to find your input falling on deaf ears.

After the comment period ends, and SubPro considers the comments, the report will be submitted to the GNSO Council for approval. Subsequently, it will need to be approved by the ICANN board of directors.

It’s not impossible that this could all happen this year, but there’s a hell of a lot of implementation work to be done before ICANN starts accepting applications once more. We could be looking at 2023 before the next window opens and 2024 before the next batch of new gTLDs start to launch.

UPDATE: This post was updated August 27, 2020 to clarify procedural and timing issues.

After a year’s delay, .gay reveals launch dates

Top Level Design has revealed the launch plan for its .gay gTLD, after almost a year of delays.

General availability was originally planned for October last year, but it was pushed out twice, first due to marketing reasons and then because of coronavirus.

The new plan is for GA to begin at 1500 UTC on September 16. Unlike last year’s planned launch, there does not appear to be any special symbolism to the date.

There’s also going to be an early access period first, from September 8 through 15. This is the period where reg prices start high and reduce every day until they settle at regular GA pricing.

As I’ve previously reported, the registry has reserved five tiers of premium names, from $12,500 down to $100, all of which will renew at premium prices to deter domainers.

The base registry fee is $25, but expect to pay more at the checkout.

Most of the large registrars are on board, with half a dozen set to offer pre-regs, but I don’t see any of the big Chinese registrars on the registry’s list.

Countries ask Amazon for thousands more domain blocks

The eight South American nations of the Amazon region are demanding Amazon block more domain names in the recently delegated .amazon gTLD.

Amazon Cooperation Treaty Organization secretary general Alexandra Moreira has written to Amazon VP of public policy Brian Huseman to complain that Amazon’s current set of “cultural” safeguards do not go far enough.

The August 14 letter, which was forwarded to DI, seems to mark a new phase of bilateral talks, after ICANN washed its hands of its reluctant role of third-party facilitator last month.

Currently, .amazon is governed by a set of Public Interest Commitments in its registry contract designed to protect the “Culture and Heritage specific to the Amazonia region”.

ACTO, as well as disagreeing with the use of the term “Amazonia”, has a narrow interpretation of the PICs that Moreira says is “insufficient to ensure respect for the historic and cultural heritage of the Amazon region”.

Under ACTO’s reading, Amazon is only obliged to block a handful of domains from use, namely the words “OTCA”, “culture”, “heritage”, “forest”, “river”, “rainforest”, the names of indigenous peoples and national symbols.

Moreira writes:

That would leave out a vast number of terms that can still cause confusion or mislead the public about matters specific to the Amazon region, such as the names of cities, villages, mountains, rivers, animals, plants, food and other expressions of the Amazon biome, biodiversity, folklore and culture.

ACTO wants the list of protected domains to be expanded to include these additional categories, and for Amazon and ACTO to sign a binding agreement to that effect.

Given that the Amazon forest is home to literally tens of thousands of distinct species and Brazil alone has over 5,500 municipalities, this could translate to a hell of a long list.

I should probably note that the .amazon PICs also offer ACTO the chance to block 1,500 strings of its own choosing, so ACTO’s narrow interpretation may not tell the whole story.

Dot-brand fizzles out after acquisition

Another dot-brand gTLD has decided to terminate its ICANN contract, but this time it’s because the brand itself has been discontinued.

.ceb was applied for by the Corporate Executive Board Company, a consulting company, in 2012.

But the company was acquired by Gartner in 2017, and the CEB brand was discontinued the following year.

For some reason it’s taken Gartner a couple of years to remember it has a gTLD it doesn’t need, and it’s told ICANN it no longer wishes to operate it.

The .ceb dot-brand was never used.

It’s the 81st dot-brand to self-terminate, the 12th this year.

After Chapter 11 filing, JCPenney dumps its dot-brand

American retailer JCPenney has told ICANN it no longer wishes to own its dot-brand gTLD, .jcp.

The notice was filed just a month after the company entered Chapter 11 bankruptcy protection and announced the permanent closure of hundreds of stores.

Like many retailers of non-essential goods, the company’s fortunes have been badly affected by the coronavirus pandemic.

I suspect the gTLD would have been scrapped eventually regardless — JCPenney never used it, and even the obligatory nic.jcp site merely redirects to the company’s primary .com.

It’s the 80th dot-brand to be dumped by its registry. the 11th this year.

ICANN close to becoming $200 million gift-giver

Remember how ICANN raised hundreds of millions of dollars auctioning off new gTLD contracts, with only the vaguest of ideas how to spend the cash? Well, it’s coming pretty close to figuring out where the money goes.

The GNSO Council approved a plan last Thursday that will turn ICANN into a giver of grants, with some $211 million at its initial disposal.

And the plan so far does not exclude ICANN itself for applying to use the funds.

The plan calls for the creation of a new Independent Project Applications Evaluation Panel, which would be charged with deciding whether to approve applications for this auction cash.

Each project would have to fit these criteria:

• Benefit the development, distribution, evolution and structures/projects that support the Internet’s unique identifier systems;
• Benefit capacity building and underserved populations, or;
• Benefit the open and interoperable Internet

Examples given include improving language services, providing PhD scholarships, and supporting TLD registries and registrars in the developing world.

The evaluation panel would be selected “based on their grant-making expertise, ability to demonstrate independence over time, and relevant knowledge.” Diversity would also be considered.

While existing ICANN community members would not be banned from being on the panel, it’s being strongly discouraged. The plan over and over again stresses how there must be rigorous conflict-of-interest rules in place.

What’s less clear right now is what role ICANN will play in the distribution of funds.

The Cross-Community Working Group that came up with the proposal offers three possible mechanisms, but there was no strong consensus on any of them.

The one being pushed, “Mechanism A”, would see ICANN org create a new department — potentially employing as many as 20 new staff — to oversee applications and the evaluation panel.

Mechanism B would see the same department created, but it would work with an existing independent non-profit third party.

Mechanism C would see the function offloaded to a newly created “ICANN Foundation”, but ICANN’s lawyers are not keen on this idea.

The Intellectual Property Constituency was the lone dissenting voice at Thursday’s GNSO Council vote. The IPC says that support for Mechanism A actually came from a minority of CCWG participants, depending on how you count the votes.

It thinks that ICANN should divorce itself as far as possible from the administration of funds, and that not to do so creates the “unreasonable risk” of ICANN being perceived as “self-dealing”.

But as the plan stands, ICANN is free too plunder the auction funds at will anyway. ICANN’s board of directors said as long ago as 2018:

ICANN maintains legal and fiduciary responsibility over the funds, and the directors and officers have an obligation to protect the organization through the use of available resources. In such a case, while ICANN would not be required to apply for the proceeds, the directors and officers would have a fiduciary obligation to use the funds to meet the organization’s obligations.

It already took $36 million from the auction proceeds to rebuild its reserve fund, which had been diminished by ICANN swelling its ranks and failing to predict the success of the new gTLD market.

The CCWG also failed to come to a consensus on whether ICANN or its constituent parts should be banned from formally applying for funds through the program.

Because the plan is a cross-community effort, it needs to be approved by all of ICANN’s supporting organizations and advisory committees before heading to the ICANN board for final approval.

There also looks to be huge amount of decision-making and implementation work to be done before ICANN puts its hand in its pocket for anyone.

The $135 million battle for .web could be won in weeks

Afilias is to get its day in “court” to decide the fate of the .web gTLD just 10 days from now.

The registry is due to face off with ICANN before an Independent Review Process panel in a series of virtual hearings beginning August 3.

The IRP complaint was filed late 2018 as the endgame of Afilias’ attempt to have the results of the July 2016 .web auction overturned.

You’ll recall that Verisign secretly bankrolled the winning bidder, a new gTLD investment vehicle called Nu Dot Co, to the tune of $135 million, causing rival bidders to cry foul.

If that win was vacated, Afilias could take control of .web with its second-place bid.

Afilias claims that ICANN broke its own rules by refusing to thoroughly analyze whether NDC had a secret sugar daddy, something DI first reported on two weeks before the auction.

It has put forward the entirely plausible argument that Verisign splashed out what amounts to about a month’s .com revenue on .web in order to bury it and fortify its .com mindshare monopoly against what could be its most formidable competitor.

In the IRP case to date, ICANN has been acting as transparently as you’d expect when its legal team is involved.

It first redacted all the juiciest details from the Verisign-NDC “Domain Acquisition Agreement” and the presumably damaging testimony of one of its own directors, and more recently has been fighting Afilias’ demands for document discovery.

In March, the IRP panel ruled against ICANN’s protests on almost every count, ordering the org to hand over a mountain of documentation detailing its communications with Verisign and NDC and its internal deliberations around the time of the auction.

But the ace up ICANN’s sleeve may be an allegation made by Verisign that Afilias itself is the one that broke the auction’s rules.

Verisign has produced evidence that an Afilias exec contacted his NDC counterpart five days before the auction, breaking a “blackout period” rule so serious that violators could lose their applications.

While Afilias denies the allegation, the IRP panel ruled in March that Afilias must hand over copies of all communications between itself and rival bidders over the auction period.

We’re not likely to see any of this stuff until the panel issues its final declaration, of course.

In the past, IRP panels have taken as long as six or seven months after the final hearing to deliver their verdicts, but the most-recently decided case, Amazon v ICANN, was decided in just eight or nine weeks.

ICANN washes its hands of Amazon controversy

ICANN has declined to get involved in the seemingly endless spat between Amazon and the governments representing the Amazonia region of South American.

CEO Göran Marby has written to the head of the Amazon Cooperation Treaty Organization to say that if ACTO still has beef with Amazon after the recent delegation of .amazon, it needs to take it up with Amazon.

ACTO failed to stop ICANN from awarding Amazon its dot-brand gTLD after eight years of controversy, with ICANN usually acting as a mediator in attempts to resolve ACTO’s issues.

But Marby yesterday told Alexandra Moreira: “”With the application process concluded and the Registry Agreement in force, ICANN no longer can serve in a role of facilitating negotiation”.

She’d asked ICANN back in May, shortly before .amazon and its Japanese and Chinese translations hit the root, to bring Amazon back to the table for more talks aimed at getting ACTO more policy power over the gTLDs.

As it stands today, Amazon has some Public Interest Commitments that give ACTO’s eight members the right to block any domains they feel have cultural significance to the region.

Marby told Moreira (pdf) that it’s now up to ACTO to work with Amazon to figure out how that’s going to work in practice, but that ICANN’s not going to get involved.

Google’s .new now generally available

After many months of pre-launch registration periods, Google has taken its .new gTLD to general availability today.

Names in .new are not cheap, have strict usage restrictions, and are not available at most of the larger registrars.

You may recall that Google is doing something quite innovative with the gTLD — each .new domain must resolve to a page in which the visitor can immediately (or after logging in) create something new, such as a blog, image, spreadsheet, presentation, webcast and so on.

Over 500 domains have been claimed during sunrise and limited registration periods so far, and dozens are live and functioning according to spec already.

I’ve seen prices ranging from about $450 at Gandi to $550 at 101domain. Google Domains prices names at about $540.

Due to the high registry pricing and restrictions, many registrars do not seem to be carrying the TLD. But GA started just a few minutes ago at time of posting so it’s possible more might come online shortly.