<div dir="ltr"><div>John,</div><div><br></div><div>Looking back, I note that I have not made an ISP initial IPv4</div><div>request after 02/21/2017 when the policy was changed.</div><div><br></div><div>My previous ISP initial IPv4 requests asked for a</div><div>3 month, 12 month, and 18 month projection.<br></div><div><br></div><div>I assumed this was to comply with "4.2.2.1.3. Three Months"</div><div>that existed until 02/21/2017.</div><div><br></div><div>Was this information used prior to 02/21/2017?</div><div>Is this information used since 02/21/2017?</div><div><br></div><div>Or is it ignored and collected only because the </div><div>initial ISP IPv4 request uses the same form as the </div><div>subsequent requests?</div><div><br></div><div><br></div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">"4.2.2.1.3. Three Months" </span>disappeared on 02/21/2017<div><br></div><div>That version was modified by:</div><div>2015-2</div><div>2016-1</div><div>2016-4</div><div>2016-5</div><div>2016-6</div><div><br></div><div>2016-4 replaces section 4.2.2 text.</div><div><div><br></div><div>It does not clearly state that it </div><div>replaces, removes, or modifies </div><div>any of the sub sections.</div><div><br></div><div><div>4.2.2.1. ISP Requirements</div><div>4.2.2.1.1. Use of /24</div><div>4.2.2.1.2. Efficient Utilization</div><div>4.2.2.1.3. Three Months</div><div>4.2.2.1.4. Renumber and Return</div><div>4.2.2.2. [Section Number Retired] </div></div></div><div><br></div><div><br></div><div>I never noticed that the sub-section disappeared</div><div>and assumed 2016-4 only changed the 4.2.2</div><div>text.</div><div><br></div><div><br></div><div>When I voiced my support for the 2016-4 it was</div><div>with the understanding that (at that time):</div><div><br></div><div>An ISP without a direct IPv4 block would</div><div>automatically qualify for a /24, (without needing</div><div>to go to an upstream and get IPv4 space and </div><div>pressing it into service).</div><div><br></div><div>Furthermore an ISP without a direct IPv4 block</div><div>could get more than a /24 so long as it was did</div><div>not exceed a 90 day supply (for non-transfers)</div><div>or a 2 year supply (for transfers).</div><div><br></div><div>Staff understanding at the time, suggested </div><div>the same conclusions.</div><div><br></div><div><br></div><div>__Jason</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 26, 2018 at 12:34 AM, 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;line-break:after-white-space"><span class="">
On 25 Jan 2018, at 2:20 PM, Jason Schiller <<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>> wrote:<br>
<div>
<blockquote type="cite"><br class="m_-8882460444653114287Apple-interchange-newline">
<div>
<div dir="ltr">
<div>John,</div>
<div><br>
</div>
So an ISP with no resources who wanted an initial /21 from ARIN
<div>would be asked for some additional data to ensure that the /21 </div>
<div>was not more than an 90 day supply?</div>
</div>
</div>
</blockquote>
</div>
<br>
</span><div>Jason - </div>
<div> </div>
<div> No, an ISP receiving its initial assignment would have to meet the criteria in NRPM 4.2.2, and that does not specify any requirement regarding 90 day supply.</div>
<div><br>
</div>
<div> Note that as a practical matter the ISP would no IPv4 space from ARIN, but instead go to the waiting list for an uncertain chance at receiving some resources in the future. </div>
<div><br>
</div>
<div>Thanks,</div>
<div>/John</div><span class="">
<div><br>
</div>
<div>
<h5 style="margin:0.5em 0px;padding:0px;border:0px;clear:both;font-style:italic;font-family:arial,helvetica,sans-serif;font-size:12px!important">
</h5>
</div>
<blockquote type="cite">
<div>
<h5 style="margin:0.5em 0px;padding:0px;border:0px;clear:both;font-style:italic;font-family:arial,helvetica,sans-serif;font-size:12px!important">
</h5>
</div>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<div>
<h5 style="margin:0.5em 0px;padding:0px;border:0px;clear:both;font-style:italic;font-family:arial,helvetica,sans-serif;font-size:12px!important">
4.2.2. Initial allocation to ISPs</h5>
<div style="margin:0.5em 0px;padding:0px;border:0px;font-size:1.2em;line-height:1.5em;font-family:arial,helvetica,sans-serif">
All ISP organizations without direct assignments or allocations from ARIN qualify for an initial allocation of up to a /21, subject to ARIN's minimum allocation size. Organizations may qualify for a larger initial allocation by documenting how the requested
allocation will be utilized within 24 months</div>
</div>
</blockquote>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</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>