[arin-ppml] Draft Policy ARIN-2016-2 Change timeframes for IPv4 requests to 24 months

[Jason Schiller]

I'm not sure this impacts whether I support or not, but I
think it is good to have clear expectations.

How would this impact those already on the waiting list?

Would they stay in place, and the request grow to a 2
year need if they could provide justification for such?

Would they stay in place, and the request grow to a 2
year need automatically if they have transfer
pre-approval?

Would this only apply to those being added to the wait
list after the policy is implemented?

___Jason



On Tue, May 24, 2016 at 5:40 PM, ARIN <info at arin.net> wrote:

> Draft Policy ARIN-2016-2 Change timeframes for IPv4 requests to 24 months
>
> On 19 May the ARIN Advisory Council (AC) accepted "ARIN-prop-227 Change
> timeframes for all IPv4 requests to 24 months" as a Draft Policy.
>
> Draft Policy ARIN-2016-2 is below and can be found at:
> https://www.arin.net/policy/proposals/2016_2.html
>
> You are encouraged to discuss all Draft Policies on PPML. The AC will
> evaluate the discussion in order to assess the conformance of this draft
> policy with ARIN's Principles of Internet number resource policy as stated
> in the Policy Development Process (PDP). Specifically, these principles are:
>
>   * Enabling Fair and Impartial Number Resource Administration
>   * Technically Sound
>   * Supported by the Community
>
> The PDP 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)
>
>
>
> 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
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>



-- 
_______________________________________________________
Jason Schiller|NetOps|jschiller at google.com|571-266-0006
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20160525/5575545c/attachment.htm>