Some Guy wants to take over .com and .net
Some Guy has noticed that domain name prices keep going up and has offered to take over the .com and .net registries from Verisign.
The Some Guy recently filed a formal Request for Reconsideration with ICANN, asking it to overturn its recent decision to renew Verisign’s .com contract and award it to him instead. The RfR reads:
I seek to become a registry operator committed to making .COM domains more affordable and accessible to students, startups, and developers. The decision to renew Verisign’s contract hinders competition, limiting opportunities for more innovative registry operators like Asxit LLC to contribute to the digital ecosystem.
The request is accompanied by a 25-page, ChatGPT-odored analysis of why Asxit LLC would be a better .com registry than Verisign, which concludes:
The introduction of Asxit LLC as a .COM registry operator would bring significant improvements in pricing, innovation, support, and accessibility compared to Verisign’s current management. By focusing on affordable and flexible solutions, Asxit LLC aims to create a more inclusive and competitive environment for all users. This change would enhance the value of the .COM domain and support the growth of a diverse and innovative digital community.
In August, Some Guy with the same last name, who said he is a student at Liberty University in Virginia, said Asxit LLC should take over .net as well.
They’re not the funniest or craziest submissions ICANN has received over the years, but they might be worth a chuckle if you’re clock-watching on a Friday afternoon.
The sad part is of course that ICANN is now duty-bound to commit legal and board resources preparing a response to this request before throwing it out entirely.
You can’t appeal a UDRP appeal, ICANN Ombudsman says
ICANN’s independent Ombudsman has called an Indian vaccine maker’s second Request for Reconsideration over a failed UDRP case a “misuse” of the Org’s appeals process.
Zydus Lifesciences lost its UDRP over the domain zydus.com earlier this year, with a finding of Reverse Domain Name Hijacking, then used the RfR process to try to get ICANN’s board of directors to overturn the WIPO decision.
The Board Accountability Mechanisms Committee dismissed the complaint because Reconsideration is designed for challenging ICANN’s actions and WIPO is not ICANN.
Zydus immediately filed a second RfR, calling WIPO “an extension of ICANN itself” and that BAMC’s inaction on the first RfR meant the case was now subject to the board’s jurisdiction.
In a rare intervention, Ombudsman Herb Waye poo-poos that notion, writing: “Decisions by the WIPO Panel in a domain name dispute are not sufficient basis for an RfR (hence the BAMC had no ‘jurisdiction’ other than the jurisdiction necessary to dismiss the Request).”
I feel that [the second RfR] has placed the BAMC in the awkward position of policing itself; hence perhaps, its hesitancy to summarily dismiss a Request concerning its own actions. A clear attempt by the requestor to appeal the decision in [the first RfR]. An unfortunate situation that, to me, amounts to misuse of this accountability mechanism.
He concluded that for the BAMC to consider the complaint would be a “waste of resources” and that it should be dismissed.
Zydus will still be able to appeal the UDRP in court, but that of course will be much more expensive.
ICANN throws out prostitution complaint
ICANN has rejected a complaint from a man about a web site apparently offering prostitution services.
As I reported last month, the American had filed a Request for Reconsideration with ICANN’s board of directors after his complaints to Compliance about Namecheap were rejected.
He’s unhappy that US-based Namecheap won’t take down the domain adultsearch.com, which operates as a marketplace for sex workers, many of whom are offering services that may well be illegal in most parts of the US.
But ICANN’s Board Governance Committee rejected the complaint (pdf) for lack of standing.
While the ruling is procedural, rather than substantive, the BGC does spend quite a lot of time tying itself in knots to show that while the complainant may well believe prostitution is harmful to society in general, he failed to state how he, specifically, had been harmed.
The decision also directly references the part of the request the requester has specifically asked to be redacted (but was not).
RDNH loser files second appeal
A big drug company has appealed to ICANN for a second time over a Reverse Domain Name Hijacking ruling against it, claiming ICANN should be responsible for the decisions of the World Intellectual Property Organization.
India-based Zydus Lifesciences, which among other things makes Covid-19 vaccines, lost a UDRP complaint against the owner of zydus.com in June. To add insult to injury, WIPO made a RDNH finding against it.
Rather that go to court, Zydus filed a Request for Reconsideration with ICANN in July, but this was summarily dismissed because the Reconsideration mechanism only applies to the actions or inactions of the ICANN board or staff.
Now Zydus has filed a second RfR, in which its lawyers claim ICANN is responsible for WIPO’s UDRP decisions and failure to address the first RfR amounts to board inaction. The latest claim states:
when a dispute resolution service provider is accredited by ICANN to conduct mandatory administrative policy, as prescribed by the UDRP adopted by ICANN, such service providers are extension of ICANN itself
Zydus claims the WIPO panel erred by relying on what it claims were false and misleading statements by the zydus.com registrant. It wants the decision reversed and the three panelists forever barred.
I doubt the RfR will get anywhere. ICANN’s Board Accountability Mechanisms Committee is not about to make itself the de facto court of appeals for every UDRP party who thinks they got stiffed.
Covid vaccine maker takes RDNH loss to ICANN board
An Indian pharmaceuticals firm with a $2 billion turnover has complained at the highest level of ICANN after it was handed a Reverse Domain Name Hijacking decision over the .com matching its company name.
Zydus Lifesciences, which produces mainly generic drugs but last year earned government approval to manufacture a Covid-19 vaccine, says a UDRP panel “exhibited extreme bias” when it threw out its UDRP complaint against the owner of zydus.com last month.
The company had claimed the anonymous registrant was cybersquatting, but the WIPO panel instead found RDNH.
The panel was not convinced that the registrant should have been aware of Zydus’ existence when he registered the name in 2004, and said his use of the name — which it characterized as a fanciful five-letter generic — to redirect to various affiliate marketing sites was not “bad faith”.
But now Zydus is claiming that the panel ignored evidence that it was already a very large company, with a $110 million turnover, at the time of registration, and says the UDRP decision shows evidence of bias against developing-world companies. The latter card is played pretty hard.
I believe this is only the second time that a UDRP decision has been challenged with a formal Request for Reconsideration with the ICANN board of directors, and there’s a pretty good chance it will be summarily dismissed like the first one.
Zydus will probably have to sue, or pay up.
Another new gTLD applicant lawyers up on ICANN
Another rejected new gTLD applicant has filed an Independent Review Process complaint against ICANN, claiming the org failed to follow proper procedures on fairness and transparency.
And I think it’s got a pretty good chance of winning.
A Bahrain company called GCCXI has filed the IRP, eight years after its application for .gcc was thrown out by ICANN on the vague advice of its Governmental Advisory Community.
.gcc is for Gulf Cooperation Council, the short-hand English name for the Cooperation Council for the Arab States of the Persian Gulf, a proto-union of six states on the east coast of the Arabian peninsula.
The applicant’s problem is that it’s not affiliated with, nor supported by, the GCC or its member states.
The GAC, in its controversial Beijing communique of April 2013 objected to GCCXI’s application in the same breath and under the same power as it objected to DotConnectAfrica’s .africa bid.
Back then, the GAC was much more secretive than it is today, and did not have to provide a rationale for its advice. Its powers to object to gTLD applications pretty much amounted to a veto.
ICANN dutifully followed the GAC’s advice, throwing out the .gcc application later that year.
The applicant has evidently been trying to get ICANN to change its mind, using the Request for Reconsideration and then Cooperative Engagement Processes, since early 2014. That CEP concluded in May, and GCCXI filed for IRP in June.
Why did the CEP — a form of arbitration designed to avoid expensive IRP complaints and lawsuits — take so long and ultimately fail?
Don’t look to the IRP complaint published by ICANN (pdf) for answers — it’s redacted the whole ruddy lot, a few pages of text, without explanation.
That’s ironic given that a lack of transparency is one of GCCXI’s beefs against the org, along with an alleged failure to follow its bylaws on neutrality and fairness.
ICANN has ignored all of its carefully developed and documented policies, and instead has kowtowed to unspecified government concerns — devising a secret process to kill Claimant’s investment and opportunity, and completely disregarding the public interest in delegating the TLD for use.
The continued fight for a gTLD it surely has no hope of ever operating is a ballsy move by the applicant.
It’s roughly equivalent to some random European company applying to run .eu to represent the geographic region of EU member states without the consent of the EU institutions themselves and then complaining when it’s told to take a walk.
But that doesn’t necessarily mean it will lose the IRP. In fact, I think it has a pretty good chance of winning.
GCCXI does not deserve to prove it should be given .gcc, it only needs to show that ICANN broke its own bylaws.
DotConnectAfrica, which was rejected by the GAC and then ICANN for pretty much the same unsubstantiated reasons — the GAC “veto” — won its IRP in 2015, with the panel finding that ICANN accepted the GAC’s unexplained advice without even rudimentary due diligence, violating its commitment to fairness.
It was particularly embarrassing for the GAC, whose then-chair admitted that the committee deliberately kept its advice vague and open to interpretation
While .africa is not exactly the same as .gcc (the former is officially a geographic string, the latter is not), GCCXI had DCA had their applications rejected based on the exact same piece of GAC advice.
It’s also similar to Amazon’s IRP fight for .amazon, which it won. That bid was also kicked out as a result of ICANN’s adoption of opaque GAC advice from the Beijing communique.
You’ve got to think GCCXI has a decent shot at a victory here, though if recent IRPs and general ICANN foot-dragging on accountability are any guide we won’t know for a couple years.
ICANN throws out another challenge to the Donuts-Afilias deal
ICANN is set to reject a plea for it to reconsider its decision to allow Donuts to buy Afilias last December.
Its Board Accountability Mechanisms Committee recently threw out a Request for Reconsideration filed by Dot Hotel and Domain Venture Partners, part of a multi-pronged assault on the outcome of the .hotel gTLD contention set.
The RfR was “summarily dismissed”, an infrequently used way of disposing of such requests without considering their merits. BAMC concluded that the requestors had failed to sufficiently state how they’d been harmed by ICANN’s decision, and therefore lacked standing.
The requestors, both applicants for .hotel, had said that they were harmed by the fact that Donuts now owns two applications for .hotel — its own open, commercial one and Afilias’ successful community-based one.
It also said that ICANN’s seemingly deliberate opacity when it came to approving the deal broke its bylaws and sowed confusion and risk in the registry industry.
At some point before the December 17 board meeting that approved the acquisition, ICANN staff briefed the board on its decision to approve the deal, but no formal resolution was passed.
By exploiting this loophole, it’s not clear whether the board actually voted on the deal, and ICANN was not obliged by its bylaws to publish a rationale for the decision.
But BAMC, acting on the advice of ICANN’s lawyers, decided (pdf) that the statements of alleged harm were too vague or seemed to rely on potential future harms.
DVP and Dot Hotel are also party to a lawsuit and an Independent Review Process case against ICANN related to .hotel.
A Documentary Information Disclosure Request related to the Afilias acquisition was also thrown out in March.
BAMC’s dismissal will be rubber-stamped by ICANN’s full board at a later date.
Got beef with ICANN? Why you may not want to use the Ombudsman
Complaining to the independent Ombudsman may not be the best way to start a beef with ICANN, and that’s according to the Ombudsman himself.
Herb Waye told DI this week that consulting him as a first port of call may well lock complainants out of escalating their complaints through his office in future procedures.
Earlier this week, I reported on a lawsuit filed by three so-far unsuccessful .hotel gTLD applicants, which among other things alleges that ICANN’s Request for Reconsideration appeals process is a “sham”.
Reconsideration has quite a high barrier to success, and complaints are rarely successful. Requests are dealt with by the Board Accountability Mechanisms Committee, a subset of the very same board of directors that passed the resolution being complained about, advised by the same ICANN lawyers.
But RfRs are also automatically sent to the Ombudsman for a determination before the BAMC looks into them, which should provide a valuable and ostensibly independent second set of critical eyes.
However, in practice this has almost never happened since the provision was added to the ICANN bylaws five year ago.
The .hotel plaintiffs tallied up the 14 RfRs related to the new gTLD program since 2017 and found that the Ombudsman had recused himself, without detailed explanation, on every single occasion. Their complaint in California Superior Court reads:
Neither ICANN nor the Ombudsman has provided any intelligible reason for this gross flouting of ICANN’s bylaws and the Ombudsman’s dereliction of duty, other than a naked and vague claim of “conflict of interest”. The lack of any Ombudsman process not only violates ICANN’s bylaws and its contracts with Plaintiffs, but it renders the promise of a fair and independent Reconsideration process null and illusory, and the notion of true accountability a farce.
The ICANN bylaws state that the Ombudsman must recuse himself from considering RfRs “involving matters for which the Ombudsman has, in advance of the filing of the Reconsideration Request, taken a position while performing his or her role as the Ombudsman”.
According to Waye’s explanation, this is a very broad standard indeed. He told DI in an email:
it is not just me but over 18(?) years of Office of the Ombudsman involvement in complaints or investigations. So I need to go back through the archives when I receive an RR to make sure neither Chris [LaHatte] nor Frank [Fowlie] have made a determination (it doesn’t have to be a public report (or position) or a report to the Board to qualify for recusal).
Among other factors, it also doesn’t have to be a past determination directly involving the RR requestor either… if the substance of the RR has been reviewed by the Office in the past, or if the RR is about an issue similar to one that has been the subject of a complaint and a determination, then recusal is also required to avoid inconsistencies or perceived bias.
He consults with his “independent outside counsel”, Dave Marglin, when figuring out whether recusal is necessary, he said.
Waye published an explanation of his role in Reconsideration on page 19 of the Ombusdman’s most-recent annual report (pdf).
I wondered whether a 2015 decision by Waye predecessor LaHatte related to the new gTLD program’s controversial Community Priority Evaluation might account for the spate of recusals over the last few years, but Waye would not be drawn.
“I can’t identify specifics about each recusal as I must at all cost avoid identifying past complainants or subjects of complaints,” he said. “As I mentioned, some published reports may be the reason for a recusal but it may also be the result of the RfR issue having passed through my Office prior to the RfR being filed as a complaint; which may or may not be a known fact, so I err on the side of caution and treat all recusals the same.”
Given that the Ombudsman also deals with sensitive interpersonal interactions, including sexual harassment complaints, a code of confidentiality could be a good thing.
But it also means that there are an unknown number of undisclosed topics, dating back the best part of two decades, that the Ombudsman is apparently powerless to address via the Reconsideration process.
And that list of untouchable topics will only get longer as time goes by, incrementally weakening ICANN’s accountability mechanisms.
It seems to me that for companies with no interest in confidentiality but with serious complaints against an ICANN board action, complaining to the Ombudsman as the first port of call in a case that would likely be escalated to Reconsideration, Cooperative Engagement Process and Independent Review Process may be a bad idea.
Not only would they be locking the Ombudsman out of their own subsequent RfR, but they’d be preventing him or her getting involved in related RfRs for eternity.
Waye does not disagree. He said:
I think anyone considering bringing a complaint to the Office of the Ombuds should now consider their desired outcome if there is any possibility the issue may be something that could eventually take the RfR route. Do they want an informal (potentially confidential) determination from the Ombuds or do they want something more “public” from the Ombuds in the form of a substantive evaluation made directly to the BAMC. It’s still a new process and my participation in the RfR accountability mechanism is still a work in progress for the people considering using the RfR. But it’s what the community wanted and we will make it work.
It strikes me that the Reconsideration policy outlined in the ICANN bylaws is, by accident or design, self-terminating and opaque. It becomes less useful the more often it is used, as the range of topics the Ombudsman is permitted to rule on are slowly whittled away in secret.
It also occurs to be that it might be open to abuse and gaming.
Worried that a rival company will try to use Reconsideration to your disadvantage? Why not file a preemptive Ombudsman complaint on the same topic, forcing him to recusing himself and leaving the eventual RfR in the hands of the far-from-objective BAMC and ICANN board?
Waye said:
I suppose it would be possible, though it would require me making a determination or taking a position of sorts related to the eventual RfR… a complaint doesn’t automatically mean recusal. And of course it would mean me and my counsel not seeing through the “gaming” agenda and declining the complaint at the outset.
Rival wants the truth about the Afilias-Donuts deal amid “collusion” claims
Portfolio gTLD investor Domain Venture Partners wants ICANN to fully explain its decision to approve Donuts’ acquisition of Afilias, claiming the deal gives the combined company an unfair advantage in the long-running battle for the .hotel gTLD.
DVP has filed a formal Request for Reconsideration with ICANN, tearing it a new one for seemingly going out of its way to avoid its transparency obligations when it came to the December approval of the acquisition.
ICANN’s board of directors had been scheduled to discuss the mega-deal at a special meeting December 17, but instead it carried out these talks off-the-books, in such a way as to avoid bylaws rules requiring it to publish a rationale and meeting minutes.
As I noted recently, it was the second time in 2020 (after the Ethos-PIR deal) the board resorted to this tactic to avoid publicly stating why it was approving or rejecting a large M&A transaction.
DVP notes the contrast with the Ethos-PIR proposal, which endured months of public scrutiny and feedback, adding in its RfR:
Why did the ICANN Board have a Special Meeting on this topic? Why did they not publish or otherwise identify a single background fact or point of discussion from the Special Meeting? Why did they not identify a single source of evidence or advice relied upon in coming to the decision? Why have they refused to provide even the slightest hint as to anything they considered or any reason why they came to their decision? How did they vote, was there any dissent? Nobody knows, because ICANN has kept all that secret.
The company argues that all this secrecy leaves itself and other registries at a loss to predict what might happen should they be involved in future acquisitions, particularly given the allegedly anti-bylaws “discriminatory” treatment between PIR on the one hand and Afilias on the other.
DVP stops short of asking for ICANN to overturn its decision to permit the acquisition — it would be moot anyway, as the deal has already closed — but it does demand that ICANN:
Provide complete, published rationale for the Resolution of Dec. 17, 2020 to essentially approve the Afilias acquisition of Donuts, including identification of all materials relied upon by the Board and/or Staff in evaluating the transaction, publication of all communications between Board, Staff and/or outside advisors relating to the transaction, and publication of all communications regarding the transaction between ICANN on the one hand, and Afilias, Donuts and/or Ethos Capital on the other hand.
Develop, implement, publish and report results of a clear policy as to what registry combination transactions will be approved or rejected, including clearly defined criteria to be assessed — and clearly defined process to assess that criteria – as to each and every future proposed transaction.
It’s interesting that nobody has filed a Documentary Information Disclosure Policy request for this information yet.
But it’s not all just about transparency for DVP. Its big concern appears to be its application for .hotel, which is in one of the few new gTLD contention sets still not resolved almost a decade after the 2012 application round.
DVP is the Gibraltar investment vehicle that controls the 16 new gTLDs that were formerly managed by Famous Four Media and are now managed by GRS Domains (which I believe is owned by PricewaterhouseCoopers). Dot Hotel Limited is one of its application shells.
Donuts is now in possession of two competing .hotel applications — its own, which is for an open, unrestricted space gTLD, and the Afilias-owned HTLD application, which is for a restricted Community-based space.
Back in 2014, HTLD won a Community Evaluation Process, which should have enabled it to skip a potentially expensive auction with its rival bidders and go straight to contracting and delegation.
But its competing applicants, including DVP and Donuts, challenged the CPE’s legitimacy with an Independent Review Process appeal.
To cut a long story short, they lost the IRP but carried on delaying the contention set and came back with a second IRP (this one not including Donuts as a complainant), which involves claims of “hacking”, one year ago.
The contention set is currently frozen, but DVP thinks Donuts owning two applications is a problem:
Donuts now owns or controls both that Community Application, and another pending standard application in the contention set for .hotel. There is no provision in the Applicant Guidebook for applicants to own more than one application for the same gTLD string. It certainly indicates collusion among applicants within a contention set, since two of them are owned by the same master.
…
DVP is concerned that Donuts may have no intention of honoring those Community commitments, and instead intends to operate an open registry.
DVP wants ICaNN to publish a rationale for why it’s allowing Donuts to own two applications for the same TLD.
It also wants ICANN to either force Donuts to cancel its HTLD application — which would likely lead to a .hotel auction among the remaining applicants, with the winning bid flowing to either ICANN or the losing applicants — or force it to stick to its Community designation commitments after launch, which isn’t really Donuts’ usual business model.
RfRs are usually resolved by ICANN’s lawyers Board Accountability Mechanisms Committee in a matter of weeks, and are rarely successful.
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…
Recent Comments