Rules proposed for the new Trademark Clearinghouse threaten to cut off some of new gTLD registries major sources of early revenue, according to registry providers.
Premium domain sales and founders programs are among the now industry-standard practices that would be essentially banned under the current draft of the TMCH rules, they say.
The potential problems emerged in a draft TMCH Requirements document circulated to registries 10 days ago and vigorously discussed during a session at the ICANN meeting in Beijing last week.
The document lists all of the things that new gTLD registries must and must not, and may and may not, do during the mandatory Sunrise and Trademark Claims rights protection launch periods.
One of the bits that has left registries confused is this:
2.2.4 Registry Operator MUST NOT allow a domain name to be reserved or registered to a registrant who is not a Sunrise-Eligible Rights Holder prior to the conclusion of the Sunrise Period.
What this means is that trademark owners get first dibs on pretty much every possible string in every gTLD.
“Trademark owners trump everything,” Neustar business affairs veep Jeff Neuman said during the Beijing meeting. “Trademark owners trump every possible use of every possible name.”
It would mean, for example, that if a new gTLD wanted to allocate some names to high-profile anchor tenants during a “founders program”, it would not be able to do so until after the Sunrise was over.
Let’s say the successful applicant for .shop wants to reserve the names of hundreds of shop types (book.shop, food.shop, etc) as premium names, to allocate during its founders program or auction later.
Because the .shop Sunrise would have to happen first, the companies that the own rights to, for example, “wallpaper” or “butcher” (both real US trademarks) would have first rights to wallpaper.shop and butcher.shop, even if they only planned to defensively park the domains.
Because there’s likely to be some degree of gaming (there’s a proof-of-use requirement, but the passing threshold is pretty low), registries’ premium lists could be decimated during Sunrise periods.
If ICANN keeps its TMCH Requirements as they are currently written, new gTLD registries stand to lose a lot of early revenue, not to mention control over launch marketing initiatives.
However, if ICANN were to remove this rule, it might give unscrupulous registries the ability to circumvent the mandatory Sunrise period entirely by placing millions of strings on their premium lists.
“Registries should have discretion to schedule their start-up phases according to their business plans so long as rights protection processes are honored, so that’s the balancing we’ve tried to do,” ICANN operations & policy research director Karen Lenz said during Beijing.
“It’s trying to allow registries to create requirements that suit their purposes, without being able to hollow out the rights protection intention,” she said.
The requirements document is still just a draft, and discussions are ongoing, she added.
“It’s certainly not our intention to restrict business models,” Lenz said.
Registries will get some flexibility to restrict Sunrise to certain registrants. For example, they’ll be able to disqualify those without an affiliation to the industry to which the gTLD is targeted.
What they won’t be able to do is create arbitrary rules unrelated to the purpose of the TLD, or apply one set of rules during Sunrise and another during the first 90 days of general availability.
The standard Registry Agreement that ICANN expects all new gTLDs to sign up to does enable registries to reserve or block as many names as they want, but only if those names are not registered or used.
It seemed to be designed to do things like blocing ‘sensitive’ strings, rather like when ICM Registry reserved thousands of names of celebrities and cultural terms in .xxx.
The Requirements document, on the other hand, seems to allow these names being released at a later date. If they were released, the document states, they’d have to be subject to Trademark Claims notices, but not Sunrise rules.
While that may be a workaround to the premium domains problem, it doesn’t appear to help registries that want to get founders programs done before general availability.
It seems that there are still many outstanding issues surrounding the Trademark Clearinghouse — many more than discussed in this post — that will need to be settled before new gTLDs are going to feel comfortable launching.
ICANN has decided to call off its big New York City new gTLD launch “party”, DI has learned.
The high-profile media event, scheduled for April 23, was set to feature an appearance from mayor Michael Bloomberg and was expected to be a coming-out party for new gTLDs.
The original plan was for ICANN to sign the first registry agreements with new gTLD applicants during the event, but that notion was later scrapped due to ongoing contract talks.
However, during the public forum at the ICANN Beijing meeting last week, CEO Fadi Chehade said that the event was still going ahead.
That, according to an ICANN email sent to registries and registrars today, appears to be no longer the case. The email cited “current timelines” as the reason for delaying the event.
The Registry Agreement and Registrar Accreditation Agreement still under discussion between ICANN and contracted parties, and there are other factors in play such as the Governmental Advisory Committee’s wide-ranging advice from Beijing and continued uncertainties about the Trademark Clearinghouse.
With so much up in the air, a public awareness-raising event for the program may have been seen as premature.
A second, private set of meetings between ICANN and domain name companies, also scheduled for April 23 in New York, is still going ahead, according to the ICANN email.
Following on from discussions held over the last few months, the New York talks will focus on improving the image and professionalism of the domain name industry, one of Chehade’s pet projects.
Talks will cover items such as: forming a DNS industry trade association, a possible trust-mark scheme, conferences and media/analyst outreach.
Governments may want new gTLD registries to become the internet’s police force, but ICANN doesn’t have to take it lying down.
ICANN is set to open up the shock Beijing communique to public comments, CEO Fadi Chehade said Friday, while chair Steve Crocker has already raised the possibility of not following the GAC’s advice.
“Advice from governments carries quite a bit of weight and equally it is not the end of the story,” Crocker said in a post-meeting interview with ICANN PR Brad White.
“We have a carefully constructed multi-stakeholder process,” he said. “We want very much to listen to governments, and we also want to make sure there’s a balance.”
The ICANN bylaws, he reminded us, give ICANN “a preference towards following advice from the GAC, but not an absolute requirement.”
That’s a reference the the part of the bylaws that enables ICANN’s board to overrule GAC advice, as long as it carries out consultation and provides sound reasoning.
It was invoked once before, when ICANN tried to get a handle on the GAC’s concerns about .xxx in 2011.
In this case, I’d be very surprised indeed if the GAC’s advice out of Beijing does not wind up in this bylaws process, if only because the document appears to be internally contradictory in parts.
It’s also vague and broad enough in parts that ICANN is going to need much more detail if it hopes to even begin to implement it.
It looks like at least 517 new gTLD applications will be affected by the GAC’s advice, but in the vast majority of cases it’s not clear what applicants are expected to do about it.
The first part of dissecting the Beijing communique will be a public comment period, Chehade said during the interview Friday. He said:
The community wishes to participate in the discussion about the GAC communique. So, alongside the staff analysis that is starting right now on the GAC communique we have decided to put the GAC communique out for public comment, soliciting the entire community to give us their input to ensure that the GAC communique is taken seriously but also encompasses our response, encompasses the views of the whole community.
Watch the full video below.
The launch window for new gTLDs may have just got pushed back another month or two, following the announcement of a new 42-day comment period on registry and registrar contracts.
But ICANN CEO Fadi Chehade said he’s looking at ways to streamline the process to offset the delays.
During the public forum in Beijing yesterday, ICANN CEO Fadi Chehade said that he’d cancelled a scheduled April 20 meeting of its board of directors, during which the new agreements were targeted for approval.
Instead, new versions of the 2013 Registrar Accreditation Agreement and new gTLDs base Registry Agreement will be posted for public comment next week.
As these are expected to be the final versions of both documents, they’re also expected to have full comment periods of 42 days — 21 for comments and 21 for replies.
“I believe that putting the last version of RAA for 2013 out for full public comment process is actually strengthening that agreement,” Chedhade said today. “It makes it an agreement of the community.”
For the Registry Agreement, Chehade said talks with registries are going well and that he hopes to have a version ready for public comment agreed with negotiators in less than a week.
Assuming an April 19 start, that puts the earliest possible date for ICANN board approval at May 31, assuming the board waits for the comment period to end before giving it the rubber stamp.
Before the contracts are approved, they can’t be signed by registries and registrars, and before they are signed new gTLD applicants cannot progress to the final pre-launch stages of the delegation process.
But Chehade is weighing an idea put forward during the public forum by Donuts’ Jon Nevett: why not allow applicants to complete pre-delegation technical testing before contract signing?
“We could potentially do something about advancing this step ahead of contracting, finding a way to start pre-delegation testing before contracting is done,” Chehade said.
ICANN’s Governmental Advisory Committee has issued the kiss of death to two new gTLD applications and sweeping advice that will delay many, many more.
First, the GAC said that the .africa bid filed by DotConnectAfrica and the .gcc bid filed by GCCIX WLL should be rejected. Those were full consensus objections.
Two gTLDs related to Islam: .islam and .halal, have non-consensus objections, and will now have to be considered by the ICANN board of directors directly.
The GAC also said it needed more time, until ICANN’s meeting in Durban this July, to consider delivering specific advice against 14 more:
the GAC advises the ICANN Board to: not proceed beyond Initial Evaluation with the following strings: .shenzhen (IDN in Chinese), .persiangulf, .guangzhou (IDN in Chinese), .amazon (and IDNs in Japanese and Chinese), .patagonia, .date, .spa, .yun, .thai, .zulu, .wine, .vin
On the issue of plurals versus singulars, the GAC said ICANN should “Reconsider its decision to allow singular and plural versions of the same strings.” This affects about 60 applications.
But it doesn’t end there.
As predicted, the GAC has also issued swathes of advice against scores of proposed gTLDs in 12 categories: children, environmental, health and fitness, financial, gambling, charity, education, intellectual property, professional services, corporate identifiers, generic geographical terms and inherently governmental functions.
A “non-exhaustive” list of applications has been provided for each category, covering well over 100, setting the stage for a fight over inclusion for any application that the GAC forgot about.
If the GAC gets its way, any application that falls into one of these categories will have to have enhanced regulations governing Whois, abuse mitigation, and security.
The GAC also has its say on “closed generics”, which it calls “exclusive registry access” strings. They should only be awarded if they serve a public interest purpose, the GAC said.
In short, the advice is extraordinarily broad and seems to delegate the considerable work of picking through the mess to ICANN.
More analysis later…