Single/plural gTLD combos to be UNBANNED

It’s looking like ICANN won’t ban companies from applying for plural versions of existing singular gTLDs, and vice-versa, after all.

Among the pieces of the GNSO’s new gTLD policy advice ICANN’s board of directors rejected at the weekend was a proposal to essentially ban potentially confusing singular/plural combos coexisting in the DNS.

The board threw out the advice because it reckons ICANN would be put in a position where it would have to police internet content, which is outside its mission and something it is very averse to.

The recommendations would have prevented two strings existing in the DNS if one was the plural of the other, but only if they were in the same language and had the same intended usage.

The example the GNSO gave was applications for .spring and .springs — if both were intended for English-language sites related to bouncy metal coils, they would be deemed confusingly similar and only one would be allowed to exist. But if .spring was intended to relate to the season, both would be permitted to coexist.

But ICANN is uncomfortable with this because no matter what an applicant says in its application about intended language and intended use, without some post-delegation policing actual use may vary.

“Though a gTLD applicant can arbitrarily set the language of a TLD during an application round, a registrant and end-user can only see
the script of the TLD string in its practical usage. So the singular/plural determination by the gTLD applicant does not carry
onward to the registrant and end user,” the board wrote.

“Restricting the use and potentially the content of strings registered in TLDs based on the intended use therefore raises concerns for the Board in light of ICANN’s Bylaws Section 1.1 (c),” it said, referring to the part of its bylaws that says it is not allowed to regulate internet content.

So it seems likely that plural/singular clashes are probably going to be permitted in future new gTLD round after all.

This, of course, reopens the business model of a lazy applicant going after the singular/plural of an existing registry’s string and piggybacking on its installed user base or marketing budget.

ICANN rejects a whole bunch of new gTLD policy stuff

ICANN has delivered some bad news for dot-brands, applicants from poorer countries, and others, at the weekend rejecting several items of new gTLD policy advice that the community spent years cooking up.

The board of directors on Sunday approved a scorecard of determinations, including the rejection (or non-adoption) of seven GNSO recommendations that it deems “would not be in the best interests of the ICANN community or ICANN”.

In reality, it’s the latter that seems to have been foremost in the board’s mind; most of the rejections appear to be geared toward reducing ICANN Org’s legal or financial exposure.

Notably, dot-brands are denied some of the relief from cumbersome or expensive requirements that the GNSO had wanted rid of.

The board rejected a recommendation that would exempt them from the Continued Operations Instrument — a financial bond used to pay an Emergency Back-End Registry Operator should the applicant go out of business.

“[T]he Board is concerned that an exemption from an COI for Spec 9 applications would have financial impact on ICANN since there would be no fund to draw from if such a registry went into EBERO,” the board wrote.

It also rejected a request to exempt dot-brands from rules requiring them to contractually ban and monitor abuse in their TLDs. The GNSO had argued that single-registrant TLDs do not suffer abuse, but the board said this could lead to abuse from compromised domains going unaddressed.

“The Board concludes that Recommendation 9.2, if implemented, could lead to DNS abuse for second-level registrations in a single-registrant TLD going unaddressed, unobserved, and unmitigated,” it said.

Applicants hoping to benefit from the Applicant Support Program — which in 2012 offered heavily discounted application fees to poorer applicants — also got some bad news.

The GNSO wants the support to extend to other costs such as application-writing services and lawyers, which naturally enough put the frighteners on the board, which noted “such expansion of support could raise the possibility of inappropriate use of resources (e.g. inflated expenses, private benefit concerns, and other legal or regulatory concerns)”.

The board also rejected a couple of recommendations that could be seen as weakening its role as ultimate authority over all things gTLD.

It rejected a proposal to remove the controversial covenant not to sue (CNTS) from the application process unless other recommendations related to appeals processes are implemented.

ICANN said that because it has not yet approved these other recommendations, it has rejected this recommendation.

The board also rejected a recommendation that would have limited its ability to reject a gTLD application to only when permitted to do so by the rules set out in the Applicant Guidebook.

The idea was to prevent applications being arbitrarily rejected, but the board said this “may unduly limit ICANN’s discretion to reject an application in yet-to-be-identified future circumstance(s)”.

The rejections invoke part of the ICANN bylaws that now requires the GNSO Council to convene and either affirm or amend its recommendations before discussing them with the board. Presumably this could happen at ICANN 78 next month.

