Summary

A review winner, a contracted operator and an empty root

On 9 July 2015, DotConnectAfrica Trust became the prevailing party in an ICANN Independent Review Process. It did not become the operator of .AFRICA. ICANN had already entered a registry agreement on 24 March 2014 with ZA Central Registry NPC trading as Registry.Africa, but the string was still absent from the DNS root. Three institutional facts therefore existed at once: DCA had won an accountability review; ZACR held a contract with ICANN; and no registry yet held operational control through delegation.

That combination is the organising fact of the case. Governance disputes are often compressed into a contest in which a tribunal selects a winner and transfers the disputed asset. The .AFRICA record does not support that model. The Governmental Advisory Committee could issue advice. The African Union Commission and national governments could express support, opposition and regional policy preferences. Programme evaluators could decide whether an application satisfied the Applicant Guidebook. The ICANN Board and its delegated committee could convert advice and evaluation outcomes into organisational action.

An Independent Review Process panel could test Board action and inaction against ICANN’s constitutive rules. ICANN could enter and administer a registry agreement. Courts could grant or deny interim restraints and adjudicate pleaded legal claims within their jurisdiction. The IANA naming-functions process and the root-zone maintainer could verify and implement an authorised root-zone change. None of those powers was identical to the others.

The final IRP declaration was consequential. It declared that the Board’s actions and inactions concerning DCA’s application were inconsistent with ICANN’s Articles and Bylaws and declared DCA the prevailing party. The future course was framed as a recommendation: continue to refrain from delegation and return DCA’s application to the remainder of the new-gTLD process. One week later, the Board resolved to keep .AFRICA undelegated, resume evaluation and reimburse DCA US$198,046.04 in IRP costs, while each side remained responsible for its own legal representation fees and other expenses.

The same Board action identified the limit. Reopening the application was not a final determination that DCA would reach contracting or delegation. It did not erase the GAC’s advice. It did not cancel ZACR’s agreement. It did not deem DCA compliant with the geographic-support criterion. It did not instruct IANA to place DCA in the root. DCA had regained a protected opportunity to be evaluated through the process that the 2013 decision had cut short. It had not acquired a registry franchise.

The difference is operational. An application is a claim submitted to a rule-bound evaluation process. A registry agreement is a contract between ICANN and a named operator. Delegation is an authorised technical change to the root zone that makes the top-level domain operational under a sponsoring organisation. The IRP restored movement in the application process. It neither displaced the existing contract nor executed a root-zone change.

Regional preference had to enter through programme rules

The institutional conflict began before either application could prevail. African intergovernmental and ministerial bodies had treated a continent-wide top-level domain as an entity of regional policy. A communiqué from an African ICT ministers’ round-table in Dakar on 21 October 2011 promoted a Dot Africa project and asked ICANN to reserve .Africa and related language variants for a structure selected and identified by the African Union. That position carried political weight. It did not itself allocate the string under ICANN’s 2012 application programme.

ICANN’s answer drew the boundary. In a March 2012 letter to the African Union Commission, Board chair Steve Crocker said ICANN could not depart from the community-developed, documented programme rules to confer special treatment. He pointed instead to the recognised channels inside the programme: the geographic-name support requirements, GAC Early Warnings and advice, and formal objection procedures. Regional preference therefore had to be converted into instruments the programme knew how to receive. The AUC could support an applicant. National governments could provide support, non-objection or objection. The GAC could advise the Board. None could directly sign ICANN’s contract or instruct the root-zone system.

The June 2012 Applicant Guidebook made those instruments especially important for .AFRICA. Because the string appeared on the Guidebook’s list of continental or regional geographic names, an applicant had to document support or non-objection from at least 60 per cent of the relevant national governments and could face no more than one written objection from relevant governments or public authorities. The rule was an eligibility criterion to be assessed in evaluation, not a general political endorsement contest whose result could be inferred from a communiqué.

Governmental influence also entered through the GAC. An Early Warning notified an applicant of governmental concern but was not itself a formal objection or rejection. Consensus GAC advice that an application should not proceed had greater practical force: under the Guidebook it created a strong presumption for the Board that the application should not be approved. Yet the GAC still did not become ICANN’s awarding authority. The Board retained ultimate responsibility for the programme and remained accountable for how it converted advice into action.

