Summary

  • DotConnectAfrica’s 9 July 2015 Independent Review Process Final Declaration established that ICANN’s Board had acted inconsistently with its fairness, transparency and due-diligence obligations. The panel recommended that delegation remain paused and that DotConnectAfrica return to the ordinary application process. It did not find that DotConnectAfrica had satisfied the geographic-name requirements, invalidate ZA Central Registry’s evaluation result, rescind its signed Registry Agreement or direct IANA to install DotConnectAfrica as the operator.
  • The controlling merits question after the IRP remained the Applicant Guidebook’s geographic-name test. DotConnectAfrica passed the technical, operational and financial portions of its resumed Initial Evaluation, but its 17 February 2016 Extended Evaluation report found that it had not supplied the required governmental support or non-objection documentation. It therefore became ineligible for further review, leaving ZA Central Registry’s surviving agreement as the only cleared contractual route to the string.
  • Courts could temporarily stop that route without selecting an operator. A federal preliminary injunction restrained delegation in 2016, but renewed California state-court relief was denied, most decisively on 3 February 2017. IANA then confirmed readiness on 10 February, published its delegation report on 14 February and recorded completion of the root-zone change on 15 February 2017. The 2021 appellate decision ended the principal litigation aftermath; it was not the authority that delegated .AFRICA.

The contract and the procedural victory coexisted

Two dated records expose the institutional problem at the centre of .AFRICA.

On 24 March 2014, while DotConnectAfrica Trust’s accountability proceeding was already pending, ICANN executed the .AFRICA Registry Agreement with ZA Central Registry. The agreement created a contractual relationship between ICANN and the successful applicant, subject to the remaining programme and delegation requirements. It did not yet place the string in the DNS root.

Fifteen months later, on 9 July 2015, the Independent Review Process panel issued its Final Declaration. It concluded that ICANN’s Board had acted inconsistently with the organisation’s Articles and Bylaws in its treatment of DotConnectAfrica’s application. It recommended continued non-delegation while DotConnectAfrica was restored to the remainder of the new-gTLD application process.

The procedural victory was substantial. The rival agreement nevertheless remained intact.

That coexistence is sometimes described as if an external tribunal had awarded .AFRICA to DotConnectAfrica and ICANN had simply refused to comply. The primary record supports a more constrained account. The IRP determined that the Board’s process had failed the standards governing ICANN’s conduct. It did not determine that DotConnectAfrica possessed the governmental support documentation required for a geographic string. It did not disqualify ZA Central Registry, reverse that applicant’s evaluation result or execute a contractual termination. Nor did it perform the technical and administrative steps required for a root-zone delegation.

The distinction is not a technical escape from accountability. It identifies the remedy that DotConnectAfrica actually obtained and the additional institutional acts that would have been necessary to change the operator.

The .AFRICA string was not allocated by one indivisible decision. Applicants supplied evidence and representations. A Geographic Names Panel tested particular documents against the Applicant Guidebook. Governments could submit support, objections and Early Warnings. The Governmental Advisory Committee could transmit consensus advice. The New gTLD Program Committee or the full Board determined what programme consequence to attach to that advice. Reconsideration and the IRP examined different forms of institutional error. ICANN signed and administered the Registry Agreement. Courts could impose coercive restraints. The IANA functions process then checked the authorised delegation package and implemented the root-zone change.

Each body controlled a different part of the chain. A successful challenge at one stage did not automatically modify every downstream instrument. The remedy gap was therefore the distance between the institutional wrong found by the IRP and the separate evaluation, contract, court order and root-zone instruction that would have had to change for DotConnectAfrica to become the operator.

Two applications entered as standard applications

The contest began with two applications for the same geographic string.

ZA Central Registry submitted application 1-1243-89583. Its ICANN application-status record now identifies the application as delegated, records that it passed evaluation and shows that it prevailed in the contention set.

DotConnectAfrica Trust submitted application 1-1165-42560. Its status record records a terminated application that became ineligible for further review and did not prevail.

Both applicants chose the standard, rather than community-based, application route. ZA Central Registry answered “No” to the community-based designation in its public application. DotConnectAfrica likewise described its proposal as an open or standard geographic application rather than a community-based application in its own public submission.

