HTTP/2 200
date: Mon, 14 Jul 2025 09:25:16 GMT
content-type: text/html; charset=UTF-8
content-length: 19875
x-xss-protection: 1; mode=block
referrer-policy: no-referrer, same-origin, strict-origin-when-cross-origin
x-frame-options: SAMEORIGIN
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
cf-edge-cache: cache,platform=wordpress
cache-control: public, max-age=300
link:
; rel="https://api.w.org/"
link:
; rel="alternate"; title="JSON"; type="application/json"
link: ; rel=shortlink
vary: Accept-Encoding
content-encoding: gzip
x-envoy-upstream-service-time: 529
strict-transport-security: max-age=15552000; preload
last-modified: Mon, 14 Jul 2025 09:25:16 GMT
cf-cache-status: MISS
accept-ranges: bytes
content-security-policy: frame-ancestors 'self' https://rex.apnic.net https://rex.stg.xyz.apnic.net
server: cloudflare
cf-ray: 95eff8c52a83741b-BLR
prop-112: On demand expansion of IPv6 address allocation size in legacy IPv6 space – APNIC
Skip to content
prop-112: On demand expansion of IPv6 address allocation size in legacy IPv6 space
Proposal text
prop-112-v001
Synopsis
This proposal modifies the eligibility criteria for organizations with 'legacy' IPv6 blocks to enable them to extend their IPv6 address space up to a /29 without meeting the Utilization Rate criteria for
Current status
Abandoned.
Author
Tomohiro Fujisaki
Relevant forum
Policy SIG
Previous versions
N/A
Status at other RIRs
RIPE NCC: The policy "Extension of IPv6 /32 to /29 on a per-allocation vs per-LIR basis" is adopted in the RIPE NCC service region and LIRs may ask for up to a /29 IPv6 by default.
Proposal history
4 February 2015
PostedPolicy SIG mailing list for discussion.
5 March 2015
Did not reach consensus at the APNIC 39 Policy SIG and was abandoned.
