Porn firm wins .cam after years of objections

The controversial new gTLD .cam has been won at auction by Dutch porn site operator AC Webconnecting, putting an end to over two years of back-and-forth objections.
Rival applicants Rightside and Famous Four Media both withdrew their applications earlier this week.
The contest for .cam was marked by several objections and appeals.
In 2013, Verisign filed and lost String Confusion Objections against AC Webconnecting and Famous Four, but won its near-identical objection against Rightside.
Verisign had claimed that .cam and .com are so similar-looking that confusion among internet users is bound to arise.
Because the SCO panels in the three cases returned differing opinions, Rightside was one of two applicants given the right to appeal by ICANN in October 2014.
I never quite understood why Verisign wasn’t also given the right to appeal.
Rightside won the right to stay in the .cam contention set almost a year later.
Despite all that effort, it did not prevail in the resulting auction.
Separately, back in 2013, AC Webconnecting filed and lost Legal Rights Objections against its two rivals, based on a “.cam” trademark it acquired purely for the purpose of fighting off new gTLD competitors.
I’d be lying if I said I knew a lot about the soon-to-be registry.
Based in Rotterdam, its web site comes across as a wholly safe-for-work web design firm.
However, it seems to be mainly in the business of operating scores, if not hundreds, of webcam-based porn sites.
Its application for .cam states that it will be for everyone with an interest in photography, however.
When it goes live, its most direct competitor is likely to be Famous Four’s .webcam, which already has an 18-month and 70,000-domain head start.
It remains to be seen whether its clear similarity to .com will in fact cause significant confusion.

.shop among four gTLDs heading to auction

The new gTLDs .shop, .shopping, .cam and .phone are all set to go to auction after their various delays and objections were cleared up.
It seems that .shop and .shopping contention sets remain merged, so only one string from one applicant will emerge victorious.
That’s due to a completely mad String Confusion Objection decision that ruled the two words are too confusingly similar to coexist in the DNS.
That SCO ruling was made by the same guy who held up both sets of applications when he ruled that .shop and .通販 (“.onlineshopping”) were also too confusingly similar.
The two rulings combined linked the contention sets for all three strings.
.通販 applicant Amazon appealed its SCO loss using a special process that ICANN created especially for the occasion, and won.
But .shop and .shopping applicants were not given the same right to appeal, meaning the auction will take place between nine .shop applicants and .shopping applicants Uniregistry and Donuts.
Donuts is an applicant for .shop and .shopping, meaning it will have to make its mind up which string it prefers, if it intends to win the auction.
If it’s a private auction, Donuts would presumably qualify for a share of its own winning bid. Weird.
(UPDATE: That was incorrect).
The other contention set held up by an inconsistent SCO decision was .cam, which was originally ruled too similar to .com.
Rightside won its appeal too, meaning it will be fought at auction between Famous Four, Rightside and AC Webconnecting.
.phone had been held up for different reasons.
It’s a two-way fight between Donuts and Dish DBS, a TV company that wanted to run .phone as a closed generic. Like almost all closed generic applicants, Dish has since changed its plans.

.cam given the nod as Rightside wins confusion appeal

Rightside’s application for .cam will be un-rejected after the company beat Verisign in an appeal against a 2013 String Confusion Objection decision.
That’s right, .cam is officially no longer too confusingly similar to .com.
In a just-published August 26 decision (pdf) a three-person International Centre for Dispute Resolution panel overruled the original SCO panelist’s decision.
The new panel wrote:

Based on the average, reasonable Internet’s user’s experience, and the importance of search engines, in the [Final Review Panel]’s view, confusion, if any, between .COM and .CAM is highly likely to be fleeting. While a fleeting association may create some “possibility of confusion” or evoke an “association in the sense that the string brings another string to mind,” both such reactions are insufficient under the ICANN SCO standard to support a finding that confusion is probable.

