[arin-ppml] Draft Policy ARIN-2014-17: Change UtilizationRequirements from last-allocation to total-aggregate - revised
SRyerse at eclipse-networks.com
Thu Jul 17 11:54:06 EDT 2014
100 Ashford Center North, Suite 110, Atlanta, GA 30338
770.656.1460 - Cell
℠ Eclipse Networks, Inc.
Conquering Complex Networks℠
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of Mike Burns
Sent: Thursday, July 17, 2014 11:35 AM
To: Michael Peddemors; Owen DeLong
Cc: arin-ppml at arin.net
Subject: Re: [arin-ppml] Draft Policy ARIN-2014-17: Change UtilizationRequirements from last-allocation to total-aggregate - revised
> I think it will have exactly the opposite effect, actually. I think it
> lowers the barrier for smaller entities and new entrants while keeping
> roughly the same effective requirements for larger incumbents.
Maybe if you can show how the barriers are reduced for smaller entities and new entrants, vs how they will be affected if the larger entities are enabled to get the remaining space faster?
>> I think we need another idea to come up..
> Such as?
Hopefully the question will be answered, and the quicker we move on, maybe the quicker that will be answered.
How about support for removing the needs test for small transfers a la 2014-14?
It seems to benefit those whose needs are small, but who are having difficulties with justification due to niggling IPv4 policy issues like minimum sizes and utilization requirements.
Others have noted we are rearranging the deck chairs on the Titanic with these IPv4 policy issues.
Maybe it is time to metaphorically sweep those chairs into the sea so we can move on.
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