<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.6003" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=765414314-30082010><FONT face=Arial size=2>PPML
Participants....</FONT></SPAN></DIV>
<DIV>
<P><SPAN class=765414314-30082010><FONT face=Arial size=2>Below is the most
current language for PP 2010-10. The language will be 'frozen' September
24 for the upcoming Public Policy Meeting discussion in <A
href="https://www.arin.net/participate/meetings/ARIN-XXVI/">Atlanta...Oct
6-8</A>.</FONT></SPAN></P>
<P><SPAN class=765414314-30082010><FONT face=Arial size=2>As such, your
opportunity to influence language or provide formal input to the Advisory
Council which may result in wording changes, must be received by September
23. All previous comments and suggestions from the PPML, private
correspondence, converstations, etc. have been captured. Input from the
other RIR communities where this 'Global Policy' is being considered will
similarly be captured. Those inputs plus whatever we receive between now
and the Atlanta meeting will be brought to the meeting for
discussion.</FONT></SPAN></P>
<P><SPAN class=765414314-30082010><FONT face=Arial size=2>Thanks for your
participation in the <A href="https://www.arin.net/policy/pdp.html">ARIN Policy
Development Process</A> and in this forum.</FONT></SPAN></P>
<P><FONT face=Arial size=2><SPAN class=765414314-30082010>Bill Darte<BR>ARIN
Advisory Council<BR>Primary Shepherd for PP 2010-10</SPAN></FONT></P>
<P><FONT face=Arial size=2><SPAN
class=765414314-30082010></SPAN></FONT> </P>
<P><FONT face=Arial size=2><SPAN class=765414314-30082010>******* begin policy
language *******</SPAN></FONT></P>
<P>Global Policy for IPv4 Allocations by the IANA Post Exhaustio<SPAN
class=765414314-30082010>n<BR></SPAN>Version/Date: 20 July 2010</P>
<P>Policy statement:</P>
<P>1. Reclamation Pool <BR>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. </P>
<P>2. Returning Address Space to the IANA<BR> 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 or addresses allocated to RIR's unless they are being
returned by the RIR that they were orignally allocated to. Legacy address
holders may return address space directly to the IANA if they so choose. </P>
<P>3. Address Allocations from the Reclamation Pool by the IANA<BR> Allocations
from the Reclamation Pool may begin once the pool is declared active. Addresses
in the Reclamation Pool will be allocated on a CIDR boundary equal to or shorter
than the longest minimum allocation unit of all RIRs in order to complete these
allocations.The Reclamation Pool will be divided on CIDR boundaries and
distributed evenly to all eligible RIR's. Any remainder not evenly divisible by
the number of eligible RIR's based on a CIDR boundary equal to or shorter than
the longest minimum allocation unit of all RIRs will remain in the Reclamation
Pool. Addresses that are left over will be held in the Reclamation Pool until
additional IP addresses can be returned to rejoin addresses on CIDR boundaries
to the Reclamation Pool or a minumum allocation unit is set to allow allocation
from existing inventory. </P>
<P>4. RIR Eligibility for Receiving Allocations from the Reclamation Pool<BR>
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. Exhaustion is defined as an
inventory of less than the equivalent of a single /8 and the inability to
further assign address space to its customers in units equal to or shorter than
the longest of any RIR's policy defined minimum allocation unit. 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. </P>
<P>5. Reporting Requirements<BR> 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.</P>
<P>6. No Transfer Rights<BR> 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. </P></DIV></BODY></HTML>