Loophole gives trademark owners unlimited Clearinghouse records
Trademark owners will be able to add potentially thousands of strings to the Trademark Clearinghouse due to a recently introduced loophole, it emerged last night.
ICANN recently said that it will allow mark holders to add up to 50 strings related to their trademarks to their TMCH records, if the strings have been abused in the past.
It was one of the controversial “strawman” proposals that ICANN decided to adopt earlier this month.
Companies would be able to get protection for “mark+keyword” strings, for example, if a UDRP decision or court ruling had previously found that the strings had been cybersquatted.
The 50-string cap appeared to have been picked rather arbitrarily, but it turns out it’s more-or-less irrelevant anyway.
ICANN confirmed on its webinar for new gTLD applicants last night that the limit is 50 additional strings per entry in the Clearinghouse, not 50 strings per trademarked string.
What this means is that a company that has registered its trademark in multiple jurisdictions will be able to get 50 extra strings for each of those marks it enters into the Clearinghouse.
If Apple had a registered mark for “Apple” in the US and a registered mark for “Apple” in Bolivia, it would be able to submit both to the Clearinghouse and get an additional 100 “apple+keyword” records.
If it had the mark registered in 100 countries, it could put up to 5,000 more strings in the Clearinghouse.
Each string could be used to generate Trademark Claims notices, but not to secure registrations during Sunrise periods.
The apparent loophole and its implications were raised by Reg Levy of Minds + Machines during last night’s ICANN call.
In practice, the number of additional strings mark holders would qualify for would be capped by the number of trademark jurisdictions in the world and/or the number of UDRP decisions they’d won.
Few companies have secured more than a few hundred domains at UDRP to date, meaning it won’t be too difficult for trademark owners to get Trademark Claims protection for basically any previously cybersquatted string.
ICANN to pay $2 million to keep Trademark Clearinghouse “free” for registrars
ICANN is putting its money where its mouth is when it comes to helping new gTLDs be successful, committing $2 million to keep Trademark Clearinghouse access “free” for registrars.
While TMCH pricing for trademark owners is now well-publicized, ICANN COO Akram Attalah last night revealed some of the fees for new gTLD registries and registrars.
Registries will have to pay a one-time fee of $5,000 per TLD to access the TMCH, he said.
That was reduced from $10,000 during talks with TMCH back-end provider IBM after ICANN promised to handle billing and administration, he said.
There’s also going to be a $0.30 fee for each domain that matches a TMCH record registered during Sunrise and Trademark Claims periods, he added. The specifics on this fee were a little fuzzy.
But registrars won’t have to pay a penny, it seems. Attalah said that ICANN will pay IBM $2 million to make sure the Clearinghouse is accessible and free for registrars.
“ICANN will pay $400,000 per year for five years to keep the TMCH up and running and that provides free access to all registrars,” he said on last night’s new gTLDs update webinar.
It won’t be completely free for registrars, of course.
Registrars will have to do some implementation work to support the new Trademark Claims and Sunrise specs, but the absence of fees gives them one less excuse to avoid the two rights protection periods.
ICANN to water down contract powers with “Public Interest Amendments”
ICANN has made a few tweaks to its proposed unilateral-right-to-amend powers in order to fend off open hostility from registries, registrars and new gTLD applicants.
The organization is set to announce “Public Interest Amendments”, a rebadged version of its hugely unpopular proposals for the Registry Agreement and Registrar Accreditation Agreement.
As previously reported, ICANN wants to be able to change both contracts in future, if there’s a “substantial and compelling need”, even if it does not have the majority support of the affected companies.
CEO Fadi Chehade has reportedly indicated that he won’t be budged on the need for some method for ICANN to make emergency changes to the contracts.
And during last night’s new gTLD applicants webinar, he made it clear that the RA and RAA will delay the launch of new gTLDs if registries and registrars cannot agree to ICANN’s terms.
But according to documentation seen by DI today — actually a flowchart of how the amendment process would work — these terms are going to be watered down, giving more power to commercial stakeholders.
Apart from the new Pubic Interest Amendment name, there appear to be three big changes.
First, there would be a way for registrars and/or registries to make a late-stage counter-proposal to the ICANN board if they didn’t like the look of a proposed amendment.
Second, any issues that fell within the so-called “picket fence” — the list of pre-agreed topics for which ICANN is allowed to make binding policy — would have to go into a formal GNSO Policy Development Process first.
Only if the PDP failed to reach consensus would the ICANN board of directors be able to step in and attempt to legislate unilaterally.
A practical effect of that would be to give contracted parties ample opportunity to delay amendments — possibly by years — that they weren’t happy with.
Third, PIAs would only cover changes designed to “ensure competition & consumer choice and promote consumer access to fair business practices” and explicitly “not to change ICANN fees, Consensus Policy Spec., or mechanism to change PIA process”.
This would prevent ICANN unilaterally amending the contract to make its amendment powers even stronger in future, which had been one criticism of the proposed process.
“The board’s ability to introduce an amendment is very tightly defined and limited in scope, so it’s only used in extreme cases and under very strict conditions,” Chehade said last night.
It appears — though I can’t be certain — that ICANN has also decided that the full board of directors, including those with identified conflicts of interest, would be able to participate in votes on PIAs.
That would mean registry and registrar representatives to the board would get to vote on amendments affecting their stakeholder groups.
Chehade is currently explaining all of this to a cautiously optimistic Registry Stakeholder Group on a conference call, and I believe more information is due to be published later this week.
ICANN: about 274 new gTLD objections filed
There have been roughly 274 formal objections against new gTLD applications, ICANN said last night.
During a webinar with applicants, new gTLD program manager Christine Willet broke down the numbers. There have been:
- 67 String Confusion Objections — these are of the “your TLD looks like my TLD” variety.
- 71 Legal Rights Objections — “Your TLD looks like my trademark”
- 23 Limited Public Interest Objections — “Your TLD infringes human rights”
- 113 Community Objections — “Your TLD screws over my community”
Willett stressed that the numbers are based on ICANN’s non-comprehensive insight and subject to a couple of caveats.
The number could be higher if ICANN was not copied in on some objections sent to arbitration panels, or lower if the panels throw some out for not passing baseline administrative checks.
Judging by the small number of objections to be revealed by the World Intellectual Property Organization — which is handling trademark disputes for ICANN — most LROs so far are applicant versus applicant.
The International Chamber of Commerce has not yet published any information about Community Objections or Limited Public Interest Objections.
The International Center for Dispute Resolution has only revealed one String Confusion Objection so far, which we reported on a couple weeks ago.
Tucows, Directi and Namecheap to combine .online gTLD bids
Three applicants for the .online gTLD appear to have settled their differences in what I believe is the first public example of new gTLD contention set consolidation.
Tucows, Directi and Namecheap said today that that they plan to “work together to manage the .online registry.” From the press release:
applicants for the same TLDs have begun to compete, negotiate, and, in some cases, join forces to ultimately produce one winning bid.
The first such alliance was revealed today, when domain industry veterans Directi, Tucows and Namecheap announced that they would work together to manage the .online registry.
The companies are of course three of the most successful domain name registrars out there.
The press release does not specify how the combination will be carried out. Under ICANN rules, two of the applicants would have to drop their applications. It’s not possible to resubmit as a joint venture.
It also does not acknowledge that there are three other applicants for .online — Donuts and smaller portfolio applicants Dot Online LLC and I-REGISTRY Ltd — which are not party to the agreement.
Chutzpah alert! “Tube” domainer objects to Google’s .tube gTLD bid
Remember the “mystery gTLD applicant” that had promised to campaign against Google’s closed generic gTLD applications?
It turns out the company behind the campaign is actually Latin American Telecom, one of the three applicants for .tube, and that part of its strategy is a Legal Rights Objection.
According to a copy of the LRO kindly provided to DI this week, LAT claims that if Google gets to run .tube it would harm its Tube brand, for which it has a US trademark.
If you haven’t heard of Latin American Telecom, it, despite the name, appears to be primarily a domainer play. Founded in Mexico and based in Pittsburgh, its main claim to fame seems to be owning Mexico.com.
The company says it has also been building a network of roughly 1,500 video sites, all of which have a generic word or phrase followed by “tube.com” in their domains, since 2008.
It owns, for example, the domains IsraelTube.com, MozartTube.com, LabradorTube.com, AmericanWaterSpanielTube.com, DeepSeaFishingTube.com… you get the idea.
They’re all cookie-cutter microsites that pull their video content from Vimeo. Most or all of them appear to be hosted on the same server.
I’d be surprised if some of LAT’s domains, such as BlockbusterTube.com, PlaymateTube.com, FortyNinersTube.com and NascarTube.com, didn’t have trademark issues of their own.
But LAT was also granted a US trademark for the word TUBE almost a year ago, following a 2008 application, which gives it a basis to bring an LRO against Google.
According to its LRO:
The proposed purposes of and registrant limitations proposed for .TUBE by Google demonstrate that the intended purpose of Google’s .TUBE acquisition is to deprive other potential registry operators of an opportunity to build gTLD platforms for competition and innovation that challenge YouTube’s Internet video dominance. It is clear that Google’s intended use for .TUBE is identical to Objector’s TUBE Domain Channels and directly competes with Objector’s pre-existing trademark rights
There’s quite a lot of chutzpah being deployed here.
Would LAT’s ramschackle collection of –tube domains have any meaning at all were YouTube not so phenomenally successful? Who’s leveraging whose brand here, really?
For LAT to win its objection it has to show, among other things, that its TUBE trademark is famous and that Google being awarded .tube would impair its brand in some way.
But the company’s LRO is vague when it come to answering “Whether and to what extent there is recognition in the relevant sector of the public of the sign corresponding to the gTLD”.
It relies surprisingly heavily on its Twitter accounts — which have fewer followers than, for example, DI — rather than usage of its web sites, to demonstrate the success of the TUBE brand.
I don’t think its objection to Google’s .tube application is a sure thing by any stretch of the imagination.
There is a third .tube gTLD applicant, Donuts, but it has not yet received any LROs, according to WIPO’s web site.
Neustar leading the new gTLD back-end scores so far
New gTLD applications backed by registry service provider Neustar scored the highest results in the first batch of Initial Evaluation results.
All 27 of the applications that have had their IE results revealed by ICANN so far have easily passed the 22 out of 30 points threshold required for a passing score on the technical evaluation.
In most cases, each application had its technical questions answered by the applicant’s chosen back-end provider.
Eight different back-ends are involved in the first 27 bids, some with more applications than others.
Here’s the average score out of 30 for each company.
[table id=12 /]
Only Neustar and Verisign scored the full 30 points in an application with their name on it, but their averages were reduced by applications in which they fared less well.
It’s very early days, of course, with the full set of IE results not due to be completely published until August.
We’ll be tracking these scores as more results are released on DI PRO.
Chehade to play hard-ball over unilateral right to amend?
ICANN CEO Fadi Chehade has reportedly indicated that the unilateral right to amend powers ICANN wants to put in its registry and registrar contracts are non-negotiable.
Speaking at a meeting of the Association of National Advertisers last week, Chehade is reported to have said: “I’m not going to back off this one.”
He is understood to have been referring to the changes ICANN wants to impose on the base new gTLD Registry Agreement and the Registrar Accreditation Agreement.
Amy Bivins of Bloomberg BNA’s Electronic Commerce & Law Report caught the speech live and tweeted the following:
Chehade quotes on RAA: “I cannot live with a perpetual agreement,” and “I’m not going to back off this one.”
— Amy E. Bivins (@AmyEBivins) March 20, 2013
Bivins’ full report is available behind BNA’s paywall.
The unilateral right to amend is just about the most controversial thing ICANN has proposed in a while.
It would give ICANN’s board of directors the power to make changes to both agreements in situations where registrars or registries cannot agree among themselves to a “special amendment” but there’s agreement by other community members that the change is required.
Registries and registrars argue that a contract in which one party has the power to change the agreement without the consent of the other is not really a contract at all.
But ICANN says the powers are needed, partly to redress existing imbalances: the fact that the RAA and RA both last for 10 years and that the RA has a presumptive right of renewal.
Without the right to change the RA over the protests of the registries, it’s possible that in future proposed changes could be vetoed by registries whose interests are not aligned with the “public interest”, ICANN argues.
ICANN says that it’s impossible to know how consolidation, future new gTLD rounds and power shifts in the ICANN community will affect the balance of power, meaning it needs a way to resist a registry choke-hold should the situation arise.
I suspect the fact that it’s taken about three years to get close to adding the recommendations of law enforcement relating to registrar conduct to the RAA may also have something to do with it.
Five interesting nuggets from the first batch of gTLD evaluations
ICANN gave many in the industry cause for celebration on Friday when it released its first batch of 27 new gTLD applications that have passed Initial Evaluation.
The plan is to release 30 per week, ramping up to 100 at some point in future, but three applications in the first 30 still have change requests or clarifying questions being processed.
Here are some interesting bits of information we’ve gleaned from the first batch.
Donuts has passed its background checks
Donuts has had the first of its new gTLD applications approved. This means that the evaluation team doing background screening found no reason to be fail the company due to its executives’ track records.
During the public comment period last year, Donuts’ opponents said the company should be barred from getting any new gTLDs because of its close ties to Demand Media, a company with a record of adverse UDRP decisions.
It was also claimed that a Donuts director was involved in cybersquatting the Olympic and Disney brands, but it turned out the director in question had left the company in late 2011.
But ICANN’s evaluation team appears to have given Donuts the all clear.
The Donuts application that has passed Initial Evaluation, for .商店 (shop/store), is one of 199 applications, each filed by unique corporate shells, that share a parent, Dozen Donuts LLC.
The balance of Donuts’ applying companies are owned by Covered TLD LLC, believed to be its joint venture with Demand Media. All 307 are signed up to use Demand Media’s registry back-end.
Seven IDN scripts passed IE
New gTLDs in seven internationalized domain name scripts — Chinese, Arabic, Japanese, Hindi, Korean, German, Cyrillic — have passed through Initial Evaluation.
Transliterations of .com/.net are apparently fine
Some of Verisign’s applications for transliterations of .com and .net in scripts such as Chinese and Hindi have passed IE, meaning the evaluators weren’t worried about possible clashes with their legacy equivalents.
There’s been some concern from some parts of the world that because the applied-for strings are meaningless in the relevant languages, but sound like “com” and “net” when spoken, that it could cause confusion.
New back-end providers have cause for celebration
While there was little doubt that back-end providers Verisign, Neustar, Afilias and CORE would receive passing grades by ICANN — they all run gTLDs already — new market entrants did not have reasons for the same confidence.
However, ARI Registry Services, Demand Media, CentralNIC, KISA, KSRegistry and KNET are all named back-ends for passing applications in the first batch.
This should come as a cause for celebration for these companies, and a relief for their clients.
Because many applications used the same boilerplate back-end text, there’s good reason to believe that other bids using these registry providers are likely to pass the technical portion of Initial Evaluation too.
Afilias doesn’t have any passes yet
Top-three player Afilias, so far, does not have any passing apps.
One of its clients is at position #7 in the priority queue, but it’s one of the three applications in the top 30 to be still chasing follow-up questions or change requests with ICANN.
Probably nothing to worry about here.
Trademark Clearinghouse lowers prices
The Deloitte-managed Trademark Clearinghouse has slashed its bulk submission prices in response to feedback from registrars.
A newly revised TMCH price list leaves the basic fees of $145 to $95 per mark per year untouched, but makes it much easier for large trademark owners and brand protection companies to qualify for discounts.
The system for securing bulk discounts is based on “Status Points” that accumulate as trademarks are submitted, with five pricing tiers available.
The changes mean submission agents need to rack up 1,000 points in order to become eligible for the first discount tier, instead of 3,000. The cheapest tier is accessible at 90,000 points instead of 100,000.
The TMCH has also doubled the number of bonus points awarded for submitting trademarks during the “early bird” phase, which runs until the first new gTLD sunrise period begins, making it easier to hit discount milestones.
According to the Trademark Clearinghouse Cost Calculator, which has been updated with the new numbers, savings could be substantial.
For example, a submission agent that submits 10,000 marks for five-year registrations during the early bird period will pay $5,232,125, which is $742,950 cheaper than under the old pricing scheme.
That would be an average cost of $104.64 per mark per year, compared to $119.50 under the old regime.
A listing in the TMCH is a prerequisite if a trademark owner wants to participate in new gTLD sunrise periods or take advantage of the Trademark Claims cybersquatting alert service.
We gather that the price reductions came largely as a result of feedback from registrars that plan to act as submission agents, rather than from trademark owners themselves.
Recent Comments