Summary

  • AFPUB-2026-GEN-001-DRAFT01 would formalise co-chair duties, moderation, appeals, recalls, consultations and a new Number Council so policy work can continue through governance disruption.
  • AFRINIC's staff assessment says the PDP remains within the company's bylaws and that Board functions cannot be reassigned through a subordinate policy document alone.
  • The proposal is under discussion. The practical test is therefore not whether “community” or “Board” should win, but whether every decision has a named actor, legal basis, trigger, review route and public record.

A continuity proposal born from interruption

AFRINIC's policy-development machinery has lived through a period in which basic institutional handoffs became difficult. The authors of the new working-group proposal attribute a series of disruptions to the earlier absence of a Board quorum: adopted proposals left unratified or unimplemented, missed public policy meetings, lapsed co-chair and committee appointments, unrenewed NRO Number Council representation and a frozen Resource Policy Discussion list.

Those are the authors' causal claims, not findings independently established by the source packet. But the institutional problem they point to is real enough to test: a bottom-up policy process is fragile if every routine transition depends on a single corporate organ being continuously able to act.

The draft, submitted and first posted to the policy list on 20 May 2026, responds by writing much more of the working group's operating system into policy. It defines co-chair responsibilities, selection and recall procedures, meeting rules, moderation tools, appeals, community consultations and a Regional Number Council. AFRINIC lists version 1 as under discussion; its presentation at the 24 June policy meeting was not adoption.

Procedure is the proposal's strongest layer

Much of the text addresses gaps that any durable working group should close. A temporary meeting lead may run the agenda but cannot determine consensus. A co-chair recall request needs stated reasons and support. A suspended mailing-list participant keeps receiving messages and may appeal. Moderation is tied to identified grounds such as repetition, timing and scope, with direct contact and public warning normally preceding a restriction.

These rules matter because continuity without procedure can merely shift discretion from one bottleneck to another. A working group does not become more legitimate because decisions move closer to the community; it becomes more legitimate when those decisions are visible, bounded and reviewable.

The proposed appeal structure also makes an important distinction. An objection to a co-chair action needs the support of three people who participated in the working-group discussion and must be filed within two weeks. That is a threshold for opening review, not proof that the challenged decision was wrong. The Appeal Committee would still have to hear the circumstances and explain its conclusion.

The authority conflict sits at the Board handoff

The proposal's most consequential mechanism appears when a policy reaches the Board. If the Board cannot act, or refuses to ratify without reasons, for 60 days, the draft allows a community petition supported by at least 15 eligible participants connected to distinct AFRINIC members across at least three subregions. Staff would conduct a fresh analysis. If that analysis found no new issue, the proposal text says the policy must be considered ratified and implemented.

That sequence is a resilience mechanism, but it is also an attempted transfer of authority. The draft itself acknowledges that section 11.2 of the bylaws would need amendment. AFRINIC's published staff legal assessment goes further: it says the PDP derives its authority from the bylaws, the Board remains responsible for subordinate instruments, and a duty assigned to the Board cannot be ceded to the proposed Number Council unless the membership first changes the bylaws.

This is not a court judgment, and the staff assessment should not be reported as one. It is nonetheless an institutional constraint from the organisation that would have to implement the policy. Nor can the authors' continuity objective simply be dismissed as a drafting inconvenience. The conflict is between two forms of failure: policy paralysis when the Board cannot act, and legitimacy risk when a policy document purports to replace a corporate authority that the bylaws still assign elsewhere.

An authority map can separate the layers

The proposal would be stronger if every consequential action were published in a single authority matrix. For each step, the matrix should name the actor, the source of authority, the triggering event, the evidence that must exist, the deadline, the appeal route and the public record created.

Meeting convocation would then show whether authority comes from the bylaws, a member-approved amendment or a delegated operational duty. Consensus determination would identify the co-chairs and the limits on temporary chairs. Moderation would show warning, restriction, duration and appeal. Ratification would show what the Board must consider and what reasons it must disclose. A continuity petition would show exactly which legal change makes its result effective.

That format would also expose where the draft is already clear and where it still asks readers to bridge incompatible instruments. It turns “independence” from a slogan into a set of auditable handoffs.

Operational systems are not the immediate obstacle

AFRINIC's staff assessment reports no expected impact on WHOIS, RDAP, MyAFRINIC, NetSuite, NMRP or RPKI. It likewise records no member-services, IT or HR impact. That is useful negative evidence: this is not primarily a registry-software proposal.

The implementation risk is institutional. Staff may be technically able to publish a policy or arrange a meeting, yet still lack an agreed legal instruction to do so. A system-impact table showing “none” therefore does not settle the governance question. It narrows it.

The same discipline should govern later drafts. Any claimed continuity benefit should identify the specific stalled handoff it repairs. Any new power should identify who exercises it, under which instrument and with which appeal. Any statement about past disruption should remain attributed until the record independently establishes it.

What to watch next

The current draft remains under discussion. The next meaningful signals are not merely a new version number or another meeting slot. Watch whether a revision separates bylaw amendments from CPM changes; whether it clarifies the proposed Number Council's authority; whether moderation and recall safeguards survive; and whether the 60-day petition path gains a legal basis that both community participants and AFRINIC can recognise.

AFRINIC needs a policy process that survives corporate interruption. It also needs decisions that remain lawful when the interruption ends. A public authority map and decision ledger would make those goals compatible: continuity would come from explicit, reviewable handoffs, not from allowing delay to silently move power from one institution to another.

Sources