Summary

  • On 14 September 2026, AFRINIC’s PDWG co-chairs invited the community and the authors to discuss whether the new PPM Dates proposal and the much broader PDP Working Group Guidelines and Procedures proposal should be merged for discussion at the coming Public Policy Meeting. The invitation is not evidence that a merger occurred.
  • PPM Dates author Jordi Palet objected seven minutes later, warning that a combined text could make both parts fail if either lacked consensus. The immediate governance question is therefore not document tidiness but whether two independently contestable changes would remain independently decidable.

At 15:48 UTC, AFRINIC’s policy list received a routine announcement for a small draft. At 15:50, the unit of decision was suddenly open to negotiation.

The first message introduced Public Policy Meeting Dates, AFPUB-2026-GEN-003-DRAFT01. The draft would add a short provision to Section 3 of the Consolidated Policy Manual. It asks AFRINIC to avoid clashes between Public Policy Meetings and previously announced meetings of other RIRs, the IETF, ICANN and ISOC, and to announce dates and venue a year ahead unless that is unavoidably impossible.

The second message, sent by the PDWG co-chairs, noted that PPM Dates and PDP Working Group Guidelines and Procedures, AFPUB-2026-GEN-001-DRAFT01, both affect Section 3. It invited the working group and the authors to discuss whether they should be merged and discussed at the upcoming PPM.

That wording matters. It was an invitation to discuss composition, not an instruction to merge and not a consensus determination. Seven minutes later, Jordi Palet replied that combining the drafts did not make sense: the dates rule was a specific point, and failure of either part to reach consensus could make the whole package fail. Kept apart, he argued, either could reach consensus independently.

The two texts do share a numbering surface, but they do not solve the same problem. GEN-003 proposes a meeting-calendar constraint and suggests inserting it as a new Section 3.4.3, with later provisions renumbered. GEN-001 is an institutional redesign. It would replace the existing PDWG section, relocate or recast Public Policy Meeting rules, define co-chair responsibilities, add a Number Council, revise appeal and recall arrangements, describe consensus administration, and alter the route from working-group consensus to approval.

That creates at least three separate questions.

The first is mechanical: if one draft changes the Section 3 structure while another inserts a numbered subsection into the current structure, what numbering and cross-references survive? This can be resolved by editorial coordination. It does not require the underlying policy choices to become one vote-like judgment.

The second is procedural: would the calendar rule depend on the new institutions and processes in GEN-001, or could it operate under the existing PDP? GEN-003, as published, frames the calendar obligation as a stand-alone addition. GEN-001 reaches far beyond meeting dates. A combined draft would need to show any actual dependency rather than infer one from the shared section number.

The third is decisional: what happens to support and objections already addressed to each proposal? AFRINIC’s current CPM describes a draft-policy lifecycle—publication, PPM consideration, Last Call, consensus, approval and implementation. If two existing drafts become one new draft, the record must explain whether the working group can support one component and oppose the other, and how co-chairs would report that split.

This is why a clean combined manuscript would not be sufficient evidence. The community would need a proposal-composition receipt: a public record naming the exact source versions, mapping every retained, changed and omitted provision, identifying the authors and editor, carrying forward unresolved objections, and stating whether consensus will be assessed for each component or only for the package. A new identifier and revision history should make the lineage visible.

Such a receipt would also distinguish discussion efficiency from decision integrity. Presenting related drafts in one agenda block may reduce repetition. Harmonising cross-references may prevent contradictory numbering. Neither administrative convenience answers whether a participant should have to accept a redesign of PDWG governance in order to support advance notice of meeting dates—or reject the dates rule in order to oppose the redesign.

There is no evidence in the cited record that a merge has been completed, that either proposal has consensus, or that separate drafting guarantees adoption. There is only a proposal announcement, an invitation to discuss composition and an author’s objection. That is enough to expose the control surface, but not enough to predict the outcome.

Sources