New gTLD winners could be named June 2013

ICANN has sketched out a tentative timetable for the evaluation of its new generic top-level domain applications that would see the first successful gTLDs appear over a year from now.
But the plan has little meat on its bones, and ICANN has admitted that it still doesn’t know exactly how the evaluation process is going to pan out.
In a new call for comments, ICANN confirmed that all 1,930 applications are going to be evaluated at the same time, and that the evaluators have already started work.
The winners and losers from Initial Evaluation, ICANN said, could be announced June or July 2013.
This would mean that the first new gTLDs would start going live on the internet “in late third quarter of 2013, six months later than originally expected”, ICANN said.
But which successful applications would start hitting the root first is still wide open to debate.
The idea that the applications would be processed in batches of 500 or thereabouts, is now pretty much dead. That’s been obvious since digital archery was killed off, but it’s now confirmed.
ICANN said it has a “tentative project plan” that “foresees the processing of applications in a single batch, and simultaneous release of results” about a year from now.
But with “batching” dead, we now have a “metering” problem.
Hypothetically, as many as 1,409 unique gTLD applications could emerge successfully from evaluation at the same time, in June or July next year.
That’s the theoretical ceiling; in reality the number will be substantially reduced by withdrawals, objections and contention.
But before any of them can go live the applicants need to negotiate and/or sign registry agreements with ICANN and undergo formal pre-delegation technical testing. That creates two bottlenecks at ICANN in its legal and IANA departments.
ICANN now wants to know how to “meter” successfully evaluated applications, to smooth out the roll-out so that no more than 1,000 new gTLDs are delegated in any given year.
An idea that emerged in Prague was to order applications according to how “clean” they were, as measured many clarifying questions the evaluators had to ask the applicants. But that idea has now been dismissed as “unworkable”, ICANN said.
ICANN’s board of directors had promised to make about three weeks after the Prague meeting – a deadline that passed over a week ago – but it’s now turning to the community for ideas.
Before August 19, it wants to know:

1. Should the metering or smoothing consider releasing evaluation results, and transitioning applications into the contract execution and pre-delegation testing phases, at different times?
a. How can applications be allocated to particular release times in a fair and equitable way?
b. Would this approach provide sufficient smoothing of the delegation rate?
c. Provide reasoning for selecting this approach.
2. Should the metering or smoothing be accomplished by downstream metering of application processing (i.e., in the contract execution, pre-delegation testing or delegation phases)?
a. How can applications be allocated to a particular timing in contract execution, pre-delegation testing, or delegation in a fair and equitable way?
b. Provide reasoning for selecting this approach.
3. Include a statement describing the level of importance that the order of evaluation and delegation has for your application.

My hunch based on conversations in Prague is that the majority answer to question 1 will be “No” and that the majority answer to question 2 will be “Yes”, but that’s just a hunch at this point.

.sx denies .sex gTLD objection rumor

The CEO of SX Registry has denied rumors that the company already plans to object to the two .sex new gTLD applications, but has not yet ruled out such a move.
The company runs Sint Maarten’s new ccTLD, .sx, and gossip at the ICANN meeting in Prague last month suggested that an objection or two against .sex might be made on confusing similarity grounds.
The rumors were fueled in part by SX Registry’s sexy launch marketing.
But in a recent email to DI, Normand Fortier wrote:

At this time SX Registry is still reviewing the impact of various gTLD applications and contrary to some published rumors, has not taken any official position or decision regarding a future course of action.

Existing ccTLD operators are allowed to file String Confusion Objections against gTLD applications, if they feel there’s a risk of confusion if the gTLD is approved.
And .sx/.sex is far from a unique case.
In fact, of the 375 applications for three-letter gTLDs in the first round, 304 have only one character variance with one or more existing ccTLDs, according to DI PRO’s string similarity analysis.
ICANN’s Sword algorithm, which compares the visual similarity of strings, gives .sex a score of 57% against .sx.
I’ve checked every three-character gTLD application against every existing ccTLD and found dozens of proposed gTLDs with much higher similarity scores when compared to ccTLD strings.
The full results are available to DI PRO subscribers over here.

ICANN begins evaluating new gTLD applications

ICANN has already started formally evaluating some of the 1,930 new generic top-level domain applications it has received, according to sources.
Technical and financial evaluations are believed to have been going on for several days at the three outside firms ICANN has contracted with – Ernst & Young, KPMG and JAS Global Advisors.
ICANN staff said a few times during the Prague meeting last month that July 12 was the kick-off date for evaluations, but I’m led to believe they may have started a little later than that.
Nevertheless, they’re underway.
What’s not yet known is how – or if – the 1,930 applications will be batched into more manageable chunks.
The last official word from ICANN came on June 28, when Cherine Chalaby, chair of the board’s new gTLD program committee, said an update would be provided in about three weeks.
With that admittedly vague deadline now in the past, we can only assume that the publication of a new timetable is imminent.

