<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=""><div class="">I’d argue the opposite - when crafting policy, we must be precise in our language, and in general we must avoid ambiguous terms, unless there’s a specific goal to leaving a section of language open for interpretation (and even then, it must be clear whose interpretation reigns supreme).</div><div class=""><br class=""></div><div class="">I’m a fan of the term LIR, even if it is somewhat abstract. Language clearly linking the two terms, defining an ISP as the most common example of an LIR, would be helpful as well.</div><div class=""><br class=""></div><div class="">-C</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Sep 18, 2017, at 9:48 AM, David Farmer <<a href="mailto:farmer@umn.edu" class="">farmer@umn.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">This has gone back and forth over the years, some people think "LIR" is too abstract and some people think "ISP" is too specific. While ISP doesn't have it's own subsection under definitions it is discussed under "LIR", section 2.5, so I wouldn't say it's undefined. I think it's probably dangerous to make a hard and fast rule either way. I think it is probably best to think of "ISP" and "LIR" as synonyms, at least from an ARIN policy perspective, but just like many synonyms they have subtly different connotations.<div class=""><br class=""></div><div class="">Thanks.</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Sep 18, 2017 at 11:14 AM, John Santos <span dir="ltr" class=""><<a href="mailto:john@egh.com" target="_blank" class="">john@egh.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="">
<br class="">
On 9/18/2017 10:37 AM, ARIN wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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 class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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]<span class="HOEnZb"><font color="#888888" class=""><br class="">
<br class="">
-- <br class="">
John Santos<br class="">
Evans Griffiths & Hart, Inc.<br class="">
<a href="tel:781-861-0670%20ext%20539" value="+17818610670" target="_blank" class="">781-861-0670 ext 539</a><br class="">
<br class="">
______________________________<wbr 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" target="_blank" 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" rel="noreferrer" target="_blank" class="">http://lists.arin.net/mailman/<wbr class="">listinfo/arin-ppml</a><br class="">
Please contact <a href="mailto:info@arin.net" target="_blank" class="">info@arin.net</a> if you experience any issues.</font></span></blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature">===============================================<br class="">David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank" class="">Email:farmer@umn.edu</a><br class="">Networking & Telecommunication Services<br class="">Office of Information Technology<br class="">University of Minnesota <br class="">2218 University Ave SE Phone: 612-626-0815<br class="">Minneapolis, MN 55414-3029 Cell: 612-812-9952<br class="">=============================================== </div>
</div>
_______________________________________________<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.</div></blockquote></div><br class=""></body></html>