The bylaws process essentially gives the board the ultimately authority to throw out the GNSO recommendations if it can muster up a two-thirds supermajority vote, something it rarely has a problem achieving.

Volkswagen ditches its dot-brand

Another major car-maker has thrown in the towel on its key dot-brand gTLD. This time it’s Volkswagen.

Referring to .volkswagen, the company has told ICANN: “This top level domain has never been utilized by Volkswagen of America and we do not intend to utilize it.”

The company had already ditched its secondary dot-brand, .大众汽车 (.xn--3oq18vl8pn36a), which is the Chinese version of its name.

Fiat Chrysler and Bugatti have both also previously terminated dot-brand contracts, while Seat and Audi each have thousands of names in their main dot-brand gTLDs.

Is this why WhatsApp hates some TLDs but not others?

Developers of major pieces of internet software, including the world’s most-popular messaging app, may be relying on seriously outdated lists of top-level domains.

That’s the picture that seems to be emerging from one new gTLD operator’s quest to discover why WhatsApp doesn’t recognize its TLD, and many others including major dot-brands, as valid.

And ICANN isn’t interested in helping, despite its declared focus on Universal Acceptance, the CEO of this registry claims.

When most social media apps detect the user has inputted a URL or domain name, they automatically “linkify” it so it can be easily clicked or tapped without the need for copy/paste.

But when Rami Schwartz of new gTLD .tube discovered that .tube URLs sent via WhatsApp, said to have two billion users, were not being linkified, despite the TLD being delegated by ICANN almost eight years ago, he set out to find out why.

Schwartz compiled a spreadsheet (.xlsx) listing which gTLDs are recognized by WhatsApp and which are not and discovered a rough cut-off point in November 2015. TLDs delegated before then are linkified, those delegated after were not.

According to my database, 468 TLDs have been delegated since December 2015, though not all are still in the root. That’s about a third of all TLDs.

This means that, for example, .microsoft domains linkify but .amazon and .apple domains do not; .asia domains linkify but .africa and .arab domains do not; .london works but .abudhabi doesn’t. Even .verisign missed the cut-off.

If WhatsApp users include a “www.” or “http://” then the app will linkify the domain, even if the specified TLD does not exist.

During the course of a discussion on the web site of the Public Suffix List — which maintains an open-source list of all TLDs and the levels at which names may be registered — it was discovered that the problem may be deeper rooted than the WhatsApp app.

It turns out a library in the Android operating system contains a hard-coded list of valid TLDs which hasn’t been updated since November 24, 2015.

Any app relying on Android to validate TLDs may therefore be susceptible to the same problem — any TLD younger than seven years won’t validate. Schwartz tells us he’s experienced the same issues with the Facebook app on Android devices.

The problem is of particular concern to Schwartz because he’s been planning to market .tube as a form of link-shortening service, and without full support among the most popular messaging apps such a service would be much less attractive.

“I can’t launch this now if it’s not going to work in WhatsApp, if it’s not going to work in Facebook,” he said.

While engineers from Facebook/WhatsApp parent Meta now seem to be looking into the problem, Schwartz says his complaints fell on deaf ears for a long time.

He additionally claims that “ICANN doesn’t really care about universal acceptance” and his attempts to get the Org to pay attention to the problem have been brushed off, despite ICANN making Universal Acceptance one of its key priorities.

Schwartz says ICANN is much more interested in UA when it comes to internationalized domain names (those in non-Latin scripts, such as Arabic or Chinese) and not the technical issues that underpin the functionality of all TLDs.

“I’ve no idea why ICANN makes the decisions it makes, but I think it has to do with inclusion, I think it has to do with diversity, I think it has to do with a lot of things — not technical,” he said. “But this is a technical issue.”

ICANN maintains a set of UA technical resources on its web site and supports the work of the independent Universal Acceptance Steering Group.

Blockchain startup gets $5 million to apply for gTLDs

A company backed by some familiar industry names has raised $5 million in seed funding to apply to ICANN for new gTLDs and, it says, bridge the gap between the traditional DNS and blockchain alternate roots.

Las Vegas-based D3 Global is being led by Fred Hsu, one of the founders of aftermarket pioneer Oversee.net. Among its listed founders are Paul Stahura, one of the triumvirate that launched Donuts, now Identity Digital, to apply for hundreds of gTLDs in 2012.

Also listed as founders are Shayan Rostam, who’s currently building Internet Naming Co into a prominent new gTLD portfolio player, former Network Solutions engineer Shay Chinn and investment banker Michael Ho.

