ICANN's AFRINIC Correspondence: Oversight Claim or Contractual Opinion?

Summary

• ICANN's mission and the 2024 ICP-2 implementation procedures support a narrow inquiry when the security and stability of unique Internet number identifiers may be at risk. They do not create an unlimited power to run an AFRINIC election or replace Mauritian corporate law.
• The 2025 letters mixed several different legal and institutional acts: expressing concern, asking questions, preserving evidence, signalling a possible compliance review, suggesting electoral safeguards, and seeking relief from a Mauritian court. Each act had a different source and a different degree of force.
• ICANN itself eventually said that its election proposals were not directives and that it was neither membership-based nor an election specialist. That qualification should govern how the earlier, firmer language is read.
• A legitimate review should identify the exact criterion engaged, the facts relied upon, the response and cure period, the boundary between registry continuity and corporate control, and the route by which any binding consequence could lawfully occur.
• The practical test is not whether ICANN was entitled to care. It plainly was. The test is whether a particular demand was advisory, procedural, contractual, judicial, or locally enforceable, and whether the addressee and affected operators could tell the difference.

One correspondence chain, several kinds of power

The hardest question in ICANN's 2025 correspondence with AFRINIC is not whether the risks were serious. AFRINIC had spent years under litigation, board dysfunction, receivership and contested electoral administration. A registry responsible for number-resource services across an entire region cannot treat the integrity of its records, the continuity of allocations or the legitimacy of its governing body as private housekeeping. ICANN, the other regional registries and network operators all had rational reasons to watch closely.

The harder question is what each letter did. Public debate often compresses every intervention into one of two slogans. In the first, ICANN is the global overseer and therefore can instruct a troubled regional registry. In the second, ICANN is an outsider and therefore can do no more than offer an opinion. Neither description survives a close reading of the instruments.

A letter can express a stability concern without creating an obligation. It can request information under an established assessment procedure. It can give notice that a formal review may begin. It can preserve a litigation position. It can propose safeguards that the receiver is free to accept or reject. It can also place facts before a domestic court, after which any coercive force comes from the court's jurisdiction and order rather than from ICANN's stationery. Those acts differ in source, scope, process and remedy.

That separation matters because institutional language travels. A phrase such as “we call upon” may be understood by one reader as diplomacy, by another as a threat to recognition status, and by a third as a direction that must be obeyed. In a crisis, ambiguity can become leverage. The responsible approach is therefore an authority map: identify the instrument, the clause, the trigger, the decision-maker, the procedural safeguards and the consequence for every material request.

The timeline begins before the most visible letters

The public letters of 2025 arrived after a prolonged institutional breakdown, not at the first sign of difficulty. AFRINIC's governance crisis had already involved litigation, the loss of a functioning board and court-appointed administration. The Number Resource Organization had publicly told the African Internet community in July 2022 that it stood ready to help while also stating that regional registry policy and activity were in the hands of that regional community. That 2022 NRO message is important not because its institutional self-description settles the law, but because it records a baseline: assistance was presented as support to AFRINIC, not as an announced transfer of control.

The rulebook also changed while the crisis continued. The original 2001 Internet Coordination Policy 2, or ICP-2, was primarily a framework for recognizing new regional Internet registries. In December 2024, ICANN's Board ratified implementation procedures designed to assess continuing compliance with those recognition criteria. The procedures gave ICANN a defined route to examine a limited risk to the secure and stable coordination of unique identifiers. They also imposed notice, evidence and review disciplines that are easy to lose when public statements use broad oversight language.

By March 2025, ICANN was asking about registry records, customer information, backups and election eligibility. In June it moved into increasingly specific public requests about the election. It then sought relief in a Mauritian court. Later letters posed detailed questions, asked for evidence preservation and reserved a right to initiate an ICP-2 review. In July, ICANN clarified that its election suggestions were not directives.

This sequence is more revealing than any isolated sentence. It shows an institution moving among at least four roles: technical coordinator, recognition assessor, concerned stakeholder and litigant. The legitimacy of one role does not automatically enlarge the others.

ICANN's mission is a boundary as well as a mandate

The ICANN Bylaws give ICANN a mission in the coordination of unique Internet identifiers. For Internet Protocol numbers and autonomous system numbers, that includes coordination at the top of the hierarchy and global registry services requested by the regional registries and the Internet Engineering Task Force. The Bylaws also contemplate facilitation of global number-resource policy and other tasks agreed with the regional registries.

