HTTP/2 200
date: Mon, 14 Jul 2025 03:08:02 GMT
content-type: text/html; charset=UTF-8
content-length: 19797
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: 534
strict-transport-security: max-age=15552000; preload
last-modified: Mon, 14 Jul 2025 03:08:02 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: 95edd02d6e33f470-BLR
Limiting of final /8 policy to specific /9 – APNIC
Skip to content
Limiting of final /8 policy to specific /9
Proposal text
prop-091-v001
Synopsis
This is a proposal to modify the policies for distribution of the "final /8" to only apply to a specific /9 block of the final /8, on the basis that the current policies would unnecessarily prevent the use of over 8 million IPv4 addresses that otherwise should be used to enable
Current status
Abandoned. Abandoned.
Author
David Woodgate
Relevant forum
Policy SIG
Previous versions
NA
Status at other RIRs
There is no similar policy or proposal in other regions.
Proposal history
20 January 2011
Submitted to the Policy SIG mailing list for discussion.
23 February 2011
Was withdrawn by the author at APNIC 31 Policy SIG.