It’s not quite as clear-cut a ruling as the .shop versus .通販 ruling last week, relying on the appeals panel essentially just disagreeing with some of the finer points of the original panel’s interpretation of the evidence.
Relating to one piece of evidence, the appeals panel found that the original panelist “improperly shifted the burden of proof” to Rightside to show that .cam was intended for camera-related uses.
Rightside was one of two applicants given the opportunity to appeal its SCO decision by ICANN last year, largely because two other .cam applicants managed to pass their Verisign objections with flying colors, creating obvious inconsistency.
Taryn Naidu, Rightside’s CEO, said in a statement:

We always felt strongly that the first panel’s decision was seriously flawed. How can .CAM in one application be different from the .CAM in another application when evaluated on the basis of string similarity? The fact is, it can’t.

It’s always struck me as unfair that Verisign did not get the chance to appeal the two SCOs it lost, given that the panelist in both cases was the same guy using the same thought processes.
The question now is: is the appeals panel correct?
I suppose we’ll find out after .cam goes on sale and unscrupulous domainers attempt to sell .cam names for inflated prices, hoping their would-be buyers don’t notice the difference.
The other two .cam applicants are AC Webconnecting and Famous Four Media. All three will now go to auction.

Two new gTLD confusion decisions thrown out

ICANN has reopened the contention sets for .cam and .通販 after deciding that two String Confusion Objection panels may have been wrong to reject certain applications.
Two rulings — that .cam is confusingly similar to .com and that .通販 is confusingly similar to .shop (really) — will now head to an appeals panel for a “final” determination.
The decision was made by the ICANN board’s New gTLD Program Committee this week at the ICANN 51 public meeting in Los Angeles.
The first case being reopened for scrutiny is Verisign versus Rightside, where the original SCO panel found that .cam and .com were too similar to coexist on the internet.
But a different panelist found that the two strings were not confusingly similar in objections filed by Verisign against two other applicants — Dot Agency and AC Webconnecting.
The opposing rulings meant that Rightside’s application would have been kicked out of the .cam contention set, which hardly seems fair.
This and many other “perceived inconsistencies” led to the ICANN board being pressured to come up with some kind of appeals process, which it agreed to do in February.
Verisign, unfairly in my view, was not given the opportunity to appeal the two .cam decisions that went against it, even though they were made by the same panelist for the same reasons.
The second, altogether more peculiar, case was .shop applicant Commercial Connect versus .通販 applicant Amazon.
The panelist in that case seemed to have checked his brain at the door that day, concluding that the two strings are confusingly similar simply because 通販 means “online shopping” in Japanese.
Another panelist, in a different case also involving Commercial Connect, had found that .购物 (Chinese for “shopping”) was not confusingly similar to .shop because duh.
ICANN’s NGPC has now decided that the two controversial decisions are “not being in the best interest of the New gTLD Program and the Internet community”.
Both .cam and .通販 will now be referred to a three-person panel at the International Center for Dispute Resolution, the same body that processed the original objections, for a final determination.

ICANN reveals gTLD objections appeals process

Two new gTLD applicants would get the opportunity to formally appeal String Confusion Objection decisions that went against them, under plans laid out by ICANN today.
DERCars and United TLD (Rightside), which lost SCOs for their .cars and .cam applications respectively, would be the only parties able to appeal “inconsistent” objection rulings.
DERCars was told that its .cars was too similar to Google’s .car, forcing the two bids into a contention set. But Google lost similar SCO cases against two other .cars applicants.
Likewise, Rightside’s .cam application was killed off by a Verisign SCO that stated .cam and .com were too similar, despite two other .cam applicants prevailing in virtually identical cases.
Now ICANN plans to give both losing applicants the right to appeal these decisions to a three-person panel of “Last Resort” operated by the International Centre for Dispute Resolution.
ICDR was the body overseeing the original SCO process too.
Notably, ICANN’s new plan would not give Verisign and Google the right to appeal the two .cars/.cam cases they lost.

