<div dir="ltr">Hi Owen,<br><br>Thank you for sharing your perspective. It’s encouraging to see some alignment on moving forward with a consistent term, supported by a clear definition note.<br><br>Best regards,<br>Mohibul</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Sep 18, 2025 at 9:05 PM Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</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"><div><br id="m_-8291611743350726234lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Sep 18, 2025, at 04:04, Mohibul Mahmud <<a href="mailto:mohibul.mahmud@gmail.com" target="_blank">mohibul.mahmud@gmail.com</a>> wrote:</div><br><div><div dir="ltr"><div style="direction:ltr">
<div style="direction:ltr;margin-top:0in;margin-left:0in;width:7.5in">
<div style="direction:ltr;margin-top:0in;margin-left:0in;width:7.5in"><div style="margin:0in;font-family:Calibri;font-size:11pt">Hello All,</div><p style="margin:0in;font-family:Calibri;font-size:11pt"> </p><div style="margin:0in;font-family:Calibri;font-size:11pt">Thank you for the
thoughtful perspectives shared — I hear strong points on both sides:</div><p style="margin:0in;font-family:Calibri;font-size:11pt"> </p><div style="margin:0in;font-family:Calibri;font-size:11pt">• <span style="font-weight:bold">LIR</span> aligns with global terminology and avoids
the vernacular baggage of “ISP.”</div><div style="margin:0in;font-family:Calibri;font-size:11pt">• <span style="font-weight:bold">ISP</span> is consistent with ARIN’s historic usage
and avoids confusion with structures (like NIRs) that don’t exist in our
region.</div></div></div></div></div></div></blockquote><div><br></div>I think that any potential confusion with NIRs is a bit of a red herring.</div><div><br><blockquote type="cite"><div><div dir="ltr"><div style="direction:ltr"><div style="direction:ltr;margin-top:0in;margin-left:0in;width:7.5in"><div style="direction:ltr;margin-top:0in;margin-left:0in;width:7.5in"><p style="margin:0in;font-family:Calibri;font-size:11pt"> </p><div style="margin:0in;font-family:Calibri;font-size:11pt">To bridge this, I’d
suggest we converge on a practical editorial approach:</div><div style="margin:0in;font-family:Calibri;font-size:11pt">• Select one
preferred term for the NRPM (ISP or LIR).</div><div style="margin:0in;font-family:Calibri;font-size:11pt">• Add a clear
definition note stating that ISP and LIR are used interchangeably in ARIN
policy.</div><p style="margin:0in;font-family:Calibri;font-size:11pt"> </p><div style="margin:0in;font-family:Calibri;font-size:11pt">This way, ARIN
policy remains globally intelligible while providing clarity to our community.</div></div></div></div></div></div></blockquote><blockquote type="cite"><div><div dir="ltr"><div style="direction:ltr"><div style="direction:ltr;margin-top:0in;margin-left:0in;width:7.5in"><div style="direction:ltr;margin-top:0in;margin-left:0in;width:7.5in"><p style="margin:0in;font-family:Calibri;font-size:11pt"> </p><div style="margin:0in;font-family:Calibri;font-size:11pt">Would others support
moving in this direction?</div></div></div></div></div></div></blockquote><div><br></div>Since that’s pretty much what I suggested from the start, just with the strong preference for LIR being the primary choice, yes, I think that’s exactly what we should do.</div><div><br></div><div>I think there’s been general consensus for this and the debate has largely been about which term is preferred.</div><div><br></div><div>Owen</div><div><br></div></div></blockquote></div>