Latest news of the domain name industry

Recent Posts

.cam given the nod as Rightside wins confusion appeal

Kevin Murphy, September 4, 2015, Domain Registries

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.

Did XYZ.com pay NetSol $3m to bloat .xyz?

Kevin Murphy, August 25, 2015, Domain Registries

Evidence of a possibly dodgy deal between XYZ.com and Network Solutions has emerged.

Court documents filed last week by Verisign suggest that the .xyz registry may have purchased $3 million in advertising in exchange for $3 million of .xyz domain names.

Verisign, which is suing .xyz and CEO Daniel Negari over its allegedly “false” advertising, submitted to the court a list of hundreds of exhibits (pdf) that it proposes to use at trial.

Among them are these two:

  • Email from Negari to Andrew Gorrin re EPP Feed and billing directly for $3,000,000 in domains
  • Credit Memo to Andrew from Negari “We have elected to pay for our $3MM Q2 advertising insertion order, which was dated May 20th with a credit…….” (5/31/14)

Gorrin is Web.com’s senior VP of marketing and Negari is Daniel Negari, XYZ.com’s CEO.

The documents these headings refer to are not public information, and are not likely to be any time soon, but they appear to refer to on the one hand XYZ billing NetSol for $3 million in domain names and on the other NetSol billing XYZ for $3 million in advertising.

Only one of the two document headings is dated, so we don’t know how closely they coincided.

Other headings, among the 446 documents Verisign wants to use at trial, suggest that they happened at pretty much the same time:

  • Email from Andrew Gorrin to Ashley Henning (web.com) re Bulk Purchase of .xyz domains (5/29/14)
  • Email from Andrew Gorrin to Negari re XYZ.Com Advertising IO and Marketing Agreement attaching signed agreements (5/20/14)
  • Email string Ashley Henning to Christine Nagey, Andrew Gorrin, Edward Angstadt re Bulk Purchase of .XYZ Domains (5/30/14)

The emails Verisign cites were dated May 2014, shortly before .xyz went into general availability June 2.

What we seem to be looking at here — and I’m getting into speculative territory here — are references to two more or less simultaneous transactions, both valued at exactly $3 million, between the two parties.

Both companies have consistently refused to address the nature of their deal, citing NDAs.

As you recall, the vast majority of .xyz’s early registrations were provided by NetSol, which pushed hundreds of thousands of free .xyz domains into its customers’ accounts without their explicit consent.

The number of freebies is believed to be about 350,000, based on comments Negari recently made to The Telegraph, in which he stated that .xyz, which had about 850,000 domains in its zone at the time, would have 500,000 registrations if the freebies were excluded.

With a registry fee roughly equivalent to .com’s (.xyz’s is believed to be a little lower), 350,000 names would work out to roughly $3 million.

Negari has stated previously that every .xyz registration was revenue-generating, even the freebies.

Is it possible that NetSol paid XYZ’s registry fees using money XYZ paid it for advertising? Is it possible no money changed hands at all?

I’m not saying either company has done anything illegal, and it’s completely possible I’m completely misunderstanding the situation, but it does rather put me in mind of the old “round-trip” deals that tech firms used to dishonestly prop up their tumbling revenue at the turn of the century.

Back in 2000, the dot-com bubble was on the verge of popping, taking the US economy with it, and companies facing the decline of their businesses came up with “creative” ways to show investors that they were still growing.

AOL Time Warner, for example, “effectively funded its own online advertising revenue by giving the counterparties the means to pay for advertising that they would not otherwise have purchased”.

Regulators exercised their legal options in these cases only where there appeared to be dishonest accounting, and I’ve seen no evidence to suggest that XYZ or Web.com unit NetSol have failed to adhere to anything but the highest accounting standards.

Again, I’m not saying we’re looking at a “round-trip” deal here, and there’s not a great deal of evidence to go on, but it sure smells familiar.

Certainly, questions have been raised that Verisign did not raise in its initial complaint.

Anyway.

On a personal note, I’d like to disclose that among the documents Verisign demanded from XYZ are dozens of pages of previously confidential emails exchanged between myself and Negari.

I’ve read them, and they’re mostly heated arguments about a) his refusal to give details about the NetSol deal and b) my purported lack of journalistic integrity whenever I published a post about .xyz with an even slightly negative angle.

