ISP is a very ambiguous term which carries a lot of different connotations to different people, most of which don’t describe the full range of ARIN member LIRs.
LIRs include cloud providers, CDNs, certain government entities, colocation facilities, “eyeball” providers, backbone providers, tunnel/vpn service providers, SDWAN providers, SAAS providers, etc. Sure, most of those could be called an ISP under some definition of the term, but would be excluded from the term in many other people’s minds. Best to avoid the quagmire of ambiguity and talk in terms of what ARIN is actually concerned about, which is the local registration of addresses to other entities (whether internal, external, or both). As such, yes, I have a strong belief that LIR is a term better suited to ARIN policy as it is both more descriptive of the bodies being described and more relatable to the policy intent. Owen > On Dec 12, 2023, at 11:05, Brian Jones <bjo...@vt.edu> wrote: > > Thank you for the feedback Owen. It seems you have a strong leaning toward > the LIR term over the term ISP, would you care to tell me more about why you > feel the term LIR is the better choice? Thank you agin for the valuable input > and feedback. It is greatly appreciated by myself and the NRPM working group. > > > Brian Jones > ARIN Advisory Council (NRPM Working Group) > > > >> On Dec 9, 2023, at 5:10 AM, Owen DeLong <o...@delong.com >> <mailto:o...@delong.com>> wrote: >> >> This is a step in the wrong direction… If you’re going to unify the >> terminology, ISP->LIR would be the better choice. >
_______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML@arin.net). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact i...@arin.net if you experience any issues.