That formal classification did not prevent either applicant from invoking African institutions, continental public interests or broad constituencies. ZA Central Registry relied on an asserted African Union Commission selection process, governmental support and a narrative of continent-wide institutional endorsement. DotConnectAfrica presented itself as an open, Africa-facing initiative and contested the validity and exclusivity of its rival’s claimed mandate.

Those positions mattered politically and evidentially. They did not convert either application into a Community Priority Evaluation case. Neither applicant obtained the procedural benefits that the Guidebook reserved for a qualifying community-based application. The contention therefore could not be resolved merely by asking which organisation offered the more persuasive public account of representing Africa.

The programme required those claims to be translated into recognised procedural forms: signed governmental support or non-objection documents, evaluation responses, GAC submissions, Board decisions and, if both applications remained eligible, an applicable contention-resolution mechanism.

This is the first important boundary in the case. Participation allowed applicants, governments and institutions to place material before ICANN. It did not give any one participant direct custody of the string. The relevant question at every stage was not simply who had spoken, but which institution had authority to convert a submission into a programme consequence.

A claimed mandate was evidence, not self-executing authority

ZA Central Registry’s application said that the African Union Commission had selected or appointed it following a process organised around the .AFRICA initiative. Supporting governmental materials repeated or endorsed that account. Ghana’s November 2012 GAC Early Warning, for example, opposed DotConnectAfrica’s application, supported the African Union Commission and ZA Central Registry position, and referred to a competitive selection process and backing from African governments.

Those documents prove that the claims were made and placed before the programme. They do not independently establish every legal proposition that might be drawn from them.

The available record does not include a complete official African Union Commission procurement, appointment or mandate instrument sufficient to test the legality, exclusivity and precise institutional scope of the claimed selection at its source. Nor does it expose the complete governmental support and non-objection letter sets, all clarification exchanges or the evaluator correspondence for both applicants. The published evaluation reports disclose the resulting pass or failure, but they do not provide a document-by-document account of how every signature, authority or endorsement was authenticated and weighted.

The appropriate description is therefore bounded. ZA Central Registry submitted an African Union Commission mandate claim and related governmental-support evidence. At least some governments endorsed that position. The designated Geographic Names Panel ultimately found ZA Central Registry’s documentation sufficient for the programme’s geographic-name requirements.

That is not the same as an independent judicial or administrative finding that ZA Central Registry held an exclusive legal mandate to speak for the continent. The programme did not need to decide that broader question in order to decide whether the submitted documents met its own eligibility test.

Numerical claims require similar restraint. Governmental and applicant submissions referred to substantial levels of support. Without a complete, independently checked collection of the relevant letters and Early Warnings, those totals should not be repeated as verified facts. A support count asserted by an interested party or one government is evidence of what that participant told ICANN, not an audit result.

DotConnectAfrica’s challenges to the rival mandate must be handled in the same way. They demonstrate that the asserted authority was contested. They do not, without an adjudication directed to that issue, establish that the appointment was invalid or that DotConnectAfrica itself possessed the documentation required by the Guidebook.

This evidential discipline prevents governmental endorsement from being confused with programme control. A government could issue a letter, objection or warning. A regional organisation could offer institutional support. Those acts acquired legal significance only through the particular programme rules that recognised them. They did not themselves sign a registry contract or alter the root zone.

The geographic-name provisions turned support into a formal gate

Because .AFRICA corresponded to a region identified through the United Nations M49 framework, the applications engaged the geographic-name provisions of the 2012 Applicant Guidebook.

The Guidebook’s evaluation procedures separated the substantive threshold from the documentation rules. Section 2.2.1.4.2 required an application for a relevant regional name to include support or non-objection from at least 60 per cent of the national governments in the region, while allowing no more than one written objection from a relevant government or public authority. Section 2.2.1.4.3 addressed the required form and content of those documents, including signatures, the authority of the signatory, awareness of the proposed string and intended use, and the evaluator’s ability to verify authenticity with the issuing authority.

This distinction matters. The programme was not conducting an open-ended referendum on continental legitimacy. It was applying a defined documentary test. Political support had to arrive in a recognised form, from an appropriate authority and at the required level. General endorsement, public advocacy or an applicant’s confidence in its constituency could not replace the prescribed documents.

ZA Central Registry’s Initial Evaluation report dated 12 July 2013 recorded an overall pass. The Geographic Names Panel found that the submitted support or non-objection documentation met the applicable criteria.

That pass was decisive for programme eligibility, but it should not be enlarged beyond its institutional function. It established that the evaluator regarded the application as compliant with the Guidebook’s geographic test. It did not resolve every criticism of the process through which governmental support had been assembled. It did not amount to a universal finding that one organisation embodied the political will of every African government or community.

DotConnectAfrica’s ordinary evaluation path was initially interrupted by the Board’s implementation of GAC advice. After the IRP, the application returned to evaluation. The resumed Initial Evaluation report dated 13 October 2015 is therefore central to understanding what the accountability victory did and did not accomplish.

The report did not reject DotConnectAfrica as technically or financially incapable of operating a registry. It recorded passing results in the technical, operational and financial portions of the evaluation. The unresolved failure concerned the geographic-name support or non-objection requirement. DotConnectAfrica remained eligible to enter Extended Evaluation, where it could clarify or supplement the relevant material.

The Extended Evaluation report dated 17 February 2016 found that the deficiency had not been cured. The required documentation had not been provided in a form that satisfied the geographic-name rules. The application therefore became ineligible for further review within the evaluation track.

The failure was narrow in subject but fatal in effect. A proposal that passed technical and financial review could not remain eligible for this particular geographic string without satisfying the governmental-documentation requirement.

This is where the procedural and substantive parts of the case separate. The IRP reopened the gate that ICANN had previously closed through a defective process. It did not change the standard inside the gate. It did not lower the 60 per cent threshold, convert general political arguments into signed non-objection documents or instruct the Geographic Names Panel to record a pass.

The rival contract survived because ZA Central Registry’s evaluation result had not been vacated. DotConnectAfrica’s restored opportunity could have altered the contention set only if its application also became eligible. Once Extended Evaluation ended in failure, there was no second qualified application requiring an auction, settlement or other contention-resolution step between the two applicants.

The IRP restored access to evaluation. Evaluation did not produce eligibility.

Early Warning, GAC advice and Board action were distinct interventions

Governmental opposition to DotConnectAfrica moved through several channels that are often compressed into a single “government objection”. The compression obscures who had authority to do what.

The first channel was the GAC Early Warning process. Ghana’s Early Warning was a governmental submission identifying public-policy concerns about DotConnectAfrica’s application and supporting the African Union Commission and ZA Central Registry position.

An Early Warning was consequential but not dispositive. It signalled political risk and could encourage an applicant to withdraw, respond or seek accommodation. Under the Applicant Guidebook, it was not a formal rejection and was not a prerequisite for later GAC advice. The applicant could continue despite the warning, accepting the risk that the concern might later acquire greater institutional force.

The second channel was the Governmental Advisory Committee’s 11 April 2013 consensus objection advice. The advice identified DotConnectAfrica’s application and stated that it should not proceed.

Consensus GAC advice against an application carried a strong procedural presumption under the Guidebook. That presumption made the advice substantially more powerful than an individual Early Warning. It still did not make the GAC the contracting or delegation authority. The GAC did not assign an evaluation score, sign a Registry Agreement or transmit a root-zone request.

The third intervention was the programme decision. On 4 June 2013, the New gTLD Program Committee, exercising delegated Board authority over the programme, accepted and implemented the relevant GAC advice. It determined that DotConnectAfrica’s application should not be approved.

The sequence was therefore governmental warning, consensus advisory action and then a Board-level programme decision. The political input mattered because the NGPC converted it into an operative application consequence.

This segmentation later became central to the IRP. The panel did not need to deny that governments had concerns or that the GAC had reached consensus. It examined whether the Board had discharged its own obligations when deciding what to do with that advice. A strong presumption did not eliminate the Board’s duties of fairness, transparency and due inquiry.

The GAC channels must also be distinguished from the new-gTLD programme’s formal objection procedures. A formal objection would have initiated a separate dispute-resolution process with designated standing, filing rules, grounds and adjudicators. Public comment, an Early Warning, consensus GAC advice and a formal objection were not interchangeable routes.

