Could ICANN reject Verisign’s $135m .web bid?

ICANN is looking into demands for it to throw out Verisign’s covert $135 million winning bid for the highly prized .web gTLD.
ICANN last week told the judge hearing Donuts’ .web-related lawsuit that it is “currently in the process of investigating certain of the issues raised” by Donuts through its “internal accountability mechanisms”.
Donuts is suing for $22.5 million, claiming ICANN should have forced Nu Dot Co to disclose that its .web bid was being secretly bankrolled by Verisign and alleging that the .com heavyweight used NDC as cover to avoid regulatory scrutiny.
ICANN’s latest filing (pdf), made jointly with Donuts, asked for an extension to October 26 of ICANN’s deadline to file a response to Donuts’ complaint.
It was granted, the second time the deadline has been extended, but the judge warned it was also the final time.
The referenced “internal accountability mechanism” would seem to mean the Cooperative Engagement Process — a low-formality bilateral negotiation — that Donuts and fellow .web bidder Radix initiated against ICANN August 2.
The filing states that the “resolution of certain issues in controversy may be aided by allowing [ICANN] to complete its investigation of [Donuts’] allegations prior to the filing of its responsive pleading.”
In other words, Donuts is either hopeful that ICANN may be able to resolve some of its complaints in the next month, or it’s not particularly impatient about the case progressing.
Meanwhile, fellow .web applicant Afilias has demanded for the second time that ICANN hand over .web to it, as the second-highest bidder, throwing out the NDC/Verisign application.
In a September 9 letter, published last night, Afilias told ICANN to “disqualify and reject” NDC’s application, alleging at least three breaches of ICANN rules.
Afilias says that by refusing to disclose Verisign’s support for its bid, NDC broke the rules and should have its application thrown out.
The company also confirmed on the public record for what I believe is the first time that it was the second-highest bidder in the July 27 auction.
Afilias would pay somewhere between $57.5 million and $71.9 million for the gTLD, depending on what the high bid of the third-placed applicant was.
In its new letter, Afilias says NDC broke the rule from the Applicant Guidebook that does not allow applicants to “resell, assign or transfer any of applicant’s rights or obligations in connection with the application”.
It also says that NDC was obliged by the AGB to notify ICANN of “changes in financial position and changes in ownership or control”, which it did not.
It finally says that Verisign used NDC as a front during the auction, in violation of auction rules.
“In these circumstances, we submit that ICANN should disqualify NDC’s bid and offer to accept the application of Afilias, which placed the second highest exit bid,” Afilias general counsel Scott Hemphill wrote (pdf).
Hemphill told ICANN to defer from signing a Registry Agreement with NDC or Verisign, strongly implying that Afilias intends to invoke ICANN accountability mechanisms (presumably meaning the Request for Reconsideration process and/or Independent Review Process).
While Afilias and Donuts are both taking issue with the secretive nature of Verisign’s acquisition of .web, they’re not necessarily fighting the same corner.
Donuts is looking for $22.5 million because that’s roughly what it would have received if the .web contention set had been resolved via private auction and $135 million had been the winning bid.
But Afilias wants the ICANN auction outcome to stand, albeit with NDC’s top bid rejected. That would mean Donuts, Radix, and the other applicants would still receive nothing.
There’s also the question of other new gTLD applications that have prevailed at auction and been immediately transferred to third-party non-applicants.
The most notable example of this was .blog, which was won by shell company Primer Nivel with secretive backing from WordPress maker Automattic.
Donuts itself regularly wins gTLD auctions and immediately transfers its contracts to Rightside under a pre-existing agreement.
In both of those cases, the reassignment deals predated, but were not disclosed in, the respective applications.
There’s the recipe here for a messy, protracted bun fight over .web, which should come as no surprise to anyone.

Barcelona picked for ICANN 63

ICANN will head to Barcelona, Spain for its 63rd public meeting, the organization’s board of directors has decided.
ICANN 63, that year’s Annual General Meeting, is due to take place October 20 to October 26, 2018. The specific venue has not yet been revealed.
That’s quite a way in the future. Venues have not yet been selected for the first two meetings of 2018, which will take place in ICANN’s North America and Latin America and Caribbean regions.
We’re currently up to ICANN 57, which is due to start in about six weeks in Hyderabad, India (start looking into visas today if you haven’t already).
Next year, meetings will be held in Copenhagen in March, Johannesburg in June and Abu Dhabi in October.
Barcelona was selected for 63 at an ICANN board meeting last week.
The city, Spain’s second most populous, is in the Catalonia region of Spain and is home to the .cat sponsored gTLD.

Destroy ICANN! Destroy ICANN with missiles!

