[arin-ppml] Updated text for ARIN 2014-16: Section 4.10 Austerity Policy Update

[Owen DeLong]

I object to section 4.10.1.4.

An organization should not be locked out of available space simply because they happened to be unlucky in where they got shoehorned compared to other organizations. If an organization has a /24 and needs another /24, but the adjacent /24 is not available, they should be able to obtain any available /24 in the block. (This holds true for any prefix size from /23 to /28). 

I would not have a problem with applying 4.10.2.5 or a similar provision to 4.10.1 in place of 4.10.1.4.

I would also prefer to leave 4.10.2 at /10 rather than shrinking it to /11. I realize this means only the IANA returned space becomes available for 4.10.1. I think that is appropriate.


Owen

On Sep 17, 2014, at 10:11 PM, Alexander, Daniel <Daniel_Alexander at Cable.Comcast.com> wrote:

> Hello All,
> 
> There has been an update to the text of ARIN2014-16: Section 4.10
> Austerity Policy Update. Based upon previous feedback and suggestions
> there has been substantial changes to the original text. This new text is
> included below and will be discussed at the upcoming meeting in Baltimore.
> 
> Feedback is welcome and encouraged.
> Thanks,
> 
> Dan Alexander
> Proposal Shepherd 
> 
> 
> Short summary of proposed changes
> and changes to original text
> =================================
> 
> 1) Adds an additional Austerity option to section 4.10 in addition to the
> transition technology, rather than the original approach of replacing the
> transition technology section.
> 
> 2) Shrinks the minimum transition technology pool from the existing /10 to
> a /11.
> 
> 3) Defines the new requirements for getting an assignment under the
> proposed Austerity section.
> 
> 4) Directs resources obtained by ARIN under section 10.5 to supply
> assignments for section 4.10 requests.
> 
> Updated Text
> ==============================
> 
> Policy statement:
> Replace Section 4.10 with the following policy.
> 
> 4.10 Dedicated IPv4 block to facilitate IPv6 Deployment
> 
> When ARIN receives its last /8 IPv4 allocation from IANA, a contiguous /10
> IPv4 block will be set aside and dedicated to facilitate IPv6 deployment
> and continued transition from IPv4 to IPv6.
> 
> Address space received from IANA under the “Global Policy for Post
> Exhaustion IPv4 Allocation Mechanisms by the IANA (NRPM 10.5)” by ARIN
> shall be allocated or assigned under this section.
> 
> Allocations and assignments from this block must be justified by immediate
> IPv6 deployment requirements. ARIN shall use sparse allocation within
> these blocks.
> 
> 4.10.1 Austerity Policy
> 
> Organizations must obtain an IPv6 block to receive a block under section
> 4.10.1 and show documentation on how the IPv6 and IPv4 block will be used
> to facilitate an organization¹s operational needs. These allocations or
> assignments will be subject to a minimum size of /28 and a maximum size of
> /22.
> 
> In order to receive an allocation or assignment under this policy:
> 
> 1. the organization, its parent(s), or subsidiary organizations, may not
> have received IPv4 address resources greater than or equal to a /22 from
> ARIN or any other RIR;
> 
> 2. the organization must show immediate use (within 90 days) of 25% of the
> allocation;
> 
> 3. the organization is eligible to receive only one contiguous IPv4 block
> under this section;
> 
> 4. the organization may apply to ARIN for an increase in their allocation
> up to a /22, if the previous allocation under this section shows a
> utilization of at least 80%, increases will only be granted if adjacent
> bit-boundary aligned space is available at the time of request.
> 
> 4.10.2 Transition technologies
> 
> Allocations and assignments from this block must be justified by immediate
> IPv6 deployment requirements. Examples of such needs include: IPv4
> addresses for key dual stack DNS servers, and NAT-PT or NAT464
> translators. ARIN staff will use their discretion when evaluating
> justifications.
> 
> These allocations or assignments will be subject to a minimum size of /28
> and a maximum size of /24.  ARIN shall reserve a minimum of a /11 for
> allocations under this subsection.
> 
> In order to receive an allocation or assignment under this policy:
> 
> 1. the applicant may not have received resources under this policy in the
> preceding six months;
> 
> 2. previous allocations/assignments under this policy must continue to
> meet the justification requirements of this policy;
> 
> 3. previous allocations/assignments under this policy must meet the
> utilization requirements of end user assignments;
> 
> 4. the applicant must demonstrate that no other allocations or assignments
> will meet this need;
> 
> 5. on subsequent allocation under this policy, ARIN staff may require
> applicants to renumber out of previously allocated / assigned space under
> this policy in order to minimize non-contiguous allocations.
> 
> _______________________________________________
> PPML
> 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:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.