Send ARIN-PPML mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.arin.net/mailman/listinfo/arin-ppml
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-PPML digest..."
Today's Topics:
1. Re: Clean up definition of LIR/ISP vs. end-user (Tony Hain)
2. Re: Clean up definition of LIR/ISP vs. end-user (Scott Leibrand)
3. Re: Clean up definition of LIR/ISP vs. end-user (Owen DeLong)
4. Re: Clean up definition of LIR/ISP vs. end-user (Gary Buhrmaster)
----------------------------------------------------------------------
Message: 1
Date: Tue, 30 Apr 2013 10:05:50 -0700
From: "Tony Hain" <[email protected]>
To: <[email protected]>
Subject: Re: [arin-ppml] Clean up definition of LIR/ISP vs. end-user
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
> .....
> They generally are, reference the "LIR" definition in NRPM 2.4
> <https://www.arin.net/policy/nrpm.html#two4>
>
> "A Local Internet Registry (LIR) is an IR that primarily assigns address
space to
> the users of the network services that it provides. LIRs are generally
Internet
> Service Providers (ISPs), whose customers are primarily end users and
> possibly other ISPs."
>
> and then NRPM 6.5 -
>
> "6.5.1. Terminology
>
> . The terms ISP and LIR are used interchangeably in this document and any
> use of either term shall be construed to include both meanings."
>
> > My vote goes towards a global replacement of "ISP" in all ARIN documents
> with the term "LIR" in order to match the language used by the other 4
RIRs.
> I would then support an brief statement early in the NRPM which explains
> that "The term LIR has replaced the term ISP formerly used in ARIN policy
> documents in order to simplify the global understanding of RIR policy
> documents. The definition of LIR exactly matches the previous definition
of
> ISP for the purpose of the ARIN NRPM." (well, something like that, you
get
> the point).
>
>
> Easy enough to accomplish, if folks believe that the end result will be
more
> clear than present approach.
While I agree that from the perspective of 'this allocation is for 3rd party
use' leads to LIR==ISP, the justification process and unit sizes were
historically a little different in that ISP customer ~= /30 - /32 blocks
while typical LIR customer ~< /27, and the ISP was also getting space for
an internal infrastructure while the LIR did not. My concern is that by
merging terms there might be an unintended consequence in the evaluation
side of this. I have no objection to the merge and actually support the
simplification, just asking that someone comment about potential confusion
between those with an infrastructure (ISP), and those without (LIR). If we
effectively split the ISPs into the LIR part supporting customers, and the
end-user part for their infrastructure, that may simplify policy language,
but make the justification/evaluation process more difficult.
Tony
------------------------------
Message: 2
Date: Tue, 30 Apr 2013 11:06:32 -0700
From: Scott Leibrand <[email protected]>
To: Tony Hain <[email protected]>
Cc: ARIN-PPML List <[email protected]>
Subject: Re: [arin-ppml] Clean up definition of LIR/ISP vs. end-user
Message-ID:
<cagkmwz7nqh5czqoouf0shb+t6vnbdn4_zdmqv40mmyoqjug...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
The term LIR is not used in IPv4 policy (NRPM section 4), only in IPv6
policy (section 6).
-Scott
On Tue, Apr 30, 2013 at 10:05 AM, Tony Hain <[email protected]> wrote:
> > .....
> > They generally are, reference the "LIR" definition in NRPM 2.4
> > <https://www.arin.net/policy/nrpm.html#two4>
> >
> > "A Local Internet Registry (LIR) is an IR that primarily assigns address
> space to
> > the users of the network services that it provides. LIRs are generally
> Internet
> > Service Providers (ISPs), whose customers are primarily end users and
> > possibly other ISPs."
> >
> > and then NRPM 6.5 -
> >
> > "6.5.1. Terminology
> >
> > . The terms ISP and LIR are used interchangeably in this document and
> any
> > use of either term shall be construed to include both meanings."
> >
> > > My vote goes towards a global replacement of "ISP" in all ARIN
> documents
> > with the term "LIR" in order to match the language used by the other 4
> RIRs.
> > I would then support an brief statement early in the NRPM which explains
> > that "The term LIR has replaced the term ISP formerly used in ARIN policy
> > documents in order to simplify the global understanding of RIR policy
> > documents. The definition of LIR exactly matches the previous definition
> of
> > ISP for the purpose of the ARIN NRPM." (well, something like that, you
> get
> > the point).
> >
> >
> > Easy enough to accomplish, if folks believe that the end result will be
> more
> > clear than present approach.
>
> While I agree that from the perspective of 'this allocation is for 3rd
> party
> use' leads to LIR==ISP, the justification process and unit sizes were
> historically a little different in that ISP customer ~= /30 - /32 blocks
> while typical LIR customer ~< /27, and the ISP was also getting space for
> an internal infrastructure while the LIR did not. My concern is that by
> merging terms there might be an unintended consequence in the evaluation
> side of this. I have no objection to the merge and actually support the
> simplification, just asking that someone comment about potential confusion
> between those with an infrastructure (ISP), and those without (LIR). If we
> effectively split the ISPs into the LIR part supporting customers, and the
> end-user part for their infrastructure, that may simplify policy language,
> but make the justification/evaluation process more difficult.
>
> Tony
>
>
>
> _______________________________________________
> 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:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130430/43ff6ed3/attachment-0001.html>
------------------------------
Message: 3
Date: Tue, 30 Apr 2013 11:36:30 -0700
From: Owen DeLong <[email protected]>
To: "Alexander, Daniel" <[email protected]>
Cc: ARIN-PPML List <[email protected]>
Subject: Re: [arin-ppml] Clean up definition of LIR/ISP vs. end-user
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Dan,
The definitions apply to IPv6 as well.
I believe they are still necessary.
Owen
On Apr 29, 2013, at 20:37 , "Alexander, Daniel"
<[email protected]> wrote:
> Hello All,
>
> I would be curious to hear people's opinions of whether the distinctions are
> still necessary within ARIN policy. Once the IPv4 free pool is depleted, and
> the policies become focused on processing transfers, do we need to
> distinguish between End Users, non-End Users, and PA vs PI within ARIN policy?
>
> What are the criteria in which these distinctions matter, and will they still
> apply next year?
>
> Dan
> ARIN AC
>
> From: Scott Leibrand <[email protected]>
> Date: Mon, 29 Apr 2013 13:41:56 -0700
> To: ARIN-PPML List <[email protected]>
> Subject: [arin-ppml] Clean up definition of LIR/ISP vs. end-user
>
> At ARIN 31 last week, Leslie's Policy Experience Report (slides at
> https://www.arin.net/participate/meetings/reports/ARIN_31/PDF/monday/nobile_policy.pdf
> or
> https://www.arin.net/participate/meetings/reports/ARIN_31/PPT/monday/nobile_policy.pptx)
> reported that, in ARIN staff's experience, the NRPM does not adequately
> define ISP/LIR vs. end-user. For example, by literally applying the existing
> definitions as currently written, my employer would be neither an ISP nor and
> end-user, because while they do not *primarily* assign address space to
> users, neither do they *exclusively* use it in their own networks. So I
> think those definitions need a few tweaks.
>
> I would propose that the primary difference between ISPs/LIRs vs. end-users,
> for purposes of the NRPM, is whether an organization reassigns address blocks
> to third parties. If an organization maintains full control of all of the
> equipment on its network, and doesn't need to make any reassignments to other
> organizations, then it can qualify as an end-user. In particular, an end
> user organization must be able to supply a full list of all the IP addresses
> in use on its network, and know what devices are using those addresses.
>
> An ISP/LIR, on the other hand, should be defined by whether they delegate
> that responsibility to another organization. In that case, they need to
> reassign the network space via SWIP/rwhois, which makes them an LIR.
>
> I understand that there are other considerations, such as the expectation in
> the security community that addresses within an ISP allocation are generally
> controlled by third parties, whereas addresses in an end-user assignment are
> generally controlled by the end-user organization. However, I don't believe
> it's practical to try to draw a distinction there: rather, organizations can
> decide for themselves whether they need to make reassignments (for that or
> several other reasons), and that decision can drive whether they are
> considered an ISP/LIR or end-user for purposes of ARIN policy.
>
> In light of the above, I would propose the following revised definitions:
>
> 2.4. Local Internet Registry (LIR)
> The terms Internet Service Provider (ISP) and LIR are used interchangeably in
> this document. A Local Internet Registry (LIR) is an IR that assigns address
> space to the users of the network services that it provides. Therefore, LIRs
> / ISPs are organizations that reassign addresses to end users and/or
> reallocate addresses to other ISPs/LIRs.
>
> 2.6. End-user
> An end-user is an organization receiving assignments of IP addresses
> exclusively for use in its operational networks, and does not register any
> reassignments of that space.
>
> Thoughts? Should I submit this as a policy proposal?
>
> -Scott
> _______________________________________________ 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: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact
> [email protected] if you experience any issues.
> _______________________________________________
> 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:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130430/b36ffd87/attachment-0001.html>
------------------------------
Message: 4
Date: Tue, 30 Apr 2013 18:41:54 +0000
From: Gary Buhrmaster <[email protected]>
To: John Curran <[email protected]>
Cc: Dani Roisman <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [arin-ppml] Clean up definition of LIR/ISP vs. end-user
Message-ID:
<CAMfXtQxKbSjc86ESybECU5qD3p+HWCvaMcLW8a=plke3nh-...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Apr 30, 2013 at 2:17 PM, John Curran <[email protected]> wrote:
...
> Easy enough to accomplish, if folks believe that the end result will be more
> clear than present approach.
Using one term (LIR) everywhere has an advantage in reading of
the NRPM (although I would assert few do (present company are
the exception, of course), and fewer still can actually figure out
all the nuances (or maybe I am projecting my own limits when
reading the NRPM :-)). But, so that those that think of themselves
as ISPs know how they are being referred to as, the 2.4 reference
should probably be enhanced with something like:
.. 2.4 Local Internet Registry [LIR] / ISPs
..... For consistency ... the document uses the term LIR.
As an editorial only change (since 6.5.1 explicitly states that
LIR == ISP), this should not be especially controversial. On
the other hand, I do not consider this important enough to
invest a lot of resources into.
------------------------------
_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml
End of ARIN-PPML Digest, Vol 94, Issue 46
*****************************************