Summary

  • At RIPE 93 on 29 October 2026, Address Policy co-chair Franziska Lichtblau handled a proposal to collect scattered RIPE policy texts while participants warned that correcting conflicting definitions could itself change policy.
  • She offered chair support to people with structural fixes and steered detailed wording to the public mailing list. RIPE's published policy process places consensus summaries on that list, not in the applause after a meeting.

The innocent-looking binder

Put decades of address policy into one binder and the first question is where to put the staples. The second is whose interpretation survives when two old pages disagree. In the RIPE 93 Address Policy transcript, Remco van Mook proposed gathering RIPE's scattered policy texts. People welcomed a readable collection. Peter Hessler, speaking for the Database Working Group, wanted the conflicts exposed without turning the act of gathering into a silent correction. Another participant warned that republishing old language outside the policy process could give a new reading the authority of an established rule.

Lichtblau was one of the session's chairs. She pointed to existing categorisation work and told a participant with a structural idea that chairs could help find the right language, process guidance and experienced co-authors. That is a useful invitation. The obstacle for a newcomer is often not a lack of grievance; it is knowing how a grievance becomes a proposal others can inspect. The RIPE Address Policy WG covers IPv4, IPv6 and ASN registration rules, and Lichtblau is listed among its current co-chairs.

A chair has a clock, not a magic stamp

The same session moved on to another proposal, about naming downstream users of IPv4 PA blocks. Participants disagreed over the cost of additional database records and whether a new identifier would identify the party who mattered in an incident. Lichtblau asked the room to settle the intent and take the precise drafting to the mailing list. She promised early minutes so the discussion could continue there. That exchange illustrates the chair's practical power: choose which question the room can answer now, then keep the unresolved one in public view.

The RIPE Policy Development Process, RIPE-781, requires justified objections and public chair summaries at the end of each phase. It names creation, discussion, review and conclusion as separate stages. The chairs assess consensus through that record. A lively room supplies evidence of interest; the list preserves an argument that someone absent can read, contest and improve.

Lichtblau's intervention matters because the binder and the database proposal pose the same institutional temptation. A convenient new document can look like a decision before anyone has agreed which words changed. A busy meeting can look like consent before the affected operators have calculated the work. The public record needs to show the original text, the proposed change, the objection and the chair's reasoned conclusion. Without those steps, the neatest binder is simply a faster way to misplace authority.

Sources: RIPE 93 Address Policy transcript; RIPE-781; Address Policy WG; chair biographies.