Summary

  • The official calendar is clear but compressed: approval for implementation on 20 January 2021, a public comment window from 2 to 28 February, and unanimous approval of a stated revised proposal on 3 March.
  • Archived public page bodies from 2 February and 5 March retain the same fifteen subscriber clauses and four enforcement options. Their one observed textual delta inserts “resolve” into a broken sentence about amicable dispute resolution; no public redline or response matrix connects that repair, or any other possible private revision, to a comment.
  • AFRINIC had a legitimate reason to administer its continuously available mailing lists against spam, malware, harassment, privacy breaches and legal risk. The unresolved issue is not whether it could set house rules, but whether its public record makes the consultation consequential and reviewable.
  • A proportionate remedy would be a privacy-bounded consultation receipt linking versions, comments, responses, reasons, decision authority, final text, enforcement practice, review, effective date and later corrections—without pretending that participation grants public authority to a private technical coordinator.

Three dates and a missing bridge

The most revealing feature of AFRINIC’s 2021 mailing-list consultation is not an inflammatory message or a dispute between familiar personalities. It is the documentary space between three dates. The minutes for 20 January say the Board took note of proposed Terms of Use and approved them for implementation as presented by the chief executive. On 2 February, AFRINIC invited public comments and fixed 28 February as the deadline. On 3 March, only three days after that deadline, Resolution 202103.601 said Management had considered feedback, amended and revised the initial proposal, and brought it back for approval.

The motion was proposed, seconded and approved unanimously.

That sequence establishes several things. There was a proposed instrument. The Board acted in January. A bounded comment period opened in February. Management represented that it considered feedback. The Board approved a revised proposal in March. But those facts do not answer the question a consultation is supposed to make answerable: what input changed which operative words, and why?

The public versions make the question more acute. An archived capture of AFRINIC’s official page at the opening of the consultation and another captured on 5 March show the same fifteen numbered obligations for subscribers and the same four enforcement choices. In the visible article bodies, the one observed textual delta is in clause 13. The early page said subscribers “undertake to any dispute arising amicably”; the later page says they “undertake to resolve any dispute arising amicably.” The inserted verb repairs a malformed sentence.

It is a real improvement, and consultation can be useful precisely because outside eyes catch drafting errors.

Yet the comparison cannot carry more weight than it can bear. It does not prove that “resolve” was inserted because of a public comment. It does not prove that this was the only change considered or made in a private draft. Nor does the 5 March capture establish that the page was the complete, authenticated instrument approved by the Board. Indeed, two days after approval, the page still called the text a draft and retained the invitation to comment by 28 February, a deadline already past.

The public surface therefore leaves the reader with a grammatical repair, a stale status label and a formal claim that a revised proposal had been approved, but no redline connecting them.

That gap matters because these were not decorative website conditions. They governed access to mailing lists used for member, policy and governance discussion.

The draft bound subscribers to comply with AFRINIC’s Code of Conduct and Privacy Policy; use an everyday name; maintain one account; protect passwords and avoid account transfer; respect a range of content limits; avoid malware or impairment; refrain from unauthorised data access or collection; accept attribution of their posts; avoid commercial solicitation; indemnify AFRINIC; accept Mauritius law and amicable dispute resolution; accept unilateral amendment; and recognise legal remedies. It also contained a broad clause against conduct AFRINIC judged similar to conduct already prohibited.

The enforcement section gave practical force to those obligations. It reserved roles for the chief executive and, on relevant lists, the Policy Development Working Group co-chairs. AFRINIC could issue a warning, filter or remove comments, immediately revoke posting privileges on one or all lists, or make a revocation temporary or permanent. Those options range from correction to exclusion. Their use could decide whether a contribution remained visible in a shared record and whether a subscriber could continue speaking through a significant institutional channel.

But proportional language is essential. AFRINIC is a private technical bookkeeper and coordinator. It has zero sovereign, legislative, regulatory, police, prosecutorial, punitive, confiscatory or adjudicative power. Its terms can govern its own private mailing lists; they cannot enact public law, sentence a critic, command a state, confiscate number resources or adjudicate a public right. Losing posting privileges may impose a serious participation cost inside a private forum, but it is not state punishment. Removing a message can alter the accessible discussion record, but it is not control of Internet routing.

The importance of a forum does not transform its administrator into a sovereign.

This boundary clarifies rather than weakens the institutional criticism. Because AFRINIC’s legitimate power is private and functional, it needs the ordinary disciplines of a trustworthy private coordinator: identifiable rules, stable versions, proportionate administration, recorded reasons and a route to correct mistakes. It does not need the ceremony of public authority. It does need to show members and subscribers which house rules emerged from the consultation that it chose to hold.

The official record currently supplies an assertion of consideration, not the receipt for consideration. Resolution 202103.601 records that feedback was considered and the initial proposal amended. It does not enumerate the feedback, identify affected clauses, classify suggestions as accepted, rejected or deferred, provide reasons, attach a redline, authenticate the final text, set out an effective date or identify a review route. The absence of those items from the public record does not prove that AFRINIC possessed no comments, internal drafts, legal advice or decision notes.

It proves only that a later reader cannot reconstruct them from the surviving public chain.

That is the central distinction. Opening a comment channel is an act. Receiving a comment would be another act, though the surviving record does not disclose how many arrived. Considering feedback is a further act. Amending words is another. Explaining the relationship among them is what makes the process auditable. Without that bridge, “consultation” describes a calendar and an opportunity; it does not yet demonstrate the effect of participation on the instrument.