ICANN has proposed a new policy for its new top-level domain program that would make it harder for community-based TLDs to liberalize their registration policies after they launch.
The idea is to prevent a replay of the recent .jobs controversy, in which registry Employ Media substantially altered its business model after failing to sell enough .jobs domains.
Because the Applicant Guidebook gives “community” TLD applications an opportunity to avoid a potentially costly auction if their TLD is contested by multiple applicants, there’s a risk of gaming.
Under the current rules, a company could win a contested TLD without paying big bucks, by promising to restrict it to a narrowly defined community of registrants.
It could later attempt to change its rules via ICANN’s Registry Services Evaluation Process to broaden or limit its potential customer base, potentially harming others in the community.
I call these Trojan TLDs.
Employ Media, for example, restricted .jobs domains to the names of companies, but now has licensed thousands of geographical and vocational generic names to a partner, over the objections of major jobs search engines such as Monster.com.
Under ICANN’s proposed policies (pdf), community TLDs would still have to pass through the RSEP, but they’d also be subject to a review under the Community Priority Evaluation.
The CPE is already in the Guidebook. It will be used to score applications based on the strength of community support. To avoid an auction, you need to score 14 out of 16 points.
ICANN now suggests that the CPE criteria could also be used to evaluate what it calls a “Community gTLD Change proposal” made by a TLD registry post-launch.
The new score would be used to determine whether to accept or reject the change:
If the sum of all identified score changes for the first three CPE criteria is zero or positive, the recommendation would be to accept the proposal, regardless of any relevant opposition identified. If the sum is minus one, the recommendation would be to accept the proposal, unless there is relevant opposition from a group of non-negligible size, in which case the recommendation would be to reject the proposal. If the sum is minus two or lower, the recommendation would be to reject the proposal.
The ICANN board would be able to deviate from the CPE recommendation, as long as it stated its reasons for doing so, and the registry would have the right to appeal that decision under the existing Reconsideration Request process.
These rules would apply to all new TLDs that designate themselves as community-based, apparently regardless of whether they successfully passed the CPE during the application process.
The rules are presented as a “discussion draft”, but I don’t think they’re going to be opened to official public comment.