<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><span></span></div><div dir="ltr">The IPv4 transfer market is perfectly legitimate: ARIN policy allows for the transfer of addresses to specified recipients who need them (like you) from organizations who can afford to renumber out of underutilized space if you pay them a market rate to do so. <div><br></div><div>If your only objection to the transfer market is that you’d have to pay money (to avoid paying your upstreams), then I don’t think you have a valid objection to this policy proposal. Even under this proposal, you have a higher chance of getting a small block from ARIN, maybe even one that will meet your current needs, vs. the previous situation where everyone would hold out for /21s or larger that ARIN simply doesn’t have. And you can go acquire another /22 from the transfer market when you need it. </div><div><br></div><div>If you really think that ARIN should be preferentially subsidizing your business model, you could propose a policy proposal attempting to define what IPv4-based business models are so beneficial to the Internet community that they should be funded by the entire ARIN community, not just their customers/members. But no such argument has been made (or is possible IMO) for “all entities that need fewer than 2048 but more than 1024 IPv4 addresses”. The closest we’ve come is for IPv6, where the subsidy is tiny by comparison: <a href="https://www.arin.net/participate/policy/nrpm/#6-5-9-community-network-allocations">https://www.arin.net/participate/policy/nrpm/#6-5-9-community-network-allocations</a></div><div><br><div id="AppleMailSignature" dir="ltr"><div>Scott</div></div><div dir="ltr"><br>On May 12, 2019, at 8:55 AM, Christian Lefrançois <<a href="mailto:clefranc@diffusionfermont.ca">clefranc@diffusionfermont.ca</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><span>Hi all,</span><br><span>I agree with Michael Williams, I'm in the same situation, and on the waiting</span><br><span>list for more than a year. I need a /21, to finally be free of upstream</span><br><span>providers fees for IPv4 addresses (lease). I'll gladly give back all</span><br><span>resources to ARIN in the eventuality of end of business, or if I can manage</span><br><span>to switch completely to IPv6. Not interested with the IPv4 black market.</span><br><span></span><br><span>I'm in charge of a very small coop cable operator, my market is about 1900</span><br><span>customers, we're hooking members as fast as possible, will reach (and</span><br><span>surpass) /22 in a few months. So, in my perspective, /21 should be the</span><br><span>maximum.</span><br><span></span><br><span>Christian Lefrançois</span><br><span>Diffusion Fermont</span><br><span></span><br><span>-----Message d'origine-----</span><br><span>De : ARIN-PPML <<a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a>> De la part de</span><br><span><a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a></span><br><span>Envoyé : 10 mai 2019 18:33</span><br><span>À : <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a></span><br><span>Objet : ARIN-PPML Digest, Vol 167, Issue 80</span><br><span></span><br><span>Send ARIN-PPML mailing list submissions to</span><br><span> <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a></span><br><span></span><br><span>To subscribe or unsubscribe via the World Wide Web, visit</span><br><span> <a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br><span>or, via email, send a message with subject or body 'help' to</span><br><span> <a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a></span><br><span></span><br><span>You can reach the person managing the list at</span><br><span> <a href="mailto:arin-ppml-owner@arin.net">arin-ppml-owner@arin.net</a></span><br><span></span><br><span>When replying, please edit your Subject line so it is more specific than</span><br><span>"Re: Contents of ARIN-PPML digest..."</span><br><span></span><br><span></span><br><span>Today's Topics:</span><br><span></span><br><span> 1. Re: Fwd: Advisory Council Recommendation Regarding NRPM</span><br><span> 4.1.8. Unmet Requests (Scott Leibrand)</span><br><span></span><br><span></span><br><span>----------------------------------------------------------------------</span><br><span></span><br><span>Message: 1</span><br><span>Date: Fri, 10 May 2019 15:32:17 -0700</span><br><span>From: Scott Leibrand <<a href="mailto:scottleibrand@gmail.com">scottleibrand@gmail.com</a>></span><br><span>To: Michael Williams <<a href="mailto:michael.williams@glexia.com">michael.williams@glexia.com</a>></span><br><span>Cc: Kevin Blumberg <<a href="mailto:kevinb@thewire.ca">kevinb@thewire.ca</a>>, "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>"</span><br><span> <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>></span><br><span>Subject: Re: [arin-ppml] Fwd: Advisory Council Recommendation</span><br><span> Regarding NRPM 4.1.8. Unmet Requests</span><br><span>Message-ID:</span><br><span> <<a href="mailto:CAGkMwz5Bhp=SLVipZtx=fpu9ni2_uk_L3Tt1=5Lb3x5rNPQJtg@mail.gmail.com">CAGkMwz5Bhp=SLVipZtx=fpu9ni2_uk_L3Tt1=5Lb3x5rNPQJtg@mail.gmail.com</a>></span><br><span>Content-Type: text/plain; charset="utf-8"</span><br><span></span><br><span>There are organizations of all sizes with direct unmet needs for address</span><br><span>blocks of all sizes up to /16 or larger. The waitlist is *not* intended to</span><br><span>meet all such requests: it simply can't be done, because the free pool is</span><br><span>empty, and there is way more demand than supply at a price of ~$0. Rather,</span><br><span>the waitlist is intended to make sure that returned/reclaimed addresses are</span><br><span>not stuck at ARIN, but rather distributed in a way that serves a useful</span><br><span>purpose.</span><br><span></span><br><span>Organizations that need large blocks of address space should be going to the</span><br><span>market to acquire them, and transferring them to meet their justified need.</span><br><span>Some organizations that need smaller blocks of addresses, but not urgently,</span><br><span>can try to get them via the waitlist. But the more larger allocations we</span><br><span>allow from reclaimed space, the fewer such organizations can be served, and</span><br><span>the longer they'll need to wait. So it makes sense to me to have a</span><br><span>relatively stringent maximum wait list allocation, particularly since that</span><br><span>also reduces the financial reward to fraudulent actors and/or those</span><br><span>attempting to game the system.</span><br><span></span><br><span>So I support this policy, including the /22 maximum.</span><br><span></span><br><span>-Scott (representing only myself)</span><br><span></span><br><span>On Fri, May 10, 2019 at 3:19 PM Michael Williams <</span><br><span><a href="mailto:michael.williams@glexia.com">michael.williams@glexia.com</a>> wrote:</span><br><span></span><br><blockquote type="cite"><span>Representing ARIN member organisation GLEXI-3 *I do not support* the </span><br></blockquote><blockquote type="cite"><span>policy as written. Maximum wait list allocation should be at least a /21.</span><br></blockquote><blockquote type="cite"><span>We have a direct unmet need for a /21 right now.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>My argument is if an organisation receives an allocation from the wait </span><br></blockquote><blockquote type="cite"><span>list they should have to return that allocation directly to ARIN if </span><br></blockquote><blockquote type="cite"><span>not used. There should be no organisation to organisation transfer </span><br></blockquote><blockquote type="cite"><span>allowed for IP allocations received from the wait list. That?d </span><br></blockquote><blockquote type="cite"><span>eliminate all these crazy /16 allocation sales that we see now.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Regards,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Michael</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Sent from my iPhone</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On 10 May 2019, at 17:36, Kevin Blumberg <<a href="mailto:kevinb@thewire.ca">kevinb@thewire.ca</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>David,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I would rather see a limit or delay on the number of times an </span><br></blockquote><blockquote type="cite"><span>organization can go back to the waitlist than prevent organizations </span><br></blockquote><blockquote type="cite"><span>from getting any space from the wait list.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Would I be more supportive if the number was larger? I don?t believe </span><br></blockquote><blockquote type="cite"><span>that is the right control mechanism, so no.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Limiting the size to a /22 was a way of distributing fairly to as many </span><br></blockquote><blockquote type="cite"><span>organizations as possible and limiting the abuse vector.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Thanks,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Kevin</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>*From:* ARIN-PPML <<a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a>> *On Behalf Of *David </span><br></blockquote><blockquote type="cite"><span>Farmer</span><br></blockquote><blockquote type="cite"><span>*Sent:* Friday, May 10, 2019 4:44 PM</span><br></blockquote><blockquote type="cite"><span>*To:* Tom Pruitt <<a href="mailto:tpruitt@stratusnet.com">tpruitt@stratusnet.com</a>></span><br></blockquote><blockquote type="cite"><span>*Cc:* <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a></span><br></blockquote><blockquote type="cite"><span>*Subject:* Re: [arin-ppml] Fwd: Advisory Council Recommendation </span><br></blockquote><blockquote type="cite"><span>Regarding NRPM 4.1.8. Unmet Requests</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>If /20 is too small is their another size you would propose? a /19 or </span><br></blockquote><blockquote type="cite"><span>a</span><br></blockquote><blockquote type="cite"><span>/18 maybe? Do you have an argument for why that is the right number?</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>When the AC looked at this there was strong support for limiting the </span><br></blockquote><blockquote type="cite"><span>size of the organization that could qualify to ensure these resources </span><br></blockquote><blockquote type="cite"><span>went to smaller organizations. But there were varying opinions on what </span><br></blockquote><blockquote type="cite"><span>that size should be, /20 was just the option with the most support amongst</span><br></blockquote><span>the AC.</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>This formulation also provides a limit on how many times an </span><br></blockquote><blockquote type="cite"><span>organization can go back to the waiting list, allowing smaller </span><br></blockquote><blockquote type="cite"><span>organizations more times to return to the waiting list, while limiting </span><br></blockquote><blockquote type="cite"><span>lager organization to fewer times to return to the waiting list. And </span><br></blockquote><blockquote type="cite"><span>organizations that already have more than a /20 must go to the market.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>A /20 limit, gives a new organization (with no resources) the </span><br></blockquote><blockquote type="cite"><span>opportunity receive up to 5 allocations from the waiting list if they </span><br></blockquote><blockquote type="cite"><span>got a /22 each time.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>A /19 limit would allow a new ISP up to 9 allocations if they got a </span><br></blockquote><blockquote type="cite"><span>/22 each time.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>A /18 limit would allow a new ISP up to 17 allocations if they got a </span><br></blockquote><blockquote type="cite"><span>/22 each time.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Please realize the waiting list is primarily a mechanism to ensure </span><br></blockquote><blockquote type="cite"><span>resources are not stuck at ARIN, it should not be seen as a reliable </span><br></blockquote><blockquote type="cite"><span>means of obtaining resources.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Thanks</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On Fri, May 10, 2019 at 2:45 PM Tom Pruitt <<a href="mailto:tpruitt@stratusnet.com">tpruitt@stratusnet.com</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I do not support the new text, specifically the limit of a /20 per </span><br></blockquote><blockquote type="cite"><span>organization.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The limiting of an organization to an aggregate of a /20 is a huge </span><br></blockquote><blockquote type="cite"><span>hinderance of the ability of a smaller ISP to compete. A smaller ISP </span><br></blockquote><blockquote type="cite"><span>that can win business on service and cost could lose that same business</span><br></blockquote><span>due to</span><br><blockquote type="cite"><span>simply recouping the IPv4 costs. Large ISPs will often give the IPs away</span><br></blockquote><blockquote type="cite"><span>to win the business, and it costs them nothing as they received their IPV4</span><br></blockquote><blockquote type="cite"><span>space for free. Additionally, many smaller ISPs operate in outlying</span><br></blockquote><span>areas</span><br><blockquote type="cite"><span>where IPv6 adoption will likely be slow, which will also hinder their</span><br></blockquote><blockquote type="cite"><span>ability to push IPv6. I?m not sure at what point an organization</span><br></blockquote><span>becomes</span><br><blockquote type="cite"><span>?large?, but the smaller organizations are the ones that will be hurt </span><br></blockquote><blockquote type="cite"><span>by this limit.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>What happens to organizations that are currently on the wait list that </span><br></blockquote><blockquote type="cite"><span>have an aggregate of a /20 or more? Do they still get a /22. Some of</span><br></blockquote><blockquote type="cite"><span>those organizations have been on the list for over a year. Assuming they</span><br></blockquote><blockquote type="cite"><span>played by the rules and made decisions based on the assumption that </span><br></blockquote><blockquote type="cite"><span>they would get an allotment of IPv4 addresses, denying them any </span><br></blockquote><blockquote type="cite"><span>addresses after they have waited a year or more could be very </span><br></blockquote><blockquote type="cite"><span>detrimental to them. These policy changes and decisions affect the </span><br></blockquote><blockquote type="cite"><span>smaller entities greatly, and they need some clarity.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Thanks,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Tom Pruitt</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Network Engineer</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Stratus Networks</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span><image002.png></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>*From:* ARIN-PPML <<a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a>> *On Behalf Of *Andrew </span><br></blockquote><blockquote type="cite"><span>Dul</span><br></blockquote><blockquote type="cite"><span>*Sent:* Monday, May 6, 2019 4:09 PM</span><br></blockquote><blockquote type="cite"><span>*To:* <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a></span><br></blockquote><blockquote type="cite"><span>*Subject:* [arin-ppml] Fwd: Advisory Council Recommendation Regarding </span><br></blockquote><blockquote type="cite"><span>NRPM 4.1.8. Unmet Requests</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Hello,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I'd like to bring your attention to another issue that may have been </span><br></blockquote><blockquote type="cite"><span>lost in the flurry of other emails. We are currently in a 14 day </span><br></blockquote><blockquote type="cite"><span>feedback period for the AC's response to the Board's suspension of the</span><br></blockquote><span>wait-list.</span><br><blockquote type="cite"><span>Please note the following updated text for the wait-list. Your </span><br></blockquote><blockquote type="cite"><span>comments on this updated text are welcome.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Thanks,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Andrew</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>===</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>If no such block is available, the organization will be provided the </span><br></blockquote><blockquote type="cite"><span>option to be placed on a waiting list of pre-qualified recipients, </span><br></blockquote><blockquote type="cite"><span>listing both the block size, for which the organization is qualified, </span><br></blockquote><blockquote type="cite"><span>which in the case of the waiting list shall not be larger than a /22, </span><br></blockquote><blockquote type="cite"><span>and the smallest block size acceptable to the organization. An </span><br></blockquote><blockquote type="cite"><span>organization may not be added to the waiting list if it already holds </span><br></blockquote><blockquote type="cite"><span>IPv4 resources amounting in aggregate to more than a /20 of address </span><br></blockquote><blockquote type="cite"><span>space. Resources received via section 4.1.8 may not be transferred within</span><br></blockquote><span>60 months of the issuance date.</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>-------- Forwarded Message --------</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>*Subject: *</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>[arin-ppml] Advisory Council Recommendation Regarding NRPM 4.1.8. </span><br></blockquote><blockquote type="cite"><span>Unmet Requests</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>*Date: *</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Mon, 29 Apr 2019 11:16:31 -0400</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>*From: *</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>ARIN <<a href="mailto:info@arin.net">info@arin.net</a>> <<a href="mailto:info@arin.net">info@arin.net</a>></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>*To: *</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span><a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Subject:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>At their 16 January Meeting, the Board of Trustees suspended issuance </span><br></blockquote><blockquote type="cite"><span>of number resources under NRPM section 4.1.8.2. (Fulfilling Unmet </span><br></blockquote><blockquote type="cite"><span>Needs), and referred NRPM section 4.1.8 to the ARIN Advisory Council </span><br></blockquote><blockquote type="cite"><span>for their recommendation.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The Advisory Council has provided its recommendation, and per ARIN's </span><br></blockquote><blockquote type="cite"><span>Policy Development Process, the recommendation is hereby submitted to </span><br></blockquote><blockquote type="cite"><span>the Public Policy Mailing List for a community discussion period of 14 </span><br></blockquote><blockquote type="cite"><span>days, to conclude on 13 May.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Once completed, the Board of Trustees will review the AC?s </span><br></blockquote><blockquote type="cite"><span>recommendation and the PPML discussion.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The full text of the Advisory Council's recommendation is below.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Board of Trustees meeting minutes are available at:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span><a href="https://www.arin.net/about/welcome/board/meetings/2019_0116/">https://www.arin.net/about/welcome/board/meetings/2019_0116/</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>For more details on the Policy Development Process, visit:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span><a href="https://www.arin.net/participate/policy/pdp/">https://www.arin.net/participate/policy/pdp/</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Regards,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Sean Hopkins</span><br></blockquote><blockquote type="cite"><span>Policy Analyst</span><br></blockquote><blockquote type="cite"><span>American Registry for Internet Numbers (ARIN)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Advisory Council recommendation:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>In accordance with section 10.2 of the ARIN Policy Development </span><br></blockquote><blockquote type="cite"><span>Process, the ARIN Advisory Council recommends the following actions to </span><br></blockquote><blockquote type="cite"><span>the Board of Trustees in response to the Board?s suspension of part of </span><br></blockquote><blockquote type="cite"><span>the operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering</span><br></blockquote><span>Resource Policy Manual:</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Replace section 4.1.8 as follows, then reinstate the full operation of </span><br></blockquote><blockquote type="cite"><span>sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>4.1.8. Unmet Requests</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>In the event that ARIN does not have a contiguous block of addresses </span><br></blockquote><blockquote type="cite"><span>of sufficient size to fulfill a qualified request, ARIN will provide </span><br></blockquote><blockquote type="cite"><span>the requesting organization with the option to specify the smallest </span><br></blockquote><blockquote type="cite"><span>block size they?d be willing to accept, equal to or larger than the </span><br></blockquote><blockquote type="cite"><span>applicable minimum size specified elsewhere in ARIN policy. If such a </span><br></blockquote><blockquote type="cite"><span>smaller block is available, ARIN will fulfill the request with the </span><br></blockquote><blockquote type="cite"><span>largest single block available that fulfills the request.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>If no such block is available, the organization will be provided the </span><br></blockquote><blockquote type="cite"><span>option to be placed on a waiting list of pre-qualified recipients, </span><br></blockquote><blockquote type="cite"><span>listing both the block size, for which the organization is qualified, </span><br></blockquote><blockquote type="cite"><span>which in the case of the waiting list shall not be larger than a /22, </span><br></blockquote><blockquote type="cite"><span>and the smallest block size acceptable to the organization. An </span><br></blockquote><blockquote type="cite"><span>organization may not be added to the waiting list if it already holds </span><br></blockquote><blockquote type="cite"><span>IPv4 resources amounting in aggregate to more than a /20 of address </span><br></blockquote><blockquote type="cite"><span>space. Resources received via section 4.1.8 may not be transferred within</span><br></blockquote><span>60 months of the issuance date.</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Repeated requests, in a manner that would circumvent 4.1.6, are not</span><br></blockquote><blockquote type="cite"><span>allowed: an organization may only receive one allocation, assignment, </span><br></blockquote><blockquote type="cite"><span>or transfer every 3 months, but ARIN, at its sole discretion, may </span><br></blockquote><blockquote type="cite"><span>waive this requirement if the requester can document a change in </span><br></blockquote><blockquote type="cite"><span>circumstances since their last request that could not have been </span><br></blockquote><blockquote type="cite"><span>reasonably foreseen at the time of the original request, and which now</span><br></blockquote><span>justifies additional space.</span><br><blockquote type="cite"><span>Qualified requesters whose request cannot be immediately met will also </span><br></blockquote><blockquote type="cite"><span>be advised of the availability of the transfer mechanism in section </span><br></blockquote><blockquote type="cite"><span>8.3 as an alternative mechanism to obtain IPv4 addresses.</span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>ARIN-PPML</span><br></blockquote><blockquote type="cite"><span>You are receiving this message because you are subscribed to the ARIN </span><br></blockquote><blockquote type="cite"><span>Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</span><br></blockquote><blockquote type="cite"><span>Unsubscribe or manage your mailing list subscription at:</span><br></blockquote><blockquote type="cite"><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br></blockquote><blockquote type="cite"><span>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>ARIN-PPML</span><br></blockquote><blockquote type="cite"><span>You are receiving this message because you are subscribed to the ARIN </span><br></blockquote><blockquote type="cite"><span>Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</span><br></blockquote><blockquote type="cite"><span>Unsubscribe or manage your mailing list subscription at:</span><br></blockquote><blockquote type="cite"><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br></blockquote><blockquote type="cite"><span>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>--</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>===============================================</span><br></blockquote><blockquote type="cite"><span>David Farmer Email:<a href="mailto:farmer@umn.edu">farmer@umn.edu</a></span><br></blockquote><blockquote type="cite"><span>Networking & Telecommunication Services Office of Information </span><br></blockquote><blockquote type="cite"><span>Technology University of Minnesota</span><br></blockquote><blockquote type="cite"><span>2218 University Ave SE Phone: 612-626-0815</span><br></blockquote><blockquote type="cite"><span>Minneapolis, MN 55414-3029 Cell: 612-812-9952</span><br></blockquote><blockquote type="cite"><span>===============================================</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>ARIN-PPML</span><br></blockquote><blockquote type="cite"><span>You are receiving this message because you are subscribed to the ARIN </span><br></blockquote><blockquote type="cite"><span>Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</span><br></blockquote><blockquote type="cite"><span>Unsubscribe or manage your mailing list subscription at:</span><br></blockquote><blockquote type="cite"><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br></blockquote><blockquote type="cite"><span>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>ARIN-PPML</span><br></blockquote><blockquote type="cite"><span>You are receiving this message because you are subscribed to the ARIN </span><br></blockquote><blockquote type="cite"><span>Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</span><br></blockquote><blockquote type="cite"><span>Unsubscribe or manage your mailing list subscription at:</span><br></blockquote><blockquote type="cite"><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br></blockquote><blockquote type="cite"><span>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span>-------------- next part --------------</span><br><span>An HTML attachment was scrubbed...</span><br><span>URL:</span><br><span><<a href="https://lists.arin.net/pipermail/arin-ppml/attachments/20190510/fd735392/at">https://lists.arin.net/pipermail/arin-ppml/attachments/20190510/fd735392/at</a></span><br><span>tachment.html></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Subject: Digest Footer</span><br><span></span><br><span>_______________________________________________</span><br><span>ARIN-PPML mailing list</span><br><span><a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a></span><br><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>End of ARIN-PPML Digest, Vol 167, Issue 80</span><br><span>******************************************</span><br><span></span><br><span>_______________________________________________</span><br><span>ARIN-PPML</span><br><span>You are receiving this message because you are subscribed to</span><br><span>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</span><br><span>Unsubscribe or manage your mailing list subscription at:</span><br><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br><span>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</span><br></div></blockquote></div></div></body></html>