Campaigns in Bulgaria and Greece to get ICANN to un-reject their Cyrillic and Greek-script ccTLD requests have proven successful.
The first decisions handed down by ICANN’s new Extended Process Similarity Review Panel this week said Bulgaria’s .бг and Greece’s .ελ are not “confusingly similar” to other ccTLDs after all.
However, a third appeal by the European Union over the Greek .ευ was rejected on the grounds that the string is too confusingly similar to .EV and .EY when in upper case.
Confusing strings should not be delegated, under ICANN rules, due to the risk of exacerbating the prevalence of security risks such as phishing attacks.
Bulgaria’s initial request for .бг was turned down in 2010 after a panel found it looks too similar to Brazil’s existing ccTLD, .br.
Greece’s bid for .ελ had been blocked for looking too much like .EA, a non-existent ccTLD that could be delegated to a new country in future.
While the initial panel’s process was pretty opaque, the newly published “extended” reviews appear to have employed a fairly scientific methodology to determine similarity.
Twenty American undergraduate student volunteers were shown pairs of strings briefly on screens designed to simulate web browsing. They then had to pick out which one they’d seen.
The volunteers were also shown pairs of similar-looking Latin-script ccTLDs that already exist, in order to establish a baseline for what should be considered an acceptable level of confusability.
The Greek and Bulgarian strings were both found to be less confusing than existing pairs of Latin-script ccTLDs and were therefore given the thumbs-up. The EU string flunked in upper case.
Under ICANN’s rules, it appears that .бг and .ελ can now proceed to delegation, while .ευ has been forever rejected.
The three reports can be downloaded here.
It will be interesting to see how the ICANN Governmental Advisory Committee will react to this.
It was pressure from the GAC — driven by the European Commission and Greece — back in 2012 that forced ICANN into creating the appeals process.
At ICANN’s meeting in Prague that year, the GAC said:
The GAC is of the view that decisions may have erred on the too-conservative side, in effect applying a more stringent test of confusability between Latin and non-Latin scripts than when undertaking a side by side comparison of Latin strings.
Now the EU seems to have been told that it still can’t have its requested ccTLD, and the standard applied was exactly the same standard as applies to Latin ccTLDs.
Will the GAC accept this determination, or stomp its feet?
ICANN’s Governmental Advisory Committee has elected Thomas Schneider of the Swiss government as its new chair.
The unprecedented, one-nation-one-vote secret ballot election at the ICANN 51 public meeting in Los Angeles today saw Schneider beat Lebanon’s Imad Hoballah by 61 votes to 37.
He will take over from Canadian incumbent Heather Dryden at the end of the week.
Schneider is deputy head of international affairs at the Swiss Federal Office of Communications (Ofcom).
He currently serves as one of the GAC’s three vice chairs.
The election was overseen by the Australian Continuous Improvement Group, which provides the GAC with ICANN-independent secretariat services.
Donuts today sold its millionth domain name, according to a company press release.
The name, according to Donuts, was heavenly.coffee.
I’m not saying heavenly.coffee wasn’t the one millionth name, but I reckon that if the one millionth name had been get-free-viagra.guru, I’d still be looking at a press release talking about heavenly.coffee this afternoon.
Donuts is obviously the first company to hit this target. It owns the largest portfolio of new gTLDs by a considerable margin.
The company has 150 delegated gTLDs, 140 of which are in general availability.
Iceland’s ccTLD operator has suspended one or more domain names affiliated with Islamic State, the terrorist group currently running riot in parts of Iraq and Syria.
ISNIC runs .is, which matches the IS acronym.
In a statement on its web site, the company said:
ISNIC has suspended domains that were used for the website of a known terrorist organisation. The majority of ISNIC’s board made this decision today, on the grounds of Article 9 of ISNIC’s Rules on Domain Registration, which states: “The registrant is responsible for ensuring that the use of the domain is within the limits of Icelandic law as current at any time.”
Never before has ISNIC suspended a domain on grounds of a website’s content.
The domain in question was reportedly khilafah.is, which had a web site titled “Khilafah #IS | Media Releases from Islamic State”. Khilafah is the Latin-script version of the Arabic word for Caliphate.
IS has previously been known as Islamic State of Iraq and Syria (ISIS) and Islamic State of Iraq and the Levant (ISIL). It’s current media practice here in the UK to call it “so-called Islamic State”.
ICANN’s Governmental Advisory Committee does not plan to advise against the release of two-character domain names in new gTLDs.
In fact, judging by a GAC discussion at ICANN 51 in Los Angeles yesterday, the governments of many major nations are totally cool with the idea.
Under the standard Registry Agreement for new gTLD registries, all two-character domains (any combination of letters, numbers) must not be sold or activated in the DNS.
The blanket ban was designed to avoid clashes with two-letter ccTLD codes, both existing and future.
ICANN left the door open for registries to request the release of such names, however, and many companies have formally applied to do so via the Registry Services Evaluation Process.
Some registries want all two-character domains released, others have only asked for permission to sell those strings that do not match allocated ccTLDs.
There seems to have been an underlying assumption that governments may want to protect their geographic turf. That assumption may turn out to be untrue.
Representatives from the United States, Netherlands, Spain, Denmark, Australia, Austria and Iran all said yesterday that the GAC should not issue formal advice against the the two-character proposals.
No governments opposed that apparent consensus view.
“The use of the ‘US’ two-letter country code at the second level has not presented any technical or policy issues for the United States,” US rep Suzanne Radell said.
“We, in fact, do not require any approval for the use of US two-character country codes at the second level in existing gTLDs, and do not propose to require anything for new gTLDs,” she said.
She even highlighted domains such as us.com and us.org — which are marketed by UK-based CentralNic as alternatives to the .us ccTLD — as being just fine and dandy with the US government.
It seems likely that the GAC will instead suggest to ICANN that it is the responsibility of individual governments to challenge the registries’ requests via the RSEP process.
“What we see at the moment is that ICANN is putting these RSEP requests out for public comment and it would be open to any government to use that public comment period if they did feel in some instances that there was a concern,” Australian GACer Peter Nettlefold said.
I’ve not been able to find any government comments to the relevant RSEP requests.
For example, Neustar’s .neustar, which proposes the release of all two-character strings including country codes, has yet to receive a comment from a government.
Many comments in other RSEP fora appear to be from fellow dot-brand registries that want to use two-letter codes to represent the countries where they operate.