Looks like the fight for .hotel gTLD is over
One of the longest-running fights over a new gTLD may be over, after three unsuccessful applicants for .hotel appeared to throw in the towel on their four-year-old legal fight with ICANN.
In a document quietly posted by ICANN last week, the Independent Review Process panel handling the .hotel case accepted a joint request from ICANN and applicants Fegistry, Radix and Domain Venture Partners to close the case.
The applicants lawyers had told ICANN they were “withdrawing all of their claims” and the panel terminated the case “with prejudice”.
They had been fighting to get ICANN to overturn its decision to award .hotel to HOTEL Top-Level-Domain (HTLD), formerly affiliated with Afilias, which had won a controversial Community Priority Evaluation.
CPE was a process under the 2012 new gTLD program rules that allowed applicants in contention sets to avoid an auction if they could show sufficient “community” support for their bids, which HTLD managed to do.
The Fegistry complaint was the second IRP to focus on this decision, which was perceived as unfair and inconsistent with other CPE cases. The first ran from 2015 to 2016 and led to an ICANN win.
Part of the complaints focused on allegations that an HTLD executive improperly accessed private information on competing applicants using a vulnerability in ICANN’s applications portal.
The IRP complainants had also sued in Los Angeles Superior Court, but that case was thrown out in July due to the covenant not to sue (CNTS) that all new gTLD applicants had to agree to when they applied.
The fight for .hotel had been going on for longer than that for .web, but unlike .web it appears that this fight may finally be over.
Defensive windfall on the cards for .spa? It’s not just for spas any more
Forthcoming new gTLD .spa has published its planned launch dates and registrations policies, and it’s not just for spas any more.
Asia Spa and Wellness Promotion Council, the registry, has informed ICANN that it plans to take .spa to sunrise for 30 days starting April 20 and expects to go to general availability around the start of July.
But despite being a “Community” gTLD under ICANN rules, it appears to be also marketing itself at any Italian company that uses the S.p.A corporate suffix, which is generally equivalent to the US Inc/Corp and UK Plc.
According to its eligibility criteria (pdf), under the heading “Coincidental Community Guidelines”, proof of an Italian business address should be enough for any SpA company to qualify to register.
The registry’s web site at nic.spa currently says:
Apart from the spa and wellness industry, .spa can also be a abbreviation to represent:
- Società per Azioni (a form of corporation in Italy, Public Limited Companies By Shares)
- Sociedad por acciones (Joint-stock company in South American Countries)
This offers a great opportunity for entitles in Italy and South American Countries to registered a wonderful name.
This is interesting, because ASPWC applied for .spa as a Community applicant dedicated to the spa and wellness industry.
The primary reason it’s getting to run .spa rather than rival applicant Donuts is that ASPWC won a Community Priority Evaluation, enabling it to avoid a potentially costly auction against its deeper-pocketed competitor.
There’s no mention of Italians or South Americans in its 2015 CPE result (pdf).
Donuts fought the CPE result in ICANN’s Cooperative Engagement Process for three years, but eventually backed away for unknown reasons.
In its original application, ASWPC spends a lot of time discussing its “intended use” of .spa and possible overlap with other meanings of the string. Among this text can be found:
The use of “S.p.A.” as a short form for the Italian form of stock corporation: “Società Per Azioni” is also relatively much less prevalent than the word as intended for the spa community. Furthermore, a more proper and popular way of denoting the form of corporation is “S.p.A.” with the periods included. While this is an important usage of the string “SpA”, the Registry believes that it should not take away from the significant meaning of the word “spa” in its intended use for the spa community as a TLD. Furthermore, additional preventive measures can be put in place to mitigate against any concerns for abusive utilization of the TLD in this manner.
I could find no text explicitly ruling out the Italian corporate use in the application, nor could I find any indication that it was part of the hard-C “Community” upon whose behalf ASWPC was applying for, and eventually won, the gTLD.
The application does seem to envisage some kind of reserved names list that could include S.p.A companies, but that doesn’t appear to be what the registry has in mind any more.
ICANN ordered to freeze .hotel after “serious questions” about trade secrets “theft”
ICANN has been instructed to place the proposed .hotel gTLD in limbo after four applicants for the string raised “sufficiently serious questions” that ICANN may have whitewashed the “theft” of trade secrets.
The order was handed down last month by the emergency panelist in the Independent Review Process case against ICANN by claimants Fegistry, MMX, Radix and Domain Ventures Partners.
Christopher Gibson told ICANN to “maintain the status quo” with regards the .hotel contention set, meaning currently winning applicant Hotel Top Level Domain, which is now owned by Afilias, won’t get contracted or delegated until the IRP is resolved.
At the core of the decision (pdf) is Gibson’s view that the claimants raised “sufficiently serious questions related to the merits” in allegations that ICANN mishandled and acted less than transparently in its investigation into a series of data breaches several years ago.
You may recall that ICANN seriously screwed up its new gTLD application portal, configuring in such a way that any applicant was able to search for and view the confidential data, including financial information such as revenue projections, of any other competing applicant.
Basically, ICANN was accidentally publishing applicants’ trade secrets on its web site for years.
ICANN discovered the glitch in 2015 and conducted an audit, which initially fingered Dirk Krischenowski — who at time was the half-owner of a company that owned almost half of HTLD as well as a lead consultant on the bid — as the person who appeared to have accessed the vast majority of the confidential data in March and April 2014.
ICANN did not initially go public with his identity, but it did inform the affected applicants and I managed to get a copy of the email, which said he’d downloaded about 200 records he shouldn’t have been able to access.
It later came to light that Krischenowski was not the only HTLD employee to use the misconfiguration to access data — according to ICANN, then-CEO of HTLD Katrin Ohlmer and lawyer Oliver Süme had too.
HTLD execs have always denied any wrongdoing, and as far as I know there’s never been any action against them in the proper courts. Krischenowski has maintained that he had no idea the portal was glitched, and he was using it in good faith.
Also, neither Ohlmer nor Krischenowski are still involved with HTLD, having been bought out by Afilias after the hacking claims emerged.
These claims of trade secret “theft” are being raised again now because the losing .hotel applicants think ICANN screwed up its probe and basically tried to make it go away out of embarrassment.
Back in August 2016, the ICANN board decided that demands to cancel the HTLD application were “not warranted”. Ohlmer barely gets a mention in the resolution’s rationale.
The losing applicants challenged this decision in a Request for Reconsideration in 2016, known as Request 16-11 (pdf). In that request, they argued that the ICANN board had basically ignored Ohlmer’s role.
Request 16-11 was finally rejected by the ICANN board in January last year, with the board saying it had in fact considered Ohlmer when making its decision.
But the IRP claimants now point to a baffling part of ICANN’s rationale for doing so: that it found “no evidence that any of the confidential information that Ms. Ohlmer (or Mr. Krischenowski) improperly accessed was provided to HTLD”.
In other words, ICANN said that the CEO of the company did not provide the information that she had obtained to the company of which she was CEO. Clear?
Another reason for brushing off the hacking claims has been that HTLD could have seen no benefit during the application process by having access to its rivals’ confidential data.
HTLD won the contention set, avoiding the need for an auction, in a Community Priority Evaluation. ICANN says the CPE was wholly based on information provided in its 2012 application, so any data obtained in 2014 would have been worthless.
But the losing applicants say that doesn’t matter, as HTLD/Afilias still have access to their trade secrets, which could make the company a more effective competitor should .hotel be delegated.
This all seems to have been important to Gibson’s determination. He wrote in his emergency ruling (pdf) last month:
The Emergency Panelist determines that Claimants have raised “sufficiently serious questions related to the merits” in in relation to the Board’s denial of Request 16-11, with respect to the allegations concerning the Portal Configuration issues in Request 16-11. This conclusion is made on the basis of all of the above information, and in view of Claimants’ IRP Request claim that ICANN subverted the investigation into HTLD’s alleged theft of trade secrets. In particular, Claimants claim that ICANN refused to produce key information underlying its reported conclusions in the investigation; that it violated the duty of transparency by withholding that information; that the Board’s action to ignore relevant facts and law was a violation of Bylaws; and further, to extent the BAMC and/or Board failed to have such information before deciding to disregard HTLD’s alleged breach, that violated their duty of due diligence upon reasonable investigation, and duty of independent judgment.
The Emergency Panelist echoes concerns that were raised initially by the Despegar IRP Panel regarding the Portal Configuration issues, where that Panel found that “serious allegations” had been made188 and referenced Article III(1) of ICANN’s Bylaws in effect at that time, but declined to make a finding on those issues, indicating “that it should remain open to be considered at a future IRP should one be commenced in respect of this issue.” Since that time, ICANN conducted an internal investigation of the Portal Configuration issues, as noted above; however, the alleged lack of disclosure, as well as certain inconsistencies in the decisions of the BAMC and the Board regarding the persons to whom the confidential information was disclosed and their relationship to, or position with HTLD, as well as ICANN’s decision to ultimately rely on a “no harm no foul” rationale when deciding to permit the HTLD application to proceed, all raise sufficiently serious questions related to the merits of whether the Board breached ICANN’s Article, Bylaws or other polices and commitments.
It’s important to note that this is not a final ruling that ICANN did anything wrong, it’s basically the ICANN equivalent of a ruling on a preliminary injunction and Gibson is saying the claimants’ allegations are worthy of further inquiry.
And the ruling did not go entirely the way of the claimants. Gibson in fact ruled against them on most of their demands.
For example, he said their was insufficient evidence to revisit claims that a review of the CPE process carried out by FTI Consulting was a whitewash, and he refused to order ICANN to preserve documentation relating to the case (though ICANN has said it will do so anyway).
He also ruled against the claimants on a few procedural issues, such as their demands for an Ombudsman review and for IRP administrator the International Center for Dispute Resolution to recuse itself.
Some of their claims were also time-barred under ICANN’s equivalent of the statute of limitations.
But ICANN will be prevented from contracting with HTLD/Afilias for now, which is a key strategic win.
ICANN reckons the claimants are just using the IRP to try to force deep-pocketed Afilias into a private auction they can be paid to lose, and I don’t doubt there’s more than a grain of truth in that claim.
But if it exposes another ICANN cover-up in the process, I for one can live with that.
The case continues…
Hacking claims resurface as .hotel losers force ICANN to lawyer up again
The fight over .hotel has been escalated, with four unsuccessful applicants for the gTLD whacking ICANN with a second Independent Review Process appeal.
The complaint resurrects old claims that a former lead on the successful application, now belonging to Afilias, stole trade secrets from competing applicants via a glitched ICANN web site.
It also revives allegations that ICANN improperly colluded with the consultant hired to carry out reviews of “community” applications and then whitewashed an “independent” investigation into the same.
The four companies filing the complaint are new gTLD portfolio applicants MMX (Minds + Machines), Radix, Fegistry, and Domain Venture Partners (what we used to call Famous Four).
The IRP was filed November 18 and published by ICANN December 16, but I did not spot it until more recently. Sorry.
There’s a lot of back-story to the complaint, and it’s been a few years since I got into any depth on this topic, so I’m going to get into a loooong, repetitive, soporific, borderline unreadable recap here.
This post could quite easily be subtitled “How ICANN takes a decade to decide a gTLD’s fate”.
There were seven applicants for .hotel back in 2012, but only one of them purported to represent the “hotel community”. That applicant, HOTEL Top Level Domain, was mostly owned by Afilias.
HTLD had managed to get letters of support from a large number of hotel chains and trade groups, to create a semblance of a community that could help it win a Community Priority Evaluation, enabling it to skip to the finish line and avoid a potentially costly auction against its rival applicants.
CPEs were carried out by the Economist Intelligence Unit, an independent ICANN contractor.
Surprisingly to some (including yours truly), back in 2014 it actually managed to win its CPE, scoring 15 out of the 16 available points, surpassing the 14-point winning threshold and consigning its competing bidders’ applications to the scrap heap.
There would be no auction, and no redistribution of wealth between applicants that customarily follows a new gTLD auction.
Naturally, the remaining applicants were not happy about this, and started to fight back.
The first port of call was a Request for Reconsideration, which all six losers filed jointly in June 2014. It accused the EIU of failing to follow proper procedure when it evaluated the HTLD community application.
That RfR was rejected by ICANN, so a request for information under ICANN’s Documentary Information Disclosure Policy followed. The losing applicants reckoned the EIU evaluator had screwed up, perhaps due to poor training, and they wanted to see all the communications between ICANN and the EIU panel.
The DIDP was also rejected by ICANN on commercial confidentiality grounds, so the group of six filed another RfR, asking for the DIDP to be reconsidered.
Guess what? That got rejected too.
So the applicants then filed an IRP case, known as Despegar v ICANN, in March 2015. Despegar is one of the .hotel applicants, and the only one that directly plays in the hotel reservation space already.
The IRP claimed that ICANN shirked its duties by failing to properly oversee and verify the work of the EIU, failing to ensure the CPE criteria were being consistently applied between contention sets, and failing in its transparency obligations by failing to hand over information related to the CPE process.
While this IRP was in its very early stages, it emerged that one of HTLD’s principals and owners, Dirk Krischenowski, had accessed confidential information about the other applicants via an ICANN web site.
ICANN had misconfigured its applicant portal in such a way that any user could very access any attachment on any application belonging to any applicant. This meant sensitive corporate information, such as worst-case-scenario financial planning, was easily viewable via a simple search for over a year.
Krischenowski appears to have been the only person to have noticed this glitch and used it in earnest. ICANN told applicants in May 2015 that he had carried out 60 searches and accessed 200 records using the glitch.
Krischenowski has always denied any wrongdoing and told DI in 2016 that he had always “relied on the proper functioning of ICANN’s technical infrastructure while working with ICANN’s CSC portal.”
The applicants filed another DIDP, but no additional information about the data glitch was forthcoming.
When the first IRP concluded, in February 2016, ICANN prevailed, but the three-person IRP panel expressed concern that neither the EIU nor ICANN had any process in place to ensure that community evaluations carried out by different evaluators were consistently applying the CPE rules.
The IRP panel also expressed concern about the “very serious issues” raised by the ICANN portal glitch and Krischenowski’s data access.
But the loss of the IRP did not stop the six losing applicants from ploughing on. Their lawyer wrote to ICANN in March 2016 to denounce Krischenowski’s actions as “criminal acts” amounting to “HTLD stealing trade secrets of competing applicants”, and as such HTLD’s application for .hotel should be thrown out.
Again, to the best of my knowledge, Krischenowski has never been charged with, let alone convicted of, any criminal act.
Afilias wrote to ICANN not many weeks later, April 2016, to say that it had bought out Krischenowski’s 48.8% stake in HTLD and that he was no longer involved in the company or its .hotel application.
And ICANN’s board of directors decided in August 2016 that Krischenowski may well have accessed documents he was not supposed to, but that it would have happened after the .hotel CPE had been concluded, so there was no real advantage to HTLD.
A second, parallel battle against ICANN by an unrelated new gTLD applicant had been unfolding over the same period.
A company called Dot Registry had failed in its CPE efforts for the strings .llc, .llp and .inc, and in 2014 had filed its own IRP against ICANN, claiming that the EIU had “bungled” the community evaluations, applying “inconsistent” scoring criteria and “harassing” its supporters.
In July 2016, almost two years later, the IRP panel in that case ruled that Dot Registry had prevailed, and launched a withering attack on the transparency and fairness of the ICANN process.
The panel found that, far from being independent, the EIU had actually incorporated notes from ICANN staff into its CPE evaluations during drafting.
It was as a result of this IRP decision, and the ICANN board’s decision that Krischenowski’s actions could not have benefited HTLD, that the losing .hotel applicants filed yet another RfR.
This one lasted two and a half years before being resolved, because in the meantime ICANN launched a review of the CPE process.
It hired a company called FTI Consulting to dig through EIU and ICANN documentation, including thousands of emails that passed between the two, to see if there was any evidence of impropriety. It covered .hotel, .music, .gay and other gTLD contention sets, all of which were put on hold while FTI did its work.
FTI eventually concluded, at the end of 2017, that there was “no evidence that ICANN organization had any undue influence on the CPE reports or engaged in any impropriety in the CPE process”, which affected applicants promptly dismissed as a “whitewash”.
They began lobbying for more information, unsuccessfully, and hit ICANN with yet another RfR in April 2018. Guess what? That one was rejected too.
The .hotel applicants then entered into a Cooperative Engagement Process — basically pre-IRP talks — from October 2018 to November 2019, before this latest IRP was filed.
It’s tempting to characterize it as a bit of a fishing expedition, albeit not a baseless one — any allegations of ICANN’s wrongdoing pertaining the .hotel CPE are dwarfed by the applicants’ outraged claims that ICANN appears to be covering up both its interactions with the EIU and its probe of the Krischenowski incident, partly out of embarrassment.
The claimants want ICANN to be forced to hand over documentation refused them on previous occasions, relating to: “ICANN subversion of the .HOTEL CPE and first IRP (Despegar), ICANN subversion of FTI’s CPE Process Review, ICANN subversion of investigation into HTLD theft of trade secrets, and ICANN allowing a domain registry conglomerate to takeover the ‘community-based’ applicant HTLD.”
“The falsely ‘independent’ CPE processes were in fact subverted by ICANN in violation of Bylaws, HTLD stole trade secrets from at least one competing applicant, and Afilias is not a representative of the purported community,” the IRP states.
“HTLD’s application should be denied, or at least its purported Community Priority relinquished, as a consequence not only for HTLD’s spying on its competitors’ secret information, but also because HTLD is no longer the same company that applied for the .HOTEL TLD. It is now just a registry conglomerate with no ties to the purported, contrived ‘Community’ that it claims entitled to serve,” it goes on.
ICANN is yet to file its response to the complaint.
Whether the IRP will be successful is anyone’s guess, but what’s beyond doubt is that if it runs its course it’s going to add at least a year, probably closer to two, to the delay that .hotel has been languishing under since the applications were filed in 2012.
Potentially lengthening the duration of the case is the claimants’ demand that ICANN “appoint and train” a “Standing Panel” of at least seven IRP panelists from which each three-person IRP panel would be selected.
The standing panel is something that’s been talked about in ICANN’s bylaws for at least six or seven years, but ICANN has never quite got around to creating it.
ICANN pinged the community for comments on how it should go about creating this panel last year, but doesn’t seemed to have provided a progress report for the last nine months.
The .hotel applicants do not appear to be in any hurry to get this issue resolved. The goal is clearly to force the contention set to auction, which presumably could happen at Afilias’ unilateral whim. Time-to-market is only a relevant consideration for the winner.
With .hotel, and Afilias’ lawsuit attempting to block the .web sale to Verisign, the last round of new gTLD program, it seems, is going to take at least a decade from beginning to end.
Looks like .music is finally on its way
The hard-fought battle for .music appears to be over.
I’m not yet in a position to tell you which of the eight applicants for the new gTLD has been successful, but I can tell you some of those who were not.
Two applicants have this week withdrawn their bids, an almost certain sign that the contention set has been privately settled.
The first applicant to ditch its bid was dot Music Ltd, an application vehicle of Domain Venture Partners (we used to call this outfit Famous Four Media, but that’s changed).
The other is .music LLC, also known as Far Further.
We can almost certainly expect all but one of the remaining applicants to withdraw their applications over the coming days.
Applicants typically sign NDAs when they settle contention privately, usually via an auction.
Far Further was one of two unsuccessful “community” applicants for .music. It had the backing of dozens of music trade groups, including the influential Recording Industry Association of America. Even Radiohead’s guitarist chipped in with his support.
Evidently, none of these groups were prepared to fund Far Further to the extent it could win the .music contention set.
The .music contention set has been held up by the continuing protestations of the other community applicant, DotMusic Limited, the company run by long-time .music cheerleader Constantinos Roussos.
After DotMusic lost its Community Priority Evaluation in 2016, on the basis that the “community” was pretty much illusory under ICANN rules, it started to complain that the process was unfair.
The applicant immediately filed a Request for Reconsideration with ICANN.
.music then found itself one of several proposed gTLDs frozen while ICANN conducted an outside review of alleged irregularities in the CPE process.
That review found no impropriety in early 2018, a verdict DotMusic’s lawyer dismissed as a “whitewash”.
It has since stalled the process several times with requests for information under ICANN’s Documentary Information Disclosure Policy, and more RfRs when those requests were denied.
But this series of appeals finally came to an end March 14, when ICANN’s board of directors finally ruled against DotMusic’s 2016 RfR.
That appears to have opened up the .music set for private resolution.
So who won? I don’t know yet, but the remaining applicants are: DotMusic itself, Google, Amazon, MMX, Donuts and Radix.
There are certainly two very deep-pocketed companies on that list. Could we be looking at Google or Amazon as the new proprietors of .music?
If either of those companies has won, prospective registrants might find they have a long wait before they can pick up a .music domain. Neither of these giants has a track record of rushing its new gTLDs to market.
If the victor is a conventional gTLD registry, we’d very probably be looking at a launch in 2019.
Yanks beat Aussies to accountancy gTLD
The contention set for .cpa has been resolved, clearing the way for a new accountancy-themed gTLD.
The winner is the American Institute of Certified Public Accountants, which submitted two bids for the string — one “community”, one vanilla, both overtly defensive in nature — back in 2012.
Its main rival, CPA Australia, which also applied on a community basis, withdrew its application two weeks ago.
Commercial registries Google, MMX and Donuts all have withdrawn their applications since late December, leaving only the two AICPA applications remaining.
This week, AICPA withdrew its community application, leaving its regular “single registrant” bid the winner.
AICPA is the US professional standards body for accountants, CPA Australia is the equivalent organization in Australia. ACIPA has 418,000 members, CPA Australia has 150,000.
Both groups failed their Community Priority Evaluations back in 2015 on the basis that their communities were tightly restricted to their own membership, and therefore too restrictive.
AICPA later amended its community application to permit CPAs belonging to non-US trade groups to register.
Both organizations were caught up in the CPE review that also entangled and delayed the likes of .music and .gay. They’ve also both appealed to ICANN with multiple Requests for Reconsideration and Cooperative Engagement Process engagements.
CPA Australia evidently threw in the towel after a December 14 resolution of ICANN’s Board Accountability Mechanisms Committee decision to throw out its latest RfR. It quit its CEP January 9.
It’s likely a private resolution of the set, perhaps an auction, occurred in December.
The winning application from AICPA states fairly unambiguously that the body has little appetite for actually running .cpa as a gTLD:
The main reasons for which AICPA submits this application for the .cpa gTLD is that it wants to prevent third parties from securing the TLD that is identical to AICPA’s highly distinctive and reputable trademark
So don’t get too excited if you’re an accountant champing at the bit for a .cpa domain. It’s going to be an unbelievably restrictive TLD, according to the application, with AICPA likely owning all the domains for years after delegation.
The internet is about to get a lot gayer
Seven years after four companies applied for the .gay top-level domain, we finally have a winner.
Three applicants, including the community-driven bid that has been fighting ICANN for exclusive recognition for years, this week withdrew their applications, leaving Top Level Design the prevailing bidder.
Top Level Design is the Portland, Oregon registry that already runs .ink, .design and .wiki.
The withdrawing applicants are fellow portfolio registries Donuts and MMX, and community applicant dotgay LLC, which had been the main holdout preventing the contention set being resolved.
I do not yet know how the settlement was reached, but it smells very much like a private auction.
As a contention set only goes to auction with consent of all the applicants, it seems rather like it came about after dotgay finally threw in the towel.
dotgay was the only applicant to apply as a formal “community”, a special class of applicant under ICANN rules that gives a no-auction path to delegation if a rigorous set of tests can be surmounted.
Under dotgay’s plan, registrants would have to have been verified gay or gay-friendly before they could register a .gay domain, which never sat right with me.
The other applicants, Top Level Design included, all proposed open, unrestricted TLDs.
dotgay, which had huge amounts of support from gay rights groups, failed its Community Priority Evaluation in late 2014. The panel of Economist Intelligence Unit experts awarded it 10 out the 16 available points, short of the 14-point prevailing threshold.
Basically, the EIU said dotgay’s applicant wasn’t gay enough, largely because its definition of “gay” was considered overly broad, comprising the entire LGBTQIA+ community, including non-gay people.
After dotgay appealed, ICANN a few months later overturned the CPE ruling on a technicality.
A rerun of the CPE in October 2015 led to dotgay’s bid being awarded exactly the same failing score as a year earlier, leading to more dotgay appeals.
The .gay set was also held up by an ICANN investigation into the fairness of the CPE process as carried out by the EIU, which unsurprisingly found that everything was just hunky-dory.
The company in 2016 tried crowdfunding to raise $360,000 to fund its appeal, but after a few weeks had raised little more than a hundred bucks.
Since October 2017, dotgay has been in ICANN’s Cooperative Engagement Process, a form of negotiation designed to avert a formal, expensive, Independent Review Process appeal, and the contention set had been on hold.
The company evidently decided it made more sense to cut its losses by submitting to an auction it had little chance of winning, rather than spend six or seven figures on a lengthy IRP in which it had no guarantee of prevailing.
Top Level Design, in its application, says it wants to create “the most safe, secure, and prideful .gay TLD possible” and that it is largely targeting “gay and queer people as well as those individuals that are involved in supporting gay cultures, such as advocacy, outreach, and civil rights.”
But, let’s face it, there’s going to be a hell of a lot of porn in there too.
There’s no mention in the winning bid of any specific policies to counter the abuse, such as cyberbullying or overt homophobia, that .gay is very likely to attract.
Top Level Design is likely to take .gay to launch in the back end of the year.
The settlement of the contention set is also good news for two publicly traded London companies.
MMX presumably stands to get a one-off revenue boost (I’m guessing in seven figures) from losing another auction, while CentralNic, Top Level Design’s chosen back-end registry provider, will see the benefits on an ongoing basis.
Donuts backs away from .spa fight
Donuts has finally admitted defeat in its long-running fight to run the .spa gTLD, withdrawing its application and leaving rival Asia Spa and Wellness Promotion Council the victor.
ASWPC, run from Hong Kong by .asia’s Edmon Chung, has now entered into contracting with ICANN.
The company had won a Community Priority Evaluation back in 2015, with a passing score of 14 out of 16, which Donuts has been challenging ever since.
Donuts and ICANN were in a so-called Cooperative Engagement Process, a form of informal arbitration designed to stave off a more expensive Independent Review Process fight, from January 2016 until this month.
This meant ASWPC has been sitting twiddling its thumbs, unable to sign its contract or launch its TLD, for the better part of three years.
It’s not clear why Donuts decided not to go to a full-blown IRP. The company declined to comment for this article.
As a community applicant, the company had the backing of hundreds of spas worldwide.
It also had the backing of the Belgian government, which was important because spas are (little-known fact alert!) named after the tiny Belgian town of Spa.
It is believed that ASWPC promised up to 25% of its profits to Spa in order to gain this backing, but only from domains registered by Belgian, Dutch, Luxembourgish, French or German registrants.
ICANN strikes back at “offensive” .gay bidder
ICANN has responded harshly to claims that a probe of its handling of applications for the .gay gTLD was fixed from the outset.
Writing to dotgay LLC lawyer Arif Ali this week, ICANN lawyer Kate Wallace said claims that the investigation “had a pre-determined outcome in mind” were “as offensive as they are baseless”.
FTI Consulting gave ICANN the all-clear in January, dismissing allegations that ICANN staff had interfered with Community Priority Evaluations of .gay and other gTLDs conducted by the Economist Intelligence Unit.
But dotgay quickly responded by calling the FTI report a “whitewash”, saying “a strong case could be made that the purported investigation was undertaken with a pre-determined outcome in mind.”
Now, in an unusually pointed letter (pdf) Wallace calls dotgay out for its “insulting” implications.
While dotgay LLC may have preferred a different evaluation process and may have desired a different outcome, that is not evidence that FTI undertook its investigation “with a pre-determined outcome in mind.”
Your accusations in this regard are as offensive as they are baseless. The Board initiated the CPE Process Review in its oversight role of the New gTLD Program to provide greater transparency into the CPE process. There was no pre-determined outcome in mind and FTI was never given any instruction that it was expected to come to one conclusion over another.
…
Your assertions that FTI would blatantly violate best investigative practices and compromise its integrity is insulting and without any support, and ICANN rejects them unequivocally.
Wallace works for ICANN outside counsel Jones Day — which contracted with FTI for the investigation — but states that she is writing at the behest of the ICANN board of directors.
The board “is in the process of considering the issues” raised by Ali and gay rights expert lawyer William Eskridge, she wrote.
The board’s agendas for next week’s ICANN 61 public meeting in Puerto Rico have not yet been published.
dotgay wants to avoid a costly (or lucrative) auction against other .gay applicants by gaining “community” status, but it failed its CPE in 2014, largely because its definition of “gay” over-stretches, and has been appealing the decision ever since.
Economist would sue ICANN if it publishes private emails
The Economist Intelligence Unit has threatened to sue ICANN if it publishes emails related to its evaluations of “community” gTLDs.
That’s according to a document published by ICANN this week, in which the organization refused to reveal any more information about a controversial probe into the Community Priority Evaluations the EIU conducted on its behalf.
EIU “threatened litigation” should ICANN publish emails sent between the two parties, the document states.
New gTLD applicant DotMusic, which failed its CPE for .music but years later continues to fight for the decision to be overturned, filed a Documentary Information Disclosure Policy request with ICANN a month ago.
DIDP is ICANN’s equivalent of a Freedom of Information Act.
DotMusic’s request among many other items sought the release of over 100,000 emails, many sent between ICANN and the EIU, that ICANN had provided to FTI Consulting during FTI’s investigation into whether the CPEs were fair, consistent and absent ICANN meddling.
But in its response this week, ICANN pointed out that its contract with EIU, its “CPE Provider”, has confidentiality clauses:
ICANN organization endeavored to obtain consent from the CPE Provider to disclose certain information relating to the CPE Process Review, but the CPE Provider has not agreed to ICANN organization’s request, and has threatened litigation should ICANN organization breach its contractual confidentiality obligations. ICANN organization’s contractual commitments must be weighed against its other commitments, including transparency. The commitment to transparency does not outweigh all other commitments to require ICANN organization to breach its contract with the CPE Provider.
DotMusic’s DIDP sought the release of 19 batches of information, which it hopes would bolster its case that both the EIU’s original reviews and FTI’s subsequent investigation were flawed, but all requests were denied by ICANN on various grounds.
In more than one instance, ICANN claims attorney-client privilege under California law, as it was actually ICANN’s longstanding law firm Jones Day, rather than ICANN itself, that contracted with FTI.
The FTI report cleared ICANN of all impropriety and said the EIU’s CPE process had been consistent across each of the gTLD applications it looked at.
The full DIDP request and response can be found here.
ICANN has yet to make a decision on .music, along with .gay, .hotel, .cpa, and .merck, all of which were affected by the CPE reviews.
Recent Comments