Those provisions explain why ICANN is not a random commentator. A collapse in the integrity of a regional number registry can affect the global uniqueness, traceability and continuity of number-resource administration. ICANN's IANA function allocates unallocated number pools to regional registries. The Address Supporting Organization also sits inside ICANN's governance architecture. Concern about records, recognition and continuity therefore falls within a real institutional relationship.

But the mission language is also restrictive. ICANN is not supposed to act outside its mission. Coordination at the top level is not the same thing as general supervision of every corporate decision made by a regional registry. A power to maintain a global registry or assess recognition criteria does not silently become a power to decide which members may vote, which nomination committee should sit, how proxies should be authenticated or when a domestic receiver should certify an election.

The distinction is familiar in public administration and contract law. A body may have responsibility for a system-wide outcome yet possess only specified tools over an autonomous entity. Responsibility does not erase legal personality. AFRINIC remained a Mauritian corporation with members, constitutional documents, contracts and court supervision. ICANN remained a California nonprofit with a defined global coordination mission. Any bridge from one legal sphere to the other had to be built by an instrument, consent or judicial order.

The ASO arrangement coordinates policy; it is not a general management charter

The 2019 ICANN Address Supporting Organization memorandum describes how the Number Resource Organization performs the ASO role. It allocates responsibilities for global number-resource policy, recognition recommendations and appointments within ICANN. That arrangement is a major constitutional link between ICANN and the regional registries.

It is still a limited link. The memorandum does not read like a corporate-management agreement under which ICANN may administer an individual registry's elections. Its central subjects are global policy development, the ASO Address Council, recognition of regional registries, appointments and related coordination. Even where disputes under the arrangement may be arbitrated, the existence of a dispute mechanism does not create an unstated substantive command power.

This matters when correspondence invokes “oversight” without naming its entity. ICANN has oversight responsibilities within its own organization and contractual relationships. It has an assessment role in the recognition framework. It participates in a coordination compact with the NRO. None of those statements, standing alone, answers whether ICANN can direct a court-appointed receiver administering a Mauritian company's election.

The correct legal question is narrower: did the letter exercise a right contained in the ASO arrangement, invoke the ICP-2 procedures, ask for voluntary cooperation, or request a domestic court to exercise its own powers? If none of those descriptions fits, the intervention may be influential but not binding. Institutional importance can make an opinion consequential. It does not make the opinion self-executing.

Recognition in 2005 supplies history, not a perpetual blank cheque

AFRINIC's path to recognition provides useful evidence about the relationship. The IANA report recommending AFRINIC's recognition in 2005 assessed the proposed registry against ICP-2 principles. It recorded regional support, governance arrangements, technical capability, a migration plan for existing service relationships and backup arrangements. It recommended that AFRINIC be recognized as the regional registry for Africa.

That history establishes several things. Recognition was conditional in a meaningful sense: AFRINIC was evaluated against criteria concerning community support, neutrality, technical competence, recordkeeping and service. The migration was not merely a symbolic declaration. Existing arrangements had to be transferred in a planned manner, with coordination among the incumbent registries and the new organization. Continuity and backup were present from the start.

The report does not establish a permanent, free-standing power for ICANN to direct all later corporate affairs. It is a recognition assessment, not a deed vesting ICANN with AFRINIC's voting rights. Nor does it identify network operators as having contracted directly with ICANN for regional registry service. The operators' service and membership relationships remained principally with AFRINIC.

This is why historical recognition should be used carefully. It supports ICANN's interest in whether the recognized institution continues to meet the criteria. It also shows that transition of service relationships is a substantive event requiring planning, communication and operational preparation. It does not support the inference that recognition alone authorizes any measure ICANN believes useful during a governance dispute.

ICP-2 changed from an entry standard into a continuing assessment framework

The original ICP-2 text focused on the criteria and process for recognizing a new regional Internet registry. It was supplementary to the ASO relationship and designed around an application. Over time, the regional registry system treated many of its criteria as continuing expectations. Yet expectations are not the same as a specified enforcement process.

