[arin-ppml] Draft Policy ARIN-2014-16: Section 4.10 Austerity Policy Update

Mike Burns mike at iptrading.com
Tue May 27 15:48:23 EDT 2014

If this proposal is implemented, blocks recovered from IANA would be 
distributed in sizes no larger than /22.
Does anybody know if the /11 just received has to stay at that size in 
inventory, or can it also be broken down?
I would be more likely to support this proposal if the recent IANA /11 can 
not be split if it stays in the general pool, but would be split if it goes 
into the 4.10 pool.

-----Original Message----- 
From: David Farmer
Sent: Tuesday, May 27, 2014 2:48 PM
To: andrew.dul at quark.net ; arin-ppml at arin.net
Subject: Re: [arin-ppml] Draft Policy ARIN-2014-16: Section 4.10 Austerity 
Policy Update

+1 to everything below.

However in addition to the currently reserved /10, I would like to
suggest we also designate any allocations from the IANA recovered IPv4
pool defined in section 10.5, including the /11 just received as
reserved for use by this Austerity Policy as well.

If the community wants to do this it would be good to get a clear
consensus from the community ASAP.  So, if necessary the Board could
take actions necessary to ensure events don't overtake such a change.


On 5/27/14, 10:31 , Andrew Dul wrote:
> As the primary author of this draft policy, I support the policy.
> This draft policy replaces the current section 4.10 "transition
> technology" allocations with a more generic "austerity policy" which
> more closely aligns with other RIR's austerity policies.
> This policy does the following:
> 1. Changes the requirements to be non-technology IPv6 specific, which
> allows for a broader group of organizations to qualify for IPv4 address
> space under this section.
> 2. Increases the block size to a maximum /22
> 3. Uses sparse allocation and permits an organization to possibly grow
> their allocation up to a /22, if they don't qualify for the full block
> on their initial allocation.
> 4. Places additional IANA reclaimed blocks into this pool for allocation.
> 5. Limits the number of blocks per organization to one; this directly
> mirrors other successful RIR austerity policies.
> I believe this policy along with recommended draft policy "ARIN-2014-13:
> Reduce All Minimum Allocation/Assignment Units to /24" solve many of the
> immediate IPv4 policy issues that ARIN will face after the free pool is
> depleted.  Therefore, I recommend this policy be moved forward as
> quickly as possible.
> I and the AC welcome your comments on this draft.

David Farmer               Email: farmer at umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
Please contact info at arin.net if you experience any issues. 

More information about the ARIN-PPML mailing list