Zum Hauptinhalt springen

RIPE NCC · RIR-Beobachtung

Revised IPv6 PI Assignment Policy

Beginnen Sie hier mit der Dokumentation zu jedem einzelnen Vorschlag: Was änderte sich, warum war dies von Bedeutung, wer argumentierte wofür, wie entwickelten sich die Positionen, was wurde beschlossen und wo weist die Beleglage noch Lücken auf?

Quellenbelegte Fakten

Richtlinien-ID
2024-01
RIR
RIPE NCC
Offizieller Status
Withdrawn
Eingebracht
13.08.2024
Letzte Quellenaktualisierung
18.11.2026

Wer hat die Debatte tatsächlich geprägt?

2Beteiligte insgesamt
2Formelle Akteure

Entwicklung der Richtlinie

End Site definition deferred to another proposal · Version 2 removes the proposed section 2.9 split between allocation-based and PI End Sites, including the detailed routing-policy, Layer 2, customer-device and anycast tests. Its rationale says the new End Site definition will be handled in a separate proposal. The remaining references to End Sites therefore must not be read as adopting those deleted tests.

Planning horizon for a larger PI assignment · Version 2 changes the expected-utilisation planning horizon used to justify larger or additional PI space from twelve to twenty-four months. Current or planned routing policies remain an alternative example of justification, and the nibble-boundary sizing sequence remains /48, /44, /40 and /36.

One growth procedure for existing PI holders · Version 2 applies the extension procedure to holders of one or more PI assignments without the former implementation-date distinction. It deletes the separate legacy reevaluation section. When contiguous expansion is unavailable, the holder may request a new assignment and must return previous assignments within six months; the old automatically described replacement becomes a request option.

Legacy renumbering extensions removed · Version 1 offers older assignments a twelve-month renumbering period with repeat twelve-month extensions on proof of continuing use and inability to renumber. Version 2 omits that exceptional regime and states six months for returning previous assignments after a replacement. It does not impose a new immediate renumbering obligation on every untouched existing assignment.

Explicit prohibition on splitting registrations omitted · Version 2 removes the sentence forbidding post-implementation PI registrations from being split into independent smaller assignments. The aggregation objective and permission to route more-specific prefixes without sub-assignment remain. Deleting this specific sentence does not by itself grant a general right to sub-assign or transfer fragments.

Special-purpose size exception omitted · Version 2 drops the express permission for more-specific special-purpose PI policies to depart from generic assignment criteria. The generic bounds remain. The deletion removes that cross-policy clarification; the retained proposal alone does not determine the continuing effect of a separate IXP assignment policy.

Reservation responsibility made explicit · Version 2 expressly recommends that RIPE NCC reserve space up to the next nibble boundary, replacing the recommendation simply to leave that space unused. The amount of recommended growth room is unchanged; the operational actor is now named.

Remote End Site prohibition qualified by routing exchange · Version 3 adds without the exchange of Internet routing information to the sentence prohibiting use of a PI prefix to connect another entity’s separate End Site. This qualifies the prior blanket wording and aligns it with the preceding ISP interconnection example. It does not delete the general prohibition on sub-assignment or establish unrestricted permission to provide customer access using PI space.

Persistent addressing terminology · Version 3 changes static to persistent in the server/appliance addressing example and its explanatory purpose. It supplies no new duration, assignment-size rule or addressing mechanism. The same-site condition and the surrounding /56-or-longer connectivity wording remain unchanged.

Zeitverlauf der Debatte

  1. Eingebracht

    Eingebracht

    Quellenbelegte Fakten ↗
  2. Offizielle Version

    1.0

    Quellenbelegte Fakten ↗
  3. Offizielle Version

    2.0

    Quellenbelegte Fakten ↗
  4. Offizielle Version

    3.0

    Quellenbelegte Fakten ↗
  5. Offizielle Entscheidung

    withdrawn

    withdrawn

    Quellenbelegte Fakten ↗

Entitäten

Zuletzt aktualisiert:

Wird geladen

Quellen und Abdeckung

Offizielle Richtlinienquellen

Öffentliche Diskussionsarchive

Abdeckung

Früheste Erfassung: 30.06.1992
Letzte Erfassung: 14.11.2026