The 2024 implementation and assessment procedures sought to make that process more explicit. They translate criteria into continuing requirements concerning community support, open and impartial policy processes, equal service, legal compliance, nonprofit status, technical capability, records, confidentiality, auditability and continued adherence. They also provide review triggers and procedural stages.

The most important ICANN-initiated trigger is narrow. ICANN may initiate a review when it reasonably believes there is a risk to the secure and stable coordination of unique Internet identifiers. The review must be limited to the circumstances creating that belief; it is not supposed to become a broad audit of general compliance. The procedures call for notice, supporting material, access to information, assessment, draft findings and an opportunity to correct factual errors.

They include emergency treatment for critical circumstances and, if restoration is not possible, coordination with the remaining registries around an emergency service provider.

This instrument gives ICANN something stronger than a commentator's interest. It gives ICANN a procedural role. But the same text that grants the role limits it. A request tied to record integrity, backups or secure number coordination may fit. A demand about election architecture must show how the alleged defect creates the specified identifier risk and which continuing criterion it implicates. The procedure cannot be expanded merely by attaching the vocabulary of stability to every governance disagreement.

The Board's ratification notice acknowledges what was not yet covered

The ICANN Board's December 2024 ratification notice is unusually important because it describes the limits of the procedures. The Board said they were intended to implement existing ICP-2 obligations rather than add new substantive obligations or intrude upon reserved policy processes.

Most importantly, the notice stated that formal derecognition and transition procedures were not covered and would require policy development. That is not a drafting footnote. It separates assessment from the ultimate restructuring of service. A finding that an institution is at risk does not itself answer who may replace it, how contracts move, which records may be handed over, or what rights affected resource holders possess.

For the 2025 letters, this means ICANN could legitimately ask questions linked to a possible limited review. It could preserve its ability to use the procedures. It could not treat the mere possibility of review as an already completed decision, and it could not rely on those procedures as a complete code for corporate intervention or permanent service transition.

The notice also rebuts two extremes. It rebuts the claim that ICANN had no relevant procedural authority at all. And it rebuts the claim that ratification made ICANN the all-purpose regulator of AFRINIC. The actual position is more disciplined: a defined assessment power existed; the transition architecture remained incomplete; domestic corporate and court authority continued to matter.

The 7 March letter was strongest on records and continuity

ICANN's 7 March 2025 letter to the AFRINIC receiver discussed the continuation of number-resource work, election eligibility and the need to maintain accurate registry records, including protected customer information. It asked about alignment with ICP-2 and regular backups.

The recordkeeping and backup concerns have a clear connection to the 2024 procedures. Registry integrity is not abstract corporate etiquette. If allocations, assignments, contacts, route-authorisation data or entitlement histories are lost or corrupted, uniqueness and operational continuity may be impaired. Criteria concerning technical capability, auditability, confidentiality and records provide an identifiable basis for questions.

The election aspect requires a finer line. A legitimate governing body is relevant to continuing community support and organizational capacity. A receiver's treatment of membership records can also affect whether the entity remains open, impartial and accountable. ICANN could therefore ask how the election would restore stable governance and protect registry records.

That does not mean every view about election eligibility became an enforceable instruction. The letter should be read as a combination of technical concern, information request and institutional opinion unless it expressly invokes a procedural step and satisfies that step's requirements. The addressee needed to know whether ICANN was asking for voluntary reassurance, giving formal review notice, asserting a contractual right or warning of a future determination. Where the letter left those categories blended, its persuasive force exceeded its legal clarity.

The 6 June announcement moved from inquiry toward election design

ICANN's 6 June 2025 public announcement called for transparency concerning the entry of members into the Consolidated Members Register Database, reconstitution of the nomination committee and a public assessment of remedial steps. It framed these requests through ICANN's responsibility for the stable operation of unique identifiers and top-level number coordination.

Transparency about the member register could have a direct evidentiary link to continuing criteria. If the registry's voting body is built from inaccurate, selectively admitted or inaccessible records, community support and institutional independence may be impaired. A public explanation may be a sensible remedy. Reconstituting a nomination committee, however, is a more specific corporate intervention. Its legal source cannot be assumed from the general importance of the election.

One possibility was voluntary compliance: ICANN, as a globally important counterparty, could recommend a reset. Another was a limited ICP-2 review: ICANN could state the risk, identify the criteria, notify AFRINIC and assess the response. A third was Mauritian relief: a court supervising the receiver could direct steps under local law. These routes have different safeguards. A recommendation can be declined. A review has notice and finding stages. A court application requires jurisdiction, standing and judicial decision.

