<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I refer you to section 6.5.1…<div class=""><br class=""></div><div class=""><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;" class="">6.5.1. Terminology</h5><ol class="alpha" type="a" style="margin: 0.5em 0px; padding: 0px 0px 0px 20px; border: 0px; font-size: 10px; list-style: lower-alpha; font-family: arial, helvetica, sans-serif;"><li style="margin: 0.25em 0px 0px; padding: 0px; border: 0px; line-height: 1.5em; font-size: 12px !important;" class="">The terms ISP and LIR are used interchangeably in this document and any use of either term shall be construed to include both meanings. </li><li style="margin: 0.25em 0px 0px; padding: 0px; border: 0px; line-height: 1.5em; font-size: 12px !important;" class="">The term nibble boundary shall mean a network mask which aligns on a 4-bit boundary (in slash notation, /n, where n is evenly divisible by 4, allowing unit quantities of X such that 2^n=X where n is evenly divisible by 4, such as 16, 256, 4096, etc.)</li></ol><div class=""><font face="arial, helvetica, sans-serif" class=""><br class=""></font></div><div class=""><font face="arial, helvetica, sans-serif" class="">While it is a little unusual to have definitions outside of section 2, these were placed here in section 6.5.1 in order to avoid potential conflicts with certain language that was in section 4 at the time of writing.</font></div><div class=""><font face="arial, helvetica, sans-serif" class=""><br class=""></font></div><div class=""><font face="arial, helvetica, sans-serif" class="">Owen</font></div><div class=""><font face="arial, helvetica, sans-serif" class=""><br class=""></font></div><div><blockquote type="cite" class=""><div class="">On Sep 18, 2017, at 1:14 PM, John Santos <<a href="mailto:JOHN@egh.com" class="">JOHN@egh.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><br class="">On 9/18/2017 10:37 AM, ARIN wrote:<br class=""><blockquote type="cite" class="">The following has been revised:<br class=""><br class="">* Draft Policy ARIN-2017-5: Improved IPv6 Registration Requirements<br class=""></blockquote>[snip]<br class=""><br class=""><blockquote type="cite" class="">4) Add new section 6.5.5.4 "Registration Requested by Recipient" of the NRPM, to read: "If the downstream recipient of a static assignment of /64 or more addresses requests publishing of that assignment in ARIN's registration database, the ISP should register that assignment as described in section 6.5.5.1."<br class=""></blockquote><br class="">I have been under the impression that a common goal of most people proposing NRPM changes is to eliminate the use of the term "ISP", since it is not defined in the policy and most or all the relevant sections also apply to other organizations that, while they re-allocate or reassign address space, are not, properly speaking, ISPs. Shouldn't this says "LIR" or "provider" or some other more generic term?<br class=""><br class=""><br class="">[snip]<br class=""><br class="">-- <br class="">John Santos<br class="">Evans Griffiths & Hart, Inc.<br class="">781-861-0670 ext 539<br class=""><br class="">_______________________________________________<br class="">PPML<br class="">You are receiving this message because you are subscribed to<br class="">the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="">ARIN-PPML@arin.net</a>).<br class="">Unsubscribe or manage your mailing list subscription at:<br class=""><a href="http://lists.arin.net/mailman/listinfo/arin-ppml" class="">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br class="">Please contact info@arin.net if you experience any issues.<br class=""></div></div></blockquote></div><br class=""></div></body></html>