I have no strong opinion positive or negative towards the proposal overall.

I do oppose going from /23 to 0.75 /22. If we’re going to do this, let’s just go
from /23 to /22 and keep things on prefix boundaries.

Owen


> On Sep 7, 2021, at 15:02 , Bertrand Cherrier <[email protected]> wrote:
> 
> Dear SIG members,
> 
> A new version of the proposal "prop-141-v002: Change maximum delegation
> size of IPv4 address from 512 ( /23 ) to 768 (/23+/24) addresses" has
> been sent to the Policy SIG for review.
> 
> It will be presented at the Open Policy Meeting (OPM) at APNIC 52
> on Thursday, 16 September 2021.
> 
> https://conference.apnic.net/52/program/schedule/#/day/4
> 
> We invite you to review and comment on the proposal on the mailing
> list before the OPM.
> 
> The comment period on the mailing list before the OPM is an important
> part of the Policy Development Process (PDP). We encourage you to
> express your views on the proposal:
> 
>   - Do you support or oppose this proposal?
>   - Does this proposal solve a problem you are experiencing? If so,
>      tell the community about your situation.
>   - Do you see any disadvantages in this proposal?
>   - Is there anything in the proposal that is not clear?
>   - What changes could be made to this proposal to make it more effective?
> 
> Information about earlier versions is available at:
> 
> http://www.apnic.net/policy/proposals/prop-141
> 
> Regards,
> Bertrand and Ching-Heng
> APNIC Policy SIG Chairs
> 
> 
> ----------------------------------------------------------------------------------------------------------
>  
> 
> prop-141-v002: Change maximum delegation size of IPv4 address from 512 ( /23 
> ) to 768 (/23+/24) addresses.
> 
> -----------------------------------------------------------------------------------------------------------
>  
> 
> Proposer: Simon Sohel Baroi ([email protected])
>           Aftab Siddiqui ([email protected])
> 
> 
> 1. Problem statement
> --------------------
> According to the APNIC IPv4 Address 
> Report,(https://www.apnic.net/manage-ip/ipv4-exhaustion/ ) the available
> and reserve pool size is as follows:
> 
> Available Pool : IP Address 3,782,144 | 14,774 Of /24
> Reserved Pool : IP Address 1,831,680 | 7,155 Of /24
> 
> If APNIC continues to delegate IPv4 in size of /23 with the average growth 
> rate of 145 x /23 delegations per
> month the pool will be exhausted around Aug/Sep 2027. Which means the huge 
> number of IPv4 addresses will be
> unused for a long time and large community members will still remain behind 
> the NAT box or without Internet
> Connectivity.
> 
> 
> 2. Objective of policy change
> -----------------------------
> The current final /8 allocation policy [1] advise that the current minimum 
> delegation size for IPv4 is 256 (/24)
> addresses and each APNIC account holder is only eligible to receive IPv4 
> address delegations totaling a maximum
> 512 (/23) addresses from the APNIC 103/8 IPv4 address pool. (6.1. Minimum and 
> maximum IPv4 delegations)
> 
> This is a proposal to change the maximum size of IPv4 address delegations 
> from the available IPv4 address pool to
> a totaling of 768 (/23+/24) addresses. This proposal also indicates how APNIC 
> will distribute the IPv4 resources
> systematically when the available pool size reduces.
> 
> Increasing the maximum IPv4 delegation size from /23 to /23+/24 IPv4 address 
> pool will allow Newcomers and also
> Existing APNIC account holders who only received /23 after Thursday, 28 
> February 2019 to receive 256 (/24) IPv4
> addresses.
> 
> 
> 3. Situation in other regions
> -----------------------------
> There is no similar policy in place in other RIR regions.
> 
> 
> 4. Proposed policy solution
> ---------------------------
> It is recommended to increase the IPv4 address delegation size from 512 max 
> (/23) to 768 (/23 + /24). The address
> space can now be allocated from the available 103/8 last /8 block and/or from 
> non 103/8 recovered address blocks.
> This policy will continue until the available + reserved comes down to less 
> than 900,000 IPv4 addresses i.e.
> < 3515x/24, once reaching this threshold the maximum delegation size will 
> revert back to 512 IPv4 addresses (/23)
> and will continue to do so until the available + reserved block comes down to 
> 256,000 IPv4 addresses i.e 1000x/24
> then the delegation size will further reduce to 256 IPv4 addresses i.e. /24. 
> The very first time the reserved and
> available pool goes below 190,000 IPv4 addresses then the IPv4 reserved pool 
> (APNIC-127 Section 5.1.1) for Future
> Use of /16 (i.e. 256 x /24s) will be added to the available pool.
> 
> Thresholds for IPv4 addresses (Available + Reserved):
> 
> - More than 900,000 IPv4 addresses: Delegation /23 + /24
> - Less than 900,000 IPv4 addresses AND More than 256,000 IPv4 addresses: 
> Delegation /23
> - Less than 256,000 IPv4 addresses: Delegation /24
> - Less than 190,000 IPv4 addresses - add APNIC-127 5.1.1 Reserved /16 to 
> available pool: Delegation /24
> 
> 
> It is proposed to modify the section 6.1 maximum IPv4 delegations of the 
> APNIC Internet Number Resource Policies
> [1] accordingly.
> 
> Current Policy text :
> 
> Since Thursday, 28 February 2019, each APNIC account holder is only eligible 
> to receive IPv4 address delegations
> totalling a maximum /23 from the APNIC 103/8 IPv4 address pool.
> 
> New Policy text :
> 
> New APNIC account holder is only eligible to receive IPv4 address delegations 
> totaling a maximum 768 (/23+/24) from
> the APNIC available IPv4 address pool.
> 
> Existing APNIC account holders (since Thursday, 28 February 2019), who only 
> have /23 can apply for another /24 maintaining
> the criteria matched with section 7.0.
> 
> If the available IPv4 Pool size, which consists of available and reserve pool 
> goes below 900,000 addresses (3515, /24s
> after last delegation), the delegation size will automatically become 512 
> (/23) IPv4 addresses.
> 
> If the available IPv4 Pool size, which consists of available and reserve, 
> reaches 256,000 IPv4 addresses (i.e. 1000 /24s
> after last delegation), the delegation size will be reduced to 256 (/24) IPv4 
> addresses. The very first time the reserved
> and available pool goes below 190,000 IPv4 addresses then the IPv4 reserved 
> pool of /16 (256 /24s) will be added to the
> available pool (APNIC-127 Section 5.1.1).
> 
> At any point, if APNIC receives a large block of recovered/returned/etc IPv4 
> address space increasing the total available
> address space and moved into the previous threshold then the delegation size 
> will revert back to previous delegation size
> as well. Also, all delegations at this stage have to be made retrospectively 
> i.e. any member who received smaller delegation
> size will be eligible to receive more IPv4 addresses as per this policy, 
> based on their usage criteria matched with
> section 7.0 and availability of addresses.
> 
> 
> 
> 5. Advantages / Disadvantages
> -----------------------------
> Advantages:
> - This proposal will ensure smooth allocation of IPv4 addresses to existing 
> and new APNIC members.
> 
> Disadvantages:
> - This might add up to 10,000 /24s into the global routing table i.e. 1.2% 
> increase. The current growth rate without this
> policy is approximately 7% every year.
> 
> 
> 6. Impact on resource holders
> -----------------------------
> The Organization who became an APNIC member after Thursday, 28 February 2019 
> and received only /23, can receive another
> /24 IPv4 Resources.
> 
> 
> 7. References
> -------------
> [1] Section 6.1. "Minimum and maximum IPv4 delegations" of "Policies for IPv4 
> address
> space management in the Asia Pacific region"
> https://www.apnic.net/community/policy/resources#6.1.-Minimum-and-maximum-IPv4-delegations
> 
> -- 
> Cordialement,
> ___________________________________________
> Bertrand Cherrier
> Administration Systèmes - R&D
> Micro Logic Systems
> https://www.mls.nc
> Tél : +687 24 99 24
> VoIP : 65 24 99 24
> SAV : +687 36 67 76 (58F/min)
> 
> *              sig-policy:  APNIC SIG on resource management policy           
> *
> _______________________________________________
> sig-policy mailing list
> [email protected]
> https://mailman.apnic.net/mailman/listinfo/sig-policy

*              sig-policy:  APNIC SIG on resource management policy           *
_______________________________________________
sig-policy mailing list
[email protected]
https://mailman.apnic.net/mailman/listinfo/sig-policy

Reply via email to