The later IANA readiness report recorded that no formal objection had been filed against ZA Central Registry’s application. The record relied upon here does not show that a formal dispute-resolution objection supplied the operative basis for stopping DotConnectAfrica. That basis was the GAC advice and the NGPC’s decision to implement it.

The difference is practical. Public comment enables participation. An Early Warning identifies governmental risk. Consensus GAC advice creates a Board-facing presumption. A formal objection invokes an adjudicative procedure. The effect belongs to the institution controlling the relevant route, not to the general intensity of opposition.

Reconsideration did not supply an unrestricted merits appeal

DotConnectAfrica challenged the NGPC decision through Reconsideration Request 13-4.

The Board Governance Committee’s recommendation dated 1 August 2013 addressed the asserted grounds and recommended denial. On 13 August, the NGPC adopted that recommendation.

Reconsideration was not an unlimited rehearing of the application. Under the rules then in force, it addressed specified claims that staff action had contradicted established policy or that Board action had failed to consider material information, or had relied on false or inaccurate material information.

The Board Governance Committee concluded that DotConnectAfrica had not established the necessary grounds. It found that the request did not identify the kind of specific material omission or inaccurate information required to reverse the NGPC decision. It also treated consultation with an external expert as discretionary rather than mandatory.

That conclusion did not establish that the original process was beyond criticism. The later IRP reached the opposite institutional assessment on the adequacy of ICANN’s inquiry. The two outcomes can coexist because the mechanisms had different standards, decision-makers and remedial capacities.

Reconsideration was an internal and rules-bounded review. The IRP examined whether Board action and inaction conformed to the higher-order obligations in ICANN’s Articles and Bylaws. Access to both mechanisms did not make them equivalent, and filing either one did not automatically suspend every downstream act.

A party seeking to preserve the possibility of a different operator needed interim protection directed at the stage about to become harder to reverse. By the time the IRP was under way, ZA Central Registry’s application was continuing towards contracting.

Contract signature changed the object at risk

ZA Central Registry’s evaluation pass allowed it to advance while DotConnectAfrica pursued the IRP. On 24 March 2014, ICANN and ZA Central Registry signed the .AFRICA Registry Agreement.

The agreement did not itself delegate the string. Pre-delegation testing, Board authority, root-zone processing and other readiness requirements remained. Nevertheless, signature materially changed the dispute. ZA Central Registry was no longer only a rival applicant with a favourable evaluation result. It had become ICANN’s contractual counterparty for the proposed registry.

Before contracting, a remedy could preserve a contention set by stopping the rival application from moving to agreement. After contracting, a different operator outcome would require consideration of the signed legal relationship as well as the application records.

The public materials do not support an assumption that the Registry Agreement was automatically suspended, tolled or made terminable under a specific clause merely because delegation later stopped. Reaching a conclusion on those issues would require the full agreement correspondence and amendment history. The verified facts are more limited: the agreement was executed; delegation did not immediately follow; and neither the IRP Final Declaration nor the Board’s implementation decision expressly rescinded the contract.

DotConnectAfrica sought interim protection during the IRP. The accountability docket records that it requested interim measures in March 2014. On 12 May 2014, the panel directed ICANN to refrain from further processing the .AFRICA applications while the review continued.

That intervention protected the still-unimplemented root-zone outcome. It did not undo the agreement signed several weeks earlier.

The difference illustrates a recurring asymmetry in institutional remedies. A pause can preserve time without assigning rights. It can stop the next act while leaving existing evaluation and contractual positions in place. If the challenger later fails the merits test to which it is restored, the rival’s paused route can resume without a new agreement having to be created.

Contracting therefore changed the remedy landscape even though it did not complete delegation. The durable object was already waiting downstream when the IRP reached judgment.

The IRP found a serious process failure, not an operator entitlement

The 9 July 2015 Final Declaration should be read neither as a symbolic consultation nor as an award of .AFRICA.

The panel examined the Board’s acceptance of unexplained GAC consensus advice, the absence of a reasoned GAC record, the handling of DotConnectAfrica’s reconsideration request and the extent of the Board’s own inquiry. It concluded that the Board should at least have investigated further before using the advice as the basis for stopping the application.

