[arin-ppml] Post-exhaustion IPv4 policy (Proposal 97. Waiting List for Unmet IPv4 Requests)

Scott Leibrand scottleibrand at gmail.com
Tue Dec 1 20:37:19 EST 2009

William Herrin wrote:
> On Thu, Oct 29, 2009 at 6:49 PM, Scott Leibrand <scottleibrand at gmail.com> wrote:
>> William Herrin wrote:
>>> On Thu, Oct 22, 2009 at 6:13 PM, Scott Leibrand <scottleibrand at gmail.com>
>>> wrote:
>>>> "Repeated requests, in a manner that would
>>>> circumvent 4.1.6, are not allowed."  The idea, of course, is to give ARIN
>>>> staff leeway to use their excellent fraud detection skills, combined with
>>>> operational procedures that can be adjusted as needed.
>>> Staff will be making such decisions under intense scrutiny. Any
>>> judgment they're forced to exercise will tend to be the most lenient
>>> the policy allows. Which is to say: no restriction on repeat requests
>>> at all.
>>> Giving staff discretion can be a good thing if done with appropriate
>>> checks, but you also have to give them a policy vehicle that validates
>>> and reinforces that discretion. In other words, it's better to say,
>>> "You can have 1 a day but staff can waive the requirement" than "you
>>> can have as many as you want but staff can limit you to 1 a day."
>> Understood.  Do you have any specific suggestions as to how we could modify
>> proposal 97 to codify a restriction, while still giving staff leeway to make
>> exception for anyone who is clearly not trying to bend any rules?
> Tough question. How about something like a 1-year waiting period
> between requests but the BoT is empowered to waive the waiting period
> by majority vote for any individual requests they deem meritorious by
> whatever criteria. Of course waiving the waiting period doesn't grant
> the request; it just means that staff can consider it before the
> waiting period expires.


I'm just now coming back to this and taking another hard look at it.  
What if I change that sentence to read:

Repeated requests, in a manner that would circumvent 4.1.6, are not 
allowed: an organization may only receive one allocation, assignment, or 
transfer every 3 months, but ARIN, at its sole discretion, may waive 
this requirement if the requester can document an unforeseen change in 
circumstances since their last request.

I chose 3 months because it looks like 2009-8 is going to change 
from 12 months to 3 months upon IANA exhaustion.



More information about the ARIN-PPML mailing list