Hello Jahangir


Final /8 blocks that are returned from Member accounts are being held in a ‘reserved’ status by the Secretariat until the community decides to put them back in the Final /8 free pool, or place them in the IPv4 recovered pool where non-103/8 returns are placed.


At APNIC 43 the proposal reaching consensus was to return them to the Final /8 pool.


This final call will end today, unless extended by the Chairs.


Kind regards,





Adam Gosling

Senior Internet Policy Analyst, APNIC

e: adam@apnic.net

p: +61 7 3858 3142

m: +61 421 456 243




Join the conversation:   https://blog.apnic.net/





From: <sig-policy-bounces@lists.apnic.net> on behalf of Jahangir Hossain <jahangir@parween.net>
Date: Tuesday, 11 April 2017 at 19:39
To: Sumon Ahmed Sabir <sumon@fiberathome.net>
Cc: Policy Mailing List <sig-policy@apnic.net>
Subject: Re: [sig-policy] Final Comment Period for prop-117-v003: Returned IPv4 address management and Final /8 exhaustion


Hi everyone ,

I have a simple question for clarification . How 103/8 block is returned to APNIC which already assigned to members ?

Regards / Jahangir

On Tue, Mar 14, 2017 at 2:43 PM, Sumon Ahmed Sabir <sumon@fiberathome.net> wrote:

Dear colleagues,

Part of prop-117: "Returned IPv4 address management and Final /8 exhaustion",
reached consensus at the APNIC 43 Policy SIG and then later at the AGM.

Components of the proposal regarding which pool 103/8 blocks should be
returned to reached consensus. There was no agreement on the proposal for
Final /8 pool exhaustion procedures.

A new version prop-117-v003 was created to make it clear which part of
the proposal is reaching the final Comment Period.


The proposed policy solution reaching consensus is

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.

This proposal will now move to the next step in the APNIC Policy
Development Process and is being returned to the Policy SIG mailing list
for the final Comment Period.

At the end of this period the Policy SIG Chairs will evaluate comments
made and determine if the consensus reached at APNIC 43 still holds. The
Chairs may extend the Comment Period to a maximum of eight (8) weeks to
allow further discussion.

If consensus holds, the Chair of the Policy SIG will ask the APNIC Executive
Council to endorse the proposal for implementation.

   - Send all comments and questions to: <sig-policy at apnic dot net>
   - Deadline for comments:  23:59 (UTC +10) Wednesday, 12 April 2017

Proposal details, including the full text of the proposal, history, and
links to previous versions are available at:



Sumon, Ching-Heng, Bertrand
Policy SIG Chairs


prop-117-v003: Returned IPv4 address management and Final /8 exhaustion


Proposer:       Tomohiro Fujisaki

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


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


  - Simplifying management of remaining IPv4 address pools.



6. Impact on resource holders

No impact to resource holders.

7. References

*              sig-policy:  APNIC SIG on resource management policy           *
sig-policy mailing list