The panel also considered the lack of advance notice and a meaningful opportunity for DotConnectAfrica to respond before the consensus position was reached. It found that the subsequent reconsideration process had not repaired the deficiency.

Its dispositive conclusion was that Board action and inaction had been inconsistent with ICANN’s Articles and Bylaws. This was a genuine accountability judgment. It was not a finding of intentional misconduct or bad faith, and it did not convert the IRP panel into the geographic evaluator.

The panel did not find that DotConnectAfrica had already met the 60 per cent support threshold or supplied compliant documentation. It did not invalidate ZA Central Registry’s Initial Evaluation result. It did not decide that the claimed African Union Commission appointment was unlawful. Having reached the central conclusion about ICANN’s process, it found it unnecessary to decide every additional allegation.

DotConnectAfrica had sought consequences that would have materially strengthened its position, including removal of ZA Central Registry from contention, continuation of its own application and additional time or accommodation concerning governmental endorsements. The panel did not grant those outcomes. It did not award the string, disqualify the rival applicant or create an 18-month entitlement to reconstruct the support file.

The authority of the Final Declaration requires careful wording. The panel treated an IRP declaration on consistency with the Articles and Bylaws as binding, and the Board accepted and implemented the decision. Yet the paragraph setting out the practical next steps used the language of recommendation: ICANN should continue to refrain from delegating .AFRICA and should permit DotConnectAfrica to proceed through the remainder of the application process.

The distinction later became relevant in court, where the federal judge identified serious questions about the relationship between a binding inconsistency determination and the recommendation governing corrective action. For the institutional chain, however, the central boundary is clear. The panel could authoritatively determine that ICANN’s conduct was inconsistent and could identify corrective steps. It did not itself execute a contract cancellation, replace the proposed registry operator or send a delegation request to the root-zone implementer.

On 16 July 2015, the Board adopted an implementation resolution. It continued the non-delegation position, authorised DotConnectAfrica’s application to return to the established evaluation process and provided the cost relief specified by the Final Declaration.

The Board recorded US$4,600 in administrative fees, US$403,467.08 in panel costs and US$198,046.04 to reimburse DotConnectAfrica for its share of those costs. Each party remained responsible for its own legal fees. The financial allocation confirmed that DotConnectAfrica had prevailed in the accountability proceeding.

The same resolution made clear that the restored process did not predetermine contracting or delegation. No final determination had been made that DotConnectAfrica would clear evaluation and advance to an agreement.

The Board did not cancel ZA Central Registry’s contract. Instead, it corrected the exclusion identified by the panel by returning DotConnectAfrica to the process from which it had been removed. That response was narrower than the political outcome DotConnectAfrica sought, but it tracked the institutional wrong actually established.

The IRP had found that the Board had stopped the application without the inquiry required by ICANN’s constitutive obligations. The remedial implementation was to conduct the omitted process. A direct transfer of the string would have required substantive findings about eligibility and legal action against a rival contract that the panel had not supplied.

This was the remedy gap in its most concrete form. Review invalidated the quality of the earlier decision but did not establish the substantive fact DotConnectAfrica needed in order to prevail. It reopened a procedure without guaranteeing its outcome. It preserved non-delegation without removing the agreement that could later support delegation.

Resumed evaluation supplied process, then closed the application

The Board’s implementation decision became operational when DotConnectAfrica’s application returned to evaluation in September 2015.

The 13 October Initial Evaluation report shows that the restored process was not simply ceremonial. The evaluators examined the application across the ordinary technical, operational, financial and geographic categories. DotConnectAfrica passed the technical, operational and financial components. It did not pass the geographic-name documentation requirement, but it remained eligible for Extended Evaluation.

Extended Evaluation gave the applicant a further opportunity to address that criterion. It did not substitute a new standard or allow general assertions of legitimacy to replace the required governmental documents.

On 17 February 2016, the Extended Evaluation report concluded that the required support or non-objection documentation had still not been demonstrated. DotConnectAfrica became ineligible for further review in that evaluation track.

