[arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

Fri Jun 7 11:53:28 EDT 2019

Hi Carlton,

Another way of looking at it is; imagine a new organization is formed in the year 2019+N.  For what value of N do you think it is beneficial to have a small amount of IPv4 addresses available from ARIN?  Because the value of N goes down as the rate of waiting list assignments goes up (shorter waits for subsequent assignment bump out the new organizations).  The same effect occurs with fulfilling larger assignments.  By keeping assignments small, and assigning them few and far in between, we maximize N, which means new entities forming and coming online over the coming years (decades hopefully) will have access to at least some IPv4 address space.

So back to your point; if 5 years is an eternity, is that enough time for entities to move to IPv6 and keep some IPv4 available to new entities that arise in the next eternity and the one after that?

My two cents.

Matthew

From: ARIN-PPML <arin-ppml-bounces at arin.net> On Behalf Of Carlton Samuels
Sent: June 7, 2019 08:43 AM
To: John Curran <jcurran at arin.net>
Cc: ARIN-PPML List <arin-ppml at arin.net>
Subject: Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

Is my reading that the wait period is 5 years correct? For if so and in the context of Internet time, that sounds like millennium speak! I should think it is way too long.

-Carlton

==============================
Carlton A Samuels
Mobile: 876-818-1799
Strategy, Process, Governance, Assessment & Turnaround
=============================

On Thu, Jun 6, 2019 at 12:21 PM John Curran <jcurran at arin.net<mailto:jcurran at arin.net>> wrote:
Folks -

We’ve had excellent discussion of various options for the revised “Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy change – some of which is likely to have to further informed folks initial views on the matter (as well as on future policy proposals in this area), but at this time it is fairly important that we receive focused feedback on the revised policy text as written, with due consideration to the discussion that has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”  ?

(“Yes” obviously indicative that you’d like ARIN to proceed with its adoption and resumption of wait list issuance under its revised guidelines, and
 “No” being indicative that you’d rather have the suspension of wait list issuance continue unless/until some other policy change in this area reaches consensus.)

2.  If you are not supportive of ARIN making the change specified in the revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”,
is there any modification to the proposed policy change that would enable you to support it?

I would ask that PPML participants take a moment to consider the proposed policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers

Begin forwarded message:

From: ARIN <info at arin.net<mailto:info at arin.net>>
Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests
Date: 24 May 2019 at 1:04:58 PM EDT
To: <arin-ppml at arin.net<mailto:arin-ppml at arin.net>>

At their 16 May meeting, the Advisory Council revised their recommendation regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing List for a second community discussion period of 14 days, to conclude on 7 June.

Once completed, the Board of Trustees will review the AC’s recommendation and the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

Sean Hopkins
Policy Analyst
American Registry for Internet Numbers (ARIN)

Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff and was approved for further community consultation at the ARIN AC meeting on May 16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the ARIN Advisory Council recommends the following actions to the Board of Trustees in response to the Board’s suspension of part of the operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:

Replace section 4.1.8 et. seq. as follows, then reinstate the full operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.

4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an organization may qualify for at any one time is a /22. Organizations will be able to elect a smaller block size than they qualify for down to a /24. Only organizations holding a /20 or less of IPv4 address space may apply and be approved. Address space distributed from the waitlist will not be eligible for transfer for a period of 60 months. This policy will be applied to all future distributions from the waitlist to include those currently listed.

Repeated requests, in a manner that would circumvent 4.1.6, are not allowed: an organization currently on the waitlist must wait 90 days after receiving a distribution from the waitlist before applying for additional space. ARIN, at its sole discretion, may waive this requirement if the requester can document a change in circumstances since their last request that could not have been reasonably foreseen at the time of the original request, and which now justifies additional space. Qualified requesters whose request will also be advised of the availability of the transfer mechanism in section 8.3 as an alternative mechanism to obtain IPv4 addresses.

4.1.8.1 Sequencing

The position of each qualified request on the waiting list will be determined by the date it was approved. Each organization may have one approved request on the waiting list at a time.

4.1.8.2 Fulfillment

ARIN will fulfill requests on a first-approved basis, subject to the size of each available address block as address blocks become available for distribution. A timely review of the original request may be conducted by ARIN staff. Requests will not be partially filled. Any requests met through a transfer will be considered fulfilled and removed from the waiting list.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net<mailto:ARIN-PPML at arin.net>).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact info at arin.net<mailto:info at arin.net> if you experience any issues.

_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net<mailto:ARIN-PPML at arin.net>).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact info at arin.net<mailto:info at arin.net> if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20190607/95420fba/attachment.htm>