XYZ had no choice but to supply these emails. I can’t blame it for complying with its legal requirements.

I wasn’t the only affected blogger. Mike Berkens, Konstantinos Zournas, Rick Schwartz and Morgan Linton also had their private correspondence compromised by Verisign.

I don’t know how they feel about this violation, but in my view this shows Verisign’s contempt for the media and its disregard for the sanctity of off-the-record conversations between reporters and their sources.

And that’s what I have to say about that.

US gives ICANN an extra year to complete transition

Kevin Murphy, August 18, 2015, Domain Policy

US government oversight of ICANN and the domain name system will end a year later than originally expected.

The National Telecommunications and Information Administration said last night that it has extended ICANN’s IANA contract until September 30, 2016, giving the community and others more time to complete and review the transition proposals.

NTIA assistant secretary Larry Strickling wrote that “it has become increasingly apparent over the last few months that the community needs time to complete its work, have the plan reviewed by the U.S. Government and then implement it if it is approved.”

Simultaneously, NTIA has finally published a proposal — written by ICANN and Verisign — for how management of the DNS root will move away from hands-on US involvement.

The extension of the IANA contract from its September 30, 2015 end date was not unexpected. The current contract allows for such extensions.

As we recently reported, outgoing ICANN CEO Fadi Chehade had guessed a mid-2016 finalization of the transition.

Regardless, expect op-eds in the coming days to claim this as some kind of political victory against the Obama administration.

Part of the reason for the extension, beyond the fact that the ICANN community hasn’t finished its work yet, is legislation proposed in the US.

The inappropriately named DOTCOM Act, passed by the House but frozen for political reasons in the Senate by Tea Party presidential hopeful Sen Ted Cruz, would give Congress 30 legislative days (which could equal months of real time) to review the IANA transition proposals.

There are basically three prongs to the transition, each with very long names.

The “Proposal to Transition the Stewardship of the Internet Assigned Numbers Authority (IANA) Functions from the U.S. Commerce Department’s National Telecommunications and Information Administration (NTIA) to the Global Multistakeholder Community” is the first.

That was created by the multistakeholder IANA Stewardship Transition Coordination Group (ICG) and deals with how the IANA contract will be managed after the US government goes away.

The second prong comes from the Cross Community Working Group on Enhancing ICANN Accountability, which deals with how ICANN itself can improve its accountability to the internet community without the Damoclean sword of US intervention hanging over it.

The CCWG’s latest draft report would strengthen the ICANN board against capture by, for example, making certain bylaws harder to amend and giving the community the right to fire directors.

Both of these proposals are currently open for public comment here.

The third prong, which only appears to have been published this week, deals with the nuts and bolts of how changes to the DNS root zone are made.

The current system is a tripartite arrangement between IANA, NTIA and Verisign.

When a TLD operator needs a change to the DNS root — for example adding a name server for its TLD — the request is submitted to and processed by IANA, sent to NTIA for authorization, then actually implemented on the primary root server by Verisign.

Under the new proposal (pdf) to phase the NTIA out of this arrangement, the NTIA’s “authorization” role would be temporarily complemented by a parallel “authentication” role.

The proposal is not written in the clearest English, even by ICANN standards, but it seems that the current Root Zone Management System would be duplicated in its entirety and every change request would have to be processed by both systems.

The output of both would be compared for discrepancies before Verisign actually made the changes to the root.

It seems that this model is only being proposed as a temporary measure, almost like a proof of concept to demonstrate that the NTIA’s current authorization role isn’t actually required and won’t be replaced in this brave new world.

IDN .com hits the root

Eleven variants of .com and .net in non-Latin scripts joined the internet today.

Verisign’s whole portfolio of internationalized domain name new gTLDs were added to the DNS root at some point in the last 24 hours, and the company is planning to start launching them before the end of the year.

But the company has been forced to backtrack on its plans to guarantee grandfathering to thousands of existing [idn].com domains in the new domains, thereby guaranteeing a backlash from IDN domainers.

The eleven gTLDs are: .कॉम, .ком, .点看, .คอม, .नेट, .닷컴, .大拿, .닷넷, .コム, .كوم and .קוֹם. Scripts include Arabic, Cyrillic and Hebrew.

