Four new gTLD applications have been told by ICANN the strings they wanted are geographic and will require government backing if they want to be approved.
One of the affected applicants is Tata, the $100bn Indian conglomerate.
During a webinar this week, ICANN reported the results of its new gTLD program’s Geographic Names Panel, which decides whether applicants need the support of governments or not.
Six applicants that had designated their applied-for string as geographic were ruled to be actually non-geographic. Three applicants that said they weren’t geographic were ruled to be, in fact, geographic.
And four strings DI had previously said were likely to be ruled geographic, actually received a pass.
These are the applications that have been told they’re geographic:
- .bar — This was applied for by two applicants (one of which was a Demand Media subsidiary) as a TLD for drinking establishments. But “Bar” is also a commune of Montenegro, so it’s been deemed a geographic string by ICANN.
- .tata — This is a dot-brand applied for by Tata Group, the 150-year-old, $100bn-a-year Indian conglomerate. But “Tata” is also a province of Morocco.
- .tui — Applied for by TUI AG as a dot-brand, the string is also a province of Burkina Faso.
Geographic gTLDs can only be approved with the formal support or non-objection of the relevant governments.
All three of these strings were highlighted in the DI PRO database as potentially problematic geographic gTLDs over a year ago, well before the new gTLD application window closed.
I even reported for The Register in January 2012 that .tata was going to have problems.
According to ICANN’s Application Guidebook, any string that matches something on the various International Standards Organization’s lists of geographic names will be deemed geographic for new gTLD approval purposes.
But we got it wrong on some counts.
For example, we wondered whether the seven applications for .store were going to be ruled geographic, on the basis that Štore (note the accent) is a municipality of Slovenia.
Also, .delta, .est and .capital match regions of Nigeria, Burkina Faso and Denmark and all appear on the same protected ISO 3166 list as .tata, .tui and .bar, but do not appear to have been ruled geographic.
ICANN has not published the rationale behind its panel’s decisions yet.
A further six applied-for gTLD strings that had been designated geographic by their applicants were ruled to be not, in fact, geographic.
These all appear to be abbreviations of place names, or place names that do not appear on protected lists: .frl, .ist, .ryukyu, .scot, .vegas and .zulu.
There’s no real harm to applicants that find themselves in this position.
ICANN CEO Fadi Chehade has agreed to speak at an upcoming conference of the Association of National Advertisers, we’ve just been told.
Chehade, currently on a whirlwind global outreach tour, will deliver a lunch keynote on day two of the 2013 ANA Advertising Law & Public Policy Conference, held in Washington DC, March 19 and 20.
The speech is currently untitled, according to the agenda, but I’d hazard a guess that Chehade will be turning on his trademarked charm to attempt to bring more ANA members into the multistakeholder fold.
The ANA, of course, was ICANN’s primary antagonist in late 2011 and much of 2012, after it came out in strong opposition to the new gTLD program, lobbying the US Congress to have it delayed or killed off.
The relationship between the two organizations has mellowed, I sense, more recently, as the ANA has become more accustomed to working within the ICANN environment.
The ANA conference, which comes with the prescient subtitle “Change Ahead: Confrontation, Compromise or Chaos?” will also feature a panel discussion on new gTLDs featuring executives from Verizon and PayPal.
ICANN has finally delivered its String Similarity Panel’s review of all 1,930 original new gTLD applications, finding that only four applied-for strings are confusingly similar to others.
Two new contention sets have been created:
- .hotels (Booking.com B.V.) and .hoteis (Despegar Online SRL)
- .unicorn (Unicorn a.s.) and .unicom (China United Network Communications Corporation Limited)
Only one applicant in each contention set will survive; the strings may go to auction.
The list is bafflingly short given that the panel’s review was originally due in October and has been delayed several times since.
ICANN last month said it was forcing the panel to address “process” issues and heavily suggested that it was trying to make sure the review process was legally defensible, leading to speculation that the list was going to be much longer than expected.
But the panel and ICANN appear to have taken a super-strict approach to finding similarity instead.
The string similarity panel was tasked with deciding whether each applied-for string “so nearly resembles another visually that it is likely to deceive or cause confusion”.
I think the four strings included in its final report pretty conclusively pass that test.
Even the controversial Sword tool – the software algorithm ICANN commissioned to compare string similarity on objective grounds — agrees, scoring them very highly.
According to Sword, .unicorn and .unicom are 94% similar and .hotels. v .hoteis have a score of 99%. For comparison, .hotel versus .hotels produces a score of 81%.
It all seems nice and logical and uncontroversial. But.
All four affected applicants are applying for single-registrant gTLDs, in which the registry owns all of the second-level domains, drastically reducing the chance of abuse.
One of the reasons ICANN doesn’t want to create too-similar TLDs is that they could be exploited by phishers and other bad guys to rip off internet users, or worse.
But with single-registrant TLDs, that’s not really as big of an issue.
It will be interesting to see the affected applicants’ response to these latest findings. Expect complaints.
The results of the review will be a huge relief to most other applicants, which have been wondering since the list of gTLD applications was released last June what the final contention sets would look like.
The high standard that appears to have been used to find similarity may set some interesting precedents.
For example, we now know that plurals are fair game: if Donuts’ application for .dentist is approved in this round, there’s nothing stopping somebody else applying for .dentists in a future application round.
Also, brands with very short acronyms have little to fear from from being found too similar to other existing acronym dot-brands. The applicants for .ged and .gea were among those to express concern about this.
But the question of confusing similarity is not yet completely settled. There’s a second phase.
Applicants and existing TLD registries now have about a week to prepare and submit formal String Confusion Objections, kicking off an arbitration process that could create more precedent for future rounds.
Unlike the just-published visual similarity review, SCOs can take issue with similar meanings and sounds too.
Losing an SCO means your application is dumped into a contention set with the winner; if you lose against an existing TLD operator, your bid is scrapped entirely.
The National Telecommunications and Information Administration said today that all new gTLD applicants, even those that have not already been hit by government warnings, should submit Public Interest Commitments to ICANN.
In a rare comment sent to an ICANN public forum today, the NTIA suggested that applicants should use the process to help combat counterfeiting and piracy.
The agency, the part of the US Department of Commerce that oversees ICANN and participates in its Governmental Advisory Committee, said (emphasis in original):
NTIA encourages all applicants for new gTLDs to take advantage of this opportunity to address the concerns expressed by the GAC in its Toronto Communique, the individual early warnings issued by GAC members, and the ICANN public comment process on new gTLDs, as appropriate.
PICs were introduced by ICANN earlier this month as a way for applicants to voluntarily add binding commitments — for example, a promise to restrict their gTLD to a certain user base — to their registry contracts.
The idea is to let applicants craft and agree to stick to special terms they think will help them avoid receiving objections from the GAC, GAC members and others.
NTIA said that applicants should pay special attention in their PICs to helping out the “creative sector”.
Specifically, this would entail “ensuring that WHOIS data is verified, authentic and publicly accessible”.
They should also “consider providing an enforceable guaranty that the domain name will only be used for licensed and legitimate activities”, NTIA said, adding:
NTIA believes that these new tools may help in the fight against online counterfeiting and piracy and is particularly interested in seeing applicants commit to these or similar safeguards.
The PICs idea isn’t going down too well in the applicant community, judging by other submissions this week.
The Registries Stakeholder Group of ICANN, for example, says its members are feeling almost “blackmailed” into submitting PICs, saying the timing is “completely unreasonable”.
As DI noted when PICs was first announced, applicants have been given until just March 5 to submit their commitments, raising serious questions about the timetable for objections and GAC advice.
The RySG has even convened a conference call for March 4 to discuss the proposal, which it says “contains so many serious and fundamental flaws that it should be withdrawn in
The Trademark Clearinghouse is set to open its doors for submissions March 26, ICANN will announce today.
From that date, trademark owners and their agents will be able to start uploading trademark data, enabling them to participate in one or two of the new gTLD program’s rights protection mechanisms.
Adding a mark to the TMCH qualifies it for the Trademark Claims service, which notifies both rights-holders and registrants whenever somebody tries to register a domain matching the mark.
Trademark Claims will run for at least the first 60 days after each new gTLD launches, but ICANN may extend that window depending on the outcome of its “strawman” discussions.
Many trademarks will also qualify for Sunrise periods in new gTLDs by being entered into the Clearinghouse.
Submissions start at $150 per mark per year, with discounts available when marks are registered in bulk.
DI PRO subscribers can work out how painful the TMCH will be on their wallets, and how to maximize their discounts, using our Trademark Clearinghouse Cost Calculator.
The TMCH is being managed by Deloitte, with a back-end database run by IBM.
While March 26 is just four weeks before ICANN expects to approve the first new gTLDs, I wouldn’t expect to see the first Sunrise periods for a few months after that.
The TMCH is still subject to some fierce debate, and not only because of the proposed strawman changes.
On the technical side, registries and registrars have been fuming recently about the lack of any hard technical specifications for integration, which will be needed when the new gTLDs launch.
Last night, ICANN finally posted the first spec as an IETF Internet Draft.
The format, “Mark and Signed Mark Objects Mapping” describes an Extensible Provisioning Protocol extension used by the TMCH to exchange data with registries about registered trademarks.