The announcement's forceful language blurred those routes. It was understandable advocacy in a deteriorating situation, but advocacy should not be mistaken for proof of authority. The more specific the requested corporate remedy, the more important it was to name the legal bridge.

The court proceeding exposed the difference between concern and coercion

ICANN then went to a Mauritian court. Its 20 June 2025 announcement said the court required the receiver to communicate with members. The same account reported that the court found ICANN had no standing to enter the application in the manner attempted, even while recognizing the objective and making directions of its own.

That combination is analytically valuable. It shows that the domestic court did not simply treat ICANN's global coordination role as automatic local standing. The court assessed its own jurisdictional rules. Any binding direction to the receiver came from the court, not from the earlier ICANN announcement. At the same time, a standing defect did not prevent the court from considering information or acting within its supervisory authority where it thought action appropriate.

The episode therefore supports neither absolutist position. It does not show that ICANN's concern was irrelevant. It also does not show that ICANN's letter had direct coercive effect. It shows an institutional concern translated into local legal effect only through an independent decision-maker.

This is the model that should guide interpretation of the correspondence. ICANN could alert, document, request and, where procedurally available, review. If it wanted the receiver compelled under Mauritian law, it needed a valid local route and a court order. If it wanted to alter recognition status, it needed the ICP-2 process. If it wanted AFRINIC voluntarily to adopt an electoral safeguard, it could explain the request and its consequences without calling the request a directive.

The 25 June letter mapped allegations to compliance criteria

The 25 June 2025 letter was more detailed. It referred to reported voting-registration problems, alleged fraudulent powers of attorney, access to the member list and the suspension of voting. It asked a series of questions and connected potential concerns to provisions of the 2024 procedures, including community support, equal service, impartiality, independence, open membership and recordkeeping.

That criterion-by-criterion mapping was an improvement in legal clarity. It began to answer the question that broad mission statements cannot: which continuing recognition condition might be affected by which reported fact? It also made visible that some claims remained allegations. A letter repeating a report is not a factual finding, and a mapping to a criterion is not proof that the criterion was breached.

The distinction matters particularly for proxy fraud and member-list disputes. Such allegations can be grave, but they require verified evidence, a definition of the relevant membership rights and an opportunity for the affected institution and individuals to respond. The ICP-2 procedures provide for fact gathering and correction precisely because a global consequence should not rest on a contested public narrative.

The letter also expressed firm opposition to certification of the existing result. As a governance recommendation, that position was intelligible. As a binding command, its source remained uncertain. The correspondence would have been stronger if it had separated three paragraphs explicitly: facts requiring verification; formal information requested under a named procedure; and nonbinding recommendations pending a lawful domestic decision.

Criteria are not conclusions, and concerns are not findings

Institutional assessments often fail in the space between a criterion and a conclusion. “Community support” is a criterion. It does not tell the assessor how much support is enough, which population counts, or how to distinguish a temporarily divided membership from durable loss of legitimacy. “Impartiality” is a criterion. It does not automatically establish that every disputed administrative decision was partial. “Recordkeeping” is a criterion. It does not prove that every inconsistency threatens the uniqueness of number resources.

A defensible review must therefore disclose the inferential chain. What happened? Which evidence supports it? Which requirement applies? How does the event create a risk to secure and stable coordination? What less intrusive correction is available? What fact would change the conclusion? Without those steps, criteria can become labels attached to a preferred outcome.

The 2024 procedures partly guard against this problem. They contemplate limited scope, supporting information, draft findings and correction of factual errors. Those safeguards should be treated as substantive disciplines, not formalities. A letter that signals possible review should not front-load the final conclusion or use the threat of an emergency determination to bypass ordinary verification unless the emergency threshold is genuinely met.

There is also a legitimacy reason for restraint. AFRINIC's members and resource holders must be able to distinguish a recognized global standard from an interpretation advanced by one institution in a live dispute. Publishing the criterion, evidence and reasoning allows them to contest an interpretation without pretending that stability is unimportant.

The 3 July preservation request was procedural, not a verdict

