Recommended Draft Policy ARIN-2016-2: Change timeframes for IPv4 requests to 24 months [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: Implemented

Tracking Information

Discussion Tracking

Mailing List:

Formal introduction on PPML on 24 May 2016

Origin - ARIN-prop-227

Draft Policy - 24 May 2016

Recommended Draft Policy - 20 September 2016

Last Call - 26 October 2016

Recommended to Board: 22 November 2016

Implemented: 20 April 2017

Public Policy Mailing List

ARIN Public Policy Meeting:

ARIN 38

ARIN Advisory Council:

AC Shepherds:
Tina Morris, Scott Leibrand

ARIN Board of Trustees:

19 December 2016

Revisions:

Implementation:

Recommended Draft Policy ARIN-2016-2: Change timeframes for IPv4 requests to 24 months

Date: 26 October 2016

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

2016-2 is one of a set of overlapping policies involving simplification of section 8 specified transfer policy. Each takes a somewhat different approach, and all have a degree of community support. Based on community feedback at the upcoming ARIN 38 meeting in Dallas, we hope to advance whichever of those proposals is best-supported by the community, or craft and advance a unified proposal that incorporates the best attributes of the proposals currently on the docket. Moving 2016-2 to Recommended Draft will facilitate moving the best policy forward in a timely manner.

Problem Statement:

Disparity in timeframes between pre-approvals for waiting list and pre-approval for transfers is creating difficulties for organizations that initially apply to be on the waiting list and subsequently elect to satisfy their needs through transfers. Therefore, this proposal seeks to set all timeframes for IPv4 request approvals to 24 months. Prior to runout, such a change could have created great disparity in resource distribution just because of coincidence of request timing. With the free pool gone, this is no longer an issue.

Policy statement:

The following changes would be made in the NRPM:

  1. Retitle section 4.2.2.1.3 “Three months” to “Time Horizon”.

  2. Section 4.2.2.1.3 body, replace “three months” with “24 months”.

  3. Section 4.2.3.8, replace the term “three months” with “24 months”.

  4. Section 4.3.3, replace both instances of “one year” with “24 months”.

  5. Section 4.2.4.3, replace the entire paragraph which currently reads: “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.”

with:

“ISPs may request up to a 24-month supply of IPv4 addresses.”

Comments:

a. Timetable for implementation: Immediate

b. Clarification of intent - This policy would not affect the existing waiting list in any way. This policy would simply change the qualification period to 24 months, so new entrants can go to either the bottom of the waiting list or to the transfer market to seek their 24-month supply. If an existing entity on the waiting list wants to re-qualify and expand their request to a 24-month supply, they would go to the end of the list. Otherwise, they would remain on the waiting list with the original approved block size unchanged. If the organization’s needs have changed by the time IPv4 space becomes available to fill waiting list requests, the organization will be re-qualified under the new more lenient 24-month standard, but regardless of re-qualification, the organization will not be eligible to receive a larger block than they originally qualified for when they were placed on the waiting list.

##########

Earlier Version

##########

Recommended Draft Policy ARIN-2016-2: Change timeframes for IPv4 requests to 24 months

Date: 20 September 2016

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

2016-2 is one of a set of overlapping policies involving simplification of section 8 specified transfer policy. Each takes a somewhat different approach, and all have a degree of community support. Based on community feedback at the upcoming ARIN 38 meeting in Dallas, we hope to advance whichever of those proposals is best-supported by the community, or craft and advance a unified proposal that incorporates the best attributes of the proposals currently on the docket. Moving 2016-2 to Recommended Draft will facilitate moving the best policy forward in a timely manner.

Problem Statement:

Disparity in timeframes between pre-approvals for waiting list and pre-approval for transfers is creating difficulties for organizations that initially apply to be on the waiting list and subsequently elect to satisfy their needs through transfers. Therefore, this proposal seeks to set all timeframes for IPv4 request approvals to 24 months. Prior to runout, such a change could have created great disparity in resource distribution just because of coincidence of request timing. With the free pool gone, this is no longer an issue.

Policy statement:

The following changes would be made in the NRPM:

  1. Retitle section 4.2.2.1.3 “Three months” to “Time Horizon”.

  2. Section 4.2.2.1.3 body, replace “three months” with “24 months”.

  3. Section 4.2.3.8, replace the term “three months” with “24 months”.

  4. Section 4.3.3, replace both instances of “one year” with “24 months”.

  5. Section 4.2.4.3, replace the entire paragraph which currently reads:

“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.”

with:

“ISPs may request up to a 24-month supply of IPv4 addresses.”

Comments:

a. Timetable for implementation: Immediate

b. Clarification of intent - This policy would not affect the existing waiting list in any way. This policy would simply change the qualification period to 24 months, so new entrants can go to either the bottom of the waiting list or to the transfer market to seek their 24-month supply. If an existing entity on the waiting list wants to re-qualify and expand their request to a 24-month supply, they would go to the end of the list. Otherwise, they would remain on the waiting list with the original approved block size unchanged. If the organization’s needs have changed by the time IPv4 space becomes available to fill waiting list requests, the organization will be re-qualified under the new more lenient 24-month standard, but regardless of re-qualification, the organization will not be eligible to receive a larger block than they originally qualified for when they were placed on the waiting list.

##########

Earlier Version

##########

ARIN-2016-2: Change timeframes for IPv4 requests to 24 months

Date: 24 May 2016

Problem Statement:

Disparity in timeframes between pre-approvals for waiting list and pre-approval for transfers is creating difficulties for organizations that initially apply to be on the waiting list and subsequently elect to satisfy their needs through transfers.

Therefore, this proposal seeks to set all timeframes for IPv4 request approvals to 24 months. Prior to runout, such a change could have created great disparity in resource distribution just because of coincidence of request timing. With the free pool gone, this is no longer an issue.

Policy Statement:

Retitle section 4.2.2.1.3 “Three months” to “Time Horizon”.

In section 4.2.2.1.3 body, replace “three months” with “24 months”.

In section 4.2.3.8, replace the term “three months” with “24 months”.

In section 4.3.3, replace both instances of “one year” with “24 months”.

In section 4.2.4.3, replace the entire paragraph which currently reads: “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.”

with:

“ISPs may request up to a 24 month supply of IPv4 addresses.”

Timetable for implementation: Immediate

#########################

ARIN STAFF & LEGAL ASSESSMENT
Draft Policy ARIN-2016-2
CHANGE TIMEFRAMES FOR IPV4 REQUESTS TO 24 MONTHS
https://www.arin.net/policy/proposals/2016_2.html

Date of Assessment: 11 August 2016

  1. Summary (Staff Understanding)

This policy language would change the needs-assessment time horizon considered for requests to be added to the waiting list for unmet requests. For ISP organizations it would change from 3 months to 24 months. For end-user organizations it would change from 12 months to 24 months. All requests for IPv4 address space destined for the waiting list for unmet requests would consider the 24-month needs of the requesting organization.

  1. Comments

A. ARIN Staff Comments

* All documentation related to the request process on the ARIN public web site and in outreach materials that describe the 3-month, 12-month (one year), and 24-month request horizons will require updating. This includes request guides, descriptions about the request process, and training materials.

* The ARIN Online IPv4 request screens will need to be updated to describe the proper x-months needs horizon, accordingly.

* This policy could be implemented as written.

B. ARIN General Counsel – Legal Assessment

The policy does not appear to create any material legal issue.

  1. Resource Impact

This policy would have a moderate resource impact to implement. It is estimated it will take up to six months to implement following the ratification of these policy changes. The following would be needed in order to implement:

* Updated guidelines and internal procedures

* Updates to ARIN Online request screens

* Updates to descriptions of the request process on the ARIN public website, in outreach materials, and training/outreach slide decks. This impacts web publications, print publications, and electronic and/or slide-deck publications.

* Staff training

  1. Proposal / Draft Policy Text Assessed

Draft Policy ARIN-2016-2
Change Timeframes for IPv4 Requests to 24 Months

Date: 24 May 2016

Problem statement:

Disparity in timeframes between pre-approvals for waiting list and pre-approval for transfers is creating difficulties for organizations that initially apply to be on the waiting list and subsequently elect to satisfy their needs through transfers.

Therefore, this proposal seeks to set all timeframes for IPv4 request approvals to 24 months. Prior to runout, such a change could have created great disparity in resource distribution just because of coincidence of request timing. With the free pool gone, this is no longer an issue.

Policy statement:

Retitle section 4.2.2.1.3 “Three months” to “Time Horizon”.

In section 4.2.2.1.3 body, replace “three months” with “24 months”.

In section 4.2.3.8, replace the term “three months” with “24 months”.

In section 4.3.3, replace both instances of “one year” with “24 months”.

In section 4.2.4.3, replace the entire paragraph which currently reads: “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.”

with:

“ISPs may request up to a 24 month supply of IPv4 addresses.”

Comments:

a. Timetable for implementation: Immediate

END

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.