RIPE NCC · RIR Watchdog
Start here for the proposal-by-proposal record: what changed, why it mattered, who argued for what, how positions evolved, what was decided, and where the evidence still has gaps.
Source facts
Who actually shaped the debate?
BTW Analysis
The accepted proposal clarified the definition of "ASSIGNED PA". The prior wording referred to address space assigned to an End User; version 1.0 expressly included address space assigned to the issuing LIR's infrastructure or an End User. The documented formal change is therefore a textual clarification, while any operational change remains unestablished.
The issue was whether the definition should explicitly recognize the issuing LIR's own infrastructure, rather than referring only to End-User assignments. The proposal framed this as a question of precision and reduced ambiguity. The available record does not support broader claims about institutional, commercial or political motives, nor does it provide enough discussion evidence to reconstruct a contested debate.
Proposal 2019-01 was introduced and version 1.0 was published on 17 January 2019. A distinct accepted decision was recorded on 16 May 2019. The captured record contains zero messages, zero discussion participants and zero active days, so it documents the formal outcome but not a substantive debate. Acceptance should therefore be distinguished from evidence of broad consensus, and the proposal text's statement that it had no opposing arguments is not independently corroborated by a discussion record.
The captured participation set contains one formal actor and one total participant, with no discussion messages or discussion participants. This is a highly sparse record, not evidence that one person controlled the decision. The reported HHI and top-message shares of 0.0 are not meaningfully interpretable because there were no messages or effective participants; they must not be treated as evidence of dispersed participation.
The substantive chokepoint was the classification of address space assigned for use with services provided by the issuing LIR. Version 1.0 resolved that textual ambiguity by expressly naming LIR infrastructure. This gives LIR infrastructure clearer wording-level recognition and may reduce reliance on case-by-case interpretation. The supplied facts do not establish whether this changed operational treatment, merely clarified existing practice, or was implemented in an operative policy.
Loading
Partial
Earliest captured: Jun 30, 1992
Latest captured: Nov 12, 2026
