Africa hands coffin nails to DotConnectAfrica evaluators

The African Union and a United Nations commission have formally told ICANN that they don’t support DotConnectAfrica’s bid for .africa.
When it comes to showing governmental support, a necessity under ICANN’s rules for a geographic gTLD applications, the UN Economic Commission for Africa was DCA’s only prayer.
Company CEO Sophia Bekele had managed to get somebody at UNECA to write a letter supporting .africa back in 2008, and DCA has continued to pretend that the letter was relevant even after the entire continent came out in support of rival applicant ZA Central Registry.
During its Independent Review Process appeal, DCA begged the IRP panel to declare that the 2008 letter showed it had the support of the 60% of African governments that it requires to be approved by ICANN.
The panel naturally declined to take this view.
Now UNECA has said in a letter to the African Union Commission (pdf) dated July 20, which has since been forwarded to ICANN:

ECA as United Nations entity is neither a government nor a public authority and therefore is not qualified to issue a letter of support for a prospective applicant in support of their application. In addition, ECA does not have a mandate represent the views or convey the support or otherwise of African governments in matters relating to application for delegation of the gTLD.
…
It is ECA’s position that the August 2008 letter to Ms Bekele cannot be properly considered as a “letter of support or endorsement” with the context of ICANN’s requirements and cannot be used as such.

The AUC itself has also now confirmed for the umpteenth time, in a September 29 letter (pdf), that it doesn’t support the DCA bid either. It said:

Any reliance by DCA in its application… proclaiming support or endorsement by the AUC, must be dismissed. The AUC does not support the DCA application and, if any such support was initially provided, it has subsequently been withdrawn with the full knowledge of DCA even prior to the commencement of ICANN’s new gTLD application process.

The AUC went on to say that if DCA is claiming support from any individual African government, such claims should be treated “with the utmost caution and sensitivity”.
That’s because a few years ago African Union member states all signed up to a declaration handing authority over .africa to the AUC.
The AUC ran an open process to find a registry operator. DCA consciously decided to not participate, proclaiming the process corrupt, and ZACR won.
The new letters are relevant because DCA is currently being evaluated for the second time by ICANN’s independent Geographic Names Panel, which has to decide whether DCA has the support of 60% of African governments.
ZACR passed its GNP review largely due to a letter of support from the AUC.
If DCA does not have the same level of support, its application will fail for the second time.
The 2008 UNECA letter was the only thing DCA had left showing any kind of support from any governmental authority.
Now that’s gone, does this mean the DCA application is dead?
No. DCA has a track record of operating irrationally and throwing good money after bad. There’s every chance that when it fails the Geographic Names Review it will simply file another Request for Reconsideration and then another IRP, delaying the delegation of .africa for another year or so.

ICANN finally publishes THAT .africa letter, makes me look like an idiot

ICANN has finally published the letter it controversially drafted for the African Union Commission in order to help it express support for ZA Central Registry’s .africa bid.
Having now read the draft letter for the first time, on balance I’d have to say my previous opinions on its contents were more wrong than right.
The letter was central to claims by rival .africa applicant DotConnectAfrica that ICANN treated ZACR preferentially during the evaluation of both applications.
It was drafted by ICANN staffer Trang Nguyen around June 25, 2013, and sent to ZACR.
It was then edited by ZACR and the AUC, signed by the AUC, and returned to ICANN, whereupon it was forwarded to the new gTLD’s program’s Geographic Names Panel at InterConnect Communications.
The GNP took the letter as an official endorsement of ZACR’s bid, enabling it to pass the Geographic Names Review and proceed to the next stage of the program.
Having seen (and published) the signed AUC letter, I opined here in July that it looked like it had been mostly been written by ZACR and/or the AUC.
I no longer believe that.
It’s now proven that the AUC redraft goes far beyond the “minor edits” that have been claimed by DCA and others — for starters, it’s 40% longer — but a lot of the text that I believed to be ZACR’s work turns out in fact to have come from ICANN.
I’ve put the two letters into a single document (pdf), so you can do a side-by-side comparison if you wish.
There’s still no question that ZACR had African government support for its bid and DCA did not. The dispute centers entirely on whether InterConnect had received expressions of support in the correct format.
An Independent Review Process panel declined to issue an opinion on whether ICANN did anything wrong by drafting the letter, though it is mentioned in its final declaration.
ICANN itself says that it did nothing wrong by drafting the letter, and had DCA had any governmental support it would have done exactly the same thing for it.
The draft letter was among hundreds of pages of documents published last night by ICANN following a Documentary Information Disclosure Process request filed by DI a little over a month ago.

