<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Thank you for your feedback Dale. We are still gathering data at this point and I appreciate the mention of RFCs as I had not really considered that angle.<div class=""><br class=""></div><div class=""><br class=""><div class="">
<div>Brian Jones</div><div>ARIN Advisory Council (NRPM W<i class="">orking Group</i><span style="font-style: normal;" class="">)</span></div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Dec 5, 2023, at 5:10 PM, Dale W. Carder <<a href="mailto:dwcarder@es.net" class="">dwcarder@es.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Thus spake Brian Jones (<a href="mailto:bjones@vt.edu" class="">bjones@vt.edu</a>) on Tue, Dec 05, 2023 at 02:28:18PM -0500:<br class=""><blockquote type="cite" class=""><br class="">Section 6.5.1.a “Terminology” explains that ISP and LIR terms are used interchangeably throughout the entire document. The NRPM working group in discussions with ARIN staff has concluded that the term LIR could be replaced everywhere in the NRPM with the term ISP. By my counts the term LIR appears 37 times in the NRPM currently, while ISP is referenced 62 times. The LIR term is utilized less nowadays than in times past and ISP is a more widely used and well understood term. The LIR term occurs more frequently in other RIRs and it is likely that if section 6 were written solely for ARIN the ISP term would have been used. So the question to the community is, would replacing the term LIR with ISP make the NRPM more consistent and readable? The NRPM working group would like to hear your feedback.<br class=""></blockquote><br class="">I think that would be a step in the wrong direction. To me, the term<br class="">ISP seems to carry a strong commercial connotation that excludes the <br class="">existence of LIR entities that include governments, academic<br class="">institutions, non-profits, large scale enterprises, or even cloud or <br class="">content providers. <br class=""><br class="">Of course, I have some bias coming from a network that is very much not<br class="">an isp... ;-)<br class=""><br class="">The term LIR is used at other RIR's as you mention, as well as in a<br class="">number of RFC's since the mid 90's. Why should we diverge?<br class=""><br class="">I think you could delete 6.5.1.a and clarify in section 2 that LIR and<br class="">ISP may be used interchangably in the document, but personally I would <br class="">prefer use of the term ISP be cleaned up, not LIR.<br class=""><br class=""><blockquote type="cite" class="">Part b<br class="">Section 6.5.1.b defines the IPv6 nibble boundaries . The working group feels like this definition would be a better fit if moved to section 2 of the NRPM which is the Definitions section. Your thoughts about moving the IPv6 nibble boundaries definition from section 6.5.1.b to section 2 would be appreciated.<br class=""></blockquote><br class="">Sounds perfectly reasonable.<br class=""><br class="">Dale<br class=""></div></div></blockquote></div><br class=""></div></body></html>