ICANN's 3 July 2025 letter reserved ICANN's rights to initiate a review, asked that relevant material be preserved and returned to earlier questions about recordkeeping, backups and escrow. A preservation notice has a different character from a direction about election outcome.

Where a possible assessment or court dispute is foreseeable, asking the custodian not to destroy records is proportionate. Registry records, membership data, voting material and technical backups may be needed to determine what occurred and whether continuity is at risk. Preservation can protect all sides by keeping the evidentiary record available.

Yet preservation is not adjudication. It does not prove misconduct, establish noncompliance or authorize a service transfer. The phrase “reserves rights” is equally limited. It signals that ICANN may rely on an available procedure later. It does not mean that the procedure has already been initiated or completed.

The letter's questions about escrow were more directly connected to continuity. But even there, the response should distinguish backup existence, backup accessibility, lawful custody and authority to use the backed-up information. A copy can be technically recoverable while its activation remains legally constrained. The presence of data in escrow is not itself permission for another institution to assume the full registry relationship.

The 16 July clarification should control the reading of election proposals

The 16 July 2025 open letter contains the most important qualification in the chain. ICANN said its election ideas should not be considered directives to AFRINIC. It also acknowledged that ICANN is not membership-based and is not an election expert.

Those sentences do not erase the earlier pressure. Nor do they prevent ICANN from assessing whether governance failures create a stability risk. They do, however, settle the proper legal category for the election proposals: recommendations, not self-executing commands. If a receiver adopted them, the receiver needed authority from AFRINIC's constitutional arrangements, the court order or Mauritian law. If a court required them, the court supplied coercive force. If ICANN later made a recognition finding, the ICP-2 procedure supplied that separate consequence.

The open letter also repeated claims about particular companies and actors. Those statements must be treated as attributed positions in a contested dispute, not neutral findings merely because they appeared in official correspondence. The relevant analytical question is not which side told the more vivid story. It is whether the evidentiary and procedural route was adequate for the consequence sought.

The clarification is therefore more than diplomatic softening. It restores a necessary institutional boundary. ICANN can be a technically informed assessor and an interested advocate without becoming AFRINIC's electoral authority.

An authority matrix makes the differences visible

The correspondence can be evaluated through a simple matrix:

Act	Plausible source	Legal character	Necessary limit
Express concern about continuity	ICANN mission and institutional interest	Persuasive statement	Must not be presented as a binding local order
Ask about records, backups and technical integrity	ICP-2 continuing criteria and limited-review provisions	Information request or possible review step	Must identify scope, risk and requested evidence
Preserve relevant evidence	Anticipated review or litigation	Procedural request; potentially reinforced by court	Must be proportionate and protect confidential data
Suggest election safeguards	Institutional expertise and stakeholder influence	Nonbinding recommendation	Corporate or judicial authority must support implementation
Initiate a compliance review	2024 ICP-2 procedures	Formal assessment power	Notice, narrow trigger, evidence, response and factual correction
Direct the receiver under Mauritian law	Mauritian court or valid local corporate authority	Binding domestic act	Jurisdiction, standing and due process
Change recognition status or arrange emergency service	ICP-2-related decision and still-developing transition rules	System-level consequence	Transparent criteria, defined service scope and affected-party safeguards

The matrix explains why “oversight claim or contractual opinion” is not a binary. Some parts of the chain were opinions. Some were requests within an institutional compact. Some pointed toward a formal recognition assessment. One route sought judicial action. None should borrow authority from another without saying so.

“Contractual” is useful shorthand but not a complete legal description

It is tempting to describe ICANN's position as contractual because the regional registry system is held together by memoranda, recognition arrangements and repeated commitments. That description captures part of the architecture but can mislead if it suggests a conventional bilateral contract between ICANN and every AFRINIC member or resource holder.

The ASO memorandum links ICANN and the NRO. The NRO memorandum links the regional registries. AFRINIC joined the NRO arrangement. ICP-2 supplies recognition criteria and procedures. AFRINIC's own membership and service agreements govern many direct rights of members and operators. Domestic law governs the corporation and receiver. These instruments overlap, but they do not merge into a single contract with one all-powerful enforcer.

The question “what is the contractual source?” should therefore be answered with precision. If ICANN relies on a memorandum, cite the clause and explain the remedy. If it relies on recognition procedures, call the act an assessment step rather than a contractual direction. If it relies on AFRINIC's promises to its own members, explain how ICANN has standing to enforce them. If the answer is voluntary cooperation, say so.

