Summary
- AFRINIC proposal AFPUB-2026-GEN-004-DRAFT01 remains under discussion. It would allow RPD digest subscriptions only when the preceding two-month average exceeds 20 messages per day.
- The official 2026 RPD archive contains 173 unique messages from 18 August through 16 October, or 2.9 per day across 60 days. The live subscription page still offers a daily digest.
The proposal’s threshold is not close to the list’s recent traffic. That gap makes a small convenience feature a test of who gets to set the cost of following policy: the participant choosing a digest, or the institution choosing which inbox formats remain available.
AFRINIC’s draft AFPUB-2026-GEN-004-DRAFT01, submitted on 17 October and still marked “Under Discussion”, would bar digest subscriptions unless the preceding two-month average exceeded 20 messages per day. Once the threshold was crossed, digest mode could stay on until a later two-month window fell below it. The official RPD archive records 173 unique messages in the 60 days from 18 August through 16 October: 2.88 per day. That is about one-seventh of the proposed gate.
Today’s RPD subscription page still offers a daily digest. The proposal has not changed that control. Its concern is real: a reply sent to a digest can lose the message’s thread metadata, making a discussion harder to follow. The draft’s remedy combines a participation guide, a published Mailman version, and a strict rule: if digest mode is available, replies to a digest are discarded and the sender receives instructions for replying to the original message or opening a new topic.
The volume test is blunt. It treats a quiet list as a reason to remove batching, even though the stated thread problem arises when someone replies to a digest, not simply when the list is busy. A guide and a clear reply path address that failure more directly. The archive count does not prove who uses digests or how often threading breaks; AFRINIC publishes no subscription-mode totals or incident count in these records.
That missing evidence matters because the policy process is open to anyone, including readers outside the region, and depends on mailing-list discussion as well as public meetings. A person may value batching precisely because they cannot monitor a live stream of email. The proposal instead makes list-wide volume the switch for every subscriber.
The next useful change is a revised draft or an impact analysis that connects the 20-message line to observed thread loss and subscriber needs. Until then, the public record shows a live digest option, a draft that would sharply constrain it, and traffic far below the draft’s trigger.
Sources
Member Briefing
Deeper Profile Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock profile briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance





