Donuts blames “license” problems for Chinese gTLD delays

Donuts says that problems obtaining “licenses” from the Chinese government are to blame for the fact that it is yet to launch any of its Chinese-script new gTLDs.
Currently, four of the company’s portfolio of 156 gTLDs are in Chinese. Three have been delegated to the DNS root but none of them have been launched.
The first, .游戏 (for “games”) has been in the root since October 2013, but does not yet have a firm date for Sunrise. Another, .商店 (“shop”), was delegated just last week, almost a year after Donuts signed its Registry Agreement with ICANN.
Donuts explained the .游戏 delay with the following statement:

The Chinese government division which handles this area is MIIT [Ministry of Industry and Information Technology] and in conjunction with [.cn registry] CNNIC they are still to advise of the licensing application process. We hope to make these TLDs available during the first half of 2015.

No additional details were available and it’s not clear what licenses Donuts — which is based in the United States — thinks it needs to obtain before launching.
I’ve heard rumors that China may introduce a licensing system in future, but other new gTLD registries with Chinese-script strings in their stable have managed to launch their gTLDs just fine without a Chinese government license.
TLD Registry — legally based in Dublin, Ireland, founded by Finns — launched .中文网 and .在线 earlier this year and has tens of thousands of names under management.
Thousands of those domains, which match Chinese geographic names, were allocated to Chinese government, however.
“No licenses are currently possible, because the new law is MIA,” TLD Registry chief marketing officer Simon Cousins told us.

ICANN 53 will be in Buenos Aires

ICANN has picked Buenos Aires, Argentina, for its 53rd public meeting.
The choice of city was approved by the ICANN board late last week.
The meeting will be held June 21-25 next year, sandwiched between February’s return to Singapore and October’s first foray into Dublin.
The BA venue has not been disclosed yet, but it’s possible ICANN will return to the Sheraton hotel and convention center.
It’s the third time ICANN has held one of its public meetings in Argentina. It visited BA last year for ICANN 48 and the sleepy seaside town of Mar Del Plata in 2005.
Having attended both previous meetings, I’ve discovered that it’s possible for a vegetarian to quickly become seriously malnourished in Argentina, so it’s quite likely DI’s coverage of ICANN 53 will heavily leverage the excellent remote participation facilities.
BA’s great if you love steak, however.

Black Ice suspended by ICANN

A small Israeli registrar has had its registrar accreditation suspended by ICANN.
Black Ice domains, which has a few thousand .com and .net domains under management, failed to comply with an ICANN audit and was overdue on its fees by over $5,000, according to the ICANN notice (pdf).
It won’t be allowed to sell gTLD domains or accept inbound transfers from December 19 to March 18, and may be terminated if it fails to come back into compliance.
The registrar is the fourth to have its accreditation suspended by ICANN in 2014. The organization has terminated a further seven registrars, down on the 11 terminated in the whole of 2013.

Community proposes way to replace US oversight of ICANN

The process of removing the US government from management of the DNS root system took a significant step forward today, with the publication of a community proposal for a transition.
The Cross Community Working Group, which convened itself earlier this year, has published a proposal to replace the US with a new contracting company and a bunch of committees.
The DNS community has been tasked with coming up with a way to transition stewardship of the IANA functions from the US National Telecommunications and Information administration, which said in March this year that it intends to relinquish its historic, but largely symbolic, Damoclean role.
After discussions which by any measure of ICANN policy-making have been forcibly swift, the 119-member CWG has now presented two broad options.
The first, a description of which forms the bulk of its report, would see ICANN overseen by a new, lightweight non-profit company managed by multi-stakeholder committees.
The other, which doesn’t get much airplay in the document, would see ICANN simply take over the NTIA’s responsibilities entirely. Accountability would be provided by enhanced accountability processes within the existing ICANN structure.
Under the primary proposal, the CWG was keen to avoid creating something ICANN-like to oversee ICANN, due to the complexity and cost, but it also decided that ICANN remains the best place to house the IANA function for the foreseeable future.
It’s proposed a new company, known currently as “Contract Co”, that would be replace the NTIA as the party that contracts with ICANN to run IANA. It would have “little or no staff”.
The contract itself would be developed and overseen by a Multistakeholder Review Team, comprising people drawn from each area of the ICANN community.
The precise make-up of this MRT is still open to discussion and will be, I suspect, the subject of some pretty fierce debate as the various competing interest groups wrestle to have themselves with the strongest possible representation.
Like the NTIA, the MRT would have the power to pick another entity to run IANA in future, should ICANN screw up.
A new Customer Standing Panel would comprise executives from gTLD and ccTLD registries — the “customers” of IANA’s naming functions — and would have the job of relaying the concerns of registries to the MRT, keeping ICANN accountable to its primary users.
Finally, there’d be an Independent Appeals Panel. Any IANA decision — presumably including the delegation or redelegation of a TLD — could be appealed to this IAP. This function would very probably be outsourced on a case-by-case basis to an existing arbitration body.
Is this worrying? Arbitration panels handling new gTLD disputes haven’t exactly inspired confidence in their ability to provide consistent — or even rational — decisions over the last year or so. Should the last word on what goes into or stays out of the DNS root really go to the same folk who think .通販 and .shop are too confusingly similar to coexist on the internet?
There doesn’t appear to be anything massively surprising in the proposal. When ICANN or its community try to solve a problem the answer is usually a new committee, and the ideas of MRTs, CSPs and IAPs do seem to mirror existing structures to an extent.
The whole thing can be downloaded and read over here.
There’s a December 22 deadline for comment. It will be submitted to the IANA Stewardship Transition Coordination Group by the end of January, with a view to getting a final proposal to the US government next summer in time for the hoped-for September 30 handover date.

Richemont pulls two dot-brand bids

Luxury goods company Richemont has withdrawn two of its original 14 new gTLD applications.
The company, which has been a vocal supporter of dot-brand gTLDs, pulled its bids for .netaporter and .mrporter this week.
Mr Porter and Net A Porter are fashion retail web sites for men and women respectively.
It’s not clear why these two bids have been withdrawn — the company isn’t commenting — but it’s certainly not a signal that Richemont is abandoning the new gTLD program completely.
The company has already entered into ICANN contracts for six dot-brands including .cartier, .montblanc and .chloe.
It has another five applications — four generics and one brand — that are still active: .手表 (“.watches”), .珠宝 (.jewelry), .watches, .jewelry and .jlc.
It has previously withdrawn an application for .love.

ICANN meetings in for big shake-up, more dancing

Could you tolerate an eight-day ICANN meeting?
Could you get all your work done in just four days?
Would you be happy to wait up to nine months between Public Forums?
Do you want to see more regional dancing during ICANN opening ceremonies?
These are question you’re going to have to start asking yourself, because come 2016 ICANN meetings are in for a big change.
Recommendations adopted wholesale by the ICANN board last week would scrap the three six-day meetings schedule and replace it with one six-day meeting at the start of the year, one four-day meeting in the middle and one eight-day meeting towards the end.
The first of the year would be formatted pretty much the same as all meetings are currently.
The second, however, would scrap formalities such as the opening ceremony, as well as the Public Forum and public board meeting. Instead, the focus would be on policy development work within and between advisory committees and supporting organizations.
The final meeting of the year, the AGM, would add two extra days to the regular schedule for outreach sessions and SO/AC policy-making. There would be two Public Forum sessions, one immediately after the opening ceremony on day three, the other on day six as usual.
As this would be the official outreach “event” of the year, the opening ceremony would usually have some display of local culture, such as music or dance. That was once a staple of ICANN meetings, but we haven’t seen much of it the last couple of years.
The shake-up was recommended in a report published by the Meeting Strategy Working Group in February and adopted in its entirely by the ICANN board last week.
The third meeting of the year would be “would have a focus on showcasing ICANN’s work to a broader global audience”, according to the report. It would have an anticipated attendance of over 2,000 people and would therefore likely be held in a large hub city.
The smaller (it is anticipated) second meeting, with its reduced focus on formality and outreach, would (contrarily) be able to visit cities with smaller facilities, perhaps in parts of the world ICANN has not been able to visit before, the report says.
To be honest, I’m not really sure whether what’s been adopted will be any better than what’s in place today.
I’m pretty certain of one effect, however: if bombshells are dropped shortly after the first meeting of the year, you’re looking at somewhere between seven and nine months before you’ll be able to stand at a mic and yell at the ICANN board about it in public.

Where to find new gTLD dropping domain lists

With hundreds of thousands of currently blocked new gTLD domain names about to hit the market, many without premium pricing, some domain investors have been wondering where they can get hold of the lists of soon-to-be available names.
Fortunately, ICANN freely publishes several lists that could prove useful.
As we’ve been reporting this week, names that were previously reserved by new gTLD registries due to name collisions have started to become unblocked, as mandatory 90-day “controlled interruption” phases start to expire.
By definition, a name collision domain has received traffic in the past.
A CSV file containing a list of all domain names currently subject to CI can be downloaded from ICANN here.
Be warned, it’s a 68MB file with millions and millions of lines — your spreadsheet software may not be able to open it. It also changes regularly, so it could get bigger as more new gTLDs begin their CI programs.
The file shows the TLD, the second-level string, the date it went into CI and the number of days it has remained in that status. When the last number hits 90, the block is due to be lifted.
A second CSV file contains all the domains that have completed CI. Find it here. It’s currently almost 7MB, but it’s going to get a lot bigger rather quickly as domains move from one list to the other.
That file shows the TLD, the SLD, the date CI started and the day it ended.
Every domain name in that list is no longer subject to a mandatory ICANN block, but that doesn’t necessarily mean that the registry has unblocked it in practice. Some registries are planning to keep hold of the newly available domains and release them in batches at a later date.
Some gTLDs have chosen to wildcard their zones rather than implement a CI response on each individual name collision. In those cases, individual domain names will not show up in the current collisions file. Instead, you’ll see an asterisk.
In those cases, you can find a list of all of each gTLD’s name collisions in separate CSV files accompanying each TLD’s ICANN contract. The contracts can be found here. Click through to the TLD you’re interested in and download the “List of SLDs to Block” file.
Note that there’s a lot of absolute garbage domains in these files. The name collisions program ain’t pretty.