Formal authority and practical influence were therefore different. The GAC advised and the Board decided, but consensus advice against an application could approach dispositive force because of the Guidebook’s strong presumption. The IRP did not hold that governments were barred from using that channel. It held that the Board could not treat the weight of the advice as a substitute for its own diligence, judgement and responsibility under ICANN’s Articles and Bylaws.

Nor can these instruments be collapsed into one category called “endorsement”. An AUC policy position, a national support letter, a national objection, a GAC Early Warning and consensus GAC advice arose from different actors and carried different procedural effects. A continental preference could be strong and coherent without possessing every legal and procedural element required to select, contract with and delegate to a registry operator.

The 2012 design separated advice, evaluation, Board action, contract and delegation

The Applicant Guidebook did not establish a single award decision. It established a sequence. Applications were checked for completeness and moved through Initial Evaluation, with Extended Evaluation available for certain deficiencies. Objections and accountability procedures could intervene. Surviving applications for the same string could remain in contention. A successful applicant then moved towards contracting, transition work, pre-delegation testing and a delegation request. Only after the downstream checks and authorisations could the root zone be changed.

A favourable outcome at one gate did not decide every later gate. Technical capability did not prove geographic support. Passing evaluation did not by itself resolve contention. Signing a registry agreement did not change the root. Completing technical testing did not authorise IANA to substitute an uncontracted applicant. An accountability review could reopen a defective Board decision without becoming a geographic-names evaluator, contracting authority and root-zone change mechanism at once.

Actor Authority in the .AFRICA chain Limit or review point
African Union Commission and national governments Express regional policy, support, non-objection or objection; provide documents relevant to the geographic-name criterion Could not allocate the string outside the Guidebook, sign ICANN’s agreement or order a root-zone change
Governmental Advisory Committee Issue Early Warnings and consensus advice to the Board Advice had exceptional weight but did not itself constitute ICANN Board action or delegation
Programme evaluators Apply the Guidebook’s geographic, technical, operational and financial criteria Did not determine whether Board conduct complied with ICANN’s Articles and Bylaws
New gTLD Program Committee and ICANN Board Act on GAC advice, direct processing, authorise programme outcomes and contracting or delegation steps Bound by ICANN’s Articles, Bylaws and programme rules; exposed to accountability review and litigation
Independent Review Process panel Compare challenged Board action or inaction with ICANN’s constitutive rules; declare consistency or inconsistency and recommend a future course under the then-governing Bylaws Did not operate as evaluator, contracting party, contention mechanism or root-zone implementer
ICANN and a registry operator Execute and administer a registry agreement Contracting created legal interests but did not itself insert the string into the root
Courts Grant or deny interim relief and decide legal claims within jurisdiction and with affected parties before them Preliminary relief preserved or released the status quo; it was not a merits award of the string
IANA naming-functions operator and root-zone maintainer Verify an approved request and implement the authorised root-zone change Did not choose between applicants or retry the Board’s governance decision

The Board was the hinge in this distribution. GAC advice could create a strong presumption, but the Board converted that advice into an ICANN decision. Evaluators answered criteria assigned to them, but the Board controlled the programme consequences. The IRP therefore examined an entity within Board responsibility: whether action and inaction concerning DCA’s application conformed to ICANN’s Articles and Bylaws. The natural target of the remedy was the Board-controlled decision path, not the technical root zone.

A review mechanism can therefore matter without controlling the final operational result. Review access supplies a forum and a standard. A practical remedy also requires authority to preserve the disputed entity, reopen a decision, allocate costs or restrain implementation. The .AFRICA IRP produced several of those effects, but it did not combine the powers needed to choose a registry operator, create a contract and implement a root-zone change.

How GAC advice became a Board-level stop in 2013

The GAC’s Beijing Communiqué of 11 April 2013 recorded consensus objection advice against DCA’s .AFRICA application, number 1-1165-42560. The communiqué did not provide an application-specific rationale explaining why the committee had reached that position. ICANN notified the affected applicant and allowed the Guidebook’s response period. That opportunity came after the GAC had reached consensus; it was not the pre-decision notice and chance to be heard that the IRP later identified as missing. On 4 June 2013, the New gTLD Program Committee, exercising authority delegated by the Board, adopted its response to the GAC’s Beijing advice and accepted the advice that DCA’s application should not proceed.

