[arin-ppml] Policy Proposal 2010-10 - Global Policy for IPv4 Allocations by the IANA Post Exhaustion

[Dylan Ebner]

Pppp

Dylan Ebner, Network Engineer
Consulting Radiologists, Ltd.
1221 Nicollet Mall, Mpls, MN 55403<geo:0,0?q=1221+Nicollet+Mall%2C+Mpls%2C+MN+55403>
Ph. 612-573-2236<tel:6125732236> Fax 612-573-2250<tel:6125732250>
dylan.ebner at crlmed.com<mailto:dylan.ebner at crlmed.com>
www.consultingradiologists.com<http://www.consultingradiologists.com>


-----Original message-----
From: David Farmer <farmer at umn.edu>
To: Bill Darte <BillD at cait.wustl.edu>, "arin-ppml at arin.net" <arin-ppml at arin.net>
Sent: Mon, Aug 30, 2010 21:30:22 GMT+00:00
Subject: Re: [arin-ppml] Policy Proposal 2010-10 - Global Policy for IPv4 Allocations by the IANA Post Exhaustion

This isn't going to fly in APNIC.  APNIC will not agree to the no
transfer provision.  Furthermore, as currently written it sets up a
winner take all race to the bottom, a maximum allocation size would be
an easy to fix this without making things to complicated.

During the afternoon tea break on Friday, Owen and had a conversation
with, Gaurab Raj Upadhaya (the new sig-policy chair for APNIC), Philip
Smith, and Filiz Yilmaz (from RIPE), and Leslie stopped by for a bit
too. Leslie did not comment on policy, but it was very helpful to have
someone who had actually interacted with IANA involved in the conversation.

The consensus of those gathered was that a very simple policy was
needed, focusing on IANA.  It should allow IANA to accept returns of /24
or large blocks. (no requirements for return by RIRs or anyone else for
that matter).  Then allow IANA to allocate on a needs basis to the RIRs
with a minimum block size /24 and no more than the equilivant of a /10
at one time.

The /10 at a time limit is intended to prevent a winner takes all race
to the bottom and allow some possibility that a larger block could be
shared between multiple RIRs without having addresses set idle if an RIR
needs them.

So my question to the rest of the AC, how should we proceed, keep text
that we know will not succeed as global policy or change text?  What
would it take to make a radical change to the Draft Policy?  Otherwise,
we would need to come to the next meeting with new text which likely be
past IANA run-out.

Comments, rotten fruit, etc...


On 8/30/10 09:59 CDT, Bill Darte wrote:
> PPML Participants....
>
> 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 Atlanta...Oct 6-8 <https://www.arin.net/participate/meetings/ARIN-XXVI/>.
>
> 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.
>
> Thanks for your participation in the ARIN Policy Development Process
> <https://www.arin.net/policy/pdp.html> and in this forum.
>
> Bill Darte
> ARIN Advisory Council
> Primary Shepherd for PP 2010-10
>
> ******* begin policy language *******
>
> Global Policy for IPv4 Allocations by the IANA Post Exhaustion
> Version/Date: 20 July 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 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.
>
> 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 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.
>
> 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. 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.
>
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20100830/d329aabc/attachment.htm>