LAST CALL for Recommended Draft Policy ARIN-2016-2: Change timeframes for IPv4 requests to 24 months
ARIN
info at arin.net
Wed Oct 26 17:14:57 EDT 2016
The ARIN Advisory Council (AC) met on 21 October 2016 and decided to
send Recommended Draft Policy ARIN-2016-2: Change timeframes for IPv4
requests to 24 months to Last Call:
The AC provided the following statement to the community:
ARIN 2016-2: "Change timeframes for IPv4 requests to 24 months"
contributes to fair and impartial number resource administration by
standardizing time frames for requests throughout the NRPM. This will
streamline procedures for all new requests. The proposal has received a
favorable community response on PPML, and at ARIN38 it was well
supported and did not generate any opposition.
Feedback is encouraged during the Last Call period. All comments should
be provided to the Public Policy Mailing List. This Last Call will
expire on 9 November 2016. After Last Call, the AC will conduct their
Last Call review.
The full text is below and available at:
https://www.arin.net/policy/proposals/
The ARIN Policy Development Process is available at:
https://www.arin.net/policy/pdp.html
Regards,
Communications and Member Services
American Registry for Internet Numbers (ARIN)
Recommended Draft Policy ARIN-2016-2: Change timeframes for IPv4
requests to 24 months
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.
More information about the Info
mailing list