RIPE NCC · RIR Watchdog

Allocations from the last /8

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

Policy ID: 2010-02
RIR: RIPE NCC
Official status: Accepted
Normalized status: Accepted
Introduced: Unknown
Last source update: Oct 28, 2026
Coverage: Partial

Who actually shaped the debate?

4Total participants

2Discussion contributors

2Formal actors

2Discussion messages

2Effective participants

100%Top-five discussion share

1People covering 50%

2People covering 80%

BTW Analysis

What changed

The proposal evolved from allowing one allocation of no more than a /22 when the RIPE NCC held an equivalent of a /8 or less, to a final-/8 policy for PA allocations that grants each eligible LIR exactly one /22. The later version also expressly excludes other allocation or assignment types, retains the IPv6-allocation prerequisite, and preserves a /16 reserve for unforeseen uses. Version 2.0 specifically emphasizes access for new entrants, while its supplied text contains rationale and summary rather than complete operative clauses. The policy was recorded as accepted on 19 January 2011.

What the debate was really about

The central choice was how to ration the final IPv4 pool: preserve access for more LIRs, including new entrants and organisations preparing for the IPv6 transition, or accommodate larger demonstrated needs from individual organisations. The design chose breadth and a uniform ceiling over case-by-case allocation based on larger requirements. It also linked access to a prior IPv6 allocation, excluded IPv4 PI assignments, reserved a /16 for unforeseen uses, and recognised the risk that organisations might create multiple LIR registrations to obtain more space.

Arguments that prevailed

The final /8 should be rationed to reduce the risk that one or a few organisations consume the pool through large, fully justified applications.
The policy should preserve some routable IPv4 space for the IPv6 transition and give new entrants an opportunity to obtain space before exhaustion.
A uniform one-per-LIR rule and, in version 3.0, an exact /22 allocation should take priority over satisfying larger individual requirements.
A /16 should be retained for unforeseen future uses rather than distributed immediately.

Arguments that did not prevail

Organisations with demonstrated IPv4 requirements larger than the permitted allocation should receive more than the policy cap from this final pool.
IPv4 PI addresses should be assigned through this policy.
The final pool should primarily address the growth needs of a small number of organisations rather than support broader transition access.
The risk of multiple LIR registrations should prevent adoption of the one-allocation framework; instead, the policy adopted administrative vigilance while acknowledging that complete compliance may be difficult.

Decision vs debate

The recorded outcome was accepted on 19 January 2011, following accepted version events for versions 1.0, 2.0 and 3.0 dated 14 August 2010. That establishes the formal decision outcome, not the depth or representativeness of support. The supplied participation record contains two messages, two discussion participants, two formal actors and four total participants; only one participant has a substantive stance observation, and that observation is procedural or neutral. Discussion activity also includes a recorded date in April 2015, after the decision, so the aggregate metrics cannot be treated as a purely pre-decision account of debate.

Participation concentration

The observed discussion is extremely small rather than dominated by one speaker. The largest contributor accounted for 50% of messages, the HHI was 0.5, and the effective participant count was 2.0. Both discussion participants contributed only once, and there were no repeat participants. Thus the sample is evenly split within its two-person discussion, but it is too narrow to support claims of broad, representative or unanimous community support. The 100% top-five and top-ten shares have little interpretive value in a two-participant sample.

Chokepoint analysis

The policy shifts allocation discretion toward a fixed scarcity rule: an eligible LIR may receive only one allocation from the final /8, and version 3.0 fixes that allocation at exactly one /22 even where documented needs are larger. Access remains conditional on meeting the applicable IPv4 eligibility criteria and already holding an IPv6 allocation. Administrative judgment remains important for eligibility review and vigilance against attempts to obtain additional space through multiple LIR registrations. The /16 reserve is another control point, preserving flexibility for unforeseen uses while allowing its later return to the distribution pool if unused. The supplied record describes these intended mechanisms but does not establish their operational results.

Uncertainties

The supplied version 2.0 text does not contain complete operative policy clauses, so every intermediate rule change cannot be reconstructed.
All three version events carry the same supplied publication timestamp, so the elapsed time between revisions is not established.
The participation metrics combine activity before and after the recorded decision and therefore do not isolate decision-forming deliberation.
The available stance record contains only one procedural-or-neutral observation, so substantive support and opposition cannot be reliably measured.
The accepted status does not establish implementation, operational effectiveness, consensus depth or representativeness.
The supplied record does not show how many allocations were made, whether multiple-LIR behaviour occurred, how the reserve was used, or whether the transition and new-entrant objectives were achieved.

Source facts

Policy evolution

1.0

Accepted · Accepted

Aug 14, 2010

BTW Analysis

What changed

What the debate was really about

Arguments that prevailed

Arguments that did not prevail

Decision vs debate

Participation concentration

Chokepoint analysis

Uncertainties

Source facts

Policy evolution

Debate timeline

1.0

2.0

3.0

[address-policy-wg] Agenda (second draft) for RIPE 61 in Rome

accepted

[address-policy-wg] Hoarding /22 out of 185/8

Entities

Sources and coverage

Official policy sources

Public discussion archives

Coverage

Freshness

Known gaps