Summary

  • On 11 May 2016, AFRINIC’s Board unanimously adopted Resolution 201605.283 after staff prepared a draft informed by codes used by other regional Internet registries and the IETF, and after the Board changed the wording of the final paragraph. The preserved minutes do not disclose the earlier wording, the precise change or its rationale.
  • The contemporaneous code covered conduct at AFRINIC meetings, AIS meetings and AFRINIC mailing lists, for people participating in person or remotely. Its only expressed consequences were a request to leave a meeting or a request to unsubscribe from a mailing list.
  • Those measures belong to the forum in which the conduct occurs. They must not determine membership, voting, candidacy, the standing of a policy proposal, number-resource eligibility, allocation service, registry records, RPKI or any other technical service.
  • The public text supplied behavioural expectations but did not publish the machinery needed to apply them consistently: complaint intake, decision ownership, an evidence standard, notice, an opportunity to respond, recusal, reasons, duration, reinstatement or review.
  • Prompt moderation and fair process are not opposites. Immediate, temporary separation may be necessary to stop active abuse, but any continuing restriction should be recorded, scoped, time-bounded, explained and open to correction and distinct reconsideration.
  • AFRINIC is a private technical bookkeeper and coordinator. It is not a sovereign, regulator, police force, prosecutor, punishment authority, confiscator or court, and a conduct code cannot create powers of that kind.

A modest act with a consequential boundary

The institutional act was compact. At its meeting on 11 May 2016, the AFRINIC Board considered a staff-prepared draft Community Code of Conduct. The minutes say that staff had drawn on codes of conduct from other regional Internet registries and the Internet Engineering Task Force. The Board altered the wording of the draft’s last paragraph. Andrew Alston proposed Resolution 201605.283, Sunday Folayan seconded it, and the Board adopted it unanimously. Both the original and corrected published minutes record the same facts relevant to this item.

That record supports a precise account, but not a more elaborate drafting history. It does not identify the staff authors, the comparison texts or the clauses borrowed from any of them. It does not preserve the final paragraph as it stood before the Board’s amendment. Nor does it explain what concern prompted the change. The fact of deliberation is visible; its internal reasoning is not. Any attempt to supply a hidden motive, a contested vote or a detailed legislative genealogy would outrun what was recorded.

The public code captured later in May stated where it applied: AFRINIC meetings, AIS meetings and mailing lists, including participation in person and at a distance. That is a recognisable platform perimeter. A meeting organiser controls access to a particular room or remote session. A mailing-list operator controls subscriptions to a particular list. Each can take limited steps to preserve the conditions under which discussion remains possible.

The code’s remedies were equally specific. A person not complying with it could be asked to leave a meeting or asked to unsubscribe from an AFRINIC mailing list. The text did not state a fine, forfeiture, cancellation of number resources, loss of membership, disqualification from an election or exclusion from policy development. It described removal from the forum affected by conduct, not a general disciplinary status attached to the person.

That distinction is the article’s central line. Behavioural moderation can protect the setting in which people speak. It cannot acquire authority over everything speakers do elsewhere merely because the registry also administers other systems on which they depend. The code could regulate participation in the listed spaces. It could not become an alternative route for deciding who may vote, stand for office, advance a proposal or receive an unrelated registry service.

The eight expectations, read as forum rules

The code expressed eight expectations. In substance, they required respectful treatment; rejected discrimination; barred personal or defamatory attacks; asked participants to handle disagreement calmly; required attention to the meeting agenda; called for restraint in the use of speaking time; asked for regard to language and other constraints on participation; and directed attention to the interests of the African Internet community. These ideas are best understood in relation to the communicative setting the code identified.

Respect and non-discrimination concern whether people can enter deliberation without being demeaned for who they are. Restraint on personal attacks protects the possibility of disputing a position without treating the speaker as a target. Calm disagreement does not require consensus or warmth; it asks participants to keep conflict in a form that others can follow. Agenda discipline and fair use of speaking time prevent one participant from consuming a shared forum.

Awareness of language and participation constraints recognises that formal openness can still exclude people when speed, idiom, bandwidth or meeting practice make entry impracticable.

