+1 I also support /22 and believe that's a reasonable size for a waiting list, specially for a newcomer.
If anyone has official numbers of how much currentlly comes into the waiting list I am open to discuss a different size. Fernando On Fri, 24 May 2019, 15:51 Scott Leibrand, <[email protected]> wrote: > What rationale is there for a /21 limit vs. /22, other than “I need more > than one /22, and think my needs for a second /22 are more important than > others’ needs for a first”? > > Scott > > > On May 24, 2019, at 11:42 AM, Christian Lefrançois < > [email protected]> wrote: > > > > I disagree with /22 limit, should be /21, the IPs received from the > waiting > > list should return to the waiting list in case of business cease, even if > > CORP-A swallow CORP-B assets, all allocations received from the waiting > list > > should be annually reviewed and reentry on the waiting list should also > be > > annually. > > > > Sorry for my bad English. > > > > Christian Lefrançois > > Diffusion Fermont > > > > -----Message d'origine----- > > De : ARIN-PPML <[email protected]> De la part de > > [email protected] > > Envoyé : 24 mai 2019 13:56 > > À : [email protected] > > Objet : ARIN-PPML Digest, Vol 167, Issue 153 > > > > Send ARIN-PPML mailing list submissions to > > [email protected] > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.arin.net/mailman/listinfo/arin-ppml > > or, via email, send a message with subject or body 'help' to > > [email protected] > > > > You can reach the person managing the list at > > [email protected] > > > > When replying, please edit your Subject line so it is more specific than > > "Re: Contents of ARIN-PPML digest..." > > > > > > Today's Topics: > > > > 1. Re: Revised - Advisory Council Recommendation Regarding NRPM > > 4.1.8. Unmet Requests (Leif Sawyer) > > 2. Re: Revised - Advisory Council Recommendation RegardingNRPM > > 4.1.8. Unmet Requests (=?utf-8?B?SGF5ZWUgQm9raGFyaQ==?=) > > 3. Re: Revised - Advisory Council Recommendation Regarding NRPM > > 4.1.8. Unmet Requests (David Farmer) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Fri, 24 May 2019 17:32:13 +0000 > > From: Leif Sawyer <[email protected]> > > To: Michael Williams <[email protected]> > > Cc: "[email protected]" <[email protected]> > > Subject: Re: [arin-ppml] Revised - Advisory Council Recommendation > > Regarding NRPM 4.1.8. Unmet Requests > > Message-ID: > > <[email protected]> > > Content-Type: text/plain; charset="windows-1252" > > > > Michael, just to be clear: > > > > You don't support the policy allowing for the transfer of IPs received by > > waitlist, for any reason? > > > > Including the purchase and transfer of all assets by Corp-A from Corp-B > , > > regardless of current utilization of the IPs? > > > > -- > > Leif Sawyer > > Enterprise Security Architect > > Enterprise Security Office > > GCI > > > > > > ________________________________ > > From: ARIN-PPML [[email protected]] on behalf of Michael > Williams > > [[email protected]] > > Sent: Friday, May 24, 2019 9:18 AM > > To: ARIN > > Cc: [email protected] > > Subject: Re: [arin-ppml] Revised - Advisory Council Recommendation > Regarding > > NRPM 4.1.8. Unmet Requests > > > > [EXTERNAL EMAIL - CAUTION: Do not open unexpected attachments or links.] > > > > 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<http://4.1.8.1> and 4.1.8.2<http://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<http://4.1.8.1> and > > 4.1.8.2<http://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<http://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<http://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<https://lists.arin.n > >> et/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< > https://lists.arin.net/mai > > lman/listinfo/arin-ppml> > > Please contact [email protected] if you experience any issues. > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > > < > https://lists.arin.net/pipermail/arin-ppml/attachments/20190524/ed56e729/at > > tachment-0001.html> > > > > ------------------------------ > > > > Message: 2 > > Date: Fri, 24 May 2019 13:40:59 -0400 > > From: "=?utf-8?B?SGF5ZWUgQm9raGFyaQ==?=" <[email protected]> > > To: "=?utf-8?B?U2NvdHQgTGVpYnJhbmQ=?=" <[email protected]>, > > "=?utf-8?B?TWljaGFlbCBXaWxsaWFtcw==?=" < > [email protected]> > > Cc: "=?utf-8?B?YXJpbi1wcG1s?=" <[email protected]> > > Subject: Re: [arin-ppml] Revised - Advisory Council Recommendation > > RegardingNRPM 4.1.8. Unmet Requests > > Message-ID: <[email protected]> > > Content-Type: text/plain; charset="utf-8" > > > > I support non-transferability of waitlist space and limited, > > > > However Transfer from one entity to other should be allowed, > > > > -When a merger is taken place > > -A company goes out of business and trustee takes over > > > > I see while we are discussing limiting the waiting list to /21 or /22 > there > > are entries being added in waiting list for blocks bigger then /21, what > > will happen to these waiting list entries, in other words what is the > plan > > for existing entries in the waiting list. > > > > > > Thanks > > > > Hayee > > > > > >> 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. > > > > Notice > > This communication is intended to be received only by the individual[s] > or > > entity[s] to whom or to which it is addressed, and contains information > > which is confidential, privileged and subject to copyright. Any > unauthorized > > use, copying, review or disclosure is prohibited. Please notify the > sender > > immediately if you have received this communication in error [by calling > > collect, if necessary] so that we can arrange for its return at our > expense. > > Thank you in advance for your anticipated assistance and cooperation. > > > > > > Cette communication est destin?e uniquement ? la personne ou ? la > personne > > morale ? qui elle est adress?e. Elle contient de l'information > > confidentielle, prot?g?e par le secret professionnel et sujette ? des > droits > > d'auteurs. Toute utilisation, reproduction, consultation ou divulgation > non > > autoris?es sont interdites. Nous vous prions d'aviser imm?diatement > > l'exp?diteur si vous avez re?u cette communication par erreur (en > appelant ? > > frais vir?s, si n?cessaire), afin que nous puissions prendre des > > dispositions pour en assurer le renvoi ? nos frais. Nous vous remercions > ? > > l'avance de votre coop?ration. > > > > > > ------------------------------ > > > > Message: 3 > > Date: Fri, 24 May 2019 12:55:41 -0500 > > From: David Farmer <[email protected]> > > To: Michael Williams <[email protected]> > > Cc: ARIN <[email protected]>, ARIN-PPML List <[email protected]> > > Subject: Re: [arin-ppml] Revised - Advisory Council Recommendation > > Regarding NRPM 4.1.8. Unmet Requests > > Message-ID: > > <CAN-Dau2Tp6JotWr_V7pVFE90QwG8= > [email protected]> > > Content-Type: text/plain; charset="utf-8" > > > > On Fri, May 24, 2019 at 12:18 PM 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 > >> > > > > Personally looking at the data I could be convinced /21 is OK from a > fraud > > prevention perspective. However, there seems to be a strong preference > for > > aligning with other RIRs on /22. That seems like as good of an argument > as I > > have seen for what is mostly an arbitrary choice. Do you have a better > > argument for why it should be /21? Unfortunately, the arguments for /21 > that > > I remember have mostly boiled down to, "that is what I have been planning > > for and need." I need more on why /21 is the right number over /22. > > > > > >> 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. > >> > > > > I can't support the elimination of M&A and reorganization transfers, ARIN > > should not be an impediment to how anyone organizes or reorganizes their > > business. There is an argument that completely eliminating transfers just > > incents people to go around the registry, reducing its accuracy, and > after > > 3 to 5 years, this shouldn't matter too much anyway, at least I hope > that is > > the case. > > > > Thanks. > > -- > > =============================================== > > David Farmer Email:[email protected] > > Networking & Telecommunication Services > > Office of Information Technology > > University of Minnesota > > 2218 University Ave SE Phone: 612-626-0815 > > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > > =============================================== > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > > < > https://lists.arin.net/pipermail/arin-ppml/attachments/20190524/0c39be5b/at > > tachment.html> > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > ARIN-PPML mailing list > > [email protected] > > https://lists.arin.net/mailman/listinfo/arin-ppml > > > > > > ------------------------------ > > > > End of ARIN-PPML Digest, Vol 167, Issue 153 > > ******************************************* > > > > _______________________________________________ > > 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.
