[sig-policy] Revised version of Prop-117 (Prop-117-v002)

    • To: "sig-policy at apnic dot net" <sig-policy at apnic dot net>
    • Subject: [sig-policy] Revised version of Prop-117 (Prop-117-v002)
    • From: Sumon Ahmed Sabir <sumon at fiberathome dot net>
    • Date: Wed, 15 Feb 2017 10:41:08 +0000
    • Delivered-to: sig-policy at mailman dot apnic dot net
    • List-archive: <http://mailman.apnic.net/mailing-lists/sig-policy/>
    • List-help: <mailto:sig-policy-request@lists.apnic.net?subject=help>
    • List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
    • List-post: <mailto:sig-policy@lists.apnic.net>
    • List-subscribe: <https://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=subscribe>

      • Dear SIG Members,

        Tomohiro Fujisaki has submitted a revised version of Prop-117 ( Prop-117-v002) after getting some feedback from the community.

        Please review and  share your thoughts if you have any comments, suggestions on the proposal. This proposal along with three 
        other proposals will be discussed in APNIC43 Policy SIG meeting. 

        Please also find all other proposals for APNIC43 Policy SIG here:


        Masato, Sumon

        ------------------------------------------------------- prop-117-v002: Returned IPv4 address management and Final /8 exhaustion ------------------------------------------------------- Proposer: Tomohiro Fujisaki fujisaki at syce dot 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 reurned 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. Guidance for 103/8 pool exhaustion: - The first time an approved request cannot be fulfilled from the 103/8 pool, Final /8 delegations will end. - APNIC will begin to manage only one (Recovered) IPv4 pool containing any residual 103/8 space and all future returns, including 103/8 returns. - Each new account holder can receive up to a /21 from the IPv4 Recovered pool. - Existing account holders who have not yet received the maximum /21 from the two pools may continue to apply for space from the Recovered pool until they have received a maximum /21 from the two pools. - A waiting list will be created if approved requests cannot be fulfilled. Each new account holder will be given priority in the waiting list. 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 -------------
        Displaying prop-117-v2.txt.