ICANN will post more uncensored .africa info

ICANN has committed to post more unredacted documents from its Independent Review Process case with DotConnectAfrica, following a request from DI.
The organization told DI today that it will publish the documents on its web site by August 31, in response to our July 27 Documentary Information Disclosure Request.
I’d asked ICANN to publish, unredacted, the entire declaration of the IRP panel, along with all equally unredacted exhibits and hearing transcripts.
Aware that ICANN enjoys invoking its “Defined Conditions for Non-Disclosure” in order to stop material being released sometimes, I added “that the public interest and transparency benefits to ICANN of disclosing this information far outweigh any benefit that could be accrued by invoking the Defined Conditions for Non-Disclosure”.
In response, ICANN said today (pdf) that it evaluates the public interest when processing DIDP requests, adding:

we have determined that to the extent additional information warrants disclosure and can be released without further consultation with third parties ICANN will publish that unredacted information no later than 31 August 2015. We will send you an email notification upon that publication. To the extent that disclosure of some information designated as confidential by third parties may be warranted and requires further consultation with third parties, or consultation with other third parties not previously consulted, ICANN has already initiated that consultation process. ICANN will publish such further unredacted information promptly upon, and to the extent that we receive, authorization from the relevant parties to release the information, and will send you an email notification upon that publication.

Since the DIDP was filed, ICANN has published over 700 pages of redacted transcripts from two in-person IRP hearings that took place in May.
Today, it also published a letter from DCA’s competing .africa applicant, ZA Central Registry, comprising an ultimately unsuccessful request for a couple of seats at the hearing.
What has not yet been published are the IRP exhibits showing exactly what ICANN did to oil the gears for ZACR’s application.
Due to Kieren McCarthy’s articles at The Register and ICANN’s subsequent admissions, we know that ICANN staff drafted a letter that the African Union Commission could use to express its support for ZACR in the correct format.
However, the IRP exhibits that would give clarity into what exactly ICANN sent and why remain redacted.
Communications between ICANN and InterConnect, which ran the Geographic Names Panel, and references to the Kenyan government’s did-they-didn’t-they support for DCA also remain redacted.

African Union slams “dysfunctional” IRP as ICANN tries to fend off cover-up claims

The African Union Commission has criticized ICANN’s “dysfunctional accountability process” that has kept the proposed .africa gTLD in limbo for the last few years.
In a communique yesterday (pdf), the AUC also reiterated that .africa applicant ZA Central Registry has the support of both the AUC and its member states, and that governments used almost every avenue available to them to object to the rival DotConnectAfrica bid.
The letter reads:

The Africa region, African Internet stakeholders, the ZACR and AUC are the unfortunate victims of a dysfunctional accountability process and an independent review panel that did not delve more deeply to understand the new gTLD process, the role of governments in that process, and how the ICANN multistakeholder model functions in general.