The sequence closes an important causal gap. ICANN did not move directly from losing the IRP to delegating the string to the rival. It maintained the pause, restored DotConnectAfrica to Initial Evaluation, allowed the application to proceed into Extended Evaluation and waited for the geographic test to be completed.

Only after the application failed that test did the Board release the next stage of ZA Central Registry’s path.

On 3 March 2016, the Board adopted Resolution 2016.03.03.01. It authorised the President and Chief Executive Officer to proceed with delegation of .AFRICA to ZA Central Registry pursuant to the existing Registry Agreement.

The source of authority was explicit. The Board authorised further processing, and it did so through the contractual relationship that had survived the IRP and resumed evaluation.

That decision did not erase the accountability finding. It represented the state of the chain after the ordered corrective process had run its course. DotConnectAfrica had regained access but had not regained substantive eligibility. ZA Central Registry’s evaluation pass and contract remained operative.

The 2021 appellate opinion later recorded that DotConnectAfrica chose not to pursue another reconsideration or IRP directed at the Extended Evaluation result before turning to court. A complete independent audit of every ICANN accountability docket has not been conducted for this article, so that judicial account should not be expanded into a broader claim about every possible submission. The verified operational point is that no later accountability determination identified in IANA’s readiness assessment barred delegation.

By March 2016, the remaining route capable of stopping performance was judicial.

Federal and state courts could hold the chain without selecting the registry

DotConnectAfrica filed its lawsuit in California state court in January 2016, before Extended Evaluation had formally concluded. The action was removed to federal court in February. The litigation introduced a body with coercive authority that the IRP panel did not possess: a court could issue an injunction binding ICANN and prevent the next programme act.

The federal court entered temporary relief in March. On 12 April 2016, it issued a preliminary injunction restraining ICANN from delegating .AFRICA while the case continued.

That order was operationally powerful. ICANN could not lawfully complete delegation while the injunction remained effective. It was nevertheless interlocutory. The court identified serious questions and weighed the threatened harms and public interest at a preliminary stage. It did not finally determine that DotConnectAfrica was entitled to the string.

The injunction did not direct ICANN to contract with DotConnectAfrica. It did not invalidate ZA Central Registry’s evaluation pass or assign a passing geographic score. It did not instruct IANA to install a different proposed manager. Its function was negative: preserve the status quo until the legal claims could be addressed.

ZA Central Registry then sought to intervene. On 19 October 2016, the federal court allowed intervention and remanded the case. It concluded that ZA Central Registry was an indispensable party to claims that threatened its contractual interest. Because the intervenor was not diverse from DotConnectAfrica, the required federal diversity jurisdiction was absent and the matter returned to California state court.

The precise continuing effect of every federal interlocutory order after remand requires an order-by-order analysis and should not be inferred from summary descriptions alone. The subsequent state proceedings show that DotConnectAfrica sought renewed protection and did not obtain a continuing restraint.

On 22 December 2016, the California Superior Court denied a motion for preliminary injunction. DotConnectAfrica then sought further emergency relief. On 4 January 2017, the court denied the requested temporary restraining order and treated the filing as a further request for preliminary relief.

The renewed motion was denied on 3 February 2017. The court found that DotConnectAfrica had not made a sufficient showing of likely success on the merits and that the balance of interim harms favoured denial. It regarded the applicable covenant not to sue as likely enforceable, considered the costs and disruption facing ZA Central Registry, and concluded that the public-interest balance did not justify another injunction.

The order also treated possible later re-delegation as relevant to the assessment of irreparable harm. Whether re-delegation would have been simple in practice is a separate operational question. At the preliminary stage, the court did not regard immediate delegation as an injury that required preservation of the existing restraint.

The court sequence demonstrates both the reach and the limit of judicial power. A federal judge had been able to stop the chain. State judges could decide whether that restraint should be recreated or continued. Once renewed relief was denied, however, the courts had not substituted DotConnectAfrica as the programme winner or altered the Registry Agreement.

Litigation continued after delegation. In August 2017, the Superior Court granted ICANN summary judgment on some claims but allowed other causes of action to continue. The ruling was partial, not the final disposition of the case.

