prop-141: Change maximum delegation size of IPv4 address from 512 (/23) to 768 (/23+/24) addresses – APNIC

prop-141: Change maximum delegation size of IPv4 address from 512 (/23) to 768 (/23+/24) addresses

Proposal textprop-141-v003
Objective

This proposal suggests delegating an additional 256 (/24) IPv4 addresses to the existing APNIC account holders who only received 512 (/23) IPv4 addresses after Thursday, 28 February 2019, and delegate 768 (/23+/24) to the new members.

Current statusWithdrawn
AuthorSimon Sohel Baroi and Aftab Siddiqui
Relevant forumPolicy SIG
Previous versionsprop-141-v001
prop-141-v002
Status at other RIRsThere is no similar policy in place in other RIR regions.
Secretariat impact assessment
prop-141-v001:

APNIC notes the proposed delegation of additional /24 to the existing members, as per the criteria under Section 7.0 “Subsequent IPv4 delegations” who received a maximum of /23 (under current policy) after Thursday, 28 February 2019, and the proposed new policy to change to the IPv4 maximum delegation size to a /23 +/24 to the new members.

APNIC also notes the following proposed thresholds:
– IPv4 maximum delegation size will automatically changes to a /23 if the available (incl reserved) IPv4 pool comes down to 900,000 addresses.

– IPv4 maximum delegation size will automatically changes to a /24 if the available (incl reserved) IPv4 pool comes down to 256,000 addresses, and add the /16 reserved for future use to the available pool.

This proposal would require changes to the website content, procedure documents and manuals, training material, membership forms and various registry systems.

If this proposal reaches consensus, implementation may be completed within 3-6 months.

Clarifications required:
When the available IPv4 pool is down to 900,000 or 256,000 addresses, and in case if a large IPv4 address space is added to this available pool, will the maximum delegation size automatically revert to /23+/24 or /23 respectively, or remain at maximum size of /24?

prop-141-v002:

APNIC notes the proposed delegation of additional /24 to the existing members, as per the criteria under Section 7.0 “Subsequent IPv4 delegations” who received a maximum of /23 (under current policy) after Thursday, 28 February 2019, and the proposed new policy to change the IPv4 maximum delegation size to a /23 +/24 to the new members. As well as, to add the IPv4 /16 reserved pool to the available pool once the address space goes below 190,000 addresses.

APNIC also notes the following proposed thresholds for available + reserved addresses:
– 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

This proposal may create confusion for existing and new members, if the maximum delegation size changes intermittently with the increase or decrease of available IPv4 address space for distribution.

At times, this change may happen real quickly in between making the delegations, and this change
may take sometime to reflect in the system as well as may take a few days to update the published documents, procedures and make announcement to the community. This also may create confusion for members and may delay processing member resource requests.

This proposal would require changes to the website content, procedure documents and manuals,
training material, membership forms and various registry systems.

Implementation of this proposal is unknown at the time of this impact assessment due to the complexity and may require stringent planning and allocation of manpower to complete the required work.
Proposal history
13 August 2021Version 1 posted to the Policy SIG mailing list for discussion and community development.
08 Septemebr 2021Version 2 posted to the Policy SIG mailing list for discussion and community development.
15 Septemebr 2021Version 3 posted to the Policy SIG mailing list for discussion and community development.
16 September 2021Did not reach consensus at APNIC 52.
21 September 2021Sent back to the community for further discussion.
18 February 2021Version 4 posted to the Policy SIG mailing list for community discussion and comments. This new version will not be put to the consensus call at APNIC 53 OPM.
02 March 2022Version 4 presented as informational for community feedback at APNIC 53.
01 March 2023Withdrawn by the authors.