Summary

  • In a communiqué published on 18 February, AFRINIC said members had reported emails from non-AFRINIC sources making “mischievous allegations” about its ratified transfer policy. It called the Board properly constituted and urged members to use official communication channels.
  • The communiqué set out AFRINIC’s claims about the PDP and the policy, but cited no court order, Receiver direction, directors’ appointment instrument or reasoned authority opinion specific to the ratification.
  • AFRINIC’s public case list subsequently recorded Skyconnect v AFRINIC & Anor, SC/COM/PWS/000132/2026, as an ongoing plaint challenging the Board’s ratification. That confirms a live dispute, not that a court has invalidated the policy.
  • AFRINIC says the policy neither confiscates resources nor changes valid RSAs, lawful use rights or day-to-day routing. The material control at issue is narrower: transfer eligibility, exit and dependence on the registry’s recognition.

A response that began by classifying the critic

AFRINIC’s 18 February communiqué did not open with the policy clause under dispute or the legal instrument empowering the ratifying body. It opened by classifying the communication it was answering.

Members, the organisation said, had reported emails from non-AFRINIC sources containing “mischievous allegations” about Policy 2020-GEN-006-D3. The senders were not named. Their emails were not reproduced. The communiqué did not provide a claim-by-claim table allowing readers to compare each allegation with the policy text, a contract, a court order or a Board instrument.

Instead, AFRINIC supplied an institutional defence. It described the Policy Development Process as globally recognised, bottom-up, consensus-based, open to all stakeholders and independent of individual commercial interests. It said a “properly constituted AFRINIC Board” had reinstated the Policy Development Working Group, then ratified two policies after documented community consensus. It said the organisation acted in the public interest and within its mandate as a Regional Internet Registry.

That distinction became harder to ignore after 9 March. AFRINIC’s own public case list records a plaint by Skyconnect, formerly Skyvision Guinee, challenging the Board’s ratification of the transfer policy. It identifies the case as SC/COM/PWS/000132/2026 and marks it ongoing.

No manuscript should turn that entry into a judgment. An ongoing case does not prove the claimant is right. But it does make one conclusion unavoidable: the words “properly constituted” in AFRINIC’s communiqué did not settle the question in the executable legal forum where the challenge was taken.

What AFRINIC did answer

The communiqué contains several substantive answers that any fair account must preserve.

AFRINIC says the policy does not confiscate number resources, modify existing Registration Service Agreements or revoke lawful rights of use. Its ratified-policy page adds that the “regional” classification does not create a visible WHOIS label, alter operational routing rights or change day-to-day use. It determines which transfer rules apply to particular resource categories.

AFRINIC also says the Board cannot amend the bylaws unilaterally. According to the communiqué, proposed amendments must pass consultation, member review and formal approval at a General Members’ Meeting. That is important counterevidence against any suggestion that the organisation openly claimed unlimited Board power.

The policy’s published financial assessment says IPv4 and ASN resources from the AFRINIC pool can only be transferred in-region. It then states a direct institutional consequence: AFRINIC will not lose current resource members to other RIRs through outgoing transfers. AFRINIC’s current explainer describes exceptions for specified categories, including certain legacy and previously inbound resources, but leaves AFRINIC-pool resources under regional transfer conditions.

So the disputed control is not whether a prefix can be routed across a border tomorrow. AFRINIC expressly says day-to-day routing is unchanged. The control is over recognised mobility: which transfers the registry will record, which resource categories can leave, and how much dependence a holder retains on the regional administrative gate.

That narrower description is more accurate than saying AFRINIC “seized” every address. It is also more consequential than dismissing the policy as bookkeeping.

The missing answer was transaction-specific authority

AFRINIC’s defence moves across five kinds of proposition: its place in the global RIR system, the virtues of the PDP, the openness of participation, the contractual status of number resources and the public-interest character of the institution.

The authority question is more specific. Which operative instrument authorised this Board, in this unresolved governance setting, to ratify this policy on this date?

The communiqué cites the bylaws in general and calls the Board properly constituted. In the fixed public packet, it does not link a court order validating the directors, an appointment instrument, a Receiver instruction, a Board resolution with authority analysis or a reasoned legal opinion addressing the ratification.

AFRINIC’s own 12 March member update shows why a generic answer was insufficient. The organisation said the directors elected in September 2025 had resumed duty under Mauritian company law, while the court-appointed Receiver remained in place pending formal discharge. It also said litigation sought to invalidate the directors’ appointments and that judgment on the Receiver’s discharge was awaited.

That update is AFRINIC’s account, not a finding against it. It nevertheless confirms that the operating environment contained two facts at once: directors were acting, and proceedings about their authority and the Receiver’s position remained live.

NRS describes the directors as a “Purported Board,” argues that the Receiver’s role was preservative rather than legislative and calls the transfer policy structural lock-in. Those are NRS’s legal and advocacy positions. The fixed packet contains no judgment adopting them. AFRINIC takes the opposite position. A news briefing should not cure that conflict by turning either label into evidence.

The reproducible route is to ask for the instrument. If AFRINIC relies on a particular court order, appointment, statutory provision, Receiver direction or resolution, it can identify it and explain how the powers connect. If a claimant says the act was ultra vires, it can publish the pleaded basis and, eventually, the court’s answer. Until then, institutional repetition is not adjudication.

“Official channels” are part of the governance event