The GAC had not itself terminated an ICANN application. The NGPC’s acceptance converted governmental advice into an organisational consequence, and evaluation of DCA’s application was halted before the normal programme path had reached a final merits result on every criterion.

DCA first used ICANN’s internal reconsideration route. It filed Request 13-4 on 19 June 2013; the Board Governance Committee recommended denial on 1 August, and the NGPC adopted that recommendation on 13 August. The final IRP declaration later treated the handling of reconsideration as part of the Board-level inconsistency, concluding that the BGC was required to conduct a meaningful review rather than merely rest on the earlier decision path. Reconsideration supplied review access, but it did not reverse the stop or restore evaluation.

DCA filed its notice of Independent Review on 24 October 2013. The filings collected on ICANN’s DCA v ICANN materials page contain many allegations about the two applicants, the AUC, the GAC and ICANN personnel. Those allegations are part of the record, but they are not interchangeable with the panel’s findings. Party submissions state contested claims. The final declaration states what the panel decided. Board resolutions state what ICANN later implemented. Court orders state what judges decided under a different body of law.

While the IRP was pending, ICANN moved further with ZACR. The official .AFRICA Registry Agreement page gives an agreement date of 24 March 2014. At an 8 April signing ceremony, ICANN said the agreement allowed .AFRICA to proceed towards delegation. The future tense was accurate. The contract established a relationship between ICANN and ZACR and gave ZACR a direct interest in the process, but further programme and technical acts still stood between the contract and the root.

That existing contract made interim relief more important. In its 12 May 2014 decision on interim measures, the IRP panel directed ICANN to refrain from further processing any .AFRICA application while the merits review continued. The measure did not transfer the string to DCA and did not rescind ZACR’s agreement. It preserved the institutional position so that the final review would not arrive after the disputed string had already become operational.

The standstill demonstrates the difference between a right to complain and a remedy capable of protecting the complaint’s entity. A declaration issued after delegation could still matter, but the costs and dependencies of reversal would be greater. By pausing further processing, the panel protected the possibility of correction. It did not decide who would ultimately benefit from that possibility.

The GAC remained active while the pause was in place. Its June 2014 London Communiqué reiterated that DCA’s application should not proceed, welcomed the NGPC’s earlier acceptance of the advice and urged the Board to move expeditiously towards delegation under ZACR’s agreement once the IRP permitted. That was a clear governmental position. It was still advice to the Board, not evidence that delegation had already occurred or that the IRP had lost authority over the Board decision under review.

What the IRP panel actually found

The final declaration filed on 9 July 2015 applied a de novo, objective and independent review to Board conduct under ICANN’s constitutive rules. The panel did not merely ask whether individual Board members had acted with subjective honesty. Nor did it retry every factual controversy raised by DCA. It examined whether the Board’s actions and inactions concerning the application were consistent with ICANN’s Articles and Bylaws.

The panel’s central concern was not that the GAC lacked permission to oppose DCA. Governments could express a collective position about a continent-wide string, and the Guidebook expressly gave consensus advice exceptional weight. The defect lay in the Board’s handling of that advice. The GAC supplied no application-specific rationale, and the Board did not investigate further before allowing the advice to end DCA’s application path. The panel also relied on the fact that DCA had received no notice or opportunity to state its position before the GAC reached consensus, and that the Board had taken no steps to address that problem.

Its criticism extended to reconsideration: the Board Governance Committee was required to conduct a meaningful review, not merely repeat the assumptions of the original decision path.

The finding exposed a structural weakness. Advice may be formally non-binding yet practically decisive. If a strong presumption is treated as self-executing, the advisory body acquires the practical effect of a decision-maker without assuming the procedural burdens attached to the final decision. The IRP placed those burdens back on the Board. The Board could agree with the GAC, but agreement had to remain a Board act supported by the diligence, independent judgement and accountability ICANN’s rules required.

This is the difference between participation and control. Governments participated through national support and objection letters, through the AUC’s regional position and through the GAC. Their influence was substantial. The Board controlled ICANN’s response. The IRP did not deny the legitimacy of governmental participation. It enforced the obligations attached to the institution that converted that participation into an adverse programme result.

