Your IP address is 54.226.81.185

Related articles

The Policy Development Process AFRINIC Public Policy Meetings View Current Policies View recent discussions
(mailing list)
Propose a policy
The Policy Development Working Group (PDWG) PPM Minutes archives View Policy Proposals
(under discussion)
Participate in the policy discussions (mailing list) Call for Comment on Documents

 

Filters

Global Policy for the Allocation of IPv4 Blocks to Regional Internet Registries

 

Details
  • Ref. Name:
    AFPUB-2009-v4-002
  • Old Ref:
    Afpol-v4gb200903
  • Status:
    Implemented
  • Date:
    11 Nov 2010
  • Author:
    • Adiel A. Akplogan,
      AfriNIC
    • Maemura Akinori,
      APNIC
    • Geoff Huston,
      APNIC
    • Paul Wilson,
      APNIC
    • Ray Plzak,
      ARIN
    • Oscar A. Robles-Garay,
      LACNIC
    • Raul Echeberria,
      LACNIC
    • Axel Pawlik,
      RIPE NCC
    • Nigel Titley,
      RIPE NCC

1) Incentive

With the depletion of the IANA free pool of IPv4 address space, the current policy regarding the allocation of IPv4 address space to the RIRs will become irrelevant. The RIRs may, according to their individual policies and procedures, recover IPv4 address space. This policy provides a mechanism for the RIRs to put the recovered IPv4 address space back to the the IANA central pool and provides the IANA the policy by which it can allocate them back to the RIRs on a needs basis. This policy creates a new global pool of IPv4 address space that can be allocated where it is needed on a global basis without a transfer of address space between the RIRs.

AFRINICwill therefore assign numbering resources to entities requiring temporary IP numbers for a fixed period of time. In this document, "IP resources" refers to unicast IPv4/v6 addresses and AS numbers.

 

2) Proposal

This document describes the policy governing the allocation of IPv4 address space from the IANA to the Regional Internet Registries (RIRs). This document does not stipulate performance requirements in the provision of services by IANA to an RIR in accordance with this policy. Such requirements should be specified by appropriate agreements among the RIRs and ICANN. This policy is to be implemented in two phases.

  1. Phase I: Recovery of IPv4 Address Space - Upon ratification of this policy by the ICANN Board of Directors, the IANA shall establish a mechanism to receive IPv4 address space which is returned to it by the RIRs, and hold that address space in a 'recovered IPv4 pool'. Each RIR through their respective chosen policies and strategies may recover IPv4 address space which is under their administration. Each RIR shall at quarterly intervals return any such recovered address space to the IANA in aggregated blocks of /24 or larger, for inclusion in the recovered IPv4 pool. During Phase I, no allocations will be made from the recovered IPv4 pool.
  2. Phase II: Allocation of Recovered IPv4 address space by the IANA- Upon ratification of this policy by the ICANN Board of Directors and a declaration by the IANA that its existing free pool of unallocated IPv4 address space is depleted; Global Addressing Policy ASO-001-2 (adopted by ICANN Board 8 April 2005 [1]) is rescinded. IANA will then commence to allocate the IPv4 address space from the recovered IPv4 pool. The following definitions apply to this policy
    • Recovered Address Space. Recovered address space is that address space that is returned to an RIR as a result of any activity that seeks to reclaim unused address space or is voluntarily returned to the RIR or is reclaimed by the RIR as a result of legal action or abuse determination. Recovered address space does not include that address space that is reclaimed because of non-payment of contractual fees whose reclamation date is less than 1 year at the time of the report.
    • IPv4 Address Holdings. IPv4 address holdings are all unallocated IPv4 address space held by an RIR to include recovered address space not yet returned less that address space that is committed in accordance with the RIR's reservation policy and practices.
    • Aggregated address blocks. Aggregated address blocks are contiguous prefixes that can be aggregated on natural bit boundaries. 10.0.0.0/24 and 10.0.1.0/24 are two contiguous prefixes that can be combined to form an aggregated address block. 10.0.0.0/24 and 10.0.1.0/25 are two contiguous prefixes that cannot be combined on a natural bit boundary to form an aggregated block.

 

3) Allocation of IPv4 Address Space

(A) For the purposes of this policy, an 'IPv4 allocation period' is defined as a 6-month period following 1 March or 1 September in each year.

(B) At the beginning of each IPv4 allocation period, the IANA will determine the 'IPv4 allocation unit' for that period, as 1/10 of its IPv4 address pool, rounded down to the next CIDR (power-of-2) boundary. The minimum 'IPv4 allocation unit' size will be a /24.

