HTTP/2 200 date: Mon, 14 Jul 2025 15:45:06 GMT content-type: text/plain content-length: 740 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 last-modified: Sun, 18 Jun 2017 00:51:26 GMT etag: "770-552316b063f80-gzip" cache-control: max-age=3600, public expires: Mon, 14 Jul 2025 16:45:06 GMT vary: Accept-Encoding content-encoding: gzip x-envoy-upstream-service-time: 7 strict-transport-security: max-age=15552000; preload 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: 95f2252c1a90741b-BLR ------------------------------------------------------- prop-117-v003: Returned IPv4 address management and Final /8 exhaustion ------------------------------------------------------- Proposer: Tomohiro Fujisaki fujisaki@syce.net 1. Problem statement -------------------- APNIC currently makes delegations from two IPv4 pools. These are the 103/8 (Final /8) pool and the non-103/8 IPv4 Recovered pool. With current policy, all returned address space, including 103/8 blocks, will be merged into the IPv4 Recovered pool. If a 103/8 block is returned, it is placed in the IPv4 Recovered pool and re-distributed as returned space. Some organisations may receive duplicate blocks from 103/8: one under the final /8 policy, the other under the returned pool policy. Current APNIC Policy requires account holders to receive address space from the 103/8 (Final /8) pool before they can apply for address space from the Recovered pool. APNIC currently manages a Recovered Pool Waiting List for approved requests that cannot be met from the IPv4 Recovered pool. 2. Objective of policy change ----------------------------- To simplify the address pool management and to provide guidance for 103/8 pool exhaustion. 3. Situation in other regions ----------------------------- None. 4. Proposed policy solution --------------------------- Handling returned address: - Recovered 103/8 space will be placed in the 103/8 (Final /8) pool. - Recovered non-103/8 space will be placed in the IPv4 Recovered pool. 5. Advantages / Disadvantages ----------------------------- Advantages: - Simplifying management of remaining IPv4 address pools. Disadvantages: None. 6. Impact on resource holders ------------------------------ No impact to resource holders. 7. References -------------