[arin-ppml] ARIN Draft Policy 2017-1: Clarify Slow Start for Transfers proposed updates
jschiller at google.com
Tue May 9 10:15:45 EDT 2017
Thank you for the statement. This makes me feel much more comfortable.
I wish such text was clearly spelled out in the policy
(as I think that is good for the community), but I will happily
take such text as part of the unwritten rules of the NRPM.
Would you say the policy proposal as written is an operation non-op
for ARIN staff?
On Mon, May 8, 2017 at 5:56 PM, John Curran <jcurran at arin.net> wrote:
> On 8 May 2017, at 12:42 PM, Jason Schiller <jschiller at google.com> wrote:
> > John,
> > In a word no.
> > One could imagine a justification that says something like:
> > - on 12/05 we got a /16
> > -- (assume we demonstrated efficient utilization of currently
> > held space at this time)
> > - on 05/05 we demonstrated efficient use of the this space
> > -- (assume efficient utilization of the new /16 is justifiable)
> > -- (assume efficient utilization of previous held space is
> > - at current consumption rate, a /14 represents a two year supply
> > - we anticipate that our product will continue growing for the for
> see-able future
> > Can we have a /14 please?
> > ---
> > Technically the request above makes no prediction about the future.
> Jason -
> Regardless of whether you call it a prediction or not, your extension of
> your consumption rate
> to establish your 'two year supply’ meets NRPM 8.5.5’s requirement for
> “documentation to
> ARIN which details the use of at least 50% of the requested IPv4 block
> size within 24 months.”
> This aligns with the clear policy intent of transfer policy as adopted by
> the community; so long
> as an officer of the organization attests to the documentation, such
> requests will be approved.
> John Curran
> President and CEO
Jason Schiller|NetOps|jschiller at google.com|571-266-0006
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ARIN-PPML