(C) In each allocation period, each RIR may issue one IPv4 request to the IANA. Providing that the RIR satisfies the allocation criteria described in paragraph 2.2, the IANA will allocate a single allocation unit, composed of the smallest possible number of blocks available in its IPv4 address pool. An example of how allocations would be made in practice is included as Appendix A.

 

4) IPv4 Address Space Allocation Criteria

A RIR is eligible to receive additional IPv4 address space from the IANA when the total of its IPv4 address holdings is less than 50% of the current IPv4 allocation unit, and providing that it has not already received an IPv4 allocation from the IANA during the current IPv4 allocation period.

 

5) Initial Allocation of IPv4 Address Space

Each new RIR shall, at the moment of recognition, be allocated one (1) allocation unit by the IANA. If an allocation unit is not available, then the IANA will issue this block as soon as one is available. This allocation will be made regardless of the newly formed RIR's projected utilization figures and shall be independent of the IPv4 address space that may have been transferred to the new RIR by the already existing RIRs as part of the formal transition process.

 

6) Reporting

(A) All returned space is to be recorded in an IANA-published log of IPv4 address space transactions, with each log entry detailing the returned address block, the date of the return, and the returning RIR.

(B) All allocated space is also to be recorded in this IANA-published log of IPv4 address space transactions, with each log entry detailing the address blocks, the date of the allocation and the recipient RIR.

(C) The IANA will maintain a public registry of the current disposition of all IPv4 address space, detailing all reservations and current allocations and current IANA-held address space that is unallocated.

(D) The IANA may make public announcements of IPv4 address block transactions that occur under this policy. The IANA will make appropriate modifications to the "Internet Protocol V4 Address Space" [2] page of the IANA website and may make announcements to its own appropriate announcement lists. The IANA announcements will be limited to which address ranges, the time of allocation and to which Registry they have been allocated.

 

7) Situation in other RIRs

This proposal has been adopted in APNIC region and is being submitted in all other RIR regions, with a view to becoming a global policy [3].

 

8) References

[1] Global Addressing Policy ASO-001-2 http://aso.icann.org/docs/aso-001-2.pdf

[2] Internet Protocol v4 Address Space http://www.iana.org/assignments/ipv4-address-space

[3] ICANN Address Supporting Organization (ASO) MoU http://aso.icann.org/docs/aso-mou2004.html

 

Appendix A

Example 1:

On 1 March 2020, IANA has the equivalent of a /17 (32,768 addresses) worth of IPv4 addresses.

a. IANA calculates that 1/10 of this space is 3,276 addresses.
b. IANA rounds this down to the next bit boundary, which creates a minimum allocation size of /21 (2,048 addresses).
c. Each RIR can request and receive a single allocation unit equivalent to a /21 worth of addresses.
d. IANA may not be able to allocate a contiguous /21 and may allocate discontinuous smaller blocks equivalent to a /21 worth of addresses.

Example 2:

On 1 March 2020, IANA has the equivalent of a /20 (4,096 addresses) worth of IPv4 addresses.

a. IANA calculates that 1/10 of this space is 409 addresses.
b. IANA rounds this down to the next bit boundary, which creates a minimum allocation size of /24 (256 addresses).
c. Each RIR can request and receive a single allocation unit equivalent to a /24 worth of addresses.
d. As the minimum size of address space returned to IANA is /24, IANA can allocate a contiguous range of addresses that amount to a /24.

Example 3:

On 1 March 2020, IANA has the equivalent of a /21 (2,048 addresses) worth of IPv4 addresses.
a. IANA calculates that 1/10 of this space is 204 addresses.
b. IANA rounds this down to the next bit boundary, which creates a minimum allocation size of /25 (128 addresses).
c. A /25 is smaller than the minimum permissible allocation size under this policy. Therefore, IANA is unable to make an allocation until more address space is received.

 


History
05.03.2009 Accepted by the ASO AC as a global policy proposal and thus open for discussion on rpd.
21.05.2009 Consensus reached at AfriNIC 10.
23.05.2009 15 Days Last Call for Comments starts.
06.06.2009 15 Days Last Call for Comments ends.
09.11.2010 Notification of board approval sent to rpd mailing list.

 

Discussions are taking place on the policy working group mailing list if you want to subscribe to the mailing send your subscription request to rpd-request [at] afrinic.net with 'Subscribe' as subject line


Mailing list archives can be found at https://lists.afrinic.net/pipermail/rpd