[arin-ppml] Proposal 98: Last Minute Assistance for Small ISPs

George, Wes E [NTK] Wesley.E.George at sprint.com
Wed Oct 28 14:21:14 EDT 2009


From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of Chris Grundemann
Sent: Tuesday, October 27, 2009 1:37 PM
Subject: Re: [arin-ppml] Proposal 98: Last Minute Assistance for Small ISPs

On Tue, Oct 27, 2009 at 09:29, Bill Darte <BillD at cait.wustl.edu> wrote:
> Reservations expressed by myself at the time of acceptance was that the
> proposal seemed overly complex with thresholds and tiggers that rely
> upon 1/ ARIN's ability to accurately assess the remaining free pool in
> small, single digit percentages; 2/ the ability of ARIN to react to
> changes in status of the free pool based upon these thresholds and
> announce the changes to the public; and 3/ most importantly, that all
> these thresholds and all the remaining FP might be eliminated with a
> single justified large allocation rendering the policy's incremental
> process mute.

I agree.  With regard to this PP and other PP and DP which deal with
IPv4-free-pool-run-out / soft-landing strategies: I am beginning to
wonder if it isn't better to do away with all of the staggered
triggers and accompanying complexity for a much simpler approach.

In this case specifically, if the community believes that lowering the
minimum allocation may help as we approach and pass IPv4 free-pool
exhaustion, why not just lower it now?  Forget the triggers all
together.

[WEG]
+1. Can we simply abandon this in favor of proposal 99, or is there something in this proposal besides the sliding trigger that would make it distinct? I've reread both, and I'm not really seeing anything, besides maybe the specific references to small ISPs, which I'm not convinced is necessary to achieve the intended result by simply making it possible to get /24s as end allocations for multihomed networks.

Thanks
Wes George

This e-mail may contain Sprint Nextel Company proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.




More information about the ARIN-PPML mailing list