ICANN has suspended the accreditation of Korean registrar Dotname Korea over failures to comply with Whois accuracy rules.
The company was told this week that it will lose the ability to sell names for three months.
“No new registrations or inbound transfers will be accepted from 7 October 2014 through 5 January 2015,” ICANN compliance chief Maguy Serad told the company (pdf).
The suspension follows breach notices earlier in the year pertaining to Dotname’s failure to show that it was responding adequately to Whois inaccuracy complaints.
Other breaches of the Whois-related parts of the 2013 Registrar Accreditation Agreement were also alleged.
The company has until December 16 to show compliance of face the possibility of termination.
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.
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.
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.
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.