<HTML>
<HEAD>
<TITLE>Global Policy Proposal for the Allocation of IPv4 Blocks to Regional Internet Registries</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Dear Members,<BR>
<BR>
Attached (and inline), please find a revised version of the above policy. Revisions on the initial draft have been made to suit the AfriNIC region.<BR>
<BR>
Regards,<BR>
<BR>
Vincent Ngundi<BR>
<B>Chair, AfriNIC PDP-MG<BR>
</B><BR>
####### Global Policy Proposal for the Allocation of IPv4 Blocks to Regional Internet Registries #######<BR>
<BR>
Proposed by: Adiel A. Akplogan (on behalf of the Drafting committee)<BR>
<BR>
Authors: <BR>
<BR>
Adiel A. Akplogan, AfriNIC<BR>
<BR>
Raul Echeberria, LACNIC<BR>
<BR>
Maemura Akinori, APNIC<BR>
<BR>
Geoff Huston, APNIC<BR>
<BR>
Axel Pawlik, RIPE NCC<BR>
<BR>
Ray Plzak, ARIN<BR>
<BR>
Oscar A. Robles-Garay, LACNIC<BR>
<BR>
Nigel Titley, RIPE NCC<BR>
<BR>
Paul Wilson, APNIC <BR>
<BR>
<BR>
<BR>
Your Organisation: AfriNIC<BR>
<BR>
Policy Affected: N/A<BR>
<BR>
Date: 09/03/2009<BR>
<BR>
Proposal Version: 3.0<BR>
<BR>
<BR>
<BR>
Proposal: Allocation of IPv4 Blocks to Regional Internet Registries<BR>
<BR>
<BR>
<BR>
A. Incentive: <BR>
<BR>
-------------<BR>
<BR>
<BR>
<BR>
With the depletion of the IANA free pool of IPv4 address space, the current<BR>
<BR>
policy regarding the allocation of IPv4 address space to the RIRs will become<BR>
<BR>
irrelevant. The RIRs may, according to their individual policies and procedures,<BR>
<BR>
recover IPv4 address space. This policy provides a mechanism for the RIRs to put<BR>
<BR>
the recovered IPv4 address space back to the the IANA central pool and provides <BR>
<BR>
the IANA the policy by which it can allocate them back to the RIRs on a needs <BR>
<BR>
basis. This policy creates a new global pool of IPv4 address space that can be <BR>
<BR>
allocated where it is needed on a global basis without a transfer of address <BR>
<BR>
space between the RIRs.<BR>
<BR>
<BR>
<BR>
B. Proposal <BR>
<BR>
------------<BR>
<BR>
<BR>
<BR>
This document describes the policy governing the allocation of IPv4 address<BR>
<BR>
space from the IANA to the Regional Internet Registries (RIRs). This document<BR>
<BR>
does not stipulate performance requirements in the provision of services by IANA<BR>
<BR>
to an RIR in accordance with this policy. Such requirements should be specified<BR>
<BR>
by appropriate agreements among the RIRs and ICANN.<BR>
<BR>
<BR>
<BR>
This policy is to be implemented in two phases.<BR>
<BR>
<BR>
<BR>
1. Phase I: Recovery of IPv4 Address Space<BR>
<BR>
<BR>
<BR>
Upon ratification of this policy by the ICANN Board of Directors, the IANA shall<BR>
<BR>
establish a mechanism to receive IPv4 address space which is returned to it by the <BR>
<BR>
RIRs, and hold that address space in a 'recovered IPv4 pool'.<BR>
<BR>
<BR>
<BR>
Each RIR through their respective chosen policies and strategies may recover IPv4 <BR>
<BR>
address space which is under their administration. Each RIR shall at quarterly <BR>
<BR>
intervals return any such recovered address space to the IANA in aggregated blocks <BR>
<BR>
of /24 or larger, for inclusion in the recovered IPv4 pool.<BR>
<BR>
<BR>
<BR>
During Phase I, no allocations will be made from the recovered IPv4 pool.<BR>
<BR>
<BR>
<BR>
2. Phase II: Allocation of Recovered IPv4 address space by the IANA<BR>
<BR>
<BR>
<BR>
Upon ratification of this policy by the ICANN Board of Directors and a declaration <BR>
<BR>
by the IANA that its existing free pool of unallocated IPv4 address space is <BR>
<BR>
depleted; Global Addressing Policy ASO-001-2 (adopted by ICANN Board 8 April 2005 <BR>
<BR>
[1]) is rescinded. IANA will then commence to allocate the IPv4 address space from <BR>
<BR>
the recovered IPv4 pool.<BR>
<BR>
<BR>
<BR>
The following definitions apply to this policy:<BR>
<BR>
<BR>
<BR>
a. Recovered Address Space. Recovered address space is that address space <BR>
<BR>
that is returned to an RIR as a result of any activity that seeks to <BR>
<BR>
reclaim unused address space or is voluntarily returned to the RIR or is<BR>
<BR>
reclaimed by the RIR as a result of legal action or abuse determination.<BR>
<BR>
Recovered address space does not include that address space that is reclaimed<BR>
<BR>
because of non-payment of contractual fees whose reclamation date is less than <BR>
<BR>
1 year at the time of the report.<BR>
<BR>
<BR>
<BR>
b. IPv4 Address Holdings. IPv4 address holdings are all unallocated IPv4<BR>
<BR>
address space held by an RIR to include recovered address space not yet returned<BR>
<BR>
less that address space that is committed in accordance with the RIR's<BR>
<BR>
reservation policy and practices.<BR>
<BR>
<BR>
<BR>
c. Aggregated address blocks. Aggregated address blocks are contiguous<BR>
<BR>
prefixes that can be aggregated on natural bit boundaries. 10.0.0.0/24 and<BR>
<BR>
10.0.1.0/24 are two contiguous prefixes that can be combined to form an<BR>
<BR>
aggregated address block. 10.0.0.0/24 and 10.0.1.0/25 are two contiguous<BR>
<BR>
prefixes that cannot be combined on a natural bit boundary to form an aggregated<BR>
<BR>
block.<BR>
<BR>
<BR>
<BR>
2.1 Allocation of IPv4 Address Space<BR>
<BR>
<BR>
<BR>
a. For the purposes of this policy, an 'IPv4 allocation period' is defined as<BR>
<BR>
a 6-month period following 1 March or 1 September in each year.<BR>
<BR>
<BR>
<BR>
b. At the beginning of each IPv4 allocation period, the IANA will determine<BR>
<BR>
the 'IPv4 allocation unit' for that period, as 1/10 of its IPv4 address pool,<BR>
<BR>
rounded down to the next CIDR (power-of-2) boundary. The minimum 'IPv4<BR>
<BR>
allocation unit' size will be a /24.<BR>
<BR>
<BR>
<BR>
c. In each allocation period, each RIR may issue one IPv4 request to the<BR>
<BR>
IANA. Providing that the RIR satisfies the allocation criteria described in<BR>
<BR>
paragraph 2.2, the IANA will allocate a single allocation unit, composed of the<BR>
<BR>
smallest possible number of blocks available in its IPv4 address pool.<BR>
<BR>
<BR>
<BR>
An example of how allocations would be made in practice is included as Appendix A.<BR>
<BR>
<BR>
<BR>
2.2 IPv4 Address Space Allocation Criteria<BR>
<BR>
<BR>
<BR>
A RIR is eligible to receive additional IPv4 address space from the IANA when the <BR>
<BR>
total of its IPv4 address holdings is less than 50% of the current IPv4 allocation <BR>
<BR>
unit, and providing that it has not already received an IPv4 allocation from the <BR>
<BR>
IANA during the current IPv4 allocation period.<BR>
<BR>
<BR>
<BR>
2.3 Initial Allocation of IPv4 Address Space<BR>
<BR>
<BR>
<BR>
Each new RIR shall, at the moment of recognition, be allocated one (1) allocation <BR>
<BR>
unit by the IANA. If an allocation unit is not available, then the IANA will issue <BR>
<BR>
this block as soon as one is available. This allocation will be made regardless of <BR>
<BR>
the newly formed RIR's projected utilization figures and shall be independent of the <BR>
<BR>
IPv4 address space that may have been transferred to the new RIR by the already <BR>
<BR>
existing RIRs as part of the formal transition process.<BR>
<BR>
<BR>
<BR>
2.4 Reporting<BR>
<BR>
<BR>
<BR>
a. All returned space is to be recorded in an IANA-published log of IPv4<BR>
<BR>
address space transactions, with each log entry detailing the returned address<BR>
<BR>
block, the date of the return, and the returning RIR.<BR>
<BR>
<BR>
<BR>
b. All allocated space is also to be recorded in this IANA-published log of<BR>
<BR>
IPv4 address space transactions, with each log entry detailing the address<BR>
<BR>
blocks, the date of the allocation and the recipient RIR.<BR>
<BR>
<BR>
<BR>
c. The IANA will maintain a public registry of the current disposition of all<BR>
<BR>
IPv4 address space, detailing all reservations and current allocations and<BR>
<BR>
current IANA-held address space that is unallocated.<BR>
<BR>
<BR>
<BR>
d. The IANA may make public announcements of IPv4 address block transactions<BR>
<BR>
that occur under this policy. The IANA will make appropriate modifications to<BR>
<BR>
the "Internet Protocol V4 Address Space" [2] page of the IANA website and may<BR>
<BR>
make announcements to its own appropriate announcement lists. The IANA<BR>
<BR>
announcements will be limited to which address ranges, the time of allocation<BR>
<BR>
and to which Registry they have been allocated.<BR>
<BR>
<BR>
<BR>
C. Situation in other RIRs <BR>
<BR>
--------------------------<BR>
<BR>
<BR>
<BR>
This proposal has been adopted in APNIC region and is being submitted in all other <BR>
<BR>
RIR regions, with a view to becoming a global policy [3].<BR>
<BR>
<BR>
<BR>
D. References<BR>
<BR>
--------------<BR>
<BR>
<BR>
<BR>
[1] Global Addressing Policy ASO-001-2 <BR>
<BR>
<a href="http://aso.icann.org/docs/aso-001-2.pdf">http://aso.icann.org/docs/aso-001-2.pdf</a><BR>
<BR>
<BR>
<BR>
[2] Internet Protocol v4 Address Space<BR>
<BR>
<a href="http://www.iana.org/assignments/ipv4-address-space">http://www.iana.org/assignments/ipv4-address-space</a><BR>
<BR>
<BR>
<BR>
[3] ICANN Address Supporting Organization (ASO) MoU<BR>
<BR>
<a href="http://aso.icann.org/docs/aso-mou2004.html">http://aso.icann.org/docs/aso-mou2004.html</a><BR>
<BR>
<BR>
<BR>
Appendix A <BR>
<BR>
-----------<BR>
<BR>
<BR>
<BR>
Example 1:<BR>
<BR>
<BR>
<BR>
On 1 March 2020, IANA has the equivalent of a /17 (32,768 addresses) worth of IPv4 <BR>
<BR>
addresses.<BR>
<BR>
<BR>
<BR>
a. IANA calculates that 1/10 of this space is 3,276 addresses.<BR>
<BR>
<BR>
<BR>
b. IANA rounds this down to the next bit boundary, which creates a minimum<BR>
<BR>
allocation size of /21 (2,048 addresses).<BR>
<BR>
<BR>
<BR>
c. Each RIR can request and receive a single allocation unit equivalent to a<BR>
<BR>
/21 worth of addresses.<BR>
<BR>
<BR>
<BR>
d. IANA may not be able to allocate a contiguous /21 and may allocate<BR>
<BR>
discontinuous smaller blocks equivalent to a /21 worth of addresses.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Example 2:<BR>
<BR>
<BR>
<BR>
On 1 March 2020, IANA has the equivalent of a /20 (4,096 addresses) worth of IPv4 <BR>
<BR>
addresses.<BR>
<BR>
<BR>
<BR>
a. IANA calculates that 1/10 of this space is 409 addresses.<BR>
<BR>
<BR>
<BR>
b. IANA rounds this down to the next bit boundary, which creates a minimum<BR>
<BR>
allocation size of /24 (256 addresses).<BR>
<BR>
<BR>
<BR>
c. Each RIR can request and receive a single allocation unit equivalent to a<BR>
<BR>
/24 worth of addresses.<BR>
<BR>
<BR>
<BR>
d. As the minimum size of address space returned to IANA is /24, IANA can<BR>
<BR>
allocate a contiguous range of addresses that amount to a /24.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Example 3:<BR>
<BR>
<BR>
<BR>
On 1 March 2020, IANA has the equivalent of a /21 (2,048 addresses) worth of IPv4 <BR>
<BR>
addresses.<BR>
<BR>
<BR>
<BR>
a. IANA calculates that 1/10 of this space is 204 addresses.<BR>
<BR>
<BR>
<BR>
b. IANA rounds this down to the next bit boundary, which creates a minimum<BR>
<BR>
allocation size of /25 (128 addresses).<BR>
<BR>
<BR>
<BR>
c. A /25 is smaller than the minimum permissible allocation size under this<BR>
<BR>
policy. Therefore, IANA is unable to make an allocation until more address<BR>
<BR>
space is received.<BR>
<BR>
####### /Global Policy Proposal for the Allocation of IPv4 Blocks to Regional Internet Registries #######</SPAN></FONT>
</BODY>
</HTML>