These are people with domain industry experience going back in some cases to the 1990s and track records of building successful disrupters, so it’s worth paying attention no matter what you think of blockchain stuff.

D3 says it plans to apply to ICANN for traditional TLDs but will also introduce interoperability with blockchain-based “Web3” naming systems.

Hsu said in a press release: “We are committed to driving forward the convergence of the traditional DNS system and Web3 to make domain names more versatile, secure, and universally accessible.”

It also talks of introducing a marketplace that combines traditional DNS names with blockchain to “significantly reduce the friction traditionally seen in domain name transactions, such as low transparency, high broker fees, transfer delays, and escrow services.”

The funding round was led by Shima Capital with participation from Lightshift, Dispersion Capital, VentureSouq, Infinite Capital, MZ Web3 Fund, Kestrel0x1, Nonagon, C² Ventures, Arthur Hayes’ Maelstrom, Stahura himself.

Buckridge to replace Shears on ICANN board

Chris Buckridge will replace Matthew Shears on ICANN’s board of directors next month.

The Non-Contracted Parties House of ICANN, their arses burned by an August 18 finger-wagging from ICANN chair Tripti Sinha, somehow managed to narrow down a slate of four candidates to just one by Sinha’s end-of-month deadline, despite seeming to be at a very early stage of the election process just last week.

Buckridge will fill seat 14, reserved for a member of the NCPH and one of two GNSO-picked seats.

He was one of the preferred candidates of the Non-Commercial Stakeholders Group, which along with the Commercial Stakeholders Group makes up the NCPH.

The CSG had rejected the NCSG’s original preference to reappoint Shears, who joined the board in 2017, for a third and final term.

Buckridge comes from the Regional Internet Registry world. He was with RIPE NCC from 2006 until this June in a variety of external relations roles, dealing with European governments and regulators, which seems like a pretty good qualification for an ICANN directorship.

Sinha had written to the NCPH leaders last month to complain that they had failed to pick a director, missing an April deadline, and demanded they name a name before the end of August.

Another six dot-brands self-terminate (two are very strange)

Three companies have asked ICANN to turn off a total of six dot-brand gTLDs. Two each.

Lifestyle Domain Holdings no longer wants to run .cityeats and .frontdoor, Paramount-owned CBS Domains wants out of .cbs and .showtime, and chocolate maker Ferrero wants rid of .kinder and .rocher.

It’s perhaps not surprising that Lifestyle Domains is done with .cityeats and .frontdoor, given that they were never used. What is surprising is that the brands themselves have been defunct for many, many years.

The registry was a part of Scripps Networks, an American cable TV company that owned HGTV and the Food Network. It’s now part of Warner Bros Discovery. CityEats.com and FrontDoor.com were part of its online empire.

But both sites were sold off to third parties in 2015 — the same year Lifestyle signed its two registry agreements with ICANN. In the case of .cityeats, the brand seems to have been sold off months before the contract was signed.

The registry appears to have been paying ICANN $50,000 a year for two TLDs is has absolutely no need for — it owned the dot-brands but not the matching brands. Very weird.

The case of CBS is little more typical. The company has three active domains in .cbs — one just a redirect to a privacy policy — and none in .showtime. It’s a case of not knowing what to do with the TLDs.

The Ferrero case is similar — the domains were not used and the company doesn’t want them any more.

I’ll give the chocolatier honesty points for the message on both nic. sites, which basically admits they were defensive registrations: “This domain is registered and protected by BARBERO & Associates Ltd”.

As both of these strings are non-English dictionary words, they could come up for grabs in the next round. “Kinder” is German for “children”, so it’s not impossible someone might want it as kid-focused generic.

ICANN might be a director light after election stalemate

Months of internecine bickering have led to ICANN facing the possibility that it might enter its 25th anniversary meeting this October without a properly elected director in one seat of the board.

Chair Tripti Sinha has written to (pdf) the heads of the Non-Commercial Stakeholder Group and Commercial Stakeholder Group — and then published the letter, no doubt to light a fire under their arses — to demand they name their candidate for Seat 14 on the board.

The name was due under ICANN’s bylaws by April 26, which is six months before the Hamburg AGM, she said.

Without an appointment, any newly picked director won’t be able to participate in training and meetings to help them hit the ground running at the conclusion of ICANN 78’s AGM, she said.