The remaining dispute eventually turned on judicial estoppel. DotConnectAfrica had argued during the IRP that the Applicant Guidebook’s covenant not to sue prevented it from obtaining judicial relief, a position that supported its request for robust IRP treatment. In court, it then sought to proceed with claims that the earlier position had said were unavailable.

Following a bifurcated trial, the Superior Court entered a final judgment in October 2019 based on judicial estoppel. The court concluded that DotConnectAfrica could not obtain the advantage of one position in the IRP and then pursue an incompatible position in litigation.

The California Court of Appeal affirmed on 20 September 2021. It held that the trial court had acted within its discretion in applying judicial estoppel. The appellate court regarded the IRP as sufficiently quasi-judicial, found the positions inconsistent and concluded that DotConnectAfrica had obtained procedural advantages from its earlier stance. It also rejected the argument that a separate finding of subjective bad faith was indispensable.

That judgment is the principal endpoint of the litigation aftermath. It did not authorise the 2017 delegation retroactively. .AFRICA had already entered the root more than four years earlier. The delegation authority came from the cleared new-gTLD process, ZA Central Registry’s surviving contract, the Board’s March 2016 decision and the absence of a continuing injunction in February 2017.

IANA implemented the approved package rather than rehearing the dispute

After the 3 February 2017 state-court order, the upstream conditions for delegation were aligned.

ZA Central Registry had passed evaluation. DotConnectAfrica was no longer an eligible application in the contention set. The Registry Agreement remained in force. The Board had authorised delegation processing. No surviving court order identified in the operational record prohibited performance.

The IANA String Delegation Readiness Report was completed on 10 February 2017. It recorded “Readiness Confirmed” for application 1-1243-89583 and treated the relevant programme stages as prerequisites rather than questions to be adjudicated again.

The checklist recorded the geographic-name review, technical and financial evaluation, contention outcome, existence of the Registry Agreement and completion of pre-delegation testing. It stated that no formal objection had been filed against ZA Central Registry’s application, that no consensus GAC advice required that application not to proceed and that no accountability determination prevented contracting or delegation.

IANA’s function at this stage was confirmatory and operational. It did not reopen the political question of continental representation. It did not reweigh government support letters or revisit whether the Board’s conduct in 2013 had been fair. Those issues had been assigned to other bodies and had produced their respective outcomes.

Several February dates describe different parts of the implementation record and should not be collapsed.

The current IANA Root Zone Database entry gives 11 February 2017 as the registration date for .AFRICA. The IANA delegation report, dated 14 February, records that the applicant matched the contracted party, the required contacts and technical processing were complete, and ZA Central Registry was the approved proposed manager.

The Root Zone Management Audit Data for February 2017 records the .AFRICA change request as completed on 15 February 2017. That audit entry provides the most precise authoritative date in the examined record for completion of the operational root-zone change. It is distinct from readiness confirmation, database registration and publication of the delegation report.

The sequence therefore ran from readiness on 10 February, through the database registration date of 11 February and the delegation report on 14 February, to recorded root-zone implementation or closure on 15 February.

IANA did not decide which applicant deserved the string. It received an authorised package naming ZA Central Registry and determined that the package was ready to execute. No institution with authority over the agreement, Board decision or delegation instruction had replaced that operator.

This is the final boundary in the remedy chain. The IRP had already answered whether ICANN’s earlier process was consistent with its constitutive obligations. The Geographic Names Panel had answered whether DotConnectAfrica’s restored application met the support-documentation test. The Board had decided whether the surviving agreement could proceed. The courts had decided whether interim coercive restraint should remain. IANA implemented the result of those upstream determinations.

What the record proves, and what it does not

The public record supports a detailed institutional chronology.

It establishes that two standard applications competed for .AFRICA. It shows that ZA Central Registry passed Initial Evaluation and that DotConnectAfrica was stopped after consensus GAC advice was accepted by the NGPC. It records the denial of Reconsideration Request 13-4, the signing of ZA Central Registry’s Registry Agreement while the IRP was pending, and the IRP panel’s conclusion that ICANN’s handling of DotConnectAfrica had been inconsistent with the organisation’s Articles and Bylaws.