The communiqué twice narrows the preferred venue. Members with questions about interpretation or implementation are encouraged to use the RPD mailing list or other official channels. At the end, AFRINIC urges members to seek information through official communication channels and established policy forums.

There is a legitimate version of this request. Mailing lists can preserve dates, arguments and replies. Formal channels can direct questions to responsible staff and reduce the circulation of unattributed screenshots or partial excerpts. AFRINIC was entitled to publish its answer and point readers to its records.

But channel design also distributes power. The institution defines the forum, administers the infrastructure, chooses what receives an organisational response and characterises outside material before readers see it. When the first description of an external challenge is “mischievous,” directing members back inside the institution’s channels risks asking the institution’s own process to certify the institution’s authority.

The packet does not establish censorship. AFRINIC did not prohibit outside speech in the material examined, and “mischievous allegations” should not be stretched into a claim that it denounced every critic. The narrower concern is epistemic: members were given AFRINIC’s classification of unseen emails, then urged to rely on venues AFRINIC treated as authoritative.

A stronger response would have published a claim-and-evidence register. It could have quoted each disputed proposition accurately, linked the policy clause, identified the applicable RSA or bylaw, cited the authority instrument, stated the current court status and marked what remained contested. That would let members test misinformation rather than merely accept its label.

Participation does not supply the missing delegation

Heng Lu’s doctrine separates symbolic legitimacy from executable authority. Consensus, community language and open participation can organise cooperation. Courts, contracts and enforceable instruments decide what can be compelled when cooperation breaks down.

The distinction is particularly relevant here because AFRINIC’s communiqué uses “community” in two roles. First, community deliberation is presented as evidence that the policy was properly developed. Second, the multistakeholder process is presented as the legitimate place to challenge or change it.

Participation can improve a policy. It can reveal technical errors and operational consequences. It can record support and opposition. But an affected stakeholder is not automatically a principal who delegated authority to an agent. A service region is not a sovereign electorate, and a mailing-list process does not by itself confer powers that the company, its contracts or the law do not provide.

This does not make the PDP useless. It makes its function narrower and more honest. The PDP can be a policy-development and coordination mechanism. It cannot be used as a substitute answer when the disputed question is whether the corporate actor ratifying the outcome held the necessary legal power.

The same doctrine clarifies why the transfer rule matters. Exit is not rhetoric. A holder that cannot obtain recognised outbound transfer for a category of resource has less institutional optionality. Lower optionality increases dependence on the registry that controls recognition. The registry may believe that result serves accurate administration and regional allocation. Affected operators may see a constraint on asset mobility. Both positions can be stated; neither “stewardship” nor “property” should be allowed to end the inquiry by slogan.

The case list is not a verdict—but it defeats closure by communiqué

AFRINIC’s case page lists three distinct Skyconnect entries. The main plaint challenges the ratification and is marked ongoing. A separate interim-order application is described as declined and not served on AFRINIC. An appeal from that order is also marked ongoing.

Those procedural entries should not be blended. A refusal of interim relief does not automatically decide the merits of a main action. An unserved application is not evidence tested against AFRINIC’s response. An appeal marked ongoing is not an appellate ruling. The fixed sources provide no pleadings and no reasoned merits judgment.

That absence cuts both ways. Critics cannot honestly say the case list proves illegality. AFRINIC cannot honestly treat the words in its February communiqué as the final legal answer. The public status is unresolved.

The appropriate disclosure is not difficult. AFRINIC could place a dated litigation note beside the policy FAQ: case number, relief sought in neutral language, current procedural status, any operative interim order, whether implementation is stayed, and links to publicly available judgments. It could separately publish the Board and Receiver instruments on which it relies, with necessary redactions.

Such a record would also protect the institution. Authority evidence is not a concession to critics; it is the shortest route out of a conflict dominated by competing descriptions.

The wider validation problem

The February communication belongs to a larger pattern of contested institutional validation. In June, NRS urged members not to approve AFRINIC financial statements in a way that could retrospectively cure disputed authority over historical expenditure, including legal fees. AFRINIC, in its March member update, blamed litigation and advocacy for millions of dollars in legal costs.

Those later positions do not prove that the February communiqué approved an invoice, validated a lawyer’s rate or caused any expenditure. This packet establishes no transaction-specific connection to the historically reported USD 1,000 hourly legal rate, and none should be invented.

The relevant common question is narrower: can a disputed institution transform contested authority into settled authority by issuing a communiqué, recording its own confidence or later obtaining a broad member vote? The answer must come from the governing instrument and the legal effect of the specific act, not from the intensity of institutional affirmation.

AFRINIC’s current Board and those supporting it can answer that challenge with documents. They can identify the instrument constituting the Board, the Receiver’s operative role at the ratification date, the resolution approving the policy, the directors present and voting, the legal basis relied on, and the exact status of litigation. If the evidence supports their account, publishing it will strengthen them. If material limits exist, members should see those too.

The conclusion of this event is therefore firm but bounded. AFRINIC answered outside criticism by classifying it, asserting procedural legitimacy and directing members toward official channels. It also supplied meaningful policy clarifications. What it did not supply in the fixed record was the transaction-specific authority document that could convert “properly constituted” from institutional self-description into a reproducible answer. Its own case list later showed why that answer was still needed.

BTW’s separate research on AFRINIC election legitimacy is linked below for readers seeking the wider governance history. It is Further reading, not the source article for this news report and not a second news item counted in this bundle.

Sources