Iraq to get IDN ccTLD

Iraq was this week granted the right to use a new Arabic-script country-code top-level domain.
ICANN said the war-torn nation’s request for عراق., which is Arabic for “Iraq”, has passed the String Evaluation phase of the IDN ccTLD Fast Track program.
Like .iq, the registry will be the government’s Communications and Media Commission.
Once delegated, the Punycode inserted into the root will be .xn--mgbtx2b.
ICANN said Iraq is the 33rd nation to have an IDN ccTLD request approved. There are currently 26 IDN ccTLDs in the root. Most of them aren’t doing very well.

Second new gTLD round “possible” but not “probable” in 2016

If there are any companies clamoring to get on the new gTLD bandwagon, they’ve got some waiting to do.
Based on a sketchy timetable published by ICANN this week, it seems unlikely that a second application round will open before 2017, and even that might be optimistic.
While ICANN said that “based on current estimates, a subsequent application round is not expected to launch until 2016 at the earliest”, that date seems unlikely even to senior ICANN staffers.
“The possibility exists,” ICANN vice president Cyrus Namazi told DI, “but the probability, from my perspective, is not that high when you think about all the pieces that have to come together.”
Here’s an ICANN graphic illustrating these pieces:

As you can see, the two biggest time-eaters on the road-map, pushing it into 2017, are a GNSO Policy Development Process (green) and the Affirmation of Commitments Review (yellow).
The timetable envisages the PDP, which will focus on what changes need to be made to the program, lasting two and a half years, starting in the first quarter 2015 and running until mid-2017.
That could be a realistic time-frame, but the GNSO has been known to work quicker.
An ICANN study in 2012 found that 263 days is the absolute minimum amount of time a PDP has to last from start to finish, but 620 days — one year and nine months — is the average.
So the GNSO could, conceivably, wrap up in late 2016 rather than mid-2017. It will depend on how cooperative everybody is feeling and how tricky it is to find consensus on the issues.
The AoC review, which will focus on “competition, consumer trust and consumer choice” is a bit harder to gauge.
The 2009 Affirmation of Commitments is ICANN’s deal with the US government that gives it some of its authority over the DNS. On the review, it states:

If and when new gTLDs (whether in ASCII or other language character sets) have been in operation for one year, ICANN will organize a review that will examine the extent to which the introduction or expansion of gTLDs has promoted competition, consumer trust and consumer choice, as well as effectiveness of (a) the application and evaluation process, and (b) safeguards put in place to mitigate issues involved in the introduction or expansion.

The AoC does not specify how long the review must last, just when it must begin, though it does say the ICANN board must react to it within six months.
That six-month window is a maximum, however, not a minimum. The board could easily take action on the review’s findings in a month or less.
ICANN’s timeline anticipates the review itself taking a year, starting in Q3 2015 and broken down like this:

Based on the timelines of previous Review Team processes, a rough estimate for this process is that the convening of the team occurs across 3-5 months, a draft report is issued within 6-9 months, and a final report is issued within 3-6 months from the draft.

Working from these estimates, it seems that the review could in fact take anywhere from 12 to 20 months. That would mean a final report would be delivered between September 2016 and July 2017.
If the review and board consideration of its report take the longest amount of time permitted or envisaged, the AoC process might not complete until early 2018, a little over three years from now.
Clearly there are a lot of variables to consider here.
Namazi is probably on safe ground by urging caution over the hypothetical launch of a second round in 2016.
Given than new gTLD evaluations were always seen as a “rolling” process, one of the things that the GNSO surely needs to look into is a mechanism to reduce the delay between rounds.

Comcast users report name collision bugs