ICANN fixes new gTLD portal bugs

ICANN has brought its new gTLD program customer service portal back online after about five days of patching-related downtime.

In a notice posted late last night, ICANN said the delay was due to the wait for a vendor patch. ICANN said:

A recent, proactive review of the CSC system identified potential vulnerabilities. To address these vulnerabilities, the CSC portal was taken offline while vendor-provided patches were applied. There have been no known compromises to any data.

New gTLD applicants will now have to log in to their TLD Application System accounts, which use the Citrix remote terminal software, to use their customer service tools.
Non-applicants will be able to ask customer service questions via email.
The Knowledge Base — essentially a program FAQ — is still offline, but ICANN said it hopes to bring it back up within a few days.

New gTLD applicants: here’s how to lobby the GAC

ICANN’s Governmental Advisory Committee has let it be known that it’s open to receiving communications from new gTLD applicants.
But the GAC will only hear briefings from applicants at the request of GAC members, according to a notice posted on the GAC’s web site recently.
The GAC has strong powers to recommend the rejection of new gTLD applications, so naturally enough some applicants have already been lobbying to reinforce their positions.
Applicants are now being asked to send information to a specific email address or — implicitly — to lobby GAC representatives individually.
The new statement reads:

It is important to bear in mind that GAC members are still in the process of analysing the list of applications and applicants for new gTLDs. However, there have been a number of requests from applicants or other interested stakeholders to brief or provide briefing material to the GAC.
Briefings for the GAC will only be scheduled on a best-efforts basis and entirely at the request of GAC members.
An internal process for handling requests and tracking materials is being put in place, but those wanting to make their interest or availability known or to express an interest in providing written materials to the GAC can contact the GAC via gacsec@gac.icann.org. A list of those expressing interest or availability or that have provided materials will be made available to the GAC membership.

The GAC caused controversy last month when it accepted the European Broadcasting Union’s application for Observer status on the committee.
The EBU is also an applicant for .radio, which is contested by Donuts, Afilias and BRS Media.
BRS Media claims this is a conflict of interest and recently started lobbying for the EBU to withdraw its application. This week, it set up a web site to promote its cause.

Dispute over ‘confusing’ new gTLD company names

Is this the first “confusing similarity” fight to emerge from ICANN’s new gTLD program?
Two new UK outfits are involved in a dispute about their very similar company names, it has emerged.
TLD Registry Services seems to have come first. It’s an offshoot of Island Networks, the registry manager for the Channel Islands country-code TLDs .gg and .je.
According to co-founder Nigel Roberts, the company plans to offer registry services to existing TLDs using the CoCCA platform and has already made headway with a few potential clients.
TLD Registrar Services, on the other hand, is affiliated with CentralNic, the relatively successful new gTLD registry back-end provider.
Judging by its placeholder web site, this company plans to offer white-label registrar services to new gTLD operators such as dot-brands.
Roberts is irked that CentralNic picked a name for its company so similar to his own, particularly given that “registry” and “registrar” are often used interchangeably outside of the domain industry.
“We’ve recently asked the Secretary of State to look into how this situation came to pass,” he said. “It’s less than ideal for both parties. We are sure they are just as keen not to be confused with us, as we are keen not to be confused with them.”
Ben Crawford, CEO of CentralNic and chairman of TLD Registrar Services, said he was not aware of a dispute over the name.
“One of our employees was approached at Prague by someone from a company called TLD Registry Services – a company nobody in our business had ever heard of before,” he said.
“They expressed concern that our company names are too similar to each others’. We will consider their concerns and our options in due course.”
With both companies barely out of stealth mode, it’s probably something of a squall in a teacup at the moment, but it does highlight how tricky it can be to find a descriptive company name in this industry.
We could of course just be looking at a profound lack of imagination here, and I’m just as guilty as the rest.
DI is published by TLD Research Ltd, which appears directly after TLD Registrar Services Ltd and TLD Registry Services LLP in the UK’s Companies House register of companies.

ICANN shuts down new gTLD portal after finding more security bugs

ICANN has closed down part of its new generic top-level domain portal after finding “potential vulnerabilities” that put “confidential applicant information” at risk.
The shutdown — which has been going on for at least 30 hours — affects the Customer Service and Knowledge Base parts of the site, but ICANN said it is so far not aware of any attacks against the system.
While it’s waiting for a patch, ICANN has decided to move the affected areas behind the unpopular Citrix remote terminal software used previously in the TLD Application System.
This notice was posted on the site:

