In the occasional DI tradition of linkbaiting Domaining.com with promises of scantily clad eye candy, I humbly invite male readers to get their goggles around this beauty:
Anyway, there’s a serious point here.
SX Registry, which is in the process of launching the new .sx ccTLD for the recently formed territory of Sint Maarten, distributed this flyer in the goody bags at ICANN 44 in Prague last week.
The marketing was aimed at registrars, presumably, but the company’s web site has similar imagery as well.
It’s pretty clear what angle SX Registry is going for, and it could portend a clash with .sex and .sexy, which have both been proposed by applicants under ICANN’s new gTLD program.
ICM Registry (.sex), Uniregistry (.sexy) and Internet Marketing Solutions Limited (.sex) may have a potential objector on their hands.
The Governmental Advisory Committee has slammed ICANN’s decisions to reject at least three non-Latin ccTLDs because they might pose security risks.
Remarkably, the GAC has also asked ICANN to “urgently reconsider” the rulings, which were made to mitigate the risk of phishing attacks and other types of domain name abuse.
In its official post-Prague communique, published over the weekend, the GAC tells ICANN that the way it decides whether to approve IDN ccTLDs has been “too conservative”.
While the letter does not single out any specific ccTLDs, I understand that the advice was formulated primarily at the behest of the European Union and Greece, which have both had IDN ccTLD applications rejected on the grounds of confusing similarity.
The Prague communique (pdf) states:
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.
It goes on to ask ICANN to publish its criteria for evaluating the similarity of IDN ccTLDs, to create an appeals process, to publish its rationales for rejecting bids, and to revisit old decisions.
The communique states, as formal GAC Advice:
Recently refused IDNs, particularly those nominated by public or national authorities should be urgently re-considered in light of the above considerations.
This request instantly loses the GAC credibility points, in my view, casting it as little more than another special interest group focused on the goals of its members first and internet security second.
To be clear, the GAC is appealing ICANN decisions that were designed to prevent phishing.
Greece’s application for .ελ,was rejected by ICANN last year due to its visual similarity with .EA, a non-existent – but potential future – ccTLD.
While there’s not much on the public record about the European case, I understand Eurid’s bid for a Greek version of .eu was blocked because it looks too much like Estonia’s EE.
Bulgarian IDN supporters have also been very vocal the last couple of years in opposition to ICANN’s decision to forbid .бг due to its alleged resemblance to Brazil’s .br.
While decent arguments can and have been made that some of these rulings were a little on the silly side, it’s hard to argue that they were made without the best of intentions.
The GAC has promised to write to ICANN with “further reflections on the methodology that should be followed when evaluating two character IDNs”.
The GAC as a technical regulator? That letter should make for some interesting reading.
HSBC, Microsoft, Yahoo and jewelry maker Richemont have told ICANN they plan to form a new GNSO stakeholder group just for single-registrant gTLD registries.
The group would comprise dot-brand registries and — potentially — other types of single-user gTLD manager.
A letter (pdf) to ICANN chair Steve Crocker, signed by executives from the four companies, reads in part:
As a completely new type of contracted party, we do not have a home to represent our unique community. In addition, the existence of conflicts with other contracted parties makes it challenging for us to reside within their stakeholder group.
Combined, the companies have applied for about 30 single-registrant gTLDs, mostly corresponding to brands.
Richemont, which is applying for dot-brands including .cartier, is also applying for the keywords .jewelry and .watches as single-user spaces.
The group plans to discuss formalizing itself at the next ICANN meeting, in Toronto this October.
During the just-concluded Prague meeting, the GNSO’s existing registries stakeholder group accepted several new gTLD applicants — I believe mainly conventional registries — into the fold as observers.
How the influx of new gTLD registries will affect the GNSO’s structure was a hot topic for the Governmental Advisory Committee during the meeting too. I guess now it has some of the answers it was looking for.
ICANN has killed off its unpopular “digital archery” scheme, which it had planned to use to rank and batch new top-level domain applications for evaluation.
But the organization has not yet replaced it with anything, leaving gTLD applicants without their much-sought-after certainty for at least the next three weeks.
In a resolution yesterday, ICANN’s New gTLD Program Committee approved the following resolution:
Resolved (2012.06.27.NG06), the New gTLD Program Committee directs the President and CEO to terminate the Digital Archery process as approved in Resolutions 2011.12.08.04-2011.12.08.07.
Given the discussions between the ICANN board and the rest of the community here at ICANN 44 in Prague this week, it would have been more surprising if archery had survived.
Not everyone is happy to see it go, of course.
Richard Schreier, CEO of erstwhile digital archery service provider Pool.com, took to the mic at the ICANN public forum this afternoon to ask that ICANN sticks to its decisions in future.
He further noted that the decision to scrap archery had been made without the input of applicants who are not in attendance at the meeting.
Now that archery has gone, the ICANN board has left a vacuum – nobody knows how applications will be prioritized for processing and evaluation.
Committee chair Cherine Chalaby said that ICANN will now open a comment period for all applicants, in order to help build a “roadmap” to “detail the next steps and timelines”.
This roadmap is due, it seems before the new gTLD committee’s next meeting, which is due to take place approximately three weeks from now.
This does not necessarily mean the program has been delayed, however. ICANN senior vice president Kurt Pritz said a few times this week that evaluators will start looking at apps July 12.
The European Broadcasting Union, which is one of four applicants for the .radio top-level domain, has asked to join ICANN’s Governmental Advisory Committee as an observer.
It is believed that its request is likely to be accepted.
The move, which comes just a couple of weeks after ICANN revealed its list of new gTLD applications, could raise conflict of interest questions.
While several GAC governments and observers are backing new gTLD bids – the UK supports .london, for example – they’re generally geographic in nature and generally not contested.
But .radio has been applied for by Afilias, BRS Media and Donuts in addition to the EBU.
While any organization can file objections against applications, under the rules of the new gTLD program the GAC has the additional right to issue special “GAC Advice on New gTLDs”.
Consensus GAC advice is expected to be enough to kill an application.
Since it’s not entirely clear how the GAC will create its formal Advice, it’s not yet clear whether the EBU will have any input into the process.
According to the GAC’s governing principles, observers do not have voting rights, but they can “participate fully in the GAC and its Committees and Working Groups”.
The EBU’s .radio gTLD would be open to all potential registrants, but it would be subject to post-registration content restrictions: web sites would have to be radio-oriented, according to the application.
It’s also the only Community-designated bid in the contention set, meaning it could attempt a Community Priority Evaluation to resolve the dispute.
The EBU has also applied for .eurovision, the name of its annual singing competition, as an uncontested dot-brand.