<div dir="ltr">John,<div><br></div><div>In a word no. </div><div><br></div><div>One could imagine a justification that says something like:</div><div>- on 12/05 we got a /16</div><div> -- (assume we demonstrated efficient utilization of currently</div><div> held space at this time)</div><div>- on 05/05 we demonstrated efficient use of the this space </div><div> -- (assume efficient utilization of the new /16 is justifiable)</div><div> -- (assume efficient utilization of previous held space is justifiable)</div><div>- at current consumption rate, a /14 represents a two year supply</div><div>- we anticipate that our product will continue growing for the for see-able future</div><div><br></div><div>Can we have a /14 please?</div><div>---</div><div><br></div><div>Technically the request above makes no prediction about the future. I suspect</div><div>such a request would get approved, but it would be nice to formalize it. </div><div><br></div><div>The difference is in the past, under slow star, it was very clear what was required </div><div>and what ARIN would accept. </div><div><br></div><div>The future-looking requirements are by necessity less clear, and hence the</div><div>result is less predictable, and can unexpectedly take longer.</div><div><br></div><div>Separation form section 4, removed a clearly stated, clearly understood, </div><div>well exercised, acceptable set of justification.</div><div><br></div><div>This policy is an attempt to re-instate that there is at least one very clearly </div><div>defined justification that ARIN finds acceptable, and hence at least one</div><div>clearly defined and predictable path </div><div><br></div><div>Beyond that it tweaks the pre-existing slow start in two ways:</div><div>1. it opens it up to end-users</div><div>2. it makes allowances for the possibility of a pause due to the inability </div><div> to get timely transfers.</div><div><br></div><div> </div><div>___Jason</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 8, 2017 at 12:41 PM, John Curran <span dir="ltr"><<a href="mailto:jcurran@arin.net" target="_blank">jcurran@arin.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
On 8 May 2017, at 11:27 AM, Jason Schiller <<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>> wrote:<br>
<div>
<blockquote type="cite"><br class="m_8565515725268118256Apple-interchange-newline">
<div>
<div dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
Comments in line.<br>
<div class="gmail_extra">
<div class="gmail_quote">
<div>...</div><span class="">
<div>In the absence of real data, people will often guess. Some people guess better, some </div>
<div>worse. Some guesses are based on intricate algorithms, real data, and Fermi maths, </div>
<div>others are just what feel right. Either type can be multiple orders of magnitude off, or </div>
<div>in the right ballpark.</div>
<div><br>
</div>
<div>Do we really want to encourage data driven companies who previously requested less IP</div>
<div>space then they needed because their requests have always been based on a real </div>
<div>measure of consumption, and not addressing speculative growth, to instead require them</div>
<div>to guess about the future? </div>
</span></div>
</div>
</div>
</div>
</blockquote>
</div>
<div><br>
</div>
<div>Jason - </div>
<div> </div>
<div> Is there a reason that data-driven companies cannot make use of the existing transfer</div>
<div> policy, and create their anticipated 24-month need based on their actual past utilization?</div>
<div><br>
</div>
<div> I am having difficulty understanding why policy is needed specifically to enable use of</div>
<div> one particular type of forward-looking projection (i.e. forecasts based on past utilization.)</div>
<div><br>
</div>
<div>Thanks,</div>
<div>/John</div><span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br>
</div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">_______________________________________________________<br></font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|571-266-0006</font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>
</div>