This precision protects ICANN as much as AFRINIC. A narrow, well-founded intervention is more credible than an expansive claim vulnerable to jurisdictional challenge. The institution does not need to pretend that every recommendation is binding in order to have influence.

The NRO memorandum limits delegated representation

The NRO memorandum adds another boundary. It creates coordination among the regional registries and permits collective operational and external activities on matters delegated under the agreement. Major undertakings and commitments depend on the participating registries' written or unanimous agreement. The document also says it does not create a partnership or agency and restricts assignment of interests, rights or obligations without the signatories' consent.

Those clauses matter because the NRO often speaks collectively and performs the ASO role. Collective voice is not the same as general agency over every registry. The executive council can represent the registries on specifically delegated subjects. It cannot assume that a regional registry's corporate rights, member contracts or operational obligations have been assigned merely because a crisis exists.

For ICANN correspondence, the NRO structure confirms the need to identify the route. ICANN may receive collective advice from the other registries. The other registries may unanimously request an ICP-2 review under the 2024 procedures. But the NRO compact does not by itself make ICANN the corporate principal of AFRINIC or make the remaining registries owners of AFRINIC's service relationships.

This is not an argument against cooperation. It is an argument that cooperation gains legitimacy when it stays within the delegation actually given.

IANA coordination is essential but sits at a different layer

The IANA number-services description states that IANA allocates blocks from unallocated global pools to the regional registries. The registries then distribute number resources under regional policies. IANA does not ordinarily make allocations directly to African network operators.

That hierarchy explains both ICANN's concern and its limitation. If a regional registry cannot maintain accurate records or receive top-level allocations, the global coordination system is affected. ICANN can reasonably investigate whether the recognized interface remains reliable. But IANA's position above the regional layer does not make ICANN a party to every downstream service agreement.

The IANA informational booklet also emphasizes that IANA implements rather than invents or interprets policy. Regional communities develop regional allocation policy, while the NRO monitors IANA's performance. In other words, the system distributes authority in both directions. ICANN coordinates a global uniqueness function; regional registries and communities retain regional policy and service responsibilities.

Any reading of the letters should preserve that architecture. A top-level coordinator can insist on reliable interfaces and assess recognition conditions. It cannot infer unlimited downstream governance power from the fact that the hierarchy has a top.

Mauritian corporate authority did not disappear during the Internet dispute

AFRINIC's institutional importance does not remove it from the law of its place of incorporation. The receiver's powers, the status of the board, membership rights, election administration and court supervision all depend materially on Mauritian law and orders. Global coordination instruments can influence what outcome is operationally acceptable, but they do not silently displace the domestic legal framework.

This dual character creates genuine difficulty. A domestic court can make a decision valid under local law that other registry institutions view as threatening technical continuity. Conversely, a global coordinator can identify a system risk without possessing standing to direct the domestic process. Neither sphere should pretend the other does not exist.

The practical solution is translation between authorities. ICANN should state the technical risk and the recognition criterion. AFRINIC or the receiver should state the local authority under which it can respond. If compulsion is necessary, a properly constituted court should decide within its jurisdiction. If recognition consequences are contemplated, ICANN should use the assessment procedure. If emergency service is considered, the transition mechanism must disclose its separate authority and safeguards.

The 2025 court episode demonstrated that this translation is not ceremonial. Standing, jurisdiction and the source of the order changed who could lawfully require what.

Members, resource holders and operators do not occupy identical positions

The letters frequently discussed membership and voting. Yet the population dependent on AFRINIC is not limited to voters. Some resource holders are members with formal governance rights; others may have different contractual statuses. Network operators rely on allocations, registration services, route-authorisation functions and contact records whether or not they can shape the election directly. Internet users experience the downstream effects without any direct institutional vote.

That diversity should affect both review design and rhetoric. “The community” is not a single principal capable of giving one undifferentiated instruction. An election may establish the corporation's board, while service contracts establish operational rights, and the recognition framework establishes system-level conditions. One constituency cannot automatically consent for all the others.