A few weeks ago, an Independent Review Process panel controversially ruled that ICANN had treated DCA’s application unfairly, in violation of its bylaws, when it accepted Governmental Advisory Committee advice to reject it.
The panel said that ICANN should have at least asked the GAC for the rationale behind its advice, something that the new gTLD program’s rules did not require it to do.
One of the issues at the heart of the subsequent debate is whether ICANN inappropriately helped out ZACR’s bid by drafting an AUC letter of support and then tried to cover its actions up by inappropriately redacting information from the IRP ruling before publication.
On Friday, ICANN published a new version of the ruling that had these references restored, while retaining redactions related to the actions of Kenyan government officials.
We know what the still-redacted text says because Kieren McCarthy, writing for The Register, obtained a clean copy and published it a couple of weeks ago.
ICANN also promised to publish its reasoning if it makes redactions to any documents in future.
In a blog post on Friday, general counsel John Jeffrey said that ICANN helping the AUC draft its letter of support was not a unique case, nor was it inappropriate:

ICANN staff has helped many applicants and their supporters understand how to properly document support. Not only did we make a template support letter publicly available to all as part of the New gTLD Program Applicant Guidebook (see Appendix to Module 2), we have answered questions, received through our customer service channel, as to how interested parties can document support for a given gTLD application. In the case of ZA Central Registry, ICANN appropriately assisted the applicant in documenting support from the AUC.
Our actions surrounding the .AFRICA applications were not unique, since we assist any applicant who requests assistance, or who needs clarification in learning how best to document support or other matters. We have provided assistance to all applicants regarding their applications to the maximum extent possible.

On the claims that ICANN tried to “cover up” this assistance by redacting the IRP’s ruling and previous IRP filings, Jeffrey said that the information was covered by a confidentiality agreement agreed to by itself and DCA and endorsed by the IRP panel.
He said that ICANN was “motivated by our obligation to the community to post the document quickly and the competing, yet mandatory obligation, to respect confidential information while being as transparent as possible.”
He said ICANN attempted to reach out to those affected by the “confidential” parts of the ruling to seek permission to remove the redactions.
But McCarthy also seems to have seen emails exchanged between DCA and ICANN, and he says that ICANN redacted it over DCA’s objections.
McCarthy further says that ICANN only became interested in removing the redactions after he had already published the clean version of the ruling at The Reg — five days after the initial publication by ICANN.
Jeffrey’s post, which refers to “erroneous reporting” in an apparent allusion to McCarthy’s articles, nevertheless fails to address this claim, lending credibility to the cover-up allegations.
The .africa gTLD has been contracted to ZACR, but DCA’s rejected application has been returned to evaluation per the IRP’s ruling, where it is broadly expected to fail for want of governmental support.
Disclosure #1: I recently filed a Documentary Information Disclosure Policy request seeking the release of all the unredacted exhibits in DCA v ICANN. Given ICANN’s wont to usually respond to such requests only at the end of the full 30 days permitted by the policy, I should not expect to see an answer one way or the other until the last week of August.
Disclosure #2: As regular readers may already be aware, due to my long-held and never-disguised view that DCA was mad to apply for .africa without government support, I was once accused of being a part of a “racial conspiracy” against DCA on a blog I believe to be controlled by DCA. Naturally, after I stopped laughing, this libelous allegation pissed me off no end and enhanced my belief that DCA is nuts. Around the same time DCA also, under its own name, filed an “official complaint” (pdf) with ICANN, omitting the race card, alleging that I was part of a conspiracy against it.

ICANN execs helped African Union win .africa — report

