Your IP address could not be determined at this time.

Draft Policies and Proposals

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

Implemented 17 September 2014

Discussion Tracking
Mailing List:
Formal introduction on PPML on 20 August 2013

Origin - ARIN-prop-190

Draft Policy - 20 August 2013

Stays on docket - 16 October 2013

Revised - 24 January 2014

Recommended Draft Policy - 25 March 2014

Last Call - 16 May through 2 June 2014

AC recommend Board adopt 24 June 2014

Adopted, to be implemented - 13 August 2014

Implemented - 17 September 2014


Public Policy Mailing List
ARIN Public Policy Meeting:





ARIN Advisory Council:

AC Shepherds:
Scott Leibrand, Kevin Blumberg, John Springer


ARIN Board of Trustees: 18 July 2014
Revisions Implementation
Previous version(s) 17 September 2014

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

Date: 16 May 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 Subscriber Members Less Than One Year
  • Remove section Subscriber Members After One Year


  • 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 Subscriber Members Less Than One Year and Subscriber Members After One Year

Replace with: ( 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. Determination of the appropriate allocation to be issued is based on efficient utilization of space within this time frame, consistent with the principles in 4.2.1."

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

Timetable for implementation: Immediate


Advanced Search

Relevant Links