ICANN's correspondence was strongest when it asked whether records and services remained reliable for affected users. It was weaker when broad community language obscured which legal constituency had the relevant right. A member-register dispute should be analyzed through membership law and the organization's constitution. A continuity concern should include resource holders and operators. A recognition review should apply the published criteria. A court application should satisfy local standing and procedure.

Separating those constituencies is not fragmentation for its own sake. It prevents a majority in one forum, or an institution speaking for an undefined public, from inadvertently extinguishing rights held elsewhere.

A narrow review is more defensible than an election veto

Suppose ICANN reasonably believed that disputed voting records, proxy handling and an unstable receiver process threatened the accuracy of the registry or the restoration of capable governance. The 2024 procedures offered a defensible next step: open a limited review, state the facts giving rise to the belief, identify the relevant criteria, request evidence and permit a response.

That approach would not have guaranteed a quick result. It would, however, have produced an auditable distinction between allegation and finding. It could have asked whether the register used for voting corresponded to the operational customer and membership records, whether privileged access occurred, whether backups were complete, and whether the proposed board could lawfully govern. Those are testable questions.

A categorical election veto asserted only through public correspondence is harder to justify. It reaches deeply into corporate governance and may affect the rights of candidates and voters who were not responsible for the underlying crisis. If such a remedy is necessary, the decision-maker should identify its authority, show why narrower measures fail and provide a route for challenge.

The principle is proportionality, not passivity. The greater the intervention, the clearer the instrument and process must be.

Emergency language should not collapse ordinary safeguards

The ICP-2 procedures recognize that some circumstances may be critical and incapable of timely cure. That is sensible. Unique number coordination cannot wait for a perfect governance settlement if core records are disappearing or essential registry services are about to fail.

Emergency clauses are also vulnerable to expansion. A serious election dispute is not automatically an operational emergency. A receiver's delayed answer is not proof that the registry is unrecoverable. The existence of litigation does not establish that uniqueness is at immediate risk. The institution invoking emergency treatment should show the threatened function, time horizon, evidence and minimum necessary intervention.

The distinction between preservation and activation is especially important. ICANN can urge backups and escrow without deciding who may use them. It can ask whether failover is technically possible without authorizing another registry to exercise discretionary functions. It can coordinate contingency preparation without pre-judging permanent recognition.

The letters would have benefited from a published severity ladder: monitor; request information; begin limited review; require corrective plan; prepare reversible continuity support; invoke emergency service; consider recognition consequences. Each step should have an objective trigger and a named authority. Such a ladder would reduce the risk that recipients interpret every urgent letter as the final step.

What a legally clear ICANN notice should contain

Future notices in a regional registry crisis should carry an authority statement near the top, not in later correspondence. At minimum, the statement should answer seven questions.

First, what is ICANN doing: expressing concern, requesting voluntary action, initiating review, preserving evidence or seeking judicial relief? Second, which instrument and clause support the act? Third, what verified facts trigger the power? Fourth, how do those facts affect unique identifier security or a continuing recognition criterion? Fifth, what response, correction or cure is available? Sixth, what consequence can ICANN itself impose, and what consequence requires another institution? Seventh, which information will be published, withheld or protected?

Where election remedies are proposed, the notice should state expressly whether they are recommendations. Where local compulsion is sought, it should identify the court route. Where records are requested, it should define confidentiality and purpose limits. Where recognition status may be affected, it should preserve draft findings and factual-correction rights.

This format would not weaken ICANN. It would make the intervention more portable across courts, registries and communities because each reader could see its legal character.

The receiver also had duties of explanation

Scrutiny of ICANN's authority does not relieve AFRINIC's receiver or administrators of their own responsibility. The public record raised material questions about membership records, proxies, voting access, technical backups and the route back to a functioning board. A receiver controlling a critical institution should answer precise questions with verifiable evidence, subject to lawful confidentiality.

Silence or opaque decision-making can increase the reasonable belief that identifier stability is at risk. It can also force counterpart institutions to prepare for contingencies. If the receiver believed an ICANN request exceeded authority, the appropriate response was not simply to ignore the underlying issue. It was to state the objection, identify the local constraint and provide the continuity evidence through a protected channel.

Authority is reciprocal in this sense: the party asking must identify its power, while the party holding critical records must explain how it is discharging its own. Transparency should be allocated according to function. Election rules and aggregate decisions should be public. Sensitive customer data should remain protected. Technical assurance can be independently verified without exposing credentials or private records.

