Summary

  • AFRINIC’s draft asks policy meetings to avoid already announced RIR, IETF, ICANN and ISOC dates, avoid other Internet events where possible, and publish the venue and date a year ahead unless unavoidable.
  • AFRINIC-38 is scheduled for 18 November 2026, one day inside IETF 127’s 14–20 November week.

A calendar is a governance document wearing office clothes. Someone decides which dates count, whose plans deserve priority and when the word “unavoidable” closes the argument. AFRINIC’s proposal on Public Policy Meeting (PPM) dates puts those decisions on the table without naming the hands that will make them.

The draft, AFPUB-2026-GEN-003-DRAFT01, asks AFRINIC to avoid clashes with previously announced meetings of “Sister Organizations”—other regional Internet registries, IETF, ICANN and ISOC. It also says to avoid other Internet events where possible and to announce the date and venue one year in advance unless that is unavoidable. The text is short. Its consequences are not.

AFRINIC-38’s PPM is scheduled for 18 November 2026 in Cape Town. IETF 127 runs from 14 to 20 November in San Francisco. The published schedules overlap on 18 November. AFRINIC’s meeting is hybrid and open to everyone; its site says remote participants follow every session and join debate on the same terms.

The hard question is who gets to define the unit of conflict. Is a clash one shared day, a travel week, a session on a relevant subject, or the moment two institutions compete for the same small group of people? The proposal gives no test. It names no priority order and no public record for an exception.

That omission matters because the discussion contains two plausible claims. In an RPD mailing-list response, AFRINIC staff and Board representatives said Cape Town was chosen in the same week and city as Africa Tech Festival and the South Africa Peering Forum because many people would already be travelling there. Contributors argued that a shared trip could help African participants attend several events. Others emphasized the global overlap and remote participation. The RPD discussion records competing forecasts.

A rule that treats every overlap as a veto could punish useful clustering. A rule that treats every overlap as harmless can make “coordination” a polite label for whoever booked first. The proposal’s one-year notice helps people plan, but notice alone does not allocate authority. The group that controls the calendar still needs a method for conflicts the rule cannot prevent.

AFRINIC’s policy process already has named decision points: an open mailing-list discussion, a PPM where the Policy Development Working Group Co-Chairs assess consensus, a separate Last Call, Board ratification of process and staff implementation. The calendar proposal should fit that institutional logic. If it creates an exception power, the community should know who exercises it, what evidence they consider and where the decision is recorded.

A workable version could define a clash by date and time first, then require organizers to publish a short reason when an overlap remains: venue availability, regional travel patterns, an immovable external date, or another concrete constraint. A second line could identify who reviews that reason and when affected participants can challenge it. “Where reasonably practicable” is a useful standard only when the record shows what was practical and for whom.

The practical stakes extend beyond one meeting. AFRINIC’s PPM is where the community debates policies governing Internet number resources in the region. The meeting’s schedule shapes who can be in the room, who can join remotely, and whether the discussion competes with another event for attention. An apparently administrative date can influence the composition of the people who form consensus.

AFRINIC has not published a participant-by-date overlap count; that count would show whether the collision is mainly a travel problem or a competing-agenda problem.

The draft has identified a real operating problem: meetings cannot coordinate around dates they do not know. It now needs to decide who runs the coordination, who can waive it, and what that person must publish. Otherwise the calendar gets a rule, while the actual power to set it stays off the page.

Sources