Only the applicant for the application that was objected to in the underlying SCO and lost (“Losing Applicant”) would have the option of whether to have the Expert Determination from that SCO reviewed.

There seems to be a presumption by ICANN already that what you might call the “minority” decision — ie, the one decision that disagreed with the other two — was the inconsistent one.
I wonder if that’s fair on Verisign.
Verisign lost two .cam SCO cases but won one, and only the one it won is open for appeal. But the two cases it lost were both decided by the same ICDR panelist, Murray Lorne Smith, on the same grounds. The decisions on .cam were really more 50-50 than they look.
According to the ICANN plan, there are two ways an appeal could go: the panel could decide that the original ruling should be reversed, or not. The standard of the review is:

Could the Expert Panel have reasonably come to the decision reached on the underlying SCO through an appropriate application of the standard of review as set forth in the Applicant Guidebook and procedural rules?

The appeals panelists would basically be asked to decide whether the original panelists are competent or not.
If the rulings were not reversed, the inconsistency would remain in place, making the contention sets for .car, .cars and .cam stay rather confusing.
ICANN said it would pay the appeals panel’s costs.
The plan (pdf) is now open for public comment.

Conflicting gTLD objection decisions to get appeals process?

ICANN seems to be considering an appeals process for new gTLD applicants that feel they’ve been wronged by dubious String Confusion Objection decisions.
But the process might be limited to applicants for .car, .cars and .cam.
In a resolution this Wednesday, ICANN’s New gTLD Program Committee said:

the NGPC is considering potential paths forward to address the perceived inconsistent Expert Determinations from the New gTLD Program String Confusion Objections process, including implementing a review mechanism. The review will be limited to the String Confusion Objection Expert Determinations for .CAR/.CARS and .CAM/.COM.

Why only those strings? I’m guessing it’s because the conflicting decisions would make for extremely confusing contention sets.
There were three SCOs against .cars applications, filed by Google, which has applied for .car. Google won one case but lost the other two.
That would mean that Google’s .car application would be in contention with one of the applicants but not the other two, hardly a fair outcome.
Similarly, Verisign objected to five .cam applications due to their similarity to .com. It won one and lost the other four.
The NGPC resolution calls for the publication, for comment, of a reviews process designed to untangle this mess. It does not appear to have been published yet.
But it seems that whatever ICANN has come up with will not apply to other applicants who feel they’ve been wronged by odd SCO, or other objection, decisions.

Famous Four says that Demand Media’s .cam should be rejected

Demand Media’s application for .cam should be rejected because it lost a String Confusion Objection filed by .com registry Verisign, according to rival applicant Famous Four Media.
“The process in the applicant guidebook is now clear: AC Webconnecting and dot Agency Limited proceed to resolve the contention set, and United TLD’s application cannot proceed,” chief legal officer Peter Young told DI.
dot Agency is Famous Four’s applicant for .cam, which along with AC Webconnecting survived identical challenges filed by Verisign. United TLD is the applicant subsidiary of Demand Media.
Serious questions were raised about the SCO process after two International Centre for Dispute Resolution panelists reached opposition conclusions in the three .cam/.com cases last month.
Demand Media subsequently called for an ICANN investigation into the process, with vice president Statton Hammock writing:

String confusion objections are meant to be applicant agnostic and have nothing to do with the registration or use of the new gTLD.

However, Famous Four thinks it has found a gotcha in a letter (pdf) written by a lawyer representing Demand which opposed consolidation of the three .cam cases, which stated:

Consolidation has the potential to prejudice the Applicants if all Applicants’ arguments are evaluated collectively, without regard to each Applicant’s unique plan for the .cam gTLD and their arguments articulating why such plans would not cause confusion.

In other words, Demand argued that the proposed usage of the TLD should be taken into account before the ICDR panel ruled against it, and now it saying usage should not have been taken into account.
Famous Four’s Young said:

Whether or not one ascribes to the view that usage should not be taken into account, and we believe that it should (otherwise we would not have argued it), the fact is that United TLD were very explicit prior to the publication that usage should indeed be taken into account.

The SCO debate expanded yesterday when the GNSO Council spent some time discussing .cam and other SCO discrepancies during its regular monthly meeting.
Concerns are such that the Council intends to inform the ICANN board of directors and its New gTLD Program Committee that it is looking into the issue.
The NGPC, has “Update on String Similarity” on its agenda for a meeting on Tuesday, which will no doubt try to figure out what, if anything, needs to be done.

String confusion in disarray as Demand’s .cam loses against Verisign’s .com

Demand Media is demanding an ICANN review of its objections policy, after its applied-for new gTLD .cam was beaten in a String Confusion Objection by .com registry Verisign.
A International Centre for Dispute Resolution panelist has ruled (pdf) that .cam and .com are too confusingly similar to coexist, meaning Demand’s bid for .cam must be rejected by ICANN.
But the ruling by Urs Laeuchli conflicts with two other ICDR panel decisions on .cam, which both found that the string is NOT confusingly similar to .com and therefore can be delegated.
So while Demand’s .cam bid, under a strict reading of the rules, is now supposed to be rejected, applications for identical strings filed by AC Webhosting and dotAgency can go ahead.
ICANN has been thrown a curve ball it is not yet fully prepared to deal with.
As Akram Atallah, president of ICANN’s Generic Domains Division, told DI last week, it’s possible that the policy or the implementation of that policy may need to be revisited by ICANN and the community.
United TLD, the Demand Media subsidiary that applied for .cam, is now calling for precisely that, with vice president of business and legal affairs Statton Hammock writing today:

String confusion objections are meant to be applicant agnostic and have nothing to do with the registration or use of the new gTLD. What matters in string confusion objections is whether a string is visually, aurally or, according to ICANN’s Applicant Guidebook, otherwise “so nearly resembles another that it is likely to deceive or cause confusion.” Individuals may disagree on whether .CAM and .COM are similarly confusing, but there can be no mistake that United TLD’s .CAM string, AC Webhosting’s .CAM string, and dotAgency Limited’s .CAM string are all identical. Either all three applications should move forward or none should move forward.

The .cam cases are not alone in presenting ICANN with SCO problems.
Last week, Donuts’ bid for .pets was ruled confusingly similar to Google’s .pet, despite previous ICDR cases finding that plurals and singulars are not too confusing to coexist.
Where the .cam panelists disagreed
While there were three .cam cases, two of them were decided by the same panelist. It seems that both panelists were provided with very similar sets of evidence in all three cases.
It’s relevant to note that neither panelist — unlike some of their colleagues in other cases — thought it was appropriate to apply trademark law such as the DuPont factors in their decisions.
They did, however, consider the expected use cases of .cam.
All three applicants take .cam as short for “webcam” or “camera” and would target registrants interested in those fields (a lot of the use will likely be pornographic — AC Webconnecting is a porn firm after all).
But all three applicants also want to run “open” gTLDs, with no registration restrictions.
ICDR panelist Murray Smith was in charge of both the AC Webconnecting and dotAgency cases. He addressed expected usage explicitly in dotAgency, and explained why:

It is not just the visual, phonetic and conceptual similarity between the words that must be taken into account. In my view the greater emphasis should be focused on the use of the disputed extensions in the context of modern Internet usage. It is this context that compels the conclusion that an average Internet user would not be confused and would know that a .com website is probably a commercial website while a .cam websites would be something more focused in a particular field.

In AC Webconnecting, he wrote:

I agree that a consumer would quickly realize that a .cam website is likely associated with photography or camera use and is different than a .com website in use generally by a myriad of commercial entities.

