On Sep 30, 2014, at 11:56 AM, Bill Owens <[email protected]> wrote: > On Tue, Sep 30, 2014 at 11:46:24AM -0400, Mike Burns wrote: >> Also we know that most allocation requests are for much larger >> blocks, thus we know that applicants will go away for at least three >> months between their meager allocations. > > Does the 4.1.8 policy of assigning only a single block for each request mean > that if an application were approved for, say, a /22 but only /24s were > available, that applicant would have only two choices, either take a single > /24 or wait until a /22 was returned to the pool?
Correct. > Is there no option for them to say that four non-contiguous /24s would be > acceptable to them? Also correct; I believe that the community was concerned that (as we approached depletion) a single very large request could effectively deplete the entire IPv4 block inventory, hence the 4.1.8 constraints on receiving a single block for each request. FYI, /John John Curran President and CEO ARIN _______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