Top ICANN executives helped the African Union Commission win the .africa gTLD on behalf of its selected registry, according to a report.
Kieren McCarthy at The Register scooped last night that Dai-Trang Nguyen, head of gTLD operations at ICANN, drafted the letter that the AU used to demonstrate governmental support for ZA Central Registry’s bid.
The basis of the report is the unredacted version of the Independent Review Process panel’s ruling in the DotConnectAfrica case.
McCarthy reports that the uncensored document shows ICANN admitting that Nguyen wrote the AU’s letter, but that “did not violate any policy” and that there was “absolutely nothing wrong with ICANN staff assisting the AUC.”
Apparently, the original AU-drafted letter did not meet the requirements of the Geographic Names Panel, generating a “Clarifying Question”, so the AU reached out to ICANN for help creating a letter that would tick the correct boxes.
The unredacted ruling also contains an allegation that ICANN told InterConnect — one of the three corporate members of the GNP — that the AU’s letter should be taken as representing all of its member states, El Reg reports.
DotConnectAfrica is expected to be shortly returned to the new gTLD application process, and then kicked out again due to its failure to meet the GNP’s criteria of support from 60% of African governments.
I’m in two minds about how damaging these new revelations are.
On the one hand, ICANN staff intervening directly in an Initial Evaluation for a contested gTLD looks incredibly bad for the organization’s neutrality.
One would not expect ICANN to draft, for example, a letter of support for a Community Priority Evaluation applicant.
I don’t think it changes the ultimate outcome for DCA, but it may have inappropriately smoothed the path to approval for ZACR.
On the other hand, the new gTLD program’s Applicant Guidebook actually contains a two-page “Sample Letter of Government Support” that governments were encouraged to print off on letterheaded paper, sign, and submit.
Giving governments assistance with their support letters was in fact baked into the program from the start.
So did the AUC get special treatment in this case, or did Nguyen just send over the AGB sample letter (or a version of it)? That may or may not become clear if and when McCarthy publishes the unredacted ruling, which he has indicated he hopes to do.
A related question might be: how did the AUC screw up its original letter so badly, given the existence of a compliant sample letter?
The optics are many times worse for ICANN because all this stuff was originally redacted, making it look like ICANN was trying to cover up its involvement.
But the redactions were not a unilateral ICANN decision.
ICANN, DCA and the IRP panel agreed after negotiation that some documents revealed during disclosure should be treated confidentially, according to this September 2014 order (pdf). References to these documents were redacted in all of the IRP’s documents, not just the ruling.
What the revelations certainly seem to show is another example of ICANN toadying up to governments, which really has to stop.

DotConnectAfrica responds to DI .africa rant

DotConnectAfrica has published a lengthy retort to DI’s recent post about the (probably) contested .africa gTLD, in which I accused DCA of being disconnected from reality.
You can read my original post here and the DCA response here.
According to DCA, DI’s post was “unprofessional, unwarranted, and sub judice to the ICANN evaluation process”, because it pointed out that Uniforum’s competing bid for .africa stands the best chance of being approved by ICANN.
Having read DCA’s response, I stand by what I wrote.
Geographic gTLDs are governed by special rules at ICANN. They need government support. Nobody disputes this.
In the case of .africa, which covers a lot of countries, support or non-objection from 60% of the relevant governments is required. I don’t think anyone is disputing this either.
Uniforum’s application has this March 2012 letter (pdf) from the African Union Commission, which provides the AUC’s explicit, unambiguous, exclusive support to Uniforum.
Uniforum also claims to have individual support from the required 60% of nations, though I have not seen documentary evidence of this.
DotConnectAfrica, on the other hand, has a August 2009 letter from AUC chair Jean Ping, which expresses support for the DCA application.
It is this 2009 letter that DCA is relying upon to pass the geographic support test in the ICANN evaluation process. In its latest blog post, DCA said, addressing DI:

If you state openly in your Blog that our 2009 endorsement that we got from the African Union Commission does not count, then you are obviously playing the same game that was started by our detractors who have been trying all along to deny and invalidate our hard-won endorsement in order to frustrate DCA’s chances of applying for DotAfrica. It is our sacred responsibility to make sure that our early-bird endorsement from the African Union Commission counts.

In response, all I can say is: “Good luck.”
The Uniforum letter of support, which is more recent by almost three years, states that it is “the only formal endorsement provided by the African Union and its member’s states with regard to dotAfrica.”
On the other hand, the DCA letter of support was “categorically” retracted by the African Union in this May 2011 communication.
The only possible interpretation of this, in my mind, is that Uniforum has African Union backing and that DCA does not.
Unless there’s some obscure nuance of African politics that I’ve failed to comprehend, I don’t think there’s a thing DCA can do to change that fact.
It sucks for DCA, but that’s the way it is.
As for DCA’s insinuations that DI’s position has somehow been bought, I’ll just say for the record that no opinion that has ever been expressed on DI has ever been paid for by a third party.
Over the last couple of years, I’ve probably turned down somewhere in the region of $20,000 from various parties who wanted me to give them favorable coverage in exchange for payment.
That’s just not how things work around here.