So he’s putting the “greater emphasis” on usage — a factor that is not explicitly mentioned in the Applicant Guidebook’s description of the SCO and which may quite often differ between applicants.
Right there, in Smith’s interpretation of his task, we have a reason why SCOs will produce different results for identical strings.
I find Smith’s thinking baffling for a couple of reasons.
First, “a consumer would quickly realize that a .cam website is likely associated with photography” seems to ignore the existence of a bazillion .com web sites that are also associated with photography.
When did “commercial entities” and “photography or camera use” become mutually exclusive? Is photographyblog.com not confusingly similar to photographyblog.cam?
Second, he ignores the fact that basically anyone will be able to register a .cam web site for basically any purpose. None of the applicants want to restrict the gTLD to camera-related stuff.
ICDR panelist Laeuchli, in the Demand Media .cam case, raised this precise point, saying:

“.com” and “.cam” would use the same channels appealing to a broad audience. Even though according to Applicant, its envisioned TLD will “likely appeal” to a specific audience, it plans to operate “.cam” as an open gTLD. This would lead to extensive overlap.

Panelist Smith has some other notions about confusion that seem to defy common sense. He wrote in the AC Webconnecting case:

The .com TLD is the most widely recognized string in the Internet world. No reasonable Internet user would fail to recognize the .com TLD. The very reputation of the .com name serves to limit the potential for an average Internet user to be confused by the proposed .cam TLD. It is indeed unlikely that an online consumer would confuse a .com website with a .cam website.

Does this not strike anyone else as bad thinking?
It seems to me to be a little like saying that it’s perfectly okay to market a brand of carbonated beverage called Cuke, because Coke is so famous that nobody could possibly be confused. I don’t know where the law stands on that issue, but I’m pretty sure Coke wouldn’t be happy about it.
There’s also some weirdness in Laeuchli’s decision in the Demand case.
He puts some weight on the similarity scores produced by the controversial Sword algorithm in his decision, but apparently without doing even the basic research. He writes in his findings:

No matter what the standards and purpose the ICANN SWORD algorithm includes, it has comparative value.
…
Since pairs such as “God” and “dog” (85%) reach similarity scores of 84% and higher, how much more similar would “cxm” and “cxm” be (x being replaced with a vowel)!

The answer is that, according to Sword, they’re less similar. Sword scores “cam” v “com” at 63%.
Laeuchli knows it’s 63%, because he makes reference to that fact in his summary of Verisign’s evidence. He doesn’t need to speculate about the number based on what “god” v “dog” scores (and if he did the “dog” v “god” query himself, why on earth didn’t he just query “com” v “cam” too?)
His finding that .cam and .com will cause probable confusion seems to be based largely on expert witness testimony provided by both Verisign and Demand, in which he found Verisign’s more persuasive.
This evidence seems to have largely comprised the opinions of linguists, examining mouth shapes and acoustic frequencies, and market research looking into internet user behavior. As none of it has been published, it’s difficult to judge which side had the better arguments.
But it’s undeniably about the similarity of the strings, rather than the proposed usage, which makes Demand Media’s statement today — that SCOs “are meant to be applicant agnostic and have nothing to do with the registration or use of the new gTLD” — quite confusing.
Demand lost its case based on the string similarity, whereas the other two applicants won theirs based on the usage.
Perhaps Demand senses that its .cam application will not be immediately rejected if ICANN reopens the debate about string similarity. If think it’s probably correct.

DotMusic loses LRO, and four other cases rejected

Constantine Roussos has lost his first Legal Rights Objection over the flagship .music gTLD.
The case, DotMusic v Charleston Road Registry (pdf) was actually thrown out on a technicality — DotMusic didn’t present any evidence to show that it was the owner of the trademarks in question.
But the WIPO panelist handling the case made it pretty clear that DotMusic wouldn’t have won on the merits anyway.
If any applicant can be said to have built a brand around a proposed generic-term gTLD, it’s Roussos. DotMusic has been promoting .music on social media an in the music industry for years.
The company also owns the string “music” in a number of second-tier TLDs such as .co, .biz and .fm.
It’s not a bogus, last-minute attempt to game the system, like the .home cases — filed using Roussos-acquired trademarks — that have been thrown out repeatedly over the last couple of weeks.
The panelist addressed this directly:

On the one hand, the Panel recognizes that there has been a real investment by the Objector and associated parties in the trademark registrations, domain name registrations, sponsorship and branding to create consumer recognition and goodwill entitled to protection. On the other hand, there is a circularity in the Objector’s position in that the rights upon which the Objector relies to defeat the application are to a certain extent conditional on the defeat of the Applicant and the Objector’s success in obtaining the <.music> gTLD string.

In other words, Catch-22.
The panelist decided that .music is generic, that Google’s proposed use of it is generic, and that obtaining a trademark on a gTLD should not be a legit way to exclude rival applicants for that gTLD.

One objective of the Objector has been to obtain precisely the type of competitive advantage (in this case in the application process for the <.music> gTLD string) that the doctrine of generic names is designed to prevent. However, as the Applicant proposes to use the <.music> gTLD string in a generic sense it is immune from this challenge.

On that basis, the LRO would have failed, had DotMusic managed to demonstrate standing to object in the first place.
Unfortunately, DotMusic didn’t present any evidence that it actually owned the trademarks in question, which were applied for by Roussos and assigned to his company CGR E-Commerce.
The objection failed on that basis.
Defender Security, which obtained trademarks on “.home” from Roussos, ran into the same problems proving ownership of the trademarks in its LROs on the .home gTLD.
Four other LROs were decided this week:
.mail (United States Postal Service v. GMO Registry)
The case (pdf) turned on whether USPS owns a trademark that exactly matches the applied-for string (it doesn’t) and whether the word “mail” should be considered generic (it is) rather than a source identifier (it isn’t).
It’s pretty much the same logic applied in the two previous .mail LROs.
.food (Scripps Networks Interactive v. Dot Food, LLC)
This is the first of two competitive LROs filed by Scripps — which runs TV stations including the Food Network — against its .food applicant rivals to be decided.
Scripps has a bunch of trademarks containing the word “food”, including a November 2011 registration in the US for “Food” alone, covering entertainment services.
The WIPO panelist found (pdf) that the trademark was legit, but decided that it was not enough to prevent Dot Food using the matching string as a gTLD.
The fact that rights protection mechanisms exist in the new gTLD program was key:

to the extent that registration and use of a particular second-level domain within the <.food> gTLD actually creates a likelihood of confusion, then Objector will have remedies available to it, including the established Uniform Domain Name Dispute Resolution Policy, the forthcoming Uniform Rapid Suspension System and relevant laws. The fact that such disputes at the second level may arise is inherent in ICANN’s new gTLD program and is not in the circumstances of this case sufficient to uphold the present legal rights objection.
Objector’s rights in the FOOD mark do not confer upon it the exclusive right to use of the word “food” in all circumstances, particularly where, as here, Applicant intends to use the <.food> gTLD in connection with the food industry. Such intended use of the word would appear to be only for its dictionary meaning and not because of Objector’s trademark rights.

.vip (i-Registry v. Charleston Road Registry)
It’s the second objection by .vip applicant to get thrown out. In this case the respondent was Google.
Like the first time, the WIPO panelist found that the i-Registry trademark had been obtained for the purposes of the new gTLD program and that Google’s use of it in its generic sense would not infringe its rights.
.cam (AC Webconnecting Holding v. Dot Agency)
The second and final LRO decision (pdf) in the .cam contention set.
AC Webconnecting, an operator of webcam-based porn sites, lost again on the grounds that it applied for its trademark just a month before ICANN opened up the new gTLD application window in January last year.
The company didn’t have time to, and produced no evidence to suggest that, it had used the trademark and built up goodwill around “.cam” in the normal course of business.
In other words, front-running doesn’t pay.