Bill & Cathy –

The policy proposal is intended to correct what is regarded as an editorial 
error. When Section 6.5.1a was added, it is believed the intention was for it 
to apply to the “section” (Section 6.5) only, and is interpreted that way in 
practice. However, it was written with the word “document,” which could 
unintentionally allow someone to suggest it implies a larger context (the whole 
of NRPM.)

This proposal seeks to clarify by adjusting the language in 6.5.1a to 
explicitly state that everything in Section 6.5 applies to both LIRs and ISPs, 
even though the language of the section only uses the term LIR. Elsewhere in 
NRPM there are distinctions between LIRs and ISPs that are relevant for policy 
implementation and, as a result, there is a distinction between LIR and ISP in 
those contexts.

To think about it holistically – for all sections of NRPM aside from 6.5, LIRs 
and ISPs have distinct differences. Inside of Section 6.5, anywhere it 
references an LIR, that policy also applies to an ISP. This policy changes the 
word “Document” to “Section” to ensure there is no confusion about that.

Hope that helps –


Doug


--
Douglas J. Camin
Member, ARIN Advisory Council
[email protected]

From: ARIN-PPML <[email protected]> on behalf of Cj Aronson 
<[email protected]>
Date: Wednesday, June 19, 2024 at 5:08 PM
To: Knowles Consulting <[email protected]>
Cc: PPML <[email protected]>
Subject: Re: [arin-ppml] Feedback Request: Policy ARIN-2024-6: 6.5.1a 
Definition Update
I think the question is why are you replacing "document" with "section"?  So is 
LIR not used in the rest of the "document"?  If it is then doesn't it still 
mean what it means in this "section"?

Thanks!
----Cathy

{Ô,Ô}
  (( ))
  ◊  ◊


On Wed, Jun 19, 2024 at 3:01 PM Knowles Consulting 
<[email protected]<mailto:[email protected]>> wrote:
Hi William,

This particular change is only to the actual word used.

The proposal seeks to replace the word “document“ with “section”.

So as it pertains to that section in policy both terms can be used.

Hope that helps.


Sent from a mobile device. Please excuse brevity and typos


> On Jun 19, 2024, at 4:51 PM, William Herrin 
> <[email protected]<mailto:[email protected]>> wrote:
>
> On Wed, Jun 19, 2024 at 12:15 PM Douglas Camin 
> <[email protected]<mailto:[email protected]>> wrote:
>> Change the text from:
>>
>> The terms ISP and LIR are used interchangeably in this document and any use 
>> of either term shall be construed to include both meanings.
>>
>> to
>>
>> The terms ISP and LIR are used interchangeably in this SECTION and any use 
>> of either term shall be construed to include both meanings.
>
> Howdy,
>
> I'm confused. Are you saying you want LIR and ISP to mean different
> things depending on where they appear in the NRPM document?
>
> Regards,
> Bill Herrin
>
>
> --
> William Herrin
> [email protected]<mailto:[email protected]>
> https://bill.herrin.us/
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List 
> ([email protected]<mailto:[email protected]>).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected]<mailto:[email protected]> if you experience any 
> issues.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List 
([email protected]<mailto:[email protected]>).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected]<mailto:[email protected]> if you experience any issues.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to