Summary

  • AFRINIC’s draft would allow digest subscriptions only when RPD averages more than 20 emails per day over the preceding two months.
  • It also proposes a how-to page and would discard replies sent to a digest, replacing them with instructions for replying to one message or opening a new topic.

A mailing-list thread is cheap until a reply falls out of it. One person answers the weekly bundle instead of the message inside it; the subject survives, perhaps, while the parent message and earlier objections go missing. AFRINIC has a proposal for that small failure with a surprisingly large switch attached: the list’s digest option would depend on how much mail the list produces.

Benson Muite submitted AFPUB-2026-GEN-004-DRAFT01 on 17 October. It is version 1.0, under discussion, and would add three sections to the Consolidated Policy Manual’s section 3.4. The first asks AFRINIC to publish instructions for plain-text email, starting a topic, replying to a specific thread, filters and bounce rules, plus the list software and version.

The second part sets the gate. Digest subscriptions would be unavailable unless more than 20 emails are sent to the list on average each day over the preceding two months. Exactly 20 does not clear a “more than 20” test. If a later two-month period falls below the threshold, digest mode may no longer stay enabled. The third part addresses the thread-breaker directly: when digests are enabled, a reply to one should be discarded and an automatic message should explain how to reply to the original message while keeping its metadata, or how to start a new topic.

Those are two policies joined at one inbox. The guide helps people use a list. The volume rule decides whether one way of reading it is available. The reply rule stops a bundle from becoming a stray branch. Policy arguments about Internet resources are debated in public, yet their record still depends on whether an answer lands beside the point it answers.

AFRINIC says anyone may propose or discuss policy regardless of geography. Its policy page describes the RPD list as the main discussion venue alongside public policy meetings. The mailing-list page says anyone may subscribe and inspect the archive, while only subscribers can post. On 21 October, the PDWG co-chairs asked contributors to keep the proposal name and ID in the subject line for follow-up and archiving. The message thread is part of the record-keeping machinery, not inbox decoration.

Email has fields for message identity and reply references. RFC 5322 defines Message-ID, In-Reply-To and References, which represent a message’s place in a conversation. A digest packages messages for reading. A reply to that package can point to the bundle instead of the specific item; clients and list software handle that differently. The proposal describes the failure mode but gives no count of how often it happens on RPD.

That missing count matters because the threshold measures traffic, not thread damage. Twenty-one emails per day could be a clean, well-indexed debate; a quieter list could still have a few tangled exchanges that consume real time. Volume is easy to count and hard to confuse with an argument. Yet the threshold also acts as a proxy for reader need: many messages arriving quickly.

The draft leaves operating details open. It publishes no current RPD baseline, defines no set of included messages, and does not say whether two months means a rolling window or calendar months. It sets no notice period for existing digest subscribers if a later count closes access. A public counting method and transition date would make the switch something members can check.

The live page lists the proposal as under discussion. A digest can make a busy list readable; a thread can make a policy argument traceable. AFRINIC’s proposal wants both, but puts one behind a counter.

Sources