Over 180,000 blocked new gTLD names to drop next week

Several new gTLD registries will release hundreds of thousands of currently blocked domain names — some of them quite nice-looking — next Wednesday.
It’s one of the first big batches of name collisions to be released to market.
The companies behind .xyz, .website, .press, .host, .ink, .wiki, .rest and .bar will release most of their blocked names at 1400 UTC on November 26. These registries all use CentralNic as their back-end.
The gTLD with the biggest “drop” is .host, with over 100,000 names. .wiki, .website and .xyz all have 10,000 to 20,000 releasing names apiece.
According to Radix business head Sandeep Ramchamdani, A smallish number — measured in the hundreds — of the .host, .press and .website names are on the company’s premium domain lists and will carry a higher price.
He gave the following sample of .website domains that will become available at the baseline, non-premium, registry fee:

analyze.website, anti.website, april.website, bookmark.website, challenge.website, classics.website, consumer.website, definitions.website, ginger.website, graffiti.website, inspired.website, jobportal.website, lenders.website, malibu.website, marvelous.website, ola.website, clients.website, commercial.website, comparison.website

Drop-catching services such as Pool.com are taking pre-orders on names set to be released.
Other registries have already released their name collisions domains.
I gather that .archi, .bio, .wien and .quebec have already unblocked their collisions this week.
Donuts tells us it has no current plan for its first drops. Rightside, which runs Donuts’ back-end, is reportedly planning to drop names in a couple dozen gTLDs on the same date in January.
As we reported earlier this week, millions of names are due to be released over the coming months, due to the expiration of the 90-day “controlled interruption” phase that ICANN forced all new gTLD registries to implement.
By definition, name collision names already have seen traffic in the past and may do so again.

Google beaten to .dot for a paltry $700k

Dish DBS, a US satellite TV company, has beaten Google to the .dot new gTLD in an ICANN auction that fetched just $700,000.
It’s further proof, if any were needed, that you don’t need to have the big bucks to beat Google at auction.
Dish plans to use .dot as a single-registrant space, but unusually it’s not a dot-brand. According to its application, the company:

intends to utilize the .dot gTLD to create a restricted, exclusively-controlled online environment for customers and other business partners with the goal of further securing the collection and transmission of personal and other confidential data required for contracted services and other product-related activities.

Google had planned an open, anything-goes space.
.dot was the only new gTLD contention set to be resolved by ICANN last-resort auction this month. The other applicants scheduled for the November auctions all settled their contests privately.

“Cyberflight” rules coming to UDRP next July

It will soon be much harder for cybersquatters to take flight to another registrar when they’re hit with a UDRP complaint.
From July 31 next year, all ICANN-accredited registrars will be contractually obliged to lock domain names that are subject to a UDRP and trademark owners will no longer have to tip off the registrant they’re targeting.
Many major registrars lock domain names under UDRP review already, but there’s no uniformity across the industry, either in terms of what a lock entails or when it is implemented. Under the amended UDRP policy, a “lock” is now defined as:

a set of measures that a registrar applies to a domain name, which prevents at a minimum any modification to the registrant and registrar information by the Respondent, but does not affect the resolution of the domain name or the renewal of the domain name.

Registrars will have two business days from the time they’re notified about the UDRP to put the lock in place.
Before the lock is active, the registrants themselves will not be aware they’ve been targeted by a complaint — registrars are banned from telling them and complainants no longer have to send them a copy of the complaint.
If the complaint is dismissed or withdrawn, registrars have one business day to remove the lock.
Because these change reduce the 20-day response window, registrants will be able to request an additional four calendar days (to account for weekends, I assume) to file their responses and the request will be automatically granted by the UDRP provider.
The new policy was brought in to stop “cyberflight”, a relatively rare tactic whereby cybersquatters transfer their domains to a new registrar to avoid losing their domains.
The policy was approved by the Generic Names Supporting Organization in August last year and approved by the ICANN board a month later. Since then, ICANN staff has been working on implementation.
The time from the first GNSO preliminary issue report (May 27, 2011) to full implementation of the policy (July 31, 2015) will be 1,526 days.
You can read a redlined version of the UDRP rules here (pdf).