<div dir="ltr">Jason,<div><br></div><div>I've been reviewing the record for ARIN-2016-2 and ARIN-2016-4;</div><div><br></div><div><a href="https://www.arin.net/policy/proposals/2016_2.html">https://www.arin.net/policy/pr<wbr>oposals/2016_2.html</a></div><div><span style="color:rgb(17,85,204);text-decoration-line:underline"><a href="https://www.arin.net/policy/pr">https://www.arin.net/policy/pr</a></span><wbr style="color:rgb(17,85,204)"><span style="color:rgb(17,85,204);text-decoration-line:underline">oposals/2016_4.html</span><br></div><div><br></div><div>Please remember that 2016-2 and 2016-4 have overlapping changes, this was noted in the comments of 2016-4, prop-227 is 2016-2.</div><div><br></div><div>See my comments inline;</div><div><br></div><div class="gmail_extra"><div class="gmail_quote">On Fri, Jan 26, 2018 at 10:26 AM, Jason Schiller <span dir="ltr"><<a href="mailto:jschiller@google.com">jschiller@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><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></blockquote><div><br></div><div>2016-2 had a slightly delayed implementation, it was impemented on 04/20/217, from the other policys approved at the same time.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><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></div></blockquote><div><br></div><div>While it is unfortunate we didn't explicitly say that the sub-sections were to be deleted, it however seems clear to me that was the intent. The Problem Statement makes it clear 4.2.2.1.1 is no longer valid, further several of the sub-sections are obviously incoporated in the new text of 4.2.2 including 4.2.2.1.3, which based on the coment within 2016-4 was removed because 2016-2 was also adopted.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><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></div></div></blockquote><div><br></div><div>Even if 4.2.2.1.3 wasn't removed ARIN-2016-2 would have clearlly changed it to 24 months.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><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></blockquote><div><br></div><div>I don't know if you also support 2016-2, but it quite cleary changes the 90 day supply (for non-transfers) to a 2 year supply (for both transfers and non-transfers), in fact this is conditionally noted in the comments for 2016-4.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Staff understanding at the time, suggested </div><div>the same conclusions.</div></div></blockquote><div><br></div><div>I believe the overlapping changes were propperly implemneted, infact staff and the AC work closely to ensure this happened correctly. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>__Jason</div></div></blockquote><div> </div><div>Thanks.</div><div><br></div></div>-- <br><div class="gmail_signature">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>===============================================</div>
</div></div>