ICANN performs ongoing monitoring and analysis of our systems, including the Customer Service system. As part of this work, we recently identified potential vulnerabilities in the system used for Customer Service and the Knowledge Base (containing new gTLD articles and information).
Patches are being provided to ICANN to address these issues.
In the mean time, given that use of the Customer Service system was recently expanded, and now includes confidential applicant information, the decision was taken to move the system behind Citrix. This will provide for additional security for applicant information.
We are now testing the installation. This should be completed in the next few days. This decision is a proactive measure. There have been no known compromises to the data, attacks or other actions by third parties (other than our own analysis).

Off the top of my head — and I may be under-counting — this is the fifth significant technical glitch to hit the new gTLD program since April.
There was the notorious TAS bug, which took the system offline entirely for six weeks while ICANN fixed a data leakage vulnerability and upgraded its system capacity.
There was the Reveal Day screw-up, during which Arab community members noticed that all the applied-for Arabic gTLDs were broadcast back-to-front in a presentation.
Then ICANN accidentally published the home addresses of many applicants’ officers and directors, something it had promised not to do. This was probably human error and it has since apologized.
Then the “digital archery” batching system was yanked, after it emerged that TAS performance still wasn’t up to the task and that the scoring results were unreliable.
Former new gTLD program director Michael Salazar resigned a month ago; it is widely believed that he was taking the fall for the gTLD system bugs to that point.
While the latest bug appears — so far — to have not compromised any data, some applicants have nevertheless been frustrated by the fact that the customer service portal has been offline for over a day.

Vignes out as CEO of OpenRegistry

OpenRegistry’s founding CEO, Jean-Christophe Vignes, left the position to join a Paris-based law firm last month.
He’s now senior counsel for the domain name practice at Caprioli & Associés.
Vignes said the change of jobs came as part of his family’s move to Paris and that he’s still a member of the OpenRegistry board of directors.
OpenRegistry (also known as Sensirius), which was selected as the back-end registry provider for 21 gTLD applications including .deloitte, .kpn and .schwarz, is based in Belgium.
It is believed that Hans Seeuws, Vignes’ former second in command, is now in charge at OpenRegistry.

.radio applicant slams GAC “conflict of interest”

BRS Media, one of the four applicants for the .radio generic top-level domain, claims ICANN’s Governmental Advisory Committee has a “direct conflict of interest” over the gTLD.
As DI reported two weeks ago, the European Broadcasting Union, another .radio applicant (the others are Afilias and Donuts), joined the GAC during ICANN’s public meeting in Prague.
While the EBU only has Observer status, and may not vote, it’s still able to participate in discussions. Whether these include discussions about GAC objections to new gTLDs is unclear.
BRS Media, which already runs the radio-themed .fm and .am ccTLDs, is not taking any chances, however. In a letter to GAC chair Heather Dryden, company CEO George Bundy wrote (pdf):

We believe these activities to be a direct Conflict of Interest, by the European Broadcasting Union within the New TLD Application process.

Optimistically, to say the least, BRS requests that the EBU “recuse itself from the New TLD process by withdrawing its applications immediately”.
While I can’t see that happening, it seems to me that the GAC does have to formally address the conflicts issue if it wants to avoid looking like a bunch of hypocrites.
The GAC does not appear to have a formal conflicts of interest policy, even though it pushed hard for similar provisions in the ICANN board.
Now that it has its hard-fought veto rights over new gTLD applications, some sort of safeguards seem appropriate.

Christian group opposes .sex, .porn, .adult

Morality In Media, one of the groups that fought the approval of .xxx for years, has launched a letter-writing campaign against the proposed .sex, .porn and .adult top-level domains.
ICANN has received a couple dozen comments of objection to the three gTLDs over the last couple of days, apparently due to this call-to-arms.
Expect more. MIM was one of the main religion-based objectors to .xxx, responsible for crapflooding ICANN with thousands of comments in the years before the gTLD was approved.
Now that .xxx has turned out to be less successful than ICM Registry hoped, MIM feels its key belief on the subject — that porn gTLDs lead to more porn — has been vindicated.
MIM president Patrick Trueman wrote in one of his comments:

During the years of this fight against the .xxx domain, we said many times that the establishment of a .xxx domain would increase, not decrease the spread of pornography on the Internet, causing even more harm to children, families and communities, and make ICANN complicit in that harm.
That prediction has been fulfilled because the porn sites on the .com domain have not vacated the .com and moved to .xxx. Rather, as we have seen, the .xxx has just added thousand of additional porn sites on the Internet and .com porn sites stayed put. ICANN bears responsibility for this. The .xxx was not needed.

For some reason, the complaints are only leveled at the three ICM Registry subsidiaries that are applying for porn-themed gTLDs, and not the other .sex applicant.
Uniregistry’s application for .sexy has not been targeted.
And MIM has apparently not read the applications it is complaining about; its call to action complains about non-porn companies having to pay “protection money” to defensively register in .sex.
However, the three ICM bids explicitly contemplate an extensive grandfathering program under which all current defensive registrations in .xxx would be reserved in .sex, .porn and .adult.