[arin-ppml] Recommended Draft Policy ARIN-2013-7: NRPM 4 (IPv4) Policy Cleanup

[ARIN]

Recommended Draft Policy ARIN-2013-7
NRPM 4 (IPv4) Policy Cleanup

On 20 March 2014 the ARIN Advisory Council (AC) recommended
ARIN-2013-7 for adoption, making it a Recommended Draft Policy.

ARIN-2013-7 is below and can be found at:
https://www.arin.net/policy/proposals/2013_7.html

You are encouraged to discuss Draft Policy 2013-7 on the PPML prior to
the upcoming ARIN 33 Public Policy Meeting. Both the discussion on the 
list and at the meeting will be used by the ARIN Advisory Council to 
determine the community consensus for adopting this as policy.

The ARIN Policy Development Process 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,

Communications and Member Services
American Registry for Internet Numbers (ARIN)


## * ##


Recommended Draft Policy ARIN-2013-7
NRPM 4 (IPv4) Policy Cleanup

Date: 25 March 2014

AC's assessment of conformance with the Principles of Internet Number 
Resource Policy:

"ARIN-2013-7: "NRPM 4 (IPv4) Policy Cleanup" enables fair and impartial 
number resource administration by removing no-longer-relevant sections 
of the NRPM, and clarifying other sections.  All of the remaining 
changes in this draft policy have proven uncontroversial thus far."

Problem Statement:

Parts of NRPM 4 are irrelevant, especially after IPv4 run-out, and 
should be cleaned up for clarity.

Policy statement:

Short list of changes with details explained below.

     Remove section 4.1.1 Routability
     Update section 4.1.5 Determination of resource requests
     Remove section 4.1.7 RFC2050
     Remove section 4.1.9 Returned IPv4 Addresses
     Replace and retitle section 4.2.4.3 Subscriber Members Less Than 
One Year
     Remove section 4.2.4.4. Subscriber Members After One Year

Details:

     Remove section 4.1.1 Routability

It is no longer necessary for the NRPM to suggest where an organization 
obtains resources from.

     Retitle and rewrite section (4.1.5 Determination of IP address 
allocation size)

Remove: "Determination of IP address allocation size is the 
responsibility of ARIN."

Replace with: (4.1.5 Resource request size) "Determining the validity of 
the amount of requested IP address resources is the responsibility of ARIN."

Rationale: Clarify that it is the validity of the request that is more 
the focus than the amount of resources requested. This does not prevent 
ARIN from suggesting that a smaller block would be justified where a 
larger one would not, but also does not suggest that it is ARIN's sole 
discretion to judge the size of the blocks needed.

     Remove section 4.1.7 RFC2050

Now that RFC2050 has been replaced with RFC 7020 and ARIN-2013-4 RIR 
Principles has been adopted, this section is no longer needed.

     Remove section 4.2.4.3 Subscriber Members Less Than One Year and 
4.2.4.4. Subscriber Members After One Year

Replace with: (4.2.4.3 Request size) "ISPs may request up to a 3-month 
supply of IPv4 addresses from ARIN, or a 24-month supply via 8.3 or 8.4 
transfer."

Rationale: Since ARIN received its last /8, by IANA implementing section 
10.4.2.2, this is now a distinction without a difference.

Timetable for implementation: Immediate

##########

ARIN Staff and Legal Assessment

ARIN-prop-2013-7bis – “NRPM 4 (IPv4) Policy Cleanup”

Date of Assessment:  04 Mar 2014

1. Summary (Staff Understanding)

The intent of this proposal is to modify several existing sections of 
NRPM 4 as the author believes that they are becoming increasingly 
irrelevant as we move closer to IPv4 run-out.  Sections to be modified 
include 4.1.1, 4.1.5, 4.1.7, 4.1.9, 4.2.4.3, 4.2.4.4, and 4.2.5.

Changes include:
1.     No longer comments on global routability for IP addresses issued 
by ARIN and no longer recommends where ISPs should consider requesting 
IP address space
2.     Removes ARIN's sole discretion to determine the size of 
additional IPv4 allocations to ISPs
3.     Removes reference to RFC2050
4.     Removes text requiring ARIN to make returned, revoked, and 
recovered IP addresses available in the ARIN region as soon as possible
5.     Codifies that all ISPs may request up to a three month supply of 
IPv4 addresses from ARIN, or a 24 month supply via 8.3 transfer
6.     Removes the web hosting policy

  2. Comments

A.    ARIN Staff Comments

·      This proposal removes or modifies 7 different policies in NRPM, 
however, these changes do not appear to alter staff’s ability to obtain 
appropriate justification for resource requests, nor create any 
potential operational impact.

·      This proposal could be implemented as written

B.    ARIN General Counsel - Legal Assessment

The policy does not create legal concerns.



3. 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:

·      Updated guidelines and internal procedures

·      Staff training

  4. Proposal Text

Problem Statement: Parts of NRPM 4 are irrelevant, especially after IPv4
run-out, and should be cleaned up for clarity.

Policy statement:

Short list of changes with details explained below.

Remove section 4.1.1 Routability
Update section 4.1.5 Determination of resource requests
Remove section 4.1.7 RFC2050
Remove section 4.1.9 Returned IPv4 Addresses
Replace and retitle section 4.2.4.3 Subscriber Members Less Than One Year
Remove section 4.2.4.4. Subscriber Members After One Year
Remove section 4.2.5 Web Hosting Policy
Details:

Remove section 4.1.1 Routability
It is no longer necessary for the NRPM to suggest where an organization
obtains resources from.

Retitle and rewrite section (4.1.5 Determination of IP address 
allocation size)
Remove: "Determination of IP address allocation size is the 
responsibility of ARIN."

Replace with: (4.1.5 Resource request size) "Determining the validity of
the amount of requested IP address resources is the responsibility of ARIN."

Rationale: Clarify that it is the validity of the request that is more 
the focus than the amount of resources requested. This does not prevent 
ARIN from suggesting that a smaller block would be justified where a 
larger one would not, but also does not suggest that it is ARIN's sole 
discretion to judge the size of the blocks needed.

Remove section 4.1.7 RFC2050
Now that RFC2050 has been replaced with RFC 7020 and ARIN-2013-4 RIR
Principles has been adopted, this section is no longer needed.

Remove section 4.2.4.3 Subscriber Members Less Than One Year and 
4.2.4.4. Subscriber Members After One Year
Replace with: (4.2.4.3 Request size) "ISPs may request up to a 3-month
supply of IPv4 addresses from ARIN, or a 24-month supply via 8.3 transfer."

Rationale: Since ARIN received its last /8, by IANA implementing section
10.4.2.2, this is now a distinction without a difference.

Remove section 4.2.5 Web Hosting Policy
This information-gathering policy has been in place for a decade now 
with no resulting policy changes, and is no longer needed in light of 
IPv4 runout.