[arin-ppml] Draft Policy ARIN-2014-17: Change Utilization Requirements from last-allocation to total-aggregate - revised

Jason Schiller jschiller at google.com
Thu Nov 20 13:18:13 EST 2014

Can ARIN staff please clarify current operating procedures and how they
would change under this proposal.

My understanding is that is an ISP assigns a subnet to an end-user
customer, and that end-site customer has a host count that exceeds 50% then
the ISP gets to count that customer assignment as 100% used toward
aggregate of each aggregate allocation.

If this policy passed would the ISP still be able to count subnets assigned
to customers which host counts over 50% as 100% utilized towards total

Same question in the case of end-sites.  If an end-user has a justifiable
reason to subnet the space, and each of the subnets are above 50%
utilization, then are those actual utilization counted towards the total
utilization, or does the end-user get to count subnets greater than 50%
full as completely utilized towards total utilization?


On Thu, Nov 20, 2014 at 1:05 PM, ARIN <info at arin.net> wrote:

> Draft Policy ARIN-2014-17
> Change Utilization Requirements from last-allocation to total-aggregate
> ARIN-2014-17 has been revised.
> Draft Policy ARIN-2014-17 is below and can be found at:
> https://www.arin.net/policy/proposals/2014_17.html
> You are encouraged to discuss the merits and your concerns of Draft
> Policy 2014-17 on the Public Policy Mailing List.
> The AC will evaluate the discussion in order to assess the conformance
> of this draft policy with ARIN's Principles of Internet Number Resource
> Policy as stated in the PDP. Specifically, these principles are:
>   * Enabling Fair and Impartial Number Resource Administration
>   * Technically Sound
>   * Supported by the Community
> The ARIN Policy Development Process (PDP) can be found at:
> https://www.arin.net/policy/pdp.html
> Draft Policies and Proposals under discussion can be found at:
> https://www.arin.net/policy/proposals/index.html
> Regards,
> Communications and Member Services
> American Registry for Internet Numbers (ARIN)
> ## * ##
> Draft Policy ARIN-2014-17 Change Utilization Requirements from
> last-allocation to total-aggregate
> Date: 19 October 2014
> Problem Statement:
> Current ARIN policy calculates utilization on a per allocation basis
> rather than in aggregate. This method of determining utilization may cause
> some organizations to be unable to qualify for additional address blocks
> despite attempting to use their resource allocations as best as possible.
> This issue has been exacerbated in the past couple of years due to the
> 3-month allocation window which causes organizations to receive smaller
> non-expandable allocations rather than a larger aggregate.
> For example, if an organization has 4 x /22 and 3 of them are utilized
> 100% and the fourth utilized at 75%, an additional allocation request would
> be denied. However, an organization with a single /20 utilized at 80% would
> have less efficient utilization but would be eligible to receive additional
> space.
> Policy statement:
> Replace Section
> ISPs must have efficiently utilized all allocations, in aggregate, to at
> least 80% and at least 50% of every allocation in order to receive
> additional space. This includes all space reassigned to their customers.
> Replace Section
> End-users must have efficiently utilized all assignments, in aggregate, to
> at least 80% and at least 50% of every assignment in order to receive
> additional space, and must provide ARIN with utilization details.
> Comments:
> a. Timetable for implementation: Immediate
> b.
> _______________________________________________
> 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.

Jason Schiller|NetOps|jschiller at google.com|571-266-0006
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20141120/658859ff/attachment-0001.html>

More information about the ARIN-PPML mailing list