Registries & Policy

RIPE proposals to simplify first ASNs and revise IPv6 PI move to Review Phase

Proposal 2026-01 would remove the needs assessment for an organisation's first AS number, and 2024-01 would revise IPv6 PI assignments. Both reached Review Phase, the RIPE Chair Team reported on 22 September.

BYOIP.info Editorial Updated Change dated

What changed

The RIPE Chair Team's September update (22 September 2026) reports two policy proposals moving to Review Phase in the Address Policy Working Group:

  • 2026-01, Simplify assignment of first ASN. Published on 7 July 2026 by Urban Suhadolnik and Leo Vegoda. It would remove the needs assessment for the first AS number assigned to an IP prefix holder. Additional AS numbers would still require a new, unique routing policy. The proposal's rationale points to the large 32-bit ASN pool. The next step is an Impact Analysis from the RIPE NCC.
  • 2024-01, Revised IPv6 PI Assignment Policy. Also in Review Phase. The Chair Team notes growing concern about the proposal's complexity and a suggestion to split it into several proposals.

Separately, the RIPE NCC is preparing a proposal to clarify the IPv6 Assignment and Allocation Policy (ripe-738). An earlier ASN proposal, 2025-01, was withdrawn and archived in July 2026.

Update - 10 November 2026

  • 2024-01 is withdrawn. The proposers withdrew it on 23 September 2026 after feedback. The RIPE NCC announced the withdrawal on 28 September. The proposal page and the archived-proposals list both show Withdrawn. The September body above still records the Chair Team's 22 September Review Phase status; that status no longer applies.
  • 2026-01 remains in Review Phase. The proposal page now carries version 2.0 (12 October 2026) and a published RIPE NCC impact analysis. The current-proposals index still lists it in Review Phase. The earlier “wait for the impact analysis” check is done.

Why it matters for BYOIP teams

Some cloud and CDN BYOIP setups let customers originate their prefixes from their own AS number, and BYOIPv6 depends on holding suitable IPv6 space. Lower friction for a first ASN would still matter for smaller organisations in the RIPE NCC service region. The withdrawn IPv6 PI rewrite means existing ripe-738 rules continue until a later proposal changes them.

What to check

  • The published impact analysis and version 2.0 text for 2026-01 before commenting further.
  • Whether a narrower IPv6 PI proposal is re-introduced on the Address Policy Working Group list after the 2024-01 withdrawal.
  • The Address Policy sessions at future RIPE meetings; RIPE 93 (26-30 October, Sofia) has already passed.

Sources

  1. The RIPE Chair Team Reports, September 2026

    RIPE Labs · published 22 Sept 2026 · checked 30 Sept 2026

  2. 2026-01 Simplify assignment of first ASN

    RIPE NCC · checked 10 Nov 2026

  3. Current Policy Proposals

    RIPE NCC · checked 10 Nov 2026

  4. Archived Policy Proposals

    RIPE NCC · checked 10 Nov 2026

  5. 2024-01 Revised IPv6 PI Assignment Policy

    RIPE NCC · checked 10 Nov 2026

  6. 2024-01 Policy Proposal Withdrawn

    RIPE NCC · published 28 Sept 2026 · checked 10 Nov 2026

Related resources

Topicsripeasnipv6policy