HTTP/2 200
date: Sun, 13 Jul 2025 18:31:53 GMT
content-type: text/html; charset=UTF-8
content-length: 20003
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: 441
strict-transport-security: max-age=15552000; preload
last-modified: Sun, 13 Jul 2025 18:31:53 GMT
cf-cache-status: EXPIRED
accept-ranges: bytes
content-security-policy: frame-ancestors 'self' https://rex.apnic.net https://rex.stg.xyz.apnic.net
server: cloudflare
cf-ray: 95eadc16fe78c19c-BLR
prop-164: Allocations of IPv6 Resources longer than a /32 with a nibble boundary alignment – APNIC
Skip to content
prop-164: Allocations of IPv6 Resources longer than a /32 with a nibble boundary alignment
Proposal text
prop-164-v001
Objective
This policy change will reduce the minimum allocation size from a /32 prefix to a /36 prefix. This is to reduce the minimum amount of resources which a member has to apply for, which in turn reduces the allocation of resources which are unnecessary and allows them to maintain more accurate Whois/RDAP records.
Current status
To be discussed at APNIC 60
Authors
Christopher Hawker and Luke Thompson
Relevant forum
Policy SIG
Previous versions
n/a
Secretariat impact assessment
TBA
Proposal history
12 June 2025
Version 1 posted to the Policy SIG mailing list for discussion and community discussion.
