If you were approved for a /21 and haven’t gotten it yet due to scarcity, I support giving you a /22 when it becomes available, and after 90 days letting you apply for another /22 and receive that if/when it becomes available. That way, you will get some space sooner (as the /21s in front of you will each only get a /22), and can either get the rest via transfer or by waiting further.
Scott > On May 24, 2019, at 10:30 AM, Michael Williams <[email protected]> > wrote: > > Scott, > > Would you support those us who are already on the waitlist for a /21? > > Regards, > > Michael > > Sent from my iPhone > >> On 25 May 2019, at 03:27, Scott Leibrand <[email protected]> wrote: >> >> I support the AC’s recommendations, and consider them sufficient to resume >> waitlist allocations. >> >> I would also be fine with Michael’s #2 (non-transferability of waitlist >> space), but would consider that a new proposal. I don’t support a larger >> (/21) limit. >> >> Scott >> >>> On May 24, 2019, at 10:18 AM, Michael Williams >>> <[email protected]> wrote: >>> >>> Representing ARIN member organisation GLEXI-3, I disagree with the >>> language of this policy proposal. Specifically: >>> >>> 1) The maximum waitlist size should be a /21 >>> 2) The policy should require all IP allocations received from the >>> waitlist be returned to ARIN if they are no longer used. IP >>> allocations received via the waitlist should not be transferred, sold, >>> or otherwise acquired in any other fashion. >>> >>> Regards, >>> >>> Michael Williams >>> President/CEO Glexia, Inc >>> >>> Sent from my iPhone >>> >>>> On 25 May 2019, at 03:04, ARIN <[email protected]> wrote: >>>> >>>> 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 ([email protected]). >>>> Unsubscribe or manage your mailing list subscription at: >>>> https://lists.arin.net/mailman/listinfo/arin-ppml >>>> Please contact [email protected] if you experience any issues. >>> _______________________________________________ >>> ARIN-PPML >>> You are receiving this message because you are subscribed to >>> the ARIN Public Policy Mailing List ([email protected]). >>> Unsubscribe or manage your mailing list subscription at: >>> https://lists.arin.net/mailman/listinfo/arin-ppml >>> Please contact [email protected] if you experience any issues. _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