Seat 14 is selected by the Non-Contracted Parties House. That’s every participant in the GNSO that is not a registry or registrar. It comprises the NCSG and CSG. The incumbent director is Matthew Shears, first picked in 2017.

The CSG has made it clear that it does not want Shears, the NCSG’s initially preferred candidate, reappointed for a third term. It seems the group is unhappy with his performance. It has also rejected alternate Rafik Dammak.

The NCSG meanwhile rejected CSG preference Mark Datysgeld, saying he lacks ICANN experience.

The problem seems to be election rules (pdf) agreed to by the two SGs in 2018 that requires them to reach a “consensus” on a candidate, which can be difficult when by definition they have two fundamentally opposing policy goals.

There may also be confusion about whose “turn” it is to pick a candidate. As the names of the SGs suggests, the two groups represent diametrically opposed interests, so there’s been an informal agreement to rotate nominations between the SGs. The question is whether NCSG/Shears’ turn has ended, or whether he gets the full nine years.

Eight months after the NCPH leaders started to discuss Seat 14, there appears to be four candidates currently under consideration, albeit only at the very early interview phase of the process.

The CSG has put forward Khaled Koubaa and Ihab Osman as candidates. The names are notable as they’re both previous ICANN directors who each served a single term as Nominating Committee appointees (until 2019 and 2022 respectively).

The NCSG has picked “ICANN Policy Ninja” Amr Elsadr and Chris Buckridge, a policy guy from the Regional Internet Registry world, as its two nominees.

With three Africans in the mix, there’s a possibility that next year’s NomCom may have more freedom than usual when trying to fill its geographic diversity quota. None of the slate are female.

Right now, with voting not yet underway, it seems the chances of the two SGs settling on a consensus candidate before Sinha’s end-of-August deadline are close to zero.

ICANN’s general counsel John Jeffrey wrote to (pdf) the NCPH heads back in May to remind them that their nomination was a month late and that any failure to pick a new director before the AGM would lead to Shears retaining the role while his successor is picked (assuming he wants the gig).

There seems to be some concern among ICANN’s top brass that the deadlock within the NCPH — caused, as so many ICANN conflicts are, by a failure to compromise — might reflect badly on ICANN and the multistakeholder model in general.

Yup.

ICANN turns down money from blockchain alt-root

It seems ICANN is turning down free money from blockchain alt-root providers, apparently as a matter of principle.

We hear one such alt-root, Freename.io, tried to sponsor the upcoming ICANN 78 meeting in Hamburg, but was rebuffed.

“At this time, ICANN is not interested in having Freename serve as a sponsor and will not be moving forward with a sponsorship agreement,” the Org told the company in an unsigned email.

Freename had offered to be a general sponsor, and not at the cheapest tier, I’m told.

ICANN sponsorship offers typically start in the low thousands but can get up to six figures at the higher tiers. Sponsorship is overall a very small part of ICANN’s revenue.

Org has become increasingly rattled in recent years with the proliferation of alt-roots, which have been gradually gaining market acceptance while ICANN’s own efforts to expand the domain universe languish in interminable policy knots.

ICANN delayed the sale of the UNR portfolio of gTLDs until buyers renounced their ownership rights to blockchain versions of their authoritative root strings.

Clearly, splashing an alt-root’s branding all over an ICANN stage would be seen as problematic.

Freename.io plans to attend the Hamburg meeting anyway.

CentralNic chief calls on industry to tackle climate change

CentralNic CEO Michael Riedl is calling on his counterparts at other large domain name registries and registrars to meet up to coordinate the industry’s response to climate change.

During a broad keynote at the London Domain Summit this morning, Riedl said that each domain company is too small to make an impact on the industry’s carbon footprint individually, and that coordination is needed.

He said the industry’s carbon footprint is currently “relatively reasonable” but said “we need to get it down to zero… together I’m pretty sure we can make an impact”.

Speaking to DI shortly after his speech, Riedl said he will soon invite industry leaders to a climate change “summit” in Hamburg, Germany, to coincide with ICANN’s 78th public meeting.

He said the domain industry needs to coordinate and standardize its approach to emissions, following the leads of other industries such as automotive.

He said he hoped he could get the CEOs of the big domain companies — he named Verisign and GoDaddy, who rarely send their CEOs to ICANN meetings — to show up.

Planning for the meeting is in the very early stages and Riedl said he has not spoken publicly about the initiative until today’s speech.