African Union can’t register .africa domain
File this one under “ironic”. Also file it under “Maarten Botterman might be the worst pen-pal in history.”
It turns out that the African Union has been unable to register its domain of choice in the .africa gTLD — for which AU support was a crucial and divisive deal-breaker — because of rules insisted upon by governments.
The AU Commission’s vice chair, Kwesi Quartey, has asked ICANN to release the string “au” from the list that all contracted registries have to agree to reserve because they match the names or acronyms of intergovernmental organizations (IGOs).
The AU is an IGO, so its string is protected from being registered by anyone, including itself.
Quartey wrote, in a letter (pdf) to ICANN chair Botterman:
Unfortunately inclusion of the AU label within the IGO List had the unintended consequence of preventing any third party, including the African Union, from registering the acronym as a domain name (au.africa), yet there is an urgent need to change the African Union digital identifier on the internet from au.int to the .africa domain name.
“Urgent need”, you say? That’s ICANN’s specialty!
Botterman immediately sprang into action and sent his urgent reply (pdf), waiting just 21 short months from Quartey’s July 2020 urgent request to urgently pass the buck to the Governmental Advisory Committee.
Only the GAC can ask for a protected acronym to be removed from the list, he wrote. ICANN Org and board have their hands tied.
Also, removing “au” from the list will release it in all gTLDs, potentially allowing it to be registered by third parties in hundreds of other zones, so watch out for that, Botterman noted.
An additional wrinkle not noted in the letter, which may help or hinder the AU, is that Australia also has rights to the same string under an entirely different new gTLD program reserved list, because it matches the Aussie ccTLD.
You’ll recall that .africa was a contested gTLD in which AU support was the deciding factor.
The AU had originally offered to support a bid from DotConnectAfrica, but after the new gTLD program got underway it withdrew that support and conducted a registry tender that was won by ZA Central Registry, which now runs .africa.
DCA has been pursuing ICANN about this in arbitration and the courts ever since.
DotConnectAfrica slammed for two-faced strategy as it loses .africa appeal
Unsuccessful gTLD applicant DotConnectAfrica has been handed what may prove to be the final nail in the coffin for its failed .africa bid.
A California appeals court has upheld ICANN’s lower-court victory over DCA in its entirety, ruling that the .africa applicant had a two-faced legal strategy that saw it first argue that it did not have a right to sue, but then suing anyway.
After having its .africa application rejected by ICANN due to lack of African government support in 2012, the following year DCA filed an Independent Review Process complaint against ICANN.
One of its key arguments in that case was that it, along with every other new gTLD applicant, had been forced to sign a legal waiver, preventing them from taking ICANN to court.
When it was handed a partial victory in the IRP, sufficient to embarrass ICANN but not enough to have .africa reassigned, DCA was one of a few parties who ignored the legal waiver and sued anyway, in 2016.
Now, the California appeals court has confirmed a lower court ruling that this violated the rule of “judicial estoppel”, which prevents a party switching between two diametrically opposing arguments to suit their strategy at any given time.
“DotConnect took two contrary positions. It told the arbitrators on the Independent Review Panel it could not sue in court. DotConnect then sued in court,” the three judges wrote.
They added that the “text of that litigation waiver was unequivocal, unconditional, and unlimited.”
The ruling describes the .africa case in pretty much the same way as I have for the last decade — DCA didn’t have government support when it applied for the gTLD and ICANN was well within its rights to throw out the application under the program’s rules.
ICANN was handed a thoroughly comprehensive victory, in other words, and awarded costs.
Is this the end of the .africa case? Given DCA boss Sophia Bekele’s apparent fondness for the sunk cost fallacy, who knows?
While all these legal shenanigans have been ongoing, .africa has been delegated to and launched by ZA Central Registry, which had the support of the African Union following an RFP that DCA refused to participate in.
There are about 30,000 .africa domains under management today, which is not terrible for a new gTLD.
The 30-page appeals court ruling (pdf) was made September 20 and ICANN published it this week.
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.
Sorry, you still can’t sue ICANN, two-faced .africa bidder told
Failed .africa gTLD applicant DotConnectAfrica appears to have lost its lawsuit against ICANN.
A California judge has said he will throw out the portions of DCA’s suit that had not already been thrown out two years ago, on the grounds that DCA was talking out of both sides of its mouth.
DCA applied for .africa in 2012 but lost out to rival applicant ZA Central Registry because ZACR had the backing of African governments and DCA did not.
It filed an Independent Review Process complaint against ICANN in 2013 and won in 2015, with the IRP panel finding that ICANN broke its own bylaws by paying undue deference to Governmental Advisory Committee advice.
It also emerged that ICANN had ghost-written letter of government support on behalf of the African Union, which looked very dodgy.
DCA then sued ICANN in 2016 on 11 counts ranging from fraud to breach of contract to negligence.
The Los Angeles Superior Court decided in 2017 that five of those charges were covered by the “covenant not to sue”, a broad waiver that all new gTLD applicants had to sign up to.
But the remaining six, relating to ICANN’s alleged fraud, were allowed to go ahead.
ICANN relied in its defense on a principle called “judicial estoppel”, where a judge is allowed to throw out a plaintiff’s arguments if it can be shown that it had previously relied on diametrically opposed arguments to win an earlier case.
The judge has now found that estoppel applies here, because DCA fought and won the IRP in part by repeatedly claiming that it was not allowed to sue in a proper court.
It had made this argument on at least seven occasions during the IRP, Judge Robert Broadbelt found. He wrote in his August 22 ruling (pdf):
DCA’s successfully taking the first position in the IRP proceeding and gaining significant advantages in that proceeding as a result thereof, and then taking the second position that its totally inconsistent in this lawsuit, presents egregious circumstances that would result in a miscarriage of justice if the court does not apply the doctrine of judicial estoppel to bar DCA from taking the second position in this lawsuit. The court therefore exercises its discretion to find in favor of ICANN, and against DCA, on ICANN’s affirmative defense of judicial estoppel and to bar DCA from bringing or maintaining its claims against ICANN alleged in the [First Amended Complaint] in this lawsuit.
In other words, ICANN’s won.
The case is not yet over, however. DCA still has an opportunity to object to the ruling, and there’s a hearing scheduled for December.
After slow launch, .africa looks to add hundreds of resellers
ZA Central Registry is opening up .africa and its South African city gTLDs to potentially hundreds of new registrars via a new proxy program.
The company today announced that its new registrar AF Proxy Services has received ICANN accreditation, which should open up .africa, .joburg, .capetown and .durban to its existing .za channel.
ZACR is the ccTLD registry for South Africa and as such it already has almost 500 partners accredited to sell .za names. But most of these resellers are not also ICANN accredited, so they cannot sell gTLD domains.
The AF Proxy service is intended to give these existing resellers the ability to sell ZACR’s four gTLDs without having to seek out an ICANN accreditation themselves.
“Effectively, all users of the AF Proxy service become resellers of the Proxy Registrar which is an elegant technical solution aimed at boosting new gTLD domain name registrations,” ZACR CEO Lucky Masilela said in a press release.
While reseller networks are of course a staple of the industry and registries acting as retail registrars is fairly common nowadays, this new ZACR business model is unusual.
According to ZACR’s web site, it has 489 accredited .za registrars active today, with 52 more in testing and a whopping 792 more in the application process.
Depending on uptake of the proxy service, that could bring the number of potential .africa resellers to over 1,300.
And they’re probably needed.
The .africa gTLD went into general availability in July — after five years of expensive legal and quasi-legal challenges from rival applicant DotConnectAfrica — but has so far managed to put just 8,600 names in its zone file.
That’s no doubt disappointing for TLD serving a population of 1.2 billion and which had been expected to see substantial domain investor activity from overseas, particularly China.
Blah blah ICANN blah .africa blah delegated blah blah…
Today blah blah ZA Central Registry blah blah .africa blah delegated blah.
ICANN blah blah root blah. Blah blah ZACR blah nic.africa.
Blah blah five years blah blah contention blah lawsuit blah blah DotConnectAfrica blah. Blah blah Bekele blah IRP blah.
ICANN blah blah Governmental Advisory Committee blah blah blah African Union blah blah blah.
Blah blah Geographic Names Panel blah blah controversy blah blah blah blah lawsuit blah blah blah leg to stand on.
Registry Africa celebrates delegation of .africa#ForAfricansByAfricans #WeAreLive pic.twitter.com/UXZX6yKSPV
— dotAfrica (@africandomain) February 15, 2017
Blah racist blah blah conspiracy blah blah blah… nutty. Blah.
Blah reporting blah damned blah story blah forever blah blah bored blah blah blah blah.
Blah blah blah.
.africa to finally go live after judge denies injunction
A Los Angeles court has rejected a demand for a preliminary injunction preventing ICANN delegating .africa, meaning the new gTLD can go live soon.
Judge Howard Halm ruled February 3, in documents published last night, that the “covenant not to sue” signed by every new gTLD applicant is enforceable and that Africans are being harmed as long as .africa is stuck in legal limbo.
The ruling comes two and a half years after ZA Central Registry, the successful of the two .africa applicants, signed its Registry Agreement with ICANN.
Rival applicant DotConnectAfrica, rejected because it has no African government support, is suing ICANN for fraud, alleging that it failed to follow its own rules and unfairly favored ZACR from the outset.
Unfortunately, the ruling does not address the merits of these claims. It merely says that DCA is unlikely to win its suit due to the covenant it signed.
Halm based his decision on the precedent in Ruby Glen v ICANN, the Donuts lawsuit that seeks to stop ICANN awarding .web to Verisign. The judge in that case ruled last November that Donuts signed away its right to sue.
An earlier judge in the DCA v ICANN case had ruled — based at least in part on a misunderstanding of the facts — that the covenant was unenforceable, but that decision now seems to have been brushed aside.
Halm was not convinced that DCA would suffer irreparable harm if ZACR got given .africa, writing:
The .Africa gTLD can be re-delegated to DCA in the event DCA prevails in this litigation… Further, it appears that any interim harm to DCA can be remedied by monetary damages
He balanced this against the harm of NOT delegating .africa:
The public interest also weighs in favor of denying the injunction because the delay in the delegation of the .Africa gTLD is depriving the people of Africa of having their own unique gTLD.
So what now?
ICANN said in a statement: “In accordance with the terms of its Registry Agreement with ZACR for .AFRICA, ICANN will now follow its normal processes towards delegation.”
As of this morning, ZACR’s .africa bid is officially still marked as “On Hold” by ICANN, though this is likely to change shortly.
Assuming ZACR has already completed pre-delegation testing, delegation itself could be less than a week away.
If DCA’s record is anything to go by, it seems unlikely that this latest setback will be enough to get it to abandon its cause.
Its usual MO whenever it receives an adverse decision or criticism is to double down and start screaming about conspiracies.
While the injunction was denied, the lawsuit itself has not been thrown out, so there’s still plenty of time for more of that.
You can read Halm’s ruling here (pdf).
DCA files for ANOTHER .africa injunction
DotConnectAfrica is continuing its legal attempt to prevent the .africa gTLD from being delegated to a competitor supported by African governments.
The recalcitrant applicant has filed for another temporary restraining order and preliminary injunction that would prevent ICANN handing .africa to the successful applicant, ZA Central Registry, according to ZACR.
DCA’s last application for an injunction was refused by a California judge in December, but last week it renewed its efforts to stymie the long-delayed geo.
ZACR said on its web site yesterday:
On January 4, 2017, DCA filed an ex parte (emergency) temporary restraining order (“TRO”) asking the Court to prevent ICANN from delegating .Africa to ZACR. The Court denied DCA’s ex parte request for a TRO on the grounds that there was no exigency that required an immediate ruling. The Court further clarified that the prior order denying DCA’s preliminary injunction motion was based upon all arguments submitted by ICANN and DCA (thereby rejecting DCA’s contention in its ex parte papers that the ruling did not include ZACR’s arguments). However, the Court agreed to consider DCA’s new arguments as grounds for a new motion for a preliminary injunction. DCA was given until January 6, 2017 to file its motion. ICANN and ZACR shall file opposition papers by January 18, 2017. DCA will then be given an opportunity to file a reply.
The court is scheduled to hear arguments for and against the injunction January 31, ZACR said.
In the meantime, .africa remains in limbo.
.africa could go live after court refuses injunction
DotConnectAfrica’s attempt to have ICANN legally blocked from delegating the .africa gTLD to rival applicant ZACR has been denied.
The ruling by a Los Angeles court, following a December 22 hearing, means ICANN could put .africa in the root, under ZACR’s control, even before the case comes to trial.
A court document (pdf) states:
The plaintiff is seeking to enjoin defendant Internet Corporation for Assigned Names and Numbers (ICANN) from issuing the .Africa generic top level domain (gTLD) until this case has been resolved…
The plaintiff’s motion for the imposition of a Preliminary Injunction is denied, based on the reasoning expressed in the oral and written arguments of defense counsel.
ICANN was just days away from delegating .africa last April when it was hit by a shock preliminary injunction by a California judge who later admitted he hadn’t fully understood the case.
My understanding is that the latest ruling means ICANN may no longer be subject to that injunction, but ICANN was off for the Christmas holidays last week and unable to comment.
“Sanity prevails and dotAfrica is now one (big) step closer to becoming a reality!” ZACR executive director Neil Dundas wrote on Facebook. He declined to comment further.
Even if ICANN no longer has its hands tied legally, it may decide to wait until the trial is over before delegating .africa anyway.
But its lawyers had argued that there was no need for an injunction, saying that .africa could be re-delegated to DCA should ICANN lose at trial.
DCA case centers on its claims that ICANN treated it unfairly, breaking the terms of the Applicant Guidebook, by awarding .africa to ZACR.
ZACR has support from African governments, as required by the Guidebook, whereas DCA does not.
But DCA argues that a long-since revoked support letter from the African Union should still count, based on the well-known principle of jurisprudence the playground “no take-backs”.
The parties are due to return to court January 23 to agree upon dates for the trial.
RANT: Governments raise yet another UN threat to ICANN
ICANN’s transition away from US government oversight is not even a month old and the same old bullshit power struggles and existential threats appear to be in play as strongly as ever.
Governments, via the chair of the Governmental Advisory Committee, last week yet again threatened that they could withdraw from ICANN and seek refuge within the UN’s International Telecommunications Union if they don’t get what they want from the rest of the community.
It’s the kind of thing the IANA transition was supposed to minimize, but just weeks later it appears that little has really changed in the rarefied world of ICANN politicking.
Thomas Schneider, GAC chair, said this on a conference call between the ICANN board and the Generic Names Supporting Organization on Thursday:
I’m just urging you about considering what happens if many governments consider that this system does not work. They go to other institutions. If we are not able to defend public interest in this institution we need to go elsewhere, and this is exactly what is happening currently at the ITU Standardization Assembly.
This is a quite explicit threat — if governments don’t like the decisions ICANN makes, they go to the ITU instead.
It’s the same threat that has been made every year or two for pretty much ICANN’s entire history, but it’s also something that the US government removing its formal oversight of ICANN was supposed to help prevent.
So what’s this “public interest” the GAC wants to defend this time around?
It’s protections for the acronyms of intergovernmental organizations (IGOs) in gTLDs, which we blogged about a few weeks ago.
IGOs are bodies ranging from the relatively well-known, such as the World Health Organization or World Intellectual Property Organization, to the obscure, such as the European Conference of Ministers of Transport or the International Tropical Timber Organization.
According to governments, the public interest would be served if the string “itto”, for example, is reserved in every new gTLD, in other words. It’s not known if any government has passed laws protecting this and other IGO strings in their own ccTLDs, but I suspect it’s very unlikely any have.
There are about 230 such IGOs, all of which have acronyms new gTLD registries are currently temporarily banned from selling as domains.
The multi-stakeholder GNSO community is on the verge of coming up with some policy recommendations that would unblock these acronyms from sale and grant the IGOs access to the UDRP and URS mechanisms, allowing them to reclaim or suspend domains maliciously exploiting their “brands”.
The responsible GNSO working group has been coming up with these recommendations for over two years.
While the GAC and IGOs were invited to participate in the WG, and may have even attended a couple of meetings, they decided they’d have a better shot at getting what they wanted by talking directly to the ICANN board outside of the usual workflow.
The WG chair, Phil Corwin of the Internet Commerce Association, recently described IGO/GAC participation as a “near boycott”.
This reluctance to participate in formal ICANN policy-making led to the creation of the so-called “small group”, a secretive ad hoc committee that has come up with an opposing set of recommendations to tackle the same IGO acronym “problem”.
I don’t think it’s too much of a stretch to call the the small group “secretive”. While the GNSO WG’s every member is publicly identified, their every email publicly archived, their every word transcribed and published, ICANN won’t even say who is in the small group.
I asked ICANN for list of its members a couple of weeks ago and this is what I got:
The group is made up of Board representatives from the New gTLD Program Committee (NGPC), primarily, Chris Disspain; the GAC Chair; and representatives from the IGO coalition that first raised the issue with ICANN and some of whom participated in the original PDP on IGO-INGO-Red Cross-IOC protections – these would include the OECD, the UN, UPU, and WIPO.
With the publication two weeks ago of the small group’s recommendations (pdf) — which conflict with the expect GNSO recommendations — the battle lines were drawn for a fight at ICANN 57, which kicks off this week in Hyderabad, India.
Last Thursday, members of the GNSO Council, including WG chair Corwin, met telephonically with GAC chair Schneider, ICANN chair Steve Crocker and board small group lead Disspain to discuss possible ways forward.
What emerged is what Crocker would probably describe as a “knotty” situation. I’d describe it as a “process clusterfuck”, in which almost all the relevant parties appear to believe their hands are tied.
The GNSO Council feels its hands are tied for various reasons.
Council chair James Bladel explained that the GNSO Council doesn’t have the power to even enter substantive talks.
“[The GNSO Council is] not in a position to, or even authorized to, negotiate or compromise PDP recommendations that have been presented to use by a PDP working group and adopted by Council,” he said.
He went on to say that while the GNSO does have the ability to revisit PDPs, to do so would take years and undermine earlier hard-fought consensus and dissuade volunteers from participating in policy making. He said on the call:
By going back and revisiting PDPs we both undermine the work of the community and potentially could create an environment where folks are reluctant to participate in PDPs and just wait until a PDP is concluded and then get engaged at a later stage when they feel that the recommendations are more likely adopted either by the board or reconciled with GAC advice.
He added that contracted parties — registries and registrars — are only obliged to follow consensus policies that have gone through the PDP process.
Crocker and Disspain agreed that the the GAC and the GNSO appear to have their hands tied until the ICANN board makes a decision.
But its hands are also currently tied, because it only has the power to accept or reject GNSO recommendations and/or GAC advice, and it currently has neither before it.
Chair Crocker explained that the board is not able to simply impose any policy it likes — such as the small group recommendations, which have no real legitimacy — it’s limited to either rejecting whatever advice the GAC comes up with, rejecting whatever the GNSO Council approves, or rejecting both.
The GNSO WG hasn’t finished its work, though the GNSO Council is likely to approve it, and the GAC hasn’t considered the small group paper yet, though it is likely to endorse it it.
Crocker suggested that rejecting both might be the best way to get everyone around a table to try to reach consensus.
Indeed, it appears that there is no way, under ICANN’s processes, for these conflicting views to be reconciled formally at this late stage.
WG chair Corwin said that any attempt to start negotiating the issue before the WG has even finished its work should be “rejected out of hand”.
With the GNSO appearing to be putting up complex process barriers to an amicable way forward, GAC chair Schneider repeatedly stated that he was attempting to reach a pragmatic solution to the impasse.
He expressed frustration frequently throughout the call that there does not appear to be a way that the GAC’s wishes can be negotiated into a reality. It’s not even clear who the GAC should be talking to about this, he complained.
He sounds like he’s the sensible one, but remember he’s representing people who stubbornly refused to negotiate in the WG over the last two years.
Finally, he raised the specter of governments running off to the UN/ITU, something that historically has been able to put the willies up those who fully support (and in many cases make their careers out of) the ICANN multistakeholder model.
Here’s a lengthier chunk of what he said, taken from the official meeting transcript:
If it turns out that there’s no way to change something that has come out of the Policy Development Process, because formally this is not possible unless the same people would agree to get together and do the same thing over again, so maybe this is what it takes, that we need to get back or that the same thing needs to be redone with the guidance from the board.
But if then nobody takes responsibility to — in case that everybody agrees that there’s a public interest at stake here that has not been fully, adequately considered, what — so what’s the point of this institution asking governments for advice if there’s no way to actually follow up on that advice in the end?
So I’m asking quite a fundamental question, and I’m just urging you about considering what happens if many governments consider that the system does not work. They go to other institutions. They think we are not able to defend public interest in this institution. We need to go elsewhere. And this is exactly what is happening currently at the ITU Standardization Assembly, where we have discussions about protection of geographic names because — and I’m not saying this is legitimate or not — but because some governments have the feeling that this hasn’t been adequately addressed in the ICANN structure.
…
I’m really serious about this urge that we all work together to find solutions within ICANN, because the alternative is not necessarily better. And the world is watching what signals we give, and please be aware of that.
The “geographic names” issue that Schneider alludes to here seems to be a proposal (Word .doc) put forward by African countries and under discussion at the ITU’s WTSA 2016 meeting this week.
The proposal calls for governments to get more rights to oppose geographic new gTLD applications more or less arbitrarily.
It emerged not from any failure of ICANN policy — geographic names are already protected at the request of the GAC — but from Africa governments being pissed off that .africa is still on hold because DotConnectAfrica is suing ICANN in a California court and some batty judge granted DCA a restraining order.
It’s not really relevant to the IGO issue, nor especially relevant to the issue of governments failing to influence ICANN policy.
The key takeaway from Schneider’s remarks for me is that, despite assurances that the IANA transition was a way to bring more governments into the ICANN fold rather than seeking solace at the UN, that change of heart is yet to manifest itself.
The “I’m taking my ball and going home” threat seems to be alive and well for now.
If you made it this far but want more, the transcript of the call is here (pdf) and the audio is here (mp3). Good luck.
Recent Comments