Draft Policy ARIN-2013-5: LIR/ISP and End-user Definitions [Archived]

OUT OF DATE?

Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.

Status: Abandoned

Tracking Information

Discussion Tracking

Mailing List:

Formal introduction on PPML on 17 May 2013

Origin - ARIN-prop-188

Draft Policy - 17 May 2013

Revised - 3 September 2013

Abandoned by AC - 24 September 2013

Public Policy Mailing List

ARIN Public Policy Meeting:

PPC at NANOG 58

ARIN Advisory Council:

AC Shepherds:
Kevin Blumberg, Owen DeLong and John Springer

ARIN Board of Trustees:

Revisions:

Previous version(s)

Implementation:

Draft Policy ARIN-2013-5
LIR/ISP and End-user Definitions

Date: 3 September 2013

Problem Statement:

At ARIN 31, the Policy Experience Report (slides at https://www.arin.net/vault/participate/meetings/reports/ARIN_31/PDF/monday/nobile_policy.pdf or https://www.arin.net/vault/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. As currently defined, and interpreted literally, many companies do not qualify as either LIRs or end-users.

The proposed text would not change any existing definitions. It would instead put the onus on the requstor to provide additional information, when it was for a new IP use.

Policy statement:

Retain existing NRPM text.

Add to Section 2:

Any organization which does not clearly fit into one of the above categories shall be treated as an LIR/ISP for policy purposes.

Timetable for implementation: Immediate

##########

ARIN Staff and Legal Assessment

DRAFT NUMBER AND NAME: Draft Policy ARIN-2013-5
LIR/ISP and End-user Definitions

DATE: 19 September 2013

Summary (Staff Understanding)

This policy proposal would require networks to be considered under the ISP/LIR policies if it isn’t clear to staff whether they are considered an end user or an ISP/LIR based on the definitions provided in the NRPM.

Comments

A. ARIN Staff Comments

· This proposal does not address the issue of which organization fits into which category.
· Staff needs guidance on what types of networks should be considered end users and what types of networks should be considered ISPs - specifically, technologies that involve assigning IP addresses to customers outside the traditional ISP context, such as cloud computing, VPNs, etc.
· This issue was raised in the last policy experience report and continues to be problematic for staff.
· Staff needs clarification on the exact placement of this policy in NRPM.

B. ARIN General Counsel - Legal Assessment

I don’t see any serious legal concerns in this policy.

Resource Impact

This policy would have minimal resource impact from an implementation aspect. It is estimated that implementation would occur within 3 months after ratification by the ARIN Board of Trustees. The following would be needed in order to implement:

A. Updated guidelines

B. Staff training

Draft Policy Text:

Proposed text:
Retain existing NRPM text.
Add to Section 2:
Any organization which does not clearly fit into one of the above categories shall be treated as an LIR/ISP for policy purposes.

Problem Statement:
At ARIN 31, the Policy Experience Report (slides athttps://www.arin.net/vault/participate/meetings/reports/ARIN_31/PDF/monday/nobile_policy.pdf
or https://www.arin.net/vault/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. As currently defined, and interpreted literally, many companies do not qualify as either LIRs or end-users.
The proposed text would not change any existing definitions. It would instead put the onus on the requstor to provide additional information, when it was for a new IP use.