The year is 2016. The Kenyan Muslim president of the United States is poised to hand over control of the internet to the United Nations in an attempt to silence lunatic conspiracy theorists Matt Drudge and Alex Jones for good.
But you can help, by engaging in missile warfare with ICANN and the UN.
That’s the deranged premise of ICANN Command, a little browser game that appeared online this week.
It’s a knock-off of the 1980 Atari classic Missile Command. The intro reads:

You will be defending actual Internet domains from UN attack! Launch surface-to-air missiles in time to destroy UN Domain Seeking Missiles. If a UN missile reaches a domain, that domain is lost forever.
Or, call your senator right now!

This related video explains more.

It’s obviously been inspired by the anti-Obama rhetoric of Senator Ted Cruz and Wall Street Journal op-eds of L Gordon Crovitz, which have fed a fringe right-wing conspiracy theory that sees the UN taking control of the internet come October 1.
That’s the date the US government proposes to remove itself from its oversight role in ICANN’s IANA functions.
After that, ICANN will be overseen by a new multistakeholder process in which everybody, not the UN, has a voice.
InfoWars.com and DrudgeReport.com are safe, sadly.
You can check out the game here if you wish. I scanned it for viruses and mind-control rays and it seems safe.

First dot-brand gTLD to go generic after TLS deal

The would-be dot-brand gTLD .observer will actually open as an unrestricted generic after the contract was bought out by Top Level Spectrum.
TLS, which has a small portfolio of gTLDs already, bought out the ICANN contract from UK newspaper publisher Guardian News and Media a couple of months ago, it emerged today.
The Observer is the title of the Guardian’s sister paper, published on Sundays.
But TLS CEO Jay Westerdal said it will be sold as a generic with pricing under $10 per name, as a thematic stable-mate for its gripe-oriented gTLD .feedback.
The price of the TLD has not been revealed, but Westerdal characterized it as a sub-$1 million deal.
It’s the first instance of a dot-brand, albeit one that that not yet gone live, being taken over by a portfolio gTLD player.
Westerdal said he’s looking for more, similar acquisition opportunities.
The gTLD is currently in pre-delegation testing, with no published go-live date.
The Guardian had signed a Registry Agreement containing Specification 9. That allows registries to disregard the Code of Conduct — which obliges them to treat registrars equally.
It seems likely this will have to be removed from the RA before .observer can go to the masses as a proper generic.

Correction: what NTIA said about .com pricing

The US government has not confirmed that it expects to keep Verisign’s .com registry fee capped at the current level until at least 2024, despite what DI reported on Monday.
At this URL we published an article reporting that the US government had confirmed that it was going to keep .com prices frozen at $7.85 for the next eight years.
That was based on a misreading of a letter from the Department of Commerce to Senator Ted Cruz and others, which merely explained how the price cap could be maintained without expressing a commitment to do so.
The letter actually said very little, and nothing of news value, so I thought it best to simply delete the original piece and replace it with this correction.
I regret the error.
Thanks to those readers who got in touch to point out the mistake.

US claims option to delay IANA transition as Cruz launches free speech doomsday clock

The US government has told ICANN that it may extend the current IANA functions contract for a year, should something unexpected happen this month.
The National Telecommunications and Information Administration wrote to ICANN (pdf) yesterday, to provide “preliminary notice” that it could extent the contract until September 30, 2017, if a “significant impediment” should occur before October 1, 2016.
It appears to be a formality. NTIA said:

the department intends to allow the IANA functions contract to expire as of October 1, 2016, barring any significant impediment. This notice preserves the Government’s rights under the contract during this interim period should there be a change in circumstance.

Under the contract, NTIA is allowed to extend the term for another year in the last 15 days of the current term, but it has to give 30 days notice to ICANN if it wants to do so.
NTIA assistant secretary Larry Strickling told ICANN (pdf) a couple weeks ago that it plans to allow the IANA contract to expire — thereby removing NTIA’s piddling influence in root zone management — October 1.
But the move is facing continued criticism from increasingly unhinged elements of the American political right, who have got it into their heads that the transition means Russia and China will be able to take over ICANN and crush free speech online.
The campaign has been spearheaded by Senator Ted Cruz and whoever pulls the strings of Wall Street Journal columnist L Gordon Crovitz, and has roped in a multitude of hard-right think-tanks.
The latest publicity push for the campaign saw Cruz yesterday launch a countdown clock on its Senate web page.

Cruz’s site states:

If that proposal goes through, countries like Russia, China, and Iran could be able to censor speech on the Internet, including here in the U.S. by blocking access to sites they don’t like.

None of that is true, needless to say.
But the anti-transition sentiment is strong enough that it’s not impossible that there will be a “significant impediment” to the transition before October 1 — a legal injunction against the Federal government, perhaps — and the extension will enable ICANN to run IANA under the current regime for another year.

Tata ponders “buy a school” strategy to release .tata from limbo

Tata Group is reportedly considering buying a school for the Moroccan province of Tata in order to unlock the .tata gTLD.
The huge Indian conglomerate has been prevented from acquiring its own dot-brand because it matches the name of the tiny region, which is as protected geographic string under ICANN rules.
Without the express permission of Morocco, Tata will not get its desired domain.
According to the New Indian Express newspaper, the company has now reached out to the Indian government in an attempt to open diplomatic channels with Morocco and finally resolve the issue.
The paper cites an unnamed “official” as stating that buying a new school for the province may be the best way to “open the door” to a formal non-objection.
That has precedent.
New gTLD registry Punto 2012, managed to get a non-objection for its .bar application from Montenegro by offering to pay $100,000, spread over 10 years, to fund a school in the Bar region of the country.
Tata came close to acquiring .tata in 2014.
It was the final new gTLD application to pass its evaluation, after it managed to produce a letter from Morocco that was taken as a non-objection.
But Morocco’s digital minister subsequently objected, denying that the government had permitted the use of the string.
Tata’s application was then returned to its Geographic Names Review, which it flunked last December.
Since then, the bid has been marked “Will Not Proceed”, a status that usually only changes when an application is withdrawn.

.hotel losers gang up to threaten ICANN with legal bills

The six losing applicants for the .hotel new gTLD are collectively threatening ICANN with a second Independent Review Process action.
Together, they this week filed a Request for Reconsideration with ICANN, challenging its decision earlier this month to allow the Afilias-owned Hotel Top Level Domain Sarl application to go ahead to contracting.
HTLD won a controversial Community Priority Evaluation in 2014, effectively eliminating all rival applicants, but that decision was challenged in an IRP that ICANN ultimately won.
The other applicants think HTLD basically cobbled together a bogus “community” in order to “game” the CPE process and avoid an expensive auction.
Since the IRP decision, the six other applicants — Travel Reservations, Famous Four Media, Radix, Minds + Machines, Donuts and Fegistry — have been arguing that the HTLD application should be thrown out due to the actions of Dirk Krischenowski, a former key executive.
Krischenowski was found by ICANN to have exploited a misconfiguration in its own applicants’ portal to download documents belonging to its competitors that should have been confidential.
But at its August 9 meeting, the ICANN board noted that the timing of the downloads showed that HTLD could not have benefited from the data exposure, and that in any event Krischenowski is no longer involved in the company, and allowed the bid to proceed.
That meant the six other applicants lost the chance to win .hotel at auction and/or make a bunch of cash by losing the auction. They’re not happy about that.
It doesn’t matter that the data breach could not have aided HTLD’s application or its CPE case, they argue, the information revealed could prove a competitive advantage once .hotel goes on sale:

What matters is that the information was accessed with the obvious intent to obtain an unfair advantage over direct competitors. The future registry operator of the .hotel gTLD will compete with other registry operators. In the unlikely event that HTLD were allowed to operate the .hotel gTLD, HTLD would have an unfair advantage over competing registry operators, because of its access to sensitive business information

They also think that HTLD being given .hotel despite having been found “cheating” goes against the spirit of application rules and ICANN’s bylaws.
The RfR (pdf) also draws heavily on the findings of the IRP panel in the unrelated Dot Registry (.llc, .inc, etc) case, which were accepted by the ICANN board also on August 9.
In that case, the panel suggested that the board should conduct more thorough, meaningful reviews of CPE decisions.
It also found that ICANN staff had been “intimately involved” in the preparation of the Dot Registry CPE decision (though not, it should be noted, in the actual scoring) as drafted by the Economist Intelligence Unit.
The .hotel applicants argue that this decision is incompatible with their own IRP, which they lost in February, where the judges found a greater degree of separation between ICANN and the EIU.
Their own IRP panel was given “incomplete and misleading information” about how closely ICANN and the EIU work together, they argue, bringing the decision into doubt.
The RfR strongly hints that another IRP could be in the offing if ICANN fails to cancel HTLD application.
The applicants also want a hearing so they can argue their case in person, and a “substantive review” of the .hotel CPE.
The HTLD application for .hotel is currently “On Hold” while ICANN sorts through the mess.

Are .mail, .home and .corp safe to launch? Applicants think so

ICANN should lift the freeze on new gTLDs .mail, .home and .corp, despite fears they could cause widespread disruption, according to applicants.
Fifteen applicants for the strings wrote to ICANN last week to ask for a risk mitigation plan that would allow them to be delegated.
The three would-be gTLDs were put on hold indefinitely almost three years ago, after studies determined that they were at risk of causing far more “name collision” problems than other strings.
If they were to start resolving on the internet, the fear is they would lead to problems ranging from data leakage to systems simply stopping working properly.
Name collisions are something all new TLDs run the risk of creating, but .home, .corp and .mail are believed to be particularly risky due to the sheer number of private networks that use them as internal namespaces.
My own ISP, which has millions of subscribers, uses .home on its home hub devices, for example. Many companies use .corp and .mail on their LANs, due to longstanding advice from Microsoft and the IETF that it was safe to do so.
A 2013 study (pdf) showed that .home received almost 880 million DNS queries over a 48-hour period, while .corp received over 110 million.
That was vastly more than other non-existent TLDs.
For example, .prod (which some organizations use to mean “production”) got just 5.3 million queries over the same period, and when Google got .prod delegated two years it prompted an angry backlash from inconvenienced admins.
While .mail wasn’t quite on the same scale as the other two, third-party studies determined that it posed similar risks to .home and .corp.
All three were put on hold indefinitely. ICANN said it would ask the IETF to consider making them officially reserved strings.
Now the applicants, noting the lack of IETF movement to formally freeze the strings, want ICANN to work on a thawing plan.
“Rather than continued inaction, ICANN owes applicants for .HOME, .CORP, and .MAIL and the public a plan to mitigate any risks and a proper pathway forward for these TLDs,” the applicants told ICANN (pdf) last Wednesday.
A December 2015 study found that name collisions have occurred in new gTLDs, but that no truly serious problems have been caused.
That does not mean .home, .corp and .mail would be safe to delegate, however.

Dot Registry backs .africa loser, batters on the ICANN lawsuit floodgates

Rejected community gTLD applicant Dot Registry has waded into the lawsuit between DotConnectAfrica and ICANN.
Filing an amicus brief on Friday in support of the unsuccessful .africa applicant, Dot Registry argues that chagrined new gTLD applicants should be allowed to sue ICANN, despite the legal releases they all signed.
The company is clearly setting the groundwork for its own lawsuit against ICANN — or at least trying to give that impression.
If the two companies are successful in their arguments, it could open the floodgates for more lawsuits by pissed-off new gTLD applicants.
Dot Registry claims applicants signed overly broad, one-sided legal waivers with the assurance that alternative dispute mechanisms would be available.
However, it argues that these mechanisms — Reconsideration, Cooperative Engagement and Independent Review — are a “sham” that make ICANN’s assurances amount to nothing more than a “bait-and-switch scheme”.
Dot Registry recently won an Independent Review Process case against ICANN that challenged the adverse Community Priority Evaluation decisions on its .inc, .llc, and .llp applications.
But while the IRP panel said ICANN should pay Dot Registry’s share of the IRP costs, the applicant came away otherwise empty-handed when panel rejected its demand to be handed the four gTLDs on a plate.
The ICANN board of directors has not yet fully decided how to handle the three applications, but forcing them to auction with competing applications seems the most likely outcome.
By formally supporting DotConnectAfrica’s claim that the legal waiver both companies signed is “unconscionable”, the company clearly reckons further legal action will soon be needed.
DotConnectAfrica is suing ICANN on different grounds. Its .africa bid did not lose a CPE; rather it failed for a lack of governmental support.
But both companies agree that the litigation release they signed is not legally enforceable.
They both say that a legal waiver cannot be enforceable in ICANN’s native California if the protected party carries out fraud.
The court seems to be siding with DotConnectAfrica on this count, having thrown out motions to dismiss the case.
Dot Registry’s contribution is to point to its own IRP case as an example of how ICANN allegedly conned it into signing the release on the assumption that IRP would be able to sort out any disputes. Its court brief (pdf) states:

although claiming to provide an alternative accountability mechanism, the Release, in practice, is just a bait-and-switch scheme, offering applicants a sham accountability procedure
…
Indeed, the “accountability” mechanism is nothing of the sort; and, instead of providing applicants a way to challenge actions or inactions by ICANN, it gives lip-service to legitimate grievances while rubber-stamping decisions made by ICANN and its staff.

That’s an allusion to the IRP panel’s declaration, which found no evidence that ICANN’s board of directors had conducted a thorough, transparent review of Dot Registry’s complaints.
Dot Registry is being represented by the law firm Dechert. That’s the current home of Arif Ali, who represented DotConnectAfrica in its own original IRP, though Ali is not a named lawyer in the Dot Registry brief.