[arin-ppml] Policy discussion - Method of calculating utilization
jeffrey.lyon at blacklotus.net
Wed Apr 30 12:10:22 EDT 2014
The problem I see is in the manner of calculation. Right now each and
every allocation must be individually utilized at 80%. This means I
can have 3 x /22 utilized at 100% and 1 x /22 at 79% and would not be
eligible for more space where an organization with 80% utilization on
a single /20 would not have the same problem.
As a case example, Black Lotus has numerous /21's all utilized at 90%+
and one of them at 80%. ARIN is requesting more documentation on the
80% one to ensure that it is really at 80%. This is fair under current
policy, but it does not make sense when one considers that
organizations with larger contiguous assignments would never run into
this issue. It is an unnecessary time drain for both the requester and
On Thu, May 1, 2014 at 1:01 AM, Paul S. <contact at winterei.se> wrote:
> While the idea is great, isn't ARIN supposed to already be implementing this
> in one way?
> i.e: You get one allocation, and until you can show 80% usage -- applying
> again generally does not get you anywhere.
> Going by this, shouldn't all previous allocs ("aggregated / per organization
> allocations") actually be used up? Or am I missing something?
> On 5/1/2014 午前 12:51, Jeffrey Lyon wrote:
>> Also, we're already in Phase 4, so isn't it fair to say that the free
>> pool is essentially exhausted?
>> Thanks, Jeff
>> On Thu, May 1, 2014 at 12:44 AM, Scott Leibrand <scottleibrand at gmail.com>
>>> This seems to me like a reasonable operational practice for ARIN to use
>>> help prevent a run on the remaining free pool from organizations with
>>> quantities of existing space.
>>> Are you trying to change this before free pool runout, or are you
>>> with making needs justification a bit easier for transfers once the free
>>> pool is exhausted? I would support the latter, but not the former.
>>> On Wednesday, April 30, 2014, Jeffrey Lyon <jeffrey.lyon at blacklotus.net>
>>>> Friends, Colleagues,
>>>> A couple of years ago I brought up an issue I had run into where the
>>>> utilization requirement for new requests is being calculated on a per
>>>> allocation basis rather than in aggregate. For example, if an
>>>> organization has 4 x /22 and 3 of them are utilized 100% and the
>>>> fourth utilized at 75%, that request would be denied. This is a bit
>>>> out of balance as an organization with a single /20 utilized at 80%
>>>> would have less efficient utilization but would be eligible to request
>>>> additional space.
>>>> The last time this was discussed it sounded as if the community would
>>>> support a policy proposal to change this calculation to be considered
>>>> in aggregate vs. per assignment. Does this remain the case?
>>>> Jeffrey A. Lyon, CISSP-ISSMP
>>>> Fellow, Black Lotus Communications
>>>> mobile: (757) 304-0668 | gtalk: jeffrey.lyon at gmail.com | skype:
>>>> 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.
> 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.
Jeffrey A. Lyon, CISSP-ISSMP
Fellow, Black Lotus Communications
mobile: (757) 304-0668 | gtalk: jeffrey.lyon at gmail.com | skype: blacklotus.net
More information about the ARIN-PPML