The declaration also separated transparency from accountability. Publication of a communiqué told observers that GAC consensus existed. It did not disclose an application-specific rationale or demonstrate that the Board had tested the basis for relying on the advice. Transparency makes the occurrence of an act visible. Accountability requires a forum able to compare the responsible decision-maker’s conduct with governing standards and attach a consequence to non-compliance. DCA obtained the latter: a formal declaration of inconsistency, protection against immediate delegation and a route back into evaluation.

The panel did not adopt DCA’s entire account of the dispute. It expressly declined to determine who was correct about every other criticism, alleged conflict or claimed irregularity in the competing application process. It made no finding that ICANN or the AUC had preselected ZACR. It did not decide the geographic-support merits, grant DCA extra time to gather governmental support or treat its existing materials as satisfying the threshold. The process finding was serious, but bounded.

Finding and remedy answered different questions. The panel declared that Board action and inaction had not conformed to ICANN’s Articles and Bylaws. Its recommended course was to preserve the undelegated string and allow DCA’s application to continue through the programme. Neither proposition answered which applicant had earned the right to operate .AFRICA.

The remedy restored an application, not an operating right

DCA won an institutional correction and a protected opportunity. The final declaration recommended that ICANN continue to refrain from delegating .AFRICA and permit DCA to proceed through the remainder of the new-gTLD process. It declared DCA the prevailing party and allocated the panel, provider and related IRP costs to ICANN, while leaving each party to bear its own legal fees and other expenses.

Those consequences had practical force. Delegation could not continue as though the review had failed. The application returned to evaluation. ICANN bore the specified review costs and reimbursed DCA US$198,046.04. The Board had to revisit an application that its delegated committee had halted. Yet the protected entity remained the application and the decision path around it. The declaration did not supply a contract, pre-delegation test results, contention resolution or an approved root-zone request.

The identity of the constrained authority followed from the claim. The panel reviewed action and inaction attributable to the Board, including the NGPC’s exercise of delegated Board authority. Its declaration therefore bore on the Board and on ICANN staff implementing Board programme directions. ICANN could pause delegation, order evaluation to resume, pay costs and decide how to re-engage with the GAC. Those were acts within the organisation’s control.

The declaration granted none of the additional acts that an operational award would have required. It did not direct the GAC to withdraw or rewrite its advice, require the AUC or national governments to issue new support letters, tell an evaluator to overlook a Guidebook criterion, declare ZACR’s contract void or instruct IANA to list DCA. Those entities remained with the institutions authorised to create, assess, cancel or implement them.

The wording of the declaration fixes the boundary. The panel formally declared inconsistency and separately recommended the future course authorised by the then-governing IRP provisions: continued non-delegation and resumption of DCA’s application. The Board accepted that result and translated it into programme instructions. The declaration did not purport to give the panel the separate powers of an evaluator, contracting party or root-zone operator.

That distinction also explains why ZACR’s agreement survived the declaration. The agreement was already part of the record, and the panel had protected the status quo against delegation. It did not declare the agreement void, order rescission or substitute DCA as contracting party. A remedy directly cancelling the agreement would have affected ZACR’s contractual interests, not merely ICANN’s internal compliance with its Articles and Bylaws. Later litigation would make the party and jurisdiction problems attached to such relief explicit.

The Board’s 16 July 2015 implementation preserved later gates

The Board resolutions adopted on 16 July 2015 provide the clearest account of what the IRP changed inside ICANN. The Board resolved that ICANN would continue to refrain from delegation, that DCA’s application would proceed through the remainder of the programme and that DCA would receive the specified cost reimbursement. It directed the chief executive to resume established evaluation processes as quickly as practicable.

At the same time, the Board stated that it was not making a final determination that DCA’s application should proceed to contracting or delegation. It also said that resuming evaluation was not, at that point, an action inconsistent with the GAC’s advice. The Board would ask the GAC whether it wished to refine the advice, provide further information or address the concerns identified in the declaration. If DCA later passed evaluation, the Board would consider the GAC’s position and other material circumstances again, using the Bylaws process required if the Board contemplated action inconsistent with GAC advice.

The response reopened the defective path without erasing the other gates. The Board did not pretend the GAC’s position had never existed, but the advice no longer operated as the immediate stop on evaluation. It stayed in the record; its programme effect would have to be reconsidered by the Board if DCA passed evaluation.