The final community-oriented expectation does not turn the institution into a sovereign representative of everyone described by the word “community”. In context, it is a behavioural orientation for deliberation, not a grant of public jurisdiction. Official vocabulary can describe how an institution sees its purpose, but it cannot manufacture legal powers. The meaning of each provision must therefore remain tied to the forum, the conduct and the two remedies the text actually states.

This reading avoids two symmetrical errors. One would dismiss the rules as merely aspirational and leave chairs or list operators unable to protect a forum. The other would treat broad language about respect or collective interests as permission to discipline any activity with some connection to AFRINIC. The first makes the platform incapable of defending participation. The second makes its boundary disappear. The text is most defensible when read as authorising practical moderation within the listed spaces and no more.

Why the remedy defines the jurisdiction

Jurisdiction here is not a claim to territory, sovereignty or public-law command. It is the ordinary capacity of a private organiser to administer a place or communication channel it operates. A chair can manage a meeting because there is a meeting to manage. A list operator can manage subscriptions because there is a list to operate. The practical authority follows from responsibility for the platform, and its limit follows from the same source.

That is why the remedy matters so much. Asking someone to leave a meeting responds directly to conduct that makes that meeting unsafe or unusable. Asking someone to unsubscribe responds directly to conduct on that mailing list. Each measure interrupts access to the surface on which the alleged problem is occurring. Neither needs to be described as a criminal sanction, civil judgment or sovereign punishment. It is a platform-access decision, potentially serious for participation but conceptually limited.

A different consequence would require a different source of decision-making authority. Membership status is governed by the organisation’s membership arrangements. Voting and candidacy depend on the applicable governance rules. Policy-proposal standing belongs to the policy process. Allocation and registry service concern the technical and contractual administration of number resources. RPKI and other operational systems have their own purposes, records and failure modes. The existence of a behavioural code does not collapse these domains into one disciplinary hierarchy.

The clean test is functional. Does the measure restore the affected forum, or does it create leverage over an unrelated right or service? A temporary request to leave a session after active disruption can restore order in that session. Cancelling a vote because of a mailing-list allegation would alter governance power. Withholding a registry service because of conduct at a meeting would use technical dependence as punishment. The latter measures do not become legitimate merely because AFRINIC operates both the forum and the ledger.

The code’s narrow remedial language therefore does useful constitutional work, even though the document is not a constitution. It keeps the response close to the problem. It also gives later institutional design a baseline: procedure should make a platform remedy fairer and more reliable, not enlarge it into membership discipline or resource enforcement.

The public text stops before procedure begins

The captured code tells participants what behaviour is expected and names two possible responses. It does not publish how a report enters the system, who decides it, what information counts, when the affected person is told, how conflicts are handled or how a decision ends. That is a limit of the public text, not proof that no unpublished practice, contract or ordinary law supplied any control.

The distinction matters. Documentary silence cannot support a sweeping historical claim about everything AFRINIC staff or meeting chairs may have done. It can, however, support a careful institutional audit of what participants could learn from the code itself. On that measure, the procedural architecture was not visible.

There was no published complaint trigger or acknowledgement path in the captured text. A contact address for questions appeared in the final paragraph, but a place to ask about a code is not necessarily a procedure for filing a report. It does not tell a participant what facts to provide, whether urgent risks receive priority, how receipt is confirmed or who safeguards the information.

The text did not name an initial decision maker. It did not distinguish the person receiving a complaint from the person gathering evidence or the person imposing a measure. It did not state an evidence threshold or a hierarchy among contemporaneous observation, documentary material and conflicting recollection. It did not require notice of the particular provision or factual allegation, nor did it publish an opportunity for the affected participant to answer.

There was no stated recusal rule, reasons duty, duration, default expiry, reinstatement path or review mechanism. A request to leave might mean the remaining minutes of one session or something longer; the text does not say. An unsubscribe request might end when a heated thread subsides or persist indefinitely; the text does not say. The reader cannot identify from the code alone who could correct mistaken identity, missing context or inconsistent application.

These gaps do not make every immediate moderation step illegitimate. They identify the work that a proportionate operating design must do if a restriction continues beyond the instant required to separate people or restore order. The more consequential or durable the platform restriction, the greater the need for notice, reasons, a time limit and reconsideration. Procedure should scale with the measure without turning a meeting chair into a court.