US cable ISP Comcast has become the latest company to experience problems caused by name collisions with new gTLDs.
In this case the gTLD in question is .network, which Donuts had delegated at the end of August.
Users of Comcast’s Xfinity service have been complaining about various issues linked to collisions ever since.
It turns out some Xfinity hubs use the domain home.network on residential networks and that this default configuration choice was not corrected by Comcast before .network went live.
The collision doesn’t appear to be causing widespread internet access issues — Xfinity has close to 20 million users so we’d have heard about it if the problems were ubiquitous — some things appear to be failing.
I’ve seen multiple reports of users unable to access storage devices on their local networks, of being unable to run the popular TeamSpeak conferencing software used by gamers, problems with installing RubyGems, and errors when attempting to use remote desktop tools.
Judging by logs published by affected users, Donuts has been returning the domain “your-dns-needs-immediate-attention.network” and the IP address 127.0.53.53.
Anyone Googling for 127.0.53.53 — the IP address selected to ICANN’s “controlled interruption” name collision management plan — will currently find this ad:

Cyrus Namazi, vice president of DNS industry engagement at ICANN, confirmed to DI that ICANN has received multiple reports of issues on Comcast residential networks and that ICANN has been in touch with the ISP.
Comcast is working on a permanent fix, he said.
Namazi said that ICANN has not received any complaints from users of other ISPs. Most collision-related complaints have been filed by residential users rather than companies, he said.

Fight over ICANN’s $400,000 Hollywood party

Corporate sponsors raised $250,000 to fund a $400,000 showbiz gala for ICANN 51 next month, but ICANN pulled the plug after deciding against making up the shortfall.
Sources tell DI that the lavish shindig was set to take place at Fox Studios in Los Angeles on October 15, but that ICANN reneged on a commitment to throw $150,000 into the pot.
Meanwhile, a senior ICANN source insists that there was no commitment and that a “misunderstanding” is to blame.
ICANN announced a week ago that its 51st public meeting would be the first in a while without a gala event. In a blog post, VP Christopher Mondini blamed a lack of sponsors and the large number of attendees, writing:

One change from past meetings is that there will not be an ICANN51 gala. Historically, the gala has been organized and supported by an outside sponsor. ICANN51 will not have such a sponsor, and therefore no gala. ICANN meetings have grown to around 3,000 attendees, and so have the challenges of finding a gala sponsor.

This explanation irked some of those involved in the aborted deal. They claim that the post was misleading.
Sources say that sponsors including Fox Studios, Neustar and MarkMonitor had contractually committed $250,000 to the event after ICANN promised to deliver the remaining $150,000.
But ICANN allegedly changed its mind about its own contribution and, the next day, published the Mondini post.
“The truth is there were sponsors, the truth is it wasn’t too big,” said a source who preferred not to be named. “There was enough money there for a gala.”
The venue was to be the Fox Studios backlot, which advertises itself as being able to handle receptions of up to 4,000 people — plenty of space for an ICANN gala.
I’ve confirmed with Neustar, operator of the .us ccTLD, that it had set aside $75,000 to partly sponsor the event.
But Mondini told DI that ICANN had not committed the $150,000, and that claims to the contrary were based on a “misunderstanding” — $150,000 was the amount ICANN spent on the Singapore gala (nominally sponsored by SGNIC), not how much it intended to spend on the LA event.
“There was no ICANN commitment to make up shortfall,” he said. “It was misheard as an ICANN commitment.”
More generally, ICANN’s top brass are of the opinion that “we shouldn’t be in the business of spending lots of money on galas”, Mondini added.
“ICANN paying for galas is the exception rather than the rule,” he said.
He added that he stood by his blog post, saying that a failure to find sponsors to cover the full $400,000 tab is in fact a failure to find sponsors.

Accent wins .tickets auction after $1.6m CentralNic investment

Accent Media, one of four applicants for .tickets, has won the new gTLD at auction after receiving a $1.62 million investment from CentralNic.
As part of the deal, Accent has dumped Afilias as its back-end provider and will switch to CentralNic instead.
Competing applicants Donuts, Famous Four Media, Shubert Internet and Tickets TLD are now expected to pull their applications, though none appear to have had their withdrawals accepted by ICANN yet.
It’s not clear how much .tickets sold for.
CentralNic acquired a 12% stake in Accent in exchange for its investment. Both companies are based in the UK.
The deal is believed to be unrelated to the $1.5 million investment in a gTLD applicant that CentralNic announced — with the proceeds earmarked for auction — last week.
Accent has applied for a quite restricted TLD, with anti-fraud measures at its heart. Its authenticated registration process is described as being a bit like the process of buying an SSL certificate.
CentralNic CEO Ben Crawford said in a statement:

The “.tickets” Top-Level Domain will be a compelling new tool to assist consumers to easily identify legitimate and trusted ticket sales sites, as well as empowering venues, entertainers and sports organizations to improve their use of the internet for enabling fans to purchase tickets. This investment realizes our strategy of investing in Top-Level Domain applicants as well as operating as a business partner to their operators.

Amid Ukraine crisis, Russia scared ICANN might switch off its domains

Russia is reportedly worried that the current wave of Western sanctions against it may wind up including ICANN turning off its domain names.
According to a report in the local Vedomosti newspaper, the nation’s Security Council is to meet Monday to discuss contingency plans for the possibility of being hit by internet-based sanctions.
Part of the discussion is expected to relate to what would happen if the US government forced ICANN to remove the local ccTLDs — .ru, .рф, and the discontinued .su — from the DNS root, according to Vedomosti’s source.
The paper reports, citing a source, that “officials want to control the entire distribution system of domain names in RUnet entirely”. RUnet is an informal term for the Russian-language web.
The report goes on to explain that the government’s goal is not to isolate the Russian internet, but to ensure it remains functioning within the country if its ccTLDs are cut off in the rest of the world.
Russia has been hit by sanctions from the US and Europe in recent months due to its involvement in the Ukraine crisis, but so far these have been of the regular economic kind.
Frankly, I find the possibility of the US government asking ICANN to intervene in this way — and ICANN complying — unlikely in the extreme. It would go dead against the current US policy of removing itself almost entirely from the little influence it already has over the root system.

Second last-resort gTLD auction raises $14.3m

ICANN has raised $14.3 million auctioning off three new gTLDs — .buy, .tech and .vip.
It was the second batch of “last resort” auctions, managed by ICANN and Power Auctions, in which the winning bids are placed in a special ICANN fund.
Notably, while Google participated in all three auctions, it failed to win any, setting a reassuring precedent for any smaller applicants that are set to face the deep-pocketed giant in future auctions.
.tech was the biggest-seller, fetching $6,760,000 after nine rounds of bidding.
The winner was Dot Tech LLC, which beat Google, Minds + Machines, Donuts, NU DOT CO, and Uniregistry.
.buy went to Amazon for $4,588,888, beating Google, Donuts and Famous Four Media. The bidding lasted seven rounds.
Finally, .vip sold to Minds + Machines for $3,000,888 after Google, Donuts, I-Registry and VIP Registry dropped out.
The prices are in the same ball-park as we’ve inferred from previous, private auctions managed by Applicant Auction (a company affiliated with Power Auctions).
That’s notable because the first last resort auction, for .信息, fetched just $600,000 when it sold to Amazon back in June.
As far as we can tell, last-resort auctions do not necessarily keep prices low, even though the losing bidders in this week’s auctions will have walked away empty-handed.
In private auctions, losers leave holding a share of the winner’s bid.
This week, most of the $14.3 million raised will go into a special ICANN fund.
Akram Atallah, president of ICANN’s Global Domains Division said in a statement:

The proceeds from these Auctions will be separated and reserved until the Board determines a plan for the appropriate use of the funds through consultation with the community. We continue to encourage parties to reach agreements amongst themselves to resolve contention.

The ICANN community has been chatting about possible uses for auction funds for years.
Ideas such as subsidizing new gTLD applicants from poorer nations in future rounds and investing in internet infrastructure in the developing world have been floated.

DotGreen is back from the dead

DotGreen Community, a popular but unsuccessful applicant for the .green gTLD, has been resurrected to manage the marketing for the successful applicant, Afilias.
It appears that Afilias, which won .green at auction against two other applicants in late February, is essentially outsourcing the marketing of .green to DotGreen.
DotGreen withdrew its bid last October, citing the high cost of the looming auction.
DotGreen’s plan for the TLD, had it won, was to distribute some of its profits to worthy environmental causes, and that plan seems to have been brought back from the dead too.
According to a press release:

DotGreen brings additional partnerships with EarthShare, a federation comprised of the world’s leading environmental and conservation charities; and The DotGreen Foundation, a California Non-profit, 501 (c)3 Public Charity. These organizations will work together to distribute a percentage of the proceeds collected from the sales of the .green domain names to programs that work towards the advancement of sustainability worldwide.

It appears to be a unique, first-of-its-kind relationship in the new gTLD space.
Afilias remains the contracted party and will continue to run the technical infrastructure of the registry, but the heavy-lifting of actually marketing the names falls on DotGreen.
Given that DotGreen spent quite a lot of time in the run-up to the new gTLD application process building relationships with environmental groups, this could be an incredibly shrewd move by Afilias.
Afilias has not yet revealed its sunrise or general availability launch dates for .green, which was delegated in June.

No gala at ICANN 51

One thing ICANN’s thrice-yearly public meetings never lack is free booze, but there’s going to be a little bit less of it at ICANN 51 in Los Angeles next month.
ICANN said yesterday that the gala event, which is typically held on the Wednesday night, will not happen in LA.
ICANN veep Christopher Mondini blogged:

Historically, the gala has been organized and supported by an outside sponsor. ICANN51 will not have such a sponsor, and therefore no gala. ICANN meetings have grown to around 3,000 attendees, and so have the challenges of finding a gala sponsor.

LA is of course ICANN’s home town, hence the lack of need for a local host/sponsor company.
There have been some really spectacular galas over the years — and some not-so-great ones — so the lack of such an event this time around may be mildly disappointing to some attendees.
On the bright side (arguably), Music Night, which was introduced in the Beckstrom era but hasn’t appeared at the last few meetings, is rumored to be making a return for LA.
Usually a Tuesday-night event sponsored by PIR and Afilias, Music Night sees musically inclined ICANN community members jamming together, followed by a bit of karaoke.
Facebook has it that the ah hoc band GEMS (Global Equal Multi-Stakeholders) will be making an appearance to play a selection of bottoms-up, consensus-based classic rock numbers.
Unfortunately, personal circumstances are very probably going to keep yours truly away from ICANN 51, but gifts of whiskey sent to the usual address will of course be consumed in solidarity on the appropriate evening.

“Yes” vote would be good for .scot

The prospect of a healthy .scot gTLD would be improved if this week’s Scottish independence referendum produces a majority “Yes” vote.
People living in Scotland this Thursday get the opportunity to vote to split the country from the United Kingdom after over 300 years together.
While the No campaign seems to have been winning most of the opinion polls recently, the margin has been reportedly narrowing, and there are still large numbers of undecided voters.
Whichever way the vote goes, Dot Scot will take .scot to general availability next Tuesday.
The registry is backed by Scotland’s first minister, Alex Salmond, the leading voice of the Yes campaign, and it seems inevitable that a Yes vote will bode much better for its business prospects.
A vote to split would no doubt create a new sense of national pride in the small majority of Yes voters, spurring registrations in that community.
But, more importantly, it will mean that .scot will become, I believe, Scotland’s de facto ccTLD.
If Scotland does vote for independence, it would not formally split from the UK until, it is planned, March 2016.
The new country would not qualify for a ccTLD until some time after that — it would first have to be recognized by the United Nations, the International Standards Organization, and then ICANN.
When it did finally get a ccTLD delegated and launched, probably in 2017, its two-character string would not have much semantic relevance to most of the world’s internet users.
The ISO 3166-1 alpha-12 list, which assigns two-character codes to countries and territories, only has three strings beginning with S — SP, SQ and SW — currently unaccounted for.
.sc belongs to the Seychelles, for example, while Sao Tome and Principe has .st and Sudan has .sd.
One alternative put forward is .ab, which could be used to represent Alba, the Scots Gaelic name for Scotland.
But it’s hardly a commonly known name outside Scotland (even in the rest of the UK) and there are only 57,000 native Scots Gaelic speakers in a Scottish population of 5.3 million.
It seems pretty clear that if .scot goes up against .ab, or any other two-character string, .scot will win in the marketplace, in much the same way as .com eclipses .us today.
That would be the case even if .scot didn’t get the three-year head start that starts next week.