ARIN-prop-227 Change timeframes for all 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.
ARIN-prop-227 Change timeframes for all IPv4 requests to 24 months
Proposal Originator: Owen DeLong
Date: 20 April 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
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.