Ce qui a changé
La seule évolution vérifiée est l’introduction de la proposition RIPE NCC 2024-02 le 14 octobre 2024. Aucun changement ultérieur de texte, de statut, de position ou de mise en œuvre ne peut être affirmé à partir des éléments fournis.
RIPE NCC · Veille des RIR
Commencez ici pour consulter l’historique, proposition par proposition : ce qui a changé, pourquoi cela comptait, qui a défendu quoi, comment les positions ont évolué, ce qui a été décidé et quelles lacunes subsistent dans les preuves.
Faits sourcés
Qui a réellement façonné le débat ?
Analyse BTW
La seule évolution vérifiée est l’introduction de la proposition RIPE NCC 2024-02 le 14 octobre 2024. Aucun changement ultérieur de texte, de statut, de position ou de mise en œuvre ne peut être affirmé à partir des éléments fournis.
L’objet substantiel du débat ne peut pas être déterminé. Aucun message, argument, objectif de politique, intérêt de partie prenante ou historique de position n’est fourni. Les faits permettent seulement de constater qu’une proposition a été introduite, sans révéler les désaccords, incitations ou arbitrages qu’elle aurait suscités.
Aucune discussion capturée ni décision finale ne peut être constatée. Le corpus mesuré compte zéro message, zéro participant à la discussion, zéro participant doté d’une position et zéro transition de position. La chronologie établit uniquement l’introduction de la proposition le 14 octobre 2024; elle ne permet pas de la qualifier d’adoptée, rejetée, retirée ou close sans consensus.
Les parts de messages des principaux participants, le HHI et le nombre effectif de participants sont tous nuls parce qu’aucun message n’est enregistré. Ces valeurs ne démontrent donc ni une participation équitable ni une faible concentration: aucune distribution de contributions n’est observable. Les deux acteurs formels et les deux participants totaux recensés ne peuvent pas être assimilés à un noyau dominant en l’absence de messages et d’informations sur leurs rôles.
Aucun point de blocage décisionnel ne peut être identifié. Le seul jalon vérifié est l’introduction de la proposition, et aucun message, position, vote, constat de consensus ou acte décisionnel ultérieur n’est fourni. Les deux acteurs formels recensés témoignent d’une implication procédurale minimale, mais leur identité, leur fonction et leur influence ne sont pas établies.
Initial allocation range · Version 2 changes the undocumented initial-allocation choice from /32 or /28 to the full range /32 up to /28. Intermediate sizes therefore become explicit options. Requests larger than /28 still require justification.
LIRs that meet the initial allocation criteria are eligible to receive an initial allocation of /32 or /28 without needing to supply any additional information.Faits sourcés ↗
LIRs that meet the initial allocation criteria are eligible to receive an initial allocation of /32 up to /28 without needing to supply any additional information.Faits sourcés ↗
One extension per organization · Version 2 replaces the entitlement of an LIR to extend each qualifying allocation with a one-time extension of one allocation per organization. The rationale identifies limiting stockpiling as the purpose. The /28 ceiling and the restriction to allocations originally issued directly by RIPE NCC as a single prefix remain.
LIRs that hold one or more IPv6 allocations that were originally issued directly by the RIPE NCC as a single prefix may request an extension of each such allocation up to a /28 without the need for additional documentation.Faits sourcés ↗
Organizations, not LIRs, that hold one or more IPv6 allocations that were originally issued directly by the RIPE NCC as a single prefix may request once an extension of one of such allocation up to a /28 without the need for additional documentation.Faits sourcés ↗
Conservation objection and reserved-space response · Version 2 replaces the absence of opposing arguments with a conservation objection: the new maximum initial block contains twice as much space as /29. Its response says RIPE NCC already reserves a /26 for each new /29 and argues the depletion rate would not increase significantly. That is a stated counter-argument, not a measured outcome; smaller requests remain possible.
This policy proposal is perceived as counterproductive to conservation efforts. Under the proposal, LIRs can initially receive up to twice the amount of IPv6 space compared to the current system. Counterarguments: For each new /29 allocation, the RIPE NCC already reserves a /26 block. This means that the proposed change will not significantly increase the depletion rate of the RIPE NCC address pool.Faits sourcés ↗
Partial-transfer objection and scope of the extension estimate · Version 2 adds the objection that a /28 can be split into sixteen /32 transfers, with the response that partially transferred allocations cannot be extended again. It also qualifies the unchanged 91% extension-availability estimate as including presumed stockpilers. Neither the numerical estimate nor the original-single-prefix restriction is newly introduced here.
Allowing extensions only for allocations originally issued as a single prefix avoids the risk of abuse by infinitely extending chunks resulting from partial IPv6 transfers.Faits sourcés ↗
By extending the initial allocation size to /28, LIRs gain the ability to split and transfer up to 16 /32 blocks (the current minimum allocation size) to other LIRs. Counterargument: This practice would be discouraged by the fact that allocations resulting from partial transfers could not be extended anymore.Faits sourcés ↗
Member-based extension entitlement and direct issuance · Version 3 replaces organization with Member and expressly requires the allocation to have been issued directly to that Member. It states separately that only one extension is available per Member regardless of how many LIR accounts it holds. The /28 limit, single-prefix origin and initial /32-to-/28 range are unchanged.
Organizations, not LIRs, that hold one or more IPv6 allocations that were originally issued directly by the RIPE NCC as a single prefix may request once an extension of one of such allocation up to a /28 without the need for additional documentation.Faits sourcés ↗
A Member, that holds one or more IPv6 allocations originally issued directly to them by the RIPE NCC as a single prefix, may request an extension of one of these allocations up to a /28 without the need for additional documentation. Only one such extension may be granted per Member, regardless of the number of LIR accounts they hold.Faits sourcés ↗
Extension allowance moves from Member to LIR · Version 4 returns the extension clause to LIRs and removes the explicit one-per-Member limit across multiple LIR accounts. Its rationale now describes one extension per LIR without further justification and cites Executive Board concerns about using Members. This changes the unit of eligibility; the initial allocation range and /28 extension ceiling remain unchanged.
Only one such extension may be granted per Member, regardless of the number of LIR accounts they hold.Faits sourcés ↗
The proposal allows only one extension per LIR without further justification, which limits some of the potential adverse effects of stock-pilers. It also addresses the RIPE NCC Executive Board’s concerns in the previous impact analysis about using “Members” instead of “LIRs”.Faits sourcés ↗
Original allocation provenance wording · Version 4 retains the requirement that the allocation originated as a single prefix directly from RIPE NCC but removes the words requiring issuance directly to the current applicant. The retained text no longer states that original-recipient condition explicitly. This wording change alone does not establish that every transferred block qualifies; the single-prefix restriction and the proposal’s warning about partial transfers remain.
A Member, that holds one or more IPv6 allocations originally issued directly to them by the RIPE NCC as a single prefix, may request an extension of one of these allocations up to a /28 without the need for additional documentation.Faits sourcés ↗
LIRs that hold one or more IPv6 allocations originally issued directly by the RIPE NCC as a single prefix can request an extension of one of these allocations up to a /28 without providing further documentation.Faits sourcés ↗
Chargement
Partielle
Première capture: 30 juin 1992
Dernière capture: 12 nov. 2026