<div dir="ltr">Please explain what is confusing about the current usage of both LIR and ISP?<div><br></div><div>The following Blog post from ARIN seems perfectly straightforward to me;</div><div> <a href="https://www.arin.net/blog/2023/02/28/ISP-or-end-user/">https://www.arin.net/blog/2023/02/28/ISP-or-end-user/</a></div><div><br></div><div>And the following page is about Requesting IP addresses.</div><div><a href="https://www.arin.net/resources/guide/request/">https://www.arin.net/resources/guide/request/</a></div><div><br></div><div><br></div><div>They both seem to address the idea that LIR and ISP are effectively the same thing.</div><div><br></div><div>Organizations that want to consider themselves as ISPs can, and those that don't want to consider themselves as ISPs have the term LIR.</div><div><br></div><div>I don't see any advantage in making the term LIR go away or any confusion around the term.</div><div><br></div><div>Thanks</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Sep 19, 2025 at 4:41 PM William Herrin <<a href="mailto:bill@herrin.us">bill@herrin.us</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, Sep 19, 2025 at 12:50 PM Owen DeLong via ARIN-PPML<br>
<<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>> wrote:<br>
> Why does the NRPM have to match ARIN internal terminology?<br>
> While I would encourage ARIN to adopt a better internal use of terminology, I don’t see that as relevant to the policy process at all.<br>
<br>
Hi Owen,<br>
<br>
Can you explain how it would benefit the community for ARIN to use one<br>
set of terminology in the NRPM and a different set of terminology in<br>
its communication with registrants?<br>
<br>
ARIN uses "ISP" in its software and operating practices, and<br>
occasionally "LIR/ISP." If we want to zero in on a different term of<br>
art, I think we have to expect the organization to harmonize on that<br>
term. Consistency is just good communication practice. Zeroing in on a<br>
term other than ISP will incur a cost in changed documents, modified<br>
training and updated software.<br>
<br>
On the other hand, adjustments to the NRPM definition of ISP that<br>
don't particularly alter ARIN's practices, and harmonizing the NRPM on<br>
that term, carry a negligible cost.<br>
<br>
Regards,<br>
Bill Herrin<br>
<br>
<br>
-- <br>
William Herrin<br>
<a href="mailto:bill@herrin.us" target="_blank">bill@herrin.us</a><br>
<a href="https://bill.herrin.us/" rel="noreferrer" target="_blank">https://bill.herrin.us/</a><br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">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>