The correspondence should therefore be judged not as a contest in which only one institution owed clarity, but as a failed exchange among institutions with different powers and overlapping responsibilities.

Concern can be reasonable even where a proposed remedy exceeds the instrument

One of the most damaging habits in governance disputes is treating criticism of authority as denial of the underlying risk. ICANN's concerns about records, backups, representation and continuity were not trivial. A regional registry that cannot demonstrate reliable custody of its records or a lawful path to governance presents a system problem.

It does not follow that every remedy proposed in response was within ICANN's unilateral power. Legal systems routinely separate a valid complaint from an available remedy. A claimant can be right about the danger and wrong about standing. A regulator can identify a breach but exceed the authorized sanction. A contract party can demand performance but not rewrite the corporate constitution.

The 2025 record is best understood through that separation. ICANN had a strong basis to care, a plausible basis to ask, and a defined but limited basis to review. It had no obvious free-standing power to administer AFRINIC's election. Its attempt to involve the Mauritian court confirmed that local coercion required a local decision. Its later statement that the election ideas were not directives aligned the rhetoric with the instruments.

This conclusion is not institutional fence-sitting. It is the rule-of-law position most capable of preserving both continuity and legitimacy.

What to watch after the letters

The next material developments should be evaluated against five tests.

The first is scope. Any ICP-2 review should state whether it concerns records, confidentiality, technical service, community support, governance capacity or a combination, and should explain the unique-identifier risk for each.

The second is procedure. Notice, access to evidence, factual correction and cure should be visible. Emergency treatment should identify why ordinary time limits are unsafe.

The third is authority. Election directions should come from AFRINIC's lawful organs or a competent Mauritian court. Recognition findings should come through the published assessment process. Service-transition decisions should not be smuggled into an information request.

The fourth is affected-party protection. Members, nonmember resource holders, operators, staff and counterpart registries have different interests. The process should specify whose contracts, data, voting rights and operational dependencies are affected.

The fifth is reversibility. Temporary continuity measures should preserve the possibility of returning service to a lawfully restored AFRINIC, with records, keys, decisions and audit trails intact. A contingency should not become permanent by administrative inertia.

These tests are more useful than asking whether ICANN “won” the correspondence. The real outcome is whether the registry system can distinguish advice from authority before another crisis makes the distinction operationally urgent.

Oversight claim, contractual opinion, or something else?

ICANN's correspondence was a hybrid. Its stability concerns arose from a genuine global coordination mission. Its questions about records, technical capacity and continuing criteria had support in the 2024 ICP-2 procedures. Its role in the ASO arrangement and AFRINIC's recognition history gave it institutional standing in the wider sense of being a proper entity.

But the letters were not a single legal instrument. Recommendations about election administration remained recommendations unless adopted under AFRINIC's constitution or ordered by a Mauritian court. A reserved right to review was not a completed review. A preservation request was not a finding. A general mission statement was not a corporate-management clause. A court's order derived from the court, not from ICANN's earlier demand.

Calling the letters mere opinion understates their procedural and systemic significance. Calling them commands overstates their legal force. The accurate description is a layered intervention: part governance advocacy, part evidence request, part notice of a possible recognition assessment and part attempt to activate domestic judicial authority.

That layered character should have been stated at the time. In a system that depends on voluntary coordination, contracts, recognition and domestic law rather than a single sovereign regulator, precision is not bureaucratic caution. It is the mechanism that keeps necessary oversight from becoming authority by assertion.

Sources and analytical limits

This analysis relies principally on the ICANN correspondence archive for 2025, the individual letters dated 7 March, 25 June, 3 July and 16 July 2025; the 2024 ICP-2 assessment procedures; the ICANN Bylaws; the ASO memorandum; the NRO memorandum; and the 2005 IANA recognition report.

Official statements establish what their authors said, which provisions they invoked and which procedural steps they described. They do not independently prove disputed allegations about voting, proxies, membership or private actors. The full Mauritian court record, sealed material, private correspondence, AFRINIC contracts and complete technical custody arrangements were not all available in the public record reviewed here. Conclusions about the legal effect of any specific private agreement would require its text and advice under the governing law.

The analysis therefore distinguishes documented institutional acts from attributed claims and focuses on the public authority architecture rather than deciding contested personal liability.