HTTP/2 200
date: Sun, 13 Jul 2025 20:49:18 GMT
content-type: text/html; charset=UTF-8
content-length: 19792
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 20:49:18 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: 95eba565db16c7cf-BLR
prop-070: Maximum IPv4 allocation size – APNIC
Skip to content
prop-070: Maximum IPv4 allocation size
Proposal text
prop-072-v001 (3.8 KB)
Synopsis
The policy seeks to create a maximum APNIC allocation size. The proposal then seeks to gradually decrease the maximum allocation size based on the remaining number of /8s in the IANA free pool.
Current status
Abandoned at APNIC 27 in Manila, Philippines.
Author
James Spenceley, Jonny Martin
Relevant forum
Policy SIG
Previous versions
N/A
Status at other RIRs
AfriNIC, ARIN, LACNIC and RIPE currently have no maximum allocation size.
This proposal has not been submitted to other RIRs, but may be in future.
Proposal history
23 January 2009
Submitted to the Policy SIG mailing list for discussion.
26 February 2009
Abandoned at APNIC 27 in Manila, Philippines.