Measured against the declaration, the Board implemented the recommended standstill, remand and cost allocation while withholding merits relief the panel had not granted. It left in place the programme’s remaining tests and the legal interests created by ZACR’s agreement. A process defect was not proof that DCA satisfied every substantive rule.

Compliance required reversal of the immediate effect of the 2013 decision, a return to the published process and protection against premature delegation. It did not require the Board to waive the Guidebook, ignore the GAC or strip a third party of contractual rights without an authorised procedure. The practical force of the remedy came from its fit with the wrong the panel had decided.

Resumed evaluation produced a distinct substantive failure

ICANN resumed evaluation on 1 September 2015. The Initial Evaluation report dated 13 October 2015 shows why the division of authority mattered. DCA passed assessments concerning DNS stability, registry services, technical and operational capability, and financial capability. Its string-similarity result left it in contention rather than eliminating it. The application did not, however, pass the Geographic Names evaluation.

The Geographic Names Panel concluded that DCA had not supplied support or non-objection documentation satisfying the Guidebook’s criteria for a continent or United Nations region. The overall Initial Evaluation status was therefore eligible for Extended Evaluation, not a final programme termination. DCA chose that route. The Extended Evaluation report dated 17 February 2016 again found the supporting material limited public evidence under the geographic-name rule and recorded the application as ineligible for further review or evaluation.

That result was not a revival of the 2013 GAC stop. It was a new decision made by an evaluator applying a substantive programme criterion that the IRP had not waived. The distinction matters even though both routes ended unfavourably for DCA. The earlier Board-level act relied on unexplained GAC advice in a manner the IRP found inconsistent with ICANN’s constitutive obligations. The later evaluator issued a criterion-specific determination after the application had been restored to the programme.

The later failure also does not make the earlier process defect harmless. The point of the remedy was that DCA should receive the institutional act the 2013 route had displaced: evaluation under the published requirements. The result supplied a criterion-specific basis and separated favourable findings on technical and financial capability from the adverse geographic-support finding. A claimant may lose after a fairer process without the original denial becoming lawful retrospectively.

The opposite overstatement is equally unsound. Passing technical and financial assessments did not establish that DCA was otherwise the rightful operator deprived only by politics. For a continent-wide string, geographic support was part of eligibility. Technical competence and political legitimacy were not substitutes for one another under the Guidebook. The IRP did not rank the criteria or empower the panel to remove one.

The next institutional decision arrived quickly. At its 3 March 2016 meeting, the Board recorded the resumed evaluation sequence, the 17 February Extended Evaluation result and DCA’s resulting ineligibility for further evaluation. It then authorised the chief executive to proceed with delegation of .AFRICA to ZACR under the 24 March 2014 registry agreement. Downstream readiness and naming-function checks still had to be completed, and judicial restraint could still block implementation. The Board therefore did not move directly from the 2014 contract to a 2017 root entry: the IRP remedy, resumed evaluation and a new Board authorisation intervened.

ICANN’s archived DCA application record describes application 1-1165-42560 as terminated, ineligible for further review and not having prevailed in contention. Those labels record the endpoint reached after the IRP restored the application; they should not be read backwards as though the 2015 declaration had never occurred. The corresponding ZACR application record records the opposite programme outcome: Initial Evaluation passed, contention prevailed and delegation completed.

A useful counterfactual lies inside the Board’s July 2015 resolutions. Had DCA passed the geographic evaluation, the Board would still have had to confront the continuing GAC advice. It might have followed the advice again, but would have done so with the panel’s concerns, a developed evaluation record and its own accountability duties in view. It might instead have considered acting inconsistently with the advice and entered the required Board-GAC consultation process. The IRP secured that conditional accountability. DCA’s substantive failure prevented the condition from becoming a claim to contracting or delegation.

The 2014 agreement was neither delegation nor a nullity

The ZACR agreement is the point at which public discussion most readily collapses separate acts. The .AFRICA Registry Agreement page identifies ZA Central Registry NPC trading as Registry.Africa as the registry operator and gives 24 March 2014 as the agreement date. The contract created contractual obligations and gave ZACR a direct legal interest in any proposed remedy that would cancel or displace it. It did not place the string in the root.

