HTTP/2 301
date: Sun, 13 Jul 2025 18:33:00 GMT
content-type: text/html; charset=iso-8859-1
content-length: 265
location: https://www.apnic.net/community/policy/proposals/prop-094
x-xss-protection: 1; mode=block
referrer-policy: no-referrer, same-origin, strict-origin-when-cross-origin
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
x-envoy-upstream-service-time: 1
strict-transport-security: max-age=15552000; preload
cf-cache-status: MISS
vary: Accept-Encoding
content-security-policy: frame-ancestors 'self' https://rex.apnic.net https://rex.stg.xyz.apnic.net
server: cloudflare
cf-ray: 95eaddc32e7bcf00-BLR
HTTP/2 301
date: Sun, 13 Jul 2025 18:33:01 GMT
content-type: text/html; charset=UTF-8
content-length: 0
location: https://www.apnic.net/community/policy/proposals/prop-094/
x-xss-protection: 1; mode=block
referrer-policy: no-referrer, same-origin, strict-origin-when-cross-origin
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
cf-edge-cache: cache,platform=wordpress
cache-control: max-age=3600
expires: Sun, 13 Jul 2025 19:33:01 GMT
x-redirect-by: WordPress
x-envoy-upstream-service-time: 152
strict-transport-security: max-age=15552000; preload
cf-cache-status: MISS
vary: Accept-Encoding
content-security-policy: frame-ancestors 'self' https://rex.apnic.net https://rex.stg.xyz.apnic.net
server: cloudflare
cf-ray: 95eaddc4787ccf00-BLR
HTTP/2 200
date: Sun, 13 Jul 2025 18:33:01 GMT
content-type: text/html; charset=UTF-8
content-length: 20130
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: 461
strict-transport-security: max-age=15552000; preload
last-modified: Sun, 13 Jul 2025 18:33:01 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: 95eaddc6dbbfcf00-BLR
prop-094: Removing renumbering requirement from final /8 policy – APNIC
Skip to content
prop-094: Removing renumbering requirement from final /8 policy
Proposal text
prop-094-v002
Synopsis
This is a proposal to add an alternative criteria to the requirement for organizations receiving their initial allocation from APNIC to renumber out of their previously deployed space when they are allocated addresses under the final /8 policy.
Current status
Implemented.
Author
Izumi Okutani, Terence Zhang Yinghao
Relevant forum
Policy SIG
Previous versions
prop-094-v001
Status at other RIRs
RIPE: The "Allocations for the last /8" policy does not define additional requirements for the renumbering of address space. See Section 5.6, "Use of last /8 for PA Allocations," in IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region .
There is no similar policy or proposal in the AfriNIC, ARIN or LACNIC regions.
Proposal history
25 January 2011
Submitted to the Policy SIG mailing list for discussion.
24 February 2011
Reached consensus at APNIC 31 Policy SIG with revised text.
1 March 2011
Version 2 renamed to "Removing renumbering requirement from final /8 policy" and sent to the Policy SIG mailing list .
1 March – 26 April 2011
Version 2 in final eight-week comment period.
6 May 2011
Endorsed by APNIC EC.
9 May 2011
Implemented