Verisign signed registry agreements with ICANN back in January, but has been trying to negotiate a way to allow it to give the owners of [idn].com domains first rights to the matching domain in the “.com” in the appropriate script.

The company laid out its plans in 2013. The idea was to reduce the risk of confusion and minimize the need for defensive registrations.

So what happened? Trademark lawyers.

Verisign CEO Jim Bidzos told financial analysts last week that due to conversations with the “community” (read: the intellectual property lobby) and ICANN, it won’t be able grandfather all existing [idn].com registrants.

All of the new IDN gTLDs will be subject to a standard ICANN Sunrise period, which means trademarks owners will have first dibs on every string.

If you own водка.com, and somebody else owns a trademark on “водка”, the trademark owner will get the first chance to buy водка.ком.

According to SeekingAlpha’s transcript, Bidzos said:

Based primarily on feedback from domain name community stakeholders, we have revised our IDN launch strategy. We will offer these new IDN top-level domains as standalone domain names, subject to normal introductory availability and rights protection mechanisms, available to all new gTLDs. This revised approach will not require ICANN approval and is designed to provide end users and businesses with the greatest flexibility and, for registrars, a simple and straightforward framework to serve the market.

Finally, we believe this approach should provide the best opportunity for increased universal acceptance of IDNs. We expect to begin a phased rollout of the IDNs towards the end of this year, and we’ll provide more information on our launch plans when appropriate.

Senior VP Pat Kane added on the call that the grandfathering provisions, which would have required ICANN approval, have been “taken out”.

The question now is whether Verisign will introduce a post-sunrise mechanism to give rights to [idn].com.

That would not be unprecedented. ICM Registry ran into similar problems getting its grandfathering program for .porn approved by ICANN. It wound up offering a limited, secondary sunrise period for existing .xxx registrants instead.

Two more legacy gTLDs agree to use URS

The registries behind .pro and .cat have agreed to new ICANN contracts with changes that, among other things, would bring the Uniform Rapid Suspension policy to the two gTLDs.

Both gTLD Registry Agreements expire this year. Proposed replacement contracts, based heavily on the base New gTLD Registry Agreement, have been published by ICANN for public comment.

They’re the second and third pre-2012 gTLDs to agree to use URS, which gives trademark owners a simpler, cheaper way to have infringing domains yanked.

Two weeks ago, .travel agreed to the same changes, which drew criticisms from the organization that represents big domain investors.

Phil Corwin of the Internet Commerce Association is worried that ICANN is trying to make URS a de facto consensus policy and thereby bring it to .com, which is still where most domainers have most of their assets.

Following DI’s report about .travel, Corwin wrote last week:

this proposed Registry Agreement (RA) contains a provision through which staff is trying to preempt community discussion and decide a major policy issue through a contract with a private party. And that very big issue is whether Uniform Rapid Suspension (URS) should be a consensus policy applicable to all gTLDs, including incumbents like .Com and .Net.

ICANN needs to hear from the global Internet community, in significant volume, that imposing the URS on an incumbent gTLD is unacceptable because it would mean that ICANN staff, not the community, is determining that URS should be a consensus policy and thereby undermining the entire bottom-up policy process. Domain suspensions are serious business – in fact they were at the heart of the SOPA proposal that inspired millions of emails to the US Congress in opposition.

The concern about .com may be a bit over-stated.

Verisign’s current .com contract is presumptively renewed November 2018 provided that it adopts terms similar to those in place at the five next-largest gTLDs.

Given that .net is the second-largest gTLD, and that .net does not have URS, we’d have to either see .net’s volume plummet or at least five new gTLDs break through the 15 million domains mark in the next three years, both of which seem extraordinarily unlikely, for .com to be forced to adopt URS.

However, if URS has become an industry standard by then, political pressure could be brought to bear regardless.

Other changes to .pro and .cat contracts include a change in ICANN fees.

While .pro appears to have been on the standard new gTLD fee scheme since 2012, .cat is currently paying ICANN $1 per transaction.

Under the new contract, .cat would pay $0.25 per transaction instead, but its annual fixed fee would increase from $10,000 to $25,000.