[arin-ppml] Policy Proposal 122: Reserved Pool for FuturePolicy Development

[Bill Darte]

I don't know...maybe some such...

Perhaps a trendline estimate just before the Fall meeting.  If there is lots of uptake for transitional technologies in that time frame, then wait until the Spring meeting to assess again.....At each inspection period (meeting time?), estimate the amount of space needed against the uptake history out to 2yrs.  Same this amount and release the remainder if any to the pool then....or if it appears that all will be used with transitional technologies, save it. At the end of 2 years, either way, return what's left to the free pool.

Augment the list of non-transitional uses with a maximum allocation size (say /24) that may qualify over that same period of time.

Or, one could authorize an abbreviated 'emergency' allocation process for the list, given AC and BoT agreement and a 'last call' to PPML, addresses could be allocated.

I think it is likely to be obvious whether transitional technologies or IPv6 uptake are the predominant mechanisms going forward by end of calendar year '11.

One can't predict the future, but such a mechanism could provide some flexibility.  I do think that having addresses available for transition rather than same ol', same ol' is best.

bd


-----Original Message-----
From: Scott Leibrand [mailto:scottleibrand at gmail.com]
Sent: Wed 11/24/2010 6:22 PM
To: Bill Darte
Cc: arin-ppml at arin.net
Subject: Re: [arin-ppml] Policy Proposal 122: Reserved Pool for FuturePolicy Development
 
What criteria would you use for "not being effectively utilized"?
Less than X% of the space given out Y months after exhaustion?  Less
than Z requests fulfilled under 4.10?

What other uses would be appropriate?  All valid requests?  Limit it
somehow to avoid giving out all of the remaining reserved space at
once to people on the waiting list?

-Scott

On Wed, Nov 24, 2010 at 4:20 PM, Bill Darte <BillD at cait.wustl.edu> wrote:
> Leave 4.10 space for what it is now for.
> Establish, if need be, an adjunct policy that allows that pool to be raided
> for other uses if after a period of time 6, 9, 12 months indicates that it
> is not being effectively utilized.
> Crumbs!
> bd
>
>
> -----Original Message-----
> From: arin-ppml-bounces at arin.net on behalf of Scott Leibrand
> Sent: Wed 11/24/2010 6:14 PM
> To: Hannigan, Martin
> Cc: arin-ppml at arin.net
> Subject: Re: [arin-ppml] Policy Proposal 122: Reserved Pool for FuturePolicy
> Development
>
> On Wed, Nov 24, 2010 at 3:57 PM, Hannigan, Martin <marty at akamai.com> wrote:
>>
>> On 11/24/10 11:53 PM, "Leo Bicknell" <bicknell at ufp.org> wrote:
>>
>>> In a message written on Wed, Nov 24, 2010 at 01:08:38PM -0800, Owen
>>> DeLong
>>> wrote:
>>>> Hence my suggestion that 122 would be more palatable if it set aside
>>>> a separate /10 for that purpose rather than raiding 4.10.
>>>
>>> I would not object to a second /10, but I'm sure I see it as necessary.
>>
>>
>> It would only amplify the defects in 4.10.
>
> So do you see the problem as being that 4.10 will leaving addresses
> reserved for too long without putting them into use?
>
> If so, would there be additional criteria for giving out 4.10 reserved
> space that would alleviate the defects in 4.10 from your perspective?
>
> -Scott
> _______________________________________________
> 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.
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20101125/9fcfa21c/attachment.htm>