It did not complete delegation. ICANN’s April 2014 signing announcement said the agreement allowed the string to proceed to delegation. Under the Applicant Guidebook, transition activities and pre-delegation testing still stood between contracting and an eligible delegation request. The IRP standstill then prevented the process from moving through those stages while review continued.

Nor was the agreement automatically void because DCA prevailed in the IRP. The panel declared a Board process failure and protected the status quo, but it did not order rescission. The July 2015 Board resolutions acknowledged both the final declaration and the existing contract while keeping delegation paused. Contracting and delegation were separate enough for those facts to coexist: ZACR could hold a contract without controlling the root, while DCA could hold a successful accountability declaration without holding the contract.

The unusual interim position was institutionally coherent. DCA held a restored application. ZACR held the agreement. ICANN controlled programme administration but was constrained from delegation. Evaluators controlled the substantive criterion assigned to them. Root-zone actors had no authorised change to implement. The conflict could not be resolved by treating any one of those facts as the entire case.

Courts could restrain implementation, but not ignore parties or jurisdiction

After the Extended Evaluation failure and the Board’s 3 March 2016 authorisation, DCA sought judicial relief. Courts applied a different remedial framework from the IRP. They were not comparing Board conduct with ICANN’s Articles and Bylaws under the accountability provisions. They had to consider causes of action, contractual terms, likelihood of success, irreparable harm, the balance of hardships, public interest, jurisdiction and the rights of parties affected by the requested relief.

On 12 April 2016, the United States District Court for the Central District of California granted DCA a preliminary injunction preventing ICANN from delegating .AFRICA while the federal case proceeded. Applying the Ninth Circuit’s sliding-scale approach, the court found serious questions concerning DCA’s claim that ICANN was required to follow the IRP result, together with likely irreparable harm, a sharply favourable balance of hardships and a public interest in preserving review before delegation. The court expressly found the binding effect of the IRP’s remedial recommendation unclear at that stage. Its account of the application record was provisional and drew in part on allegations and evidence presented for the injunction. The operative effect was an interim bar on delegation, not a merits award of the string.

The court did not finally decide that ICANN had breached an enforceable obligation. The injunction prevented the operational step that would have made later relief harder; it did not substitute a judicial selection of DCA for ICANN’s programme decision.

The federal proceedings then exposed the party problem attached to DCA’s attempt to nullify ZACR’s agreement. In an order dated 19 October 2016, the District Court permitted ZACR to intervene as of right with respect to the claim seeking to set aside the registry agreement. Because ZACR was a party to the contract and would be directly affected by its nullification, the court held it indispensable to that claim. DCA and ZACR were both foreign citizens, so ZACR’s participation destroyed complete diversity and the federal court remanded the action for lack of subject-matter jurisdiction.

The holding was narrower than saying ZACR was indispensable to every dispute between DCA and ICANN. The court granted intervention as of right for the contract-nullification claim and denied the requested intervention as to another claim. The point remains significant: a remedy against an existing registry agreement could not be treated as a purely internal correction involving only DCA and ICANN. Once the requested relief reached ZACR’s contract, ZACR’s right to be heard altered the forum’s jurisdiction.

After remand, the Los Angeles Superior Court considered another request to prevent delegation. On 3 February 2017, it denied the motion for a preliminary injunction. The court concluded that the balance of interim harms favoured denial and that DCA had not made a sufficient evidentiary showing of likely success on the merits. It treated important parts of DCA’s claimed interim harm as speculative, credited evidence of ZACR’s continuing costs, and noted that re-delegation could remain available if DCA ultimately prevailed. The order therefore removed the immediate judicial barrier without purporting to decide every underlying claim.

Timing then became decisive. The state order was filed on 3 February 2017. IANA’s root database gives .AFRICA a registration date of 11 February. Its delegation report followed on 14 February. Once the preliminary restraint ended, ICANN and the naming-functions machinery could complete the separate operational process for the contracted applicant.

The litigation continued after delegation. A California trial court entered final judgment for ICANN on 3 October 2019, ordering that DCA take nothing and dismissing its claims with prejudice. The California Court of Appeal affirmed on 20 September 2021. Its opinion described the remedial boundary directly: the IRP put DCA back into the contest by resuming consideration; it did not award the string. The affirmance rested on judicial estoppel arising from DCA’s inconsistent positions about the application covenant not to sue, not on a judicial reversal of the panel’s 2015 process finding.