It shows that the Board maintained non-delegation, reimbursed the specified review costs and restored DotConnectAfrica to evaluation. It records that DotConnectAfrica passed the technical, operational and financial components but failed the geographic support or non-objection criterion in Extended Evaluation. It shows the Board’s subsequent authorisation to proceed under ZA Central Registry’s existing agreement.

The court record documents a federal preliminary injunction, intervention and remand, the denial of renewed state-court relief, partial summary judgment, a final judgment based on judicial estoppel and the 2021 appellate affirmance. The IANA record then establishes readiness, delegation processing and completion of the root-zone change in February 2017.

Several wider claims remain outside what those materials can prove.

The applicant and governmental submissions do not independently establish the legal validity or exclusivity of the African Union Commission appointment process. That would require the underlying official procurement, selection or mandate record from an authoritative African Union or governmental archive.

The published evaluation reports do not disclose the complete support and non-objection letters, every clarification exchange or a document-by-document account of evaluator authentication. They support the recorded pass and failure, not an independent reconstruction of how each claimed endorsement was weighted.

The available materials do not justify presenting every asserted governmental-support total as an audited count. The complete set of .AFRICA Early Warnings and support letters would need to be assembled before identifying which governments made independent submissions, which used common language and which totals can be verified without relying on an interested participant’s assertion.

Procedural labels must remain distinct. A public comment was not an Early Warning. An Early Warning was not consensus GAC advice. Consensus GAC advice was not a formal objection ruling. The IANA readiness report establishes that no formal objection was filed against ZA Central Registry; the complete objection database would be needed for a definitive statement about every possible formal route involving DotConnectAfrica.

The contract record proves execution and continued existence. It does not, without the complete correspondence and amendment history, establish whether the parties invoked any express suspension, tolling, waiver or implementation clause during the IRP and litigation pauses. Non-delegation alone does not prove activation of a particular contractual mechanism.

The litigation record establishes the practical sequence of restraint and release. A definitive account of the legal survival of each federal order after remand would require a complete order-by-order analysis. The secure conclusion is narrower: DotConnectAfrica sought renewed state-court protection, the requested relief was denied, and no continuing injunction identified in the delegation record prevented the February 2017 change.

The 2021 opinion records that DotConnectAfrica declined further internal review of the Extended Evaluation outcome. Without an independent audit of all ICANN accountability filings, that account should be attributed rather than expanded into an absolute statement that no further submission of any kind was made.

These limits do not weaken the central conclusion. They prevent political claims, institutional self-description and procedural inference from being treated as established authority.

A procedural victory without custody of the downstream instruments

DotConnectAfrica’s IRP victory was real. It established that ICANN’s Board could not rely on unexplained GAC consensus advice as a complete substitute for its own obligations of fair, transparent and sufficiently diligent decision-making.

The finding produced concrete effects. Delegation remained paused. DotConnectAfrica was returned to the application process. ICANN paid the specified review costs. The application received technical, operational, financial and geographic evaluation rather than being terminated solely through the earlier Board action.

The victory did not supply the substantive result required for DotConnectAfrica to become the registry. It still had to satisfy the geographic-name support and documentation rules. It did not. ZA Central Registry’s evaluation pass and Registry Agreement remained in place.

The courts could stop performance, and for a period the federal court did. The injunction created real operational protection but no entitlement to the string. Once renewed relief was denied, no court order replaced the proposed operator or invalidated the contract.

IANA then implemented a package that had survived the preceding institutional gates.

The case therefore sets a disciplined boundary around ICANN accountability. A review mechanism can expose procedural failure and reopen a closed gate. It does not necessarily control the substantive test applied inside that gate, the contract beyond it or the technical actor at the end of the chain.

A different operator outcome required a remedy that reached at least one of those downstream instruments: preservation of DotConnectAfrica’s substantive eligibility, suspension or rescission of ZA Central Registry’s agreement, a continuing judicial prohibition on performance, or an authorised root-zone instruction naming a different manager.

None occurred.

The institutional lesson is not that procedure was irrelevant. Procedure stopped delegation for years and restored an application that had been improperly excluded. The lesson is that a procedural finding changes the final outcome only when the resulting remedy reaches the legal or operational object that makes the outcome executable.