HTTP/2 200 date: Mon, 14 Jul 2025 16:17:20 GMT content-type: text/plain content-length: 1204 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:48:36 GMT etag: "c65-5523160e44100-gzip" cache-control: max-age=3600, public expires: Mon, 14 Jul 2025 17:17:20 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: 95f25465cc3fc1b5-BLR ________________________________________________________________________ prop-063-v002: Reducing timeframe of IPv4 allocations from twelve to six months ________________________________________________________________________ Authors: Philip Smith pfs@cisco.com Randy Bush randy@psg.com Jonny Martin jonny@jonnynet.net Version: 2 Date: 17 February 2009 1. Introduction ---------------- This is a proposal to change the timeframe APNIC uses to make IPv4 allocations to meet LIRs' needs from twelve months to six months. 2. Summary of current problem ------------------------------ APNIC currently makes IPv4 allocations to LIRs to meet their addressing needs for up to twelve months. In the IPv4 run out phase, this means that any LIR applying for IPv4 address space will receive sufficient addresses for their projected needs for the next 12 months. With the rapidly diminishing pool, this is very likely to cause unfair distribution of the remaining IPv4 pool. In addition, as the date of the end of the IANA IPv4 free pool approaches, having a 12 month allocation window makes less and less logical sense as it estimates usage past when there is anything left to use. 3. Situation in other RIRs --------------------------- This proposal has not been submitted to the other RIRs. AfriNIC, ARIN, LACNIC and RIPE currently make IPv4 allocations based on an LIR's estimated needs for up to twelve months. 4. Details of the proposal --------------------------- It is proposed that APNIC change the timeframe for which IPv4 allocations are made to to meet LIR's needs from twelve months to six months. This means that an organisation applying for IPv4 address space will only receive sufficient address space for their needs for the upcoming six months. Once that six month allocation has run out, the organisation will need to apply for another six month allocation. 4.1 Allocations exempted from the proposed policy LIRs requesting the current minimum allocation size will be exempt from the proposal and will continue to have a 12 month timeframe in which to justify need for address space. 5. Advantages and disadvantages of the proposal ------------------------------------------------ 5.1 Advantages - Ensures that there is a more even distribution of the remaining IPv4 address pool. - Ensures that organisations have a greater opportunity to participate in the remaining IPv4 address pool during the runout phase. 5.2 Disadvantages - Organisations applying for IPv4 address space only receive sufficient resources for the next six months. - Organisations applying for IPv4 address space may have double the annual application administration to perform. APNIC Secretariat may also have double the administration to perform. 6. Effect on APNIC members --------------------------- The proposal impacts all APNIC members. 7. Effect on NIRs ------------------ The proposal has no direct impact on NIRS, but impacts members of NIRs in the same way it impacts APNIC members.