The sequence neither erases nor enlarges the IRP. The federal injunction showed that a court could temporarily preserve the status quo when its equitable test was satisfied. Intervention showed that cancellation of ZACR’s contract required the affected contracting party. Remand showed that jurisdiction limits even a court willing to hear serious questions. The state denial showed that preservation ends when the legal test for interim relief is not met. Final judgment showed that winning an ICANN accountability proceeding does not guarantee success on later contractual and tort claims.

Enforcement can also be described more accurately after this sequence. The IRP panel did not hold the root-zone console, but its decision produced institutional effects. ICANN paused delegation, resumed evaluation and reimbursed the specified costs. Courts then controlled whether the pause would continue through injunctions. The fact that DCA never received the string is not proof that the review went unenforced. It reflects the scope of the relief, the later substantive evaluation and the separate legal tests applied by courts.

Delegation in February 2017 was a separate operational act

The IANA delegation report published on 14 February 2017 records the final operational stage. It states that eligibility had been established, the delegation applicant matched the approved and contracted party, administrative and technical contacts were confirmed, technical conformance checks were completed, and the required new-gTLD processing and readiness work had been performed. The proposed sponsoring organisation was ZA Central Registry NPC trading as Registry.Africa.

Those checks did not reopen the IRP’s constitutional analysis or retry DCA’s support documents. That was not the naming-functions operator’s role. IANA verified that the request presented through the new-gTLD programme corresponded to the party approved and contracted by ICANN and that the administrative and technical conditions for a root change were satisfied. The root-zone maintainer then implemented the authorised change under the post-stewardship-transition maintenance arrangements.

The naming-functions operator and maintainer did not select ZACR over DCA. Their authority began after evaluation, Board action and contracting had supplied an eligible request. They could verify and implement that request; they could not infer an alternative instruction from DCA’s accountability victory. Technical neutrality depended on that separation. Root-zone actors followed an authorised chain rather than deciding which claimant had the better political or procedural case.

IANA’s .AFRICA database entry lists ZACR trading as Registry.Africa as the sponsoring organisation and gives 11 February 2017 as the registration date. The record is evidence of the observed operational outcome. It is not evidence that every earlier step was flawless. The 2015 finding of Board inconsistency and the 2017 delegation to ZACR can both be true because they answer different institutional questions.

The public lesson is remedial scope, not symbolic victory or ownership

DCA’s victory mattered because it established that the weight of GAC advice did not relieve the Board of responsibility for its own action. A consensus communiqué could create a strong presumption, but the Board still had to exercise diligence and independent judgement under ICANN’s rules. The declaration produced consequences: a standstill, a reopened application and a substantial allocation of review costs to ICANN.

The victory did not decide the ultimate allocation of .AFRICA. Evaluation later determined that DCA had not met the geographic-support rule. The Board then authorised delegation steps for ZACR. Courts applied their own standards to interim restraint, jurisdiction, affected parties and the merits of later legal claims. Once judicial restraint ended and the programme conditions were satisfied, IANA verified and implemented the root-zone change.

The separation is the only reliable way to identify power. The GAC’s influence was strong but advisory. The AUC’s regional policy role was politically consequential but not contractual. The Board’s authority was broad but reviewable. The IRP’s declaration was authoritative within its accountability function but was neither a registry agreement nor a root-zone instruction. ZACR’s contract created rights and obligations but was limited public evidence by itself for delegation. IANA’s act was decisive for DNS operation but downstream of applicant selection.

Courts could restrain the chain, yet only within jurisdiction and with affected parties before them.

The IRP was neither a total award nor empty symbolism. It did not give DCA .AFRICA, but it delayed delegation, reversed the immediate programme effect of the 2013 decision, restored evaluation and shifted specified review costs to ICANN. Those were observable governance outcomes even though the claimant did not obtain the operational prize.

An accountability mechanism should be judged by the entity it can reach. The 2015 IRP reached Board compliance and the application process the Board controlled. It did not assemble every authority required to establish eligibility, resolve the remaining governmental and contention questions, create a registry contract and implement a root-zone change. DCA won a declaration of inconsistency and a restored opportunity. ZACR later emerged from the separate contract-to-delegation chain as the sponsoring organisation. Collapsing those propositions turns a remedial-scope precedent into a false ownership story.