[arin-ppml] Revised - Recommended Draft Policy ARIN-2018-2: Clarification to ISP Initial Allocation

[ARIN]

The following has been revised:

* Recommended Draft Policy ARIN-2018-2: Clarification to ISP Initial 
Allocation

Revised text is below and can be found at:
https://www.arin.net/policy/proposals/2018_2.html

You are encouraged to discuss all Draft Policies on PPML. The AC will 
evaluate the discussion in order to assess the conformance of this draft 
policy with ARIN's Principles of Internet number resource policy as 
stated in the Policy Development Process (PDP). Specifically, these 
principles are:

* Enabling Fair and Impartial Number Resource Administration
* Technically Sound
* Supported by the Community

The PDP can be found at:
https://www.arin.net/policy/pdp.html

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html

Regards,

Sean Hopkins
Policy Analyst
American Registry for Internet Numbers (ARIN)



Recommended Draft Policy ARIN-2018-2: Clarification to ISP Initial 
Allocation

Problem Statement:

As discussed in more detail in ARIN-2017-9 and noted in the ARIN 40 
Policy Experience Report, the criteria to qualify for an initial block 
of address space in 4.2.2 and 8.5.4 are seeming at odds with each other. 
At ARIN 41 the community seemed to prefer the approach contained in this 
policy over the approach in ARIN-2017-9, which was subsequently abandoned.

Moreover, as the NRPM (2018-1) currently sits, 4.2.2 appears to state 
that an initial allocation of up to a /21 could be granted without any 
more justification than needed to qualify for a /24. Therefore, 4.2.2 
should be modified, allowing an initial allocation of only a /24 without 
any additional justification and allowing an initial allocation of up to 
a /21 when justified by a 24-month allocation plan.

Policy Statement:

Replace the current Section 4.2.2 with:

4.2.2. Initial allocation to ISPs

All ISP organizations without direct allocations, direct assignments, 
re-allocations or reassignments automatically qualify for a /24. These 
organizations are exempt from requirements of showing the efficient 
utilization of previously held IPv4 space. These organizations may 
qualify for up to and including a /21 by documenting how the requested 
allocation will be utilized within the request size specified in 4.2.4.3

ISPs holding re-allocations and/or reassignments must show the efficient 
utilization of their resources consistent with the requirements in 
sections 4.2.3 and 4.2.4

Comments:

The timetable for Implementation: Immediate

Anything Else:

This is an attempt to clarify the changes that came about from 2016-4. 
It also aligns section 4.2 with the current transfer policy. It also 
re-established the understanding that ISP can renumber and return, but 
putting the last section 4.2.2.1.4 into the ISP additional requests 
section. The policy text has been changed and the proposed section 
4.2.2.1.4 was deleted in its entirety.