Summary

  • AFRINIC’s Bylaws Review Committee must conduct a stakeholder-validation meeting before any AGMM or SGMM at which constitutional amendments are presented.
  • The Terms of Reference separately reserve final approval for members and describe the BRC as advisory and nonbinding. Validation is therefore an intermediate evidence test, not a corporate vote.
  • The checked pages do not publish the meeting date, invitation rule, participant denominator, text version, validation question, decision method, minutes standard or treatment of dissent.
  • A protocol published before registration should define what is being tested and state that attendance or silence is not endorsement; a post-meeting issue ledger should precede Board approval and the member vote.

AFRINIC has promised a meeting with an unusually powerful name: stakeholder validation.

The phrase appears in the Bylaws Review Committee’s Terms of Reference. Before any AFRINIC General or Special Members’ Meeting at which amendments are presented, the BRC “shall conduct a stakeholder validation meeting.” In a constitutional process, that requirement can become a useful last check. It can also become ambiguous if the institution later says a text was validated without showing who attended, which version they saw or what disagreement survived.

The timing matters. AFRINIC’s second consultation closed at 23:59 UTC on 21 August 2026, and its registration endpoint later displayed an expired-and-unavailable message. The BRC must now analyse the fixed input, report how each item was handled and prepare recommendations. AFRINIC says the final draft then receives an independent external legal review, goes to the Board and—subject to Board approval—reaches members at an SGMM.

The validation meeting sits somewhere in that chain. The ToR say it must happen before a member meeting presenting amendments, but the checked pages do not say whether participants will examine the BRC recommendation, the legally reviewed draft, the Board-approved version or several versions. That is not a minor scheduling detail. A meeting cannot validate a moving object.

Nor can its attendees create corporate authority. The same ToR describe the BRC as advisory and non-decision-making. They separately say final amendments are presented for approval at an AGMM or SGMM. Participation can reveal defects, test explanations and produce evidence. It cannot replace the eligible members, their voting denominator or the formal resolution.

There is a strong case for keeping the validation meeting flexible. An open discussion may expose operational consequences that a survey misses. Participants can challenge whether a revised clause answers the original objection. Lawyers can explain a correction without converting the session into a referendum. Remote and multilingual input can widen the evidence base. Sensitive personal, legal or security matters may need careful redaction. A useful workshop does not need to pretend to be an election.

The problem begins when flexibility is converted into an endorsement claim. Invitations determine who is in the room. The agenda determines which questions receive time. The displayed draft determines what can be challenged. The chair’s summary and the minutes determine which disagreement remains visible. None of these controls requires bad faith to affect the record.

At the evidence cut-off, the published pages did not name a date, notice period, eligibility rule, participant classes, observer policy, quorum, facilitator, language-access plan, agenda, validation question or decision method. They did not state whether silence counts, whether objections receive stable IDs or whether minutes and a recording will be public. This is a missing method, not proof that a required meeting is late or improperly planned. No identified AGMM or SGMM deadline in the packet made the prerequisite due.

The word validation should therefore be disaggregated. The meeting could validate that the correct version was displayed. It could test that the response report covers material issues. It could check that operational consequences were understood. It could verify that participants had a fair opportunity to object. It cannot truthfully prove unanimous regional consent unless the participant universe, denominator and decision rule support that claim.

For network operators and Resource Members, the distinction has practical weight. The Constitution can allocate rules for membership, fees, Board formation, elections, suspension, termination and institutional continuity. A validation meeting may be the last practical moment to identify a service-impacting defect before members face a binary vote. If unresolved objections are compressed into “stakeholders validated the draft,” members lose evidence precisely when their formal responsibility begins.

AFRINIC can avoid that outcome by publishing a protocol before registration. It should identify the convening authority, date and notice; the exact draft and authenticated redline; participant and observer rules; language and remote-access support; the questions in and out of scope; chairing and conflict rules; and the way objections will be recorded. Attendance and silence should be expressly separated from endorsement.

After the meeting, publish participant counts by class, minutes, any recording, a stable issue ledger and a change log. Each material objection should be marked accepted, partly accepted, rejected, merged, deferred or outside scope, with a short reason. The record should show what changed before legal review, what changed after it and what the Board approved.

NRS calls the current directors a “Purported Board” and disputes that lawful authority has been conclusively established. That is an attributed position, not a judicial finding established here. It makes event-specific notice and authority records more important; it does not prove that a future validation meeting will be invalid.

AFRINIC’s promise is potentially valuable. The evidence of fulfilment will not be a photograph of a meeting or a count of attendees. It will be a method that tells members exactly what the meeting tested, whose objections remained and how those objections altered—or failed to alter—the text.

Sources