[arin-ppml] Draft Policy 2010-10 (Global Proposal): Global Policy for IPv4 Allocations by the IANA Post Exhaustion - Last Call (text revised)

[ARIN]

The ARIN Advisory Council (AC) met on 27 October 2010 and decided to
send the following draft policy to last call:

    Draft Policy 2010-10 (Global Proposal): Global Policy for IPv4
Allocations by the IANA Post Exhaustion

The AC made the following revisions to the text:
   - The second sentence in section 2 was changed into two sentences.
"Eligible address space includes addresses that are not designated as
"special use" by an IETF RFC. Address space may only be returned by the
issuing RIR."
   - In section 4, the sentence beginning "Exhaustion is defined as..."
was changed to: "An RIR is considered at exhaustion when the inventory
is less than the equivalent of a single /8 and is unable to further
assign address space to its customers in units equal to or shorter than
the longest of that RIR's policy defined minimum allocation unit."

Feedback is encouraged during the last call period. All comments should
be provided to the Public Policy Mailing List. Last call for 2010-10
will expire on 12 November 2010. After last call the AC will conduct
their last call review.

The draft policy text is below and available at:
https://www.arin.net/policy/proposals/

The ARIN Policy Development Process is available at:
https://www.arin.net/policy/pdp.html

Regards,

Communications and Member Services
American Registry for Internet Numbers (ARIN)


## * ##


Draft Policy 2010-10 (Global Proposal)

Global Policy for IPv4 Allocations by the IANA Post Exhaustion

Version/Date: 29 October 2010

Policy statement:

1. Reclamation Pool
Upon adoption of this IPv4 address policy by the ICANN Board of
Directors, the IANA shall establish a Reclamation Pool to be utilized
post RIR IPv4 exhaustion as defined in Section 4. The reclamation pool
will initially contain any fragments that may be left over in IANA
inventory. As soon as the first RIR exhausts its inventory of IP address
space, this Reclamation Pool will be declared active. When the
Reclamation Pool is declared active, the Global Policy for the
Allocation of the Remaining IPv4 Address Space[3] and Policy for
Allocation of IPv4 Blocks to Regional Internet Registries[4] will be
formally deprecated.

2. Returning Address Space to the IANA
The IANA will accept into the Reclamation Pool all eligible IPv4 address
space that are offered for return. Eligible address space includes
addresses that are not designated as "special use" by an IETF RFC.
Address space may only be returned by the issuing RIR. Legacy address
holders may return address space directly to the IANA if they so choose.

3. Address Allocations from the Reclamation Pool by the IANA
Allocations from the Reclamation Pool may begin once the pool is
declared active. Addresses in the Reclamation Pool must be allocated on
a CIDR boundary. Allocations from the Reclamation Pool are subject to a
minimum allocation unit equal to the minimum allocation unit of all RIRs
and a maximum allocation unit of one /8. The Reclamation Pool will be
divided on CIDR boundaries and distributed evenly to all eligible RIRs
once each quarter. Any remainder not evenly divisible by the number of
eligible RIRs will remain in the Reclamation Pool until such time
sufficient address returns allow another round of allocations.

4. RIR Eligibility for Receiving Allocations from the Reclamation Pool
Upon the exhaustion of an RIR's free space pool and after receiving
their final /8 from the IANA[3], an RIR will become eligible to request
address space from the IANA Reclamation Pool when it publicly announces
via its respective global announcements email list and by posting a
notice on its website that it has exhausted its supply of IPv4 address
space. An RIR is considered at exhaustion when the inventory is less
than the equivalent of a single /8 and is unable to further assign
address space to its customers in units equal to or shorter than the
longest of that RIR's policy defined minimum allocation unit. Up to one
/10 or equivalent of IPv4 address space specifically reserved for any
special purpose by an RIR will not be counted against that RIR when
determining eligibility unless that space was received from the IANA
reclamation pool. Any RIR that is formed after the ICANN Board of
Directors has ratified this policy is not eligible to utilize this
policy to obtain IPv4 address space from the IANA.

5. Reporting Requirements
The IANA shall publish on at least a weekly basis a report that is
publicly available which at a minimum details all address space that has
been received and that has been allocated. The IANA shall publish a
Returned Address Space Report which indicates what resources were
returned, by whom and when. The IANA shall publish an Allocations Report
on at least a weekly basis which at a minimum indicates what IPv4
address space has been allocated, which RIR received the allocation and
when. The IANA shall publish a public notice confirming RIR eligibility
subsequent to Section 4.

6. No Transfer Rights
Address space assigned from the Reclamation Pool may be transferred if
there is either an ICANN Board ratified global policy or globally
coordinated RIR policy specifically written to deal with transfers
whether inter-RIR or from one entity to another. Transfers must meet the
requirements of such a policy. In the absence of such a policy, no
transfers of any kind related to address space allocated or assigned
from the reclamation pool is allowed.

7. Definitions
IANA - Internet Assigned Numbers Authority, or its successor
ICANN - Internet Corporation for Assigned Names and Numbers, or its
successor
RIR - Regional Internet Registry as recognized by ICANN
MOU - Memorandum of Understanding between ICANN and the RIRs
IPv4 - Internet Protocol Version Four(4), the target protocol of this
Global Policy
Free Space Pool - IPv4 Addresses that are in inventory at any RIR,
and/or the IANA

8. Contributors
The following individuals donated their time, resources and effort to
develop this proposal on behalf of the Internet Community:
Steve Bertrand <steve at ipv6canada.com>
Chris Grundemann <cgrundemann at gmail.com>
Martin Hannigan <marty at akamai.com>
Aaron Hughes <ahughes at bind.com>
Louie Lee <louie at equinix.com>
Matt Pounsett <matt at conundrum.com>
Jason Schiller <schiller at uu.net>

9. References

1. http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm
Global Policy for the Allocation of the Remaining IPv4 Address Space,
IANA, Retrieved 27 April 2010
2. http://aso.icann.org/documents/memorandum-of-understanding/index.html
ICANN Address Supporting Organization (ASO) MoU , Retrieved 27 May 2010.
3. http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm
Global Policy for the Allocation of the Remaining IPv4 Address Space
4. http://aso.icann.org/wp-content/uploads/2009/09/aso-001-2.pdf Policy
for Allocation of IPv4 Blocks to Regional Internet Registries