DotConnectAfrica — disconnected from reality?

DotConnectAfrica’s campaign for .africa (or .dotafrica, depending who you talk to) is getting increasingly weird.
As you may recall, DCA is the Mauritius-based company, headed by the charismatic and telegenic entrepreneur Sophia Bekele, which has been campaigning for a .africa gTLD for the last few years.
It “accidentally” applied for “.dotafrica” — a sign of almost mind-boggling incompetence — instead of the intended “.africa”, but remains confident that ICANN will allow it to change its application to correct the error.
Despite these failings, the firm has put a lot of hard work raising the profile of the .africa gTLD, for which it should be commended. Unfortunately, it’s not going to win.
If anyone is going to get the .africa registry contract, it’s the other applicant: Uniforum, the South African ccTLD registry.
Despite this painful truth, DCA appears to be in denial.
Take this op-ed, published yesterday on CircleID.
In it, somebody from DCA (the piece does not have a byline) states:

DotConnectAfrica remains a strong contender for the DotAfrica string name and actually stands the best chance of being awarded the mandate to operate the .AFRICA gTLD registry

What’s the basis for this confidence?

[DCA] has adhered to, and respected all the guidelines of the new gTLD programme, in addition to accepting ICANN’s oversight of the entire process, unlike UniForum which might be penalized for wrongly attributing the rights of DotAfrica gTLD to the AU [African Union] instead of ICANN in direct contravention of the new gTLD programme guidelines

DCA is essentially saying that ICANN, and not the African Union, should be the body that gets to decide who should run .africa.
That’s true. It’s also complete rubbish.
Nobody, not even DCA, denies that .africa is a “geographic” gTLD application, as defined by the Applicant Guidebook.
You may have noticed that in the current new gTLD round there are no applications that are both “geographic” and contested by multiple applicants. There’s a good reason for that.
According to ICANN’s rules: “If an applicant has applied for a gTLD string that is a geographic name (as defined in this Guidebook), the applicant is required to submit documentation of support for or non-objection to its application from the relevant governments or public authorities.”
Geographic gTLDs only get approved if the government(s) of that geographic region don’t object, in other words.
These letters of support or non-objection are not being published by ICANN, but the public record has quite a bit to say about which governments support which bids.
In the case of .africa, which covers a lot of countries, ICANN requires letters of support or non-objection from 60% of the nations concerned, and no more than one letter of objection from a government.
Uniforum executives told me recently that the company has this 60% support. It also has the explicit, exclusive, unambiguous support of the African Union Commission.
Here’s what the AU has to say on the matter (pdf):

the AU Commission selected UniForum SA (the ZA Central Registry Operator or ZACR), to administer and operate dotAfrica gTLD on behalf of the African community. The endorsement of the ZACR is the only formal endorsement provided by the African Union and its member’s states with regard to dotAfrica.

If DotConnectAfrica wanted to scupper the Uniforum bid, its best bet would be to lobby African governments that are not already supporting Uniforum — such as those that are not members of the AU — in order to secure more than one letter of objection.
That wouldn’t give DCA a chance to win .africa — contested geographic gTLDs do not go to auction — but it would mean Uniforum’s bid would be rejected for want of support.
But DCA is taking a different — and completely inexplicable — approach.
In a June press release, which tried and failed to explain why DCA applied for .dotafrica instead of .africa, the company said:

Uniforum should really be worrying about the more serious problem it has on its hand, to wit: the agreement signed with the AU is with Uniforum SA/ZA Central Registry, but the putative registry operator/applicant for ‘Africa’ is UniForum SA trading as Registry.Africa.
Where is UniForum SA trading as Registry.Africa’s endorsement for ‘Africa’ gTLD? Is it the specious letter of appointment to apply for DotAfrica gTLD, or the purported agreement between the AU and Uniforum SA/ZA Central Registry? DCA Trust will be watching closely to see how UniForum will try to correct these documentation problems to ensure that no illegal acts are committed.

Did you understand that?
DCA is saying that because Uniforum plans to operate .africa under a standard “doing business as” brand of Registry.Africa — something fully disclosed in its gTLD application — its official letter of support from the AU is somehow open to debate.
To make the company look even more out of touch, DCA has recently had an unhealthy focus on the “insidious mass media manipulation” campaign that it reckons Uniforum has been waging against it. Presumably this blog post can be added to that file at DCA HQ.
I’m struggling to recall where I’ve witnessed such nutty PR before.
Oh, wait.

If DCA wants to be taken seriously it’s going to have to explain — in plain, unobfuscated English — one of two things:
1) Which governments support its application (and this letter from 2009 doesn’t count).
2) Why the 60% rule does not apply to its .africa bid.
Until either of those things are clarified, DCA’s messaging is just a confusing mess.

Unbelievably, .africa will be contested

The .africa top-level domain may well be unique — the only geographic gTLD to be contested.
DotConnectAfrica, which has been campaigning for .africa for years, has confirmed that it has applied for the string, despite the fact that another bidder has support of the African Union.
DCA chief Sophia Bekele blogged:

because of the history of the DotAfrica gTLD and our experience during the ‘Yes2DotAfrica’ promotional campaign, we anticipate a prolonged process

The AU in February announced that it was providing its support to a .africa application from UniForum, the South African ccTLD registry.
DCA had previously secured what appeared to be a letter of support from an AU official, but it has since been withdrawn.
According to ICANN’s Applicant Guidebook, if you want to run a geographic gTLD representing multiple countries, you need the express support or non-objection of 60% of those countries.
I’m pretty certain DCA doesn’t have this support, but the AU’s membership does include more than 60% of the nations in Africa.
Is DCA applying in order to get a pay-off from the Uniforum bid? It’s possible, but without the required government support its negotiating position appears to be pretty weak.
Expect objections.

Sedari working on .africa gTLD bid

Sedari has been contracted to support the controversial African Union-backed .africa top-level domain application.
The new gTLD specialist will supply UniForum with its usual suite of financial, technical and policy support services, Sedari said today.
South Africa-based UniForum was given approval for its .africa bid by the AU last week, raising questions over a longstanding rival application by DotConnectAfrica.
UniForum is already responsible for South Africa’s .za country-code top-level domain.

UniForum selected for .africa gTLD app

UniForum, the South African .za domain name registry operator, has reportedly been selected to run the proposed .africa generic top-level domain.
The African Union announced the appointment today, following a December tender, according to a report on MyBroadband.co.za.
In a sane world, the deal would sound the death-knell for DotConnectAfrica’s long-running campaign to run .africa, but DCA recently has been making noises about applying with or without AU support.
The ICANN Applicant Guidebook is pretty clear when it comes to .africa – it’s a protected geographic term that will require the support of 60% of the affected nations to be approved.
It’s less clear whether AU backing can proxy for individual letters of support from all of those nations, but it’s certainly better than no government support at all.
However, if DCA can get two African governments to object to the AU-backed bid, it might stand a chance at getting a piece of the .africa action.
DCA had a letter of support from the AU dated August 2009, but it was retracted last year. The company has spent the last several months alleging cronyism as a result.
UniForum doesn’t have the best technical reputation in the world. It has managed the .za registry since 1995 but it only switched to an automated, EPP-based shared registry system last year.
Before August 2011, .co.za registrations apparently had to be carried out via email. Let’s hope its new EPP system is up to ICANN’s exacting standards for new gTLDs.