The European Broadcasting Union plans to operate the forthcoming .radio gTLD in such a way as to discourage domain investors.
It yesterday set out its launch timetable, registration restrictions, and expects registrars to charge companies between €200 and €250 per domain per year ($213 to $266).
Interestingly, it’s also proposing to charge different, lower prices for individuals, though that pricing tier has not been disclosed.
I’m not sure I can think of another company that wants to charge different prices depending on the class of registrant and it seems like would be tough to enforce.
If I’m the domain manager at a radio company, can’t I just register the domain in my own name, rather than my employer’s, in order to secure the lower price?
Other registries, notably .sucks, have come under fire in the past for charging trademark owners higher fees. Isn’t basing pricing tiers on the legal status of the registrant pretty much the same thing?
That perception could be reinforced by the angle the EBU is taking in its marketing.
“We are proposing that the radio community may like to consider securing the integrity of their web presence by requesting appropriate .radio domains for defensive reasons initially,” .radio TLD Manager Alain Artero said in a blog post.
“The TLD will be focused on content and matters specific to radio and we want to prevent speculators and cybersquatting in this TLD,” he added.
The EBU is not planning to take the TLD to general availability until November, which is a long launch runway by any measure.
Before then, for two months starting May 3, there’ll be a qualified launch program in which radio stations (as opposed to “internet” radio stations) will be able to claim priority registration for their brand.
Sunrise will begin in August.
The EBU secured rights to .radio as a “Community” gTLD, meaning it has to enforce registration restrictions, after a 2014 Community Priority Evaluation ruling allowed it to win its contention set without an auction.
The eligibility criteria are somewhat broad, including: “Radio broadcasting stations. Unions of Broadcasters. Internet radios. Radio Amateurs. Radio professionals (journalists, radio hosts, DJs…) [and] Radio-related companies selling radio goods and services”.
GMO Registry and Radix have won Chinese government approval for their respective new gTLDs .shop and .site.
It’s the second batch of foreign new gTLDs to get the nod from China’s Ministry of Industry and Information Technology, following .vip, .club and .xyz in early December.
They’re also the first two Asian registries from outside China to get the right to flog their domains in China — GMO is Japanese and Radix is UAE-based with Indian roots.
Their new Chinese government licenses mean Chinese registrars will now be able to allow their customers to actually use .shop and .site domains to host web sites.
The registries in turn have had to agree to enforce China’s rather arbitrary and Draconian censorship policies on their Chinese customers.
The approvals were announced by MIIT December 29.
.site currently has about 570,000 domains in its zone file, making it a top-10 new gTLD by volume, while .shop, which launched much more recently, has over 100,000.
The ability for Chinese customers to develop their domains is no doubt good for the long-term health of TLDs, but it’s not necessarily a harbinger of shorter-term growth in a market where domains are often treated little more than meaningless baseball cards to be traded rather than commodities with intrinsic value.
ICANN’s Security and Stability Advisory Committee has told ICANN it needs to do more to address the problem of name collisions before it approves any more new gTLDs.
In its latest advisory (pdf), published just before Christmas, SSAC says ICANN is not doing enough to coordinate with other technical bodies that are asserting authority over “special use” TlDs.
The SAC090 paper appears to be an attempt to get ICANN to further formalize its relationship with the Internet Engineering Task Force as it pertains to reserved TLDs:
The SSAC recommends that the ICANN Board of Directors take appropriate steps to establish definitive and unambiguous criteria for determining whether or not a syntactically valid domain name label could be a top-level domain name in the global DNS.
Pursuant to its finding that lack of adequate coordination among the activities of different groups contributes to domain namespace instability, the SSAC recommends that the ICANN Board of Directors establish effective means of collaboration on these issues with relevant groups outside of ICANN, including the IETF.
The paper speaks to at least two ongoing debates.
First, should ICANN approve .home and .corp?
These two would-be gTLDs were applied for by multiple parties in 2012 but have been on hold since August 2013 following an independent report into name collisions.
Names collisions are generally cases in which ICANN delegates a TLD to the public DNS that is already broadly used on private networks. This clash can result in the leakage of private data.
.home and .corp are by a considerable margin the two strings most likely to be affected by this problem, with .mail also seeing substantial volume.
But in recent months .home and .corp applicants have started to put pressure on ICANN to resolve the issue and release their applications from limbo.
The second incident the SSAC paper speaks to is the reservation in 2015 of .onion
If you’re using a browser on the privacy-enhancing Tor network, .onion domains appear to you to work exactly the same as domains in any other gTLDs, but under the hood they don’t use the public ICANN-overseen DNS.
The IETF gave .onion status as a “Special Use Domain“, in order to prevent future collisions, which caused ICANN to give it the same restricted status as .example, .localhost and .test.
But there was quite a lot of hand-wringing within the IETF before this status was granted, with some worrying that the organization was stepping on ICANN’s authority.
The SSAC paper appears to be designed at least partially to encourage ICANN to figure out how much it should take its lead from the IETF in this respect. It asks:
The IETF is an example of a group outside of ICANN that maintains a list of “special use” names. What should ICANN’s response be to groups outside of ICANN that assert standing for their list of special names?
For members of the new gTLD industry, the SSAC paper may be of particular importance because it raises the possibility of delays to subsequent rounds of the program if ICANN does not spell out more formally how it handles special use TLDs.
“The SSAC recommends that ICANN complete this work before making any decision to add new TLD names to the global DNS,” it says.
Donuts has delayed the price increases coming to its trademark-blocking service and extended availability of the “plus” version for three more months.
Domain Protected Marks List Plus, which lets companies block brands and variations such as typos and brand+keywords across Donuts stable of 200ish TLDs, will now be available until March 31.
The price hike for vanilla DPML, which does not include the variant-blocking, has also been delayed until the end of January, the registry said.
Both deadlines were previously December 31.
DPML Plus, which grants 10-year blocks on one trademark and three variants in every Donuts TLD, has a recommended retail price of $9,999.
Retail prices for the plain DPML are reportedly going up from $2,500 per string to $4,400 for a five-year block at one registrar when the price rise kicks in. That’s a 76% increase.
Japanese conglomerate Mitsubishi has told ICANN it no longer wishes to operate one of its dot-brand gTLDs.
The company has filed a termination notice covering its .mtpc domain, which stands for Mitsubishi Tanabe Pharma Corporation.
The gTLD was delegated in February 2015, but Mitsubishi has never put it to use.
Registry reports show only two names ever appeared in the .mtpc space.
It’s the 19th gTLD from the 2012 round to voluntarily self-terminate — or to allow ICANN to terminate it — after signing a Registry Agreement.
All terminated gTLDs so far have been dot-brands.
Mitsubishi also owns .mitsubishi. That dot-brand appeared earlier this year but also has not yet been put to use.