<div dir="ltr">Hi all, <br><br>Resurrecting this after many weeks. We've reviewed all the comments and have netted out with the following. Thoughts?<br><br><b>Add the ****text between asterisks**** to 8.1</b><br><br><i>8.1. Principles<br>Number resources are nontransferable and are not assignable to any other organization unless ARIN has expressly and in writing approved a request for transfer. ARIN is tasked with making prudent decisions on whether to approve the transfer of number resources. ****<span style="background-color:rgb(255,255,0)">Only IPv4 addresses or ASNs are transferable, except where explicitly permitted otherwise. The different number resource types are considered separately and independently for the purposes of transfers.****</span><br></i><br><b>Then we'd dispense with the "IPv4 addresses and/or ASN resources" awkwardness and just say "IPv4 addresses or ASNs." The updated proposal language would look like this:<br><br>In section 8.3, <br>Replace<br></b><br><i>“In addition to transfers under section 8.2, IPv4 number resources and ASNs may be transferred according to the following conditions.”<br></i><br><b>with</b><br><i><br><span style="background-color:rgb(255,255,0)">“In addition to transfers under section 8.2, IPv4 numbers or ASNs may be transferred according to the following conditions.”</span></i><br> <br><b>Replace</b><br><br><i>“The source entity must be the current registered holder of the IPv4 address resources, and not be involved in any dispute as to the status of those resources.”</i><br><br>with<br><br><span style="background-color:rgb(255,255,0)"><i>“The source entity must be the current registered holder of the IPv4 addresses or ASNs and not be involved in any dispute as to the status of those resources.”</i></span><br><br> <br><br><b>In Section 8.4:</b><br><br><b>Replace</b><br><br><i>“Inter-regional transfers of IPv4 number resources and ASNs may take place only via RIRs who agree to the transfer and share reciprocal, compatible needs-based policies.”<br></i><br><b>with</b><br><br><span style="background-color:rgb(255,255,0)"><i>“Inter-regional transfers of IPv4 addresses or ASNs may take place only via RIRs who agree to the transfer and share reciprocal, compatible needs-based policies.”</i></span><br><br><b>Replace</b><br><br><i>“The source entity must be the current rights holder of the IPv4 address resources recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources.”</i><br><br><b>with</b><br><br><span style="background-color:rgb(255,255,0)">“The source entity must be the current rights holder of the IPv4 addresses or ASN recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources.”</span><br><br><b>In Section 8.5.6:<br></b><br><b>Replace</b><br><br><i>“Organizations with direct assignments or allocations from ARIN must have efficiently utilized at least 50% of their cumulative IPv4 address blocks in order to receive additional space. This includes all space reassigned to their customers.”</i><br><br><b>with</b><br><span style="background-color:rgb(255,255,0)"><br>“Organizations with direct assignments or allocations from ARIN must have efficiently utilized at least 50% of their cumulative IPv4 address blocks in order to receive additional IPv4 space. This includes all IPv4 space reassigned to their customers.”</span><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 21, 2021 at 9:19 PM Owen DeLong via ARIN-PPML <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;"><br><div><br><blockquote type="cite"><div>On Oct 21, 2021, at 20:05 , David Farmer via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>> wrote:</div><br><div><div><div dir="auto">The problem I have with that is it strongly implies IPv6 isn’t ever transferable, even though it is through section 8.2.</div></div></div></blockquote><div><br></div>If IPv6 becomes more generally transferrable, then section 2 can be updated along side the other policy changes required.</div><div><br></div><div>In terms of 8.2, IPv6 transferability under 8.2 is exceptional compared to other transfers, so I think it’s OK to note that</div><div>exception as part of the language update in 8.2</div><div><br><blockquote type="cite"><div><div><div dir="auto"><br></div><div dir="auto">A few thoughts;</div><div dir="auto"><br></div><div dir="auto">1. Adding that resource types are considered “separately and independently”, should eliminate the need to use the awkward “and/or” construction, and we should be able to simply use “IPv4 addresses or ASNs” without confusion following that statement. I’d prefer to do this is section 8.1 instead of section 2. So it isn’t disconnected from section 8 where it is important to understand.</div></div></div></blockquote><div><br></div>Personally, I don’t see a significant difference between inclusive or (and/or) and phrasing elsewhere that clarifies that the or is inclusive followed by use of the normally exclusive or.</div><div><br></div><div>I do think that the global definition in section 2 for “transferable resources” (or if you have a better choice of terms, go for it, but some term that identifies IPv4 + ASNs and not IPv6 currently).</div><div><br></div><div>I still like making the clarification that each resource type is considered separately for each transfer.</div><div><br><blockquote type="cite"><div><div><div dir="auto">2. Rather than defining “transferable resources” in section 2, how about saying “only IPv4 addresses or ASNs are transferable, except where explicitly noted otherwise,” again in section 8.1, for similar reason as above. Then add “including IPv6” in the heading to section 8.2, making it clear that IPv6 is included for section 8.2 transfers, and only section 8.2.</div></div></div></blockquote><div><br></div>How about section 2 defining “Transferable resources" as “IPv4 addresses and ASNs, except where specifically noted otherwise” and then proceeding apace?</div><div><br><blockquote type="cite"><div><div><div dir="auto">3. In sections 8.3 and 8.4, either just simply say “number resources”, with the above clearly scoping that to IPv4 addresses or ASNs. Or, say “<span> IPv4 addresses or ASNs”, without</span> the awkward “and/or” construction. I prefer using just “number resources”, as I think it is simpler and cleaner.</div></div></div></blockquote><div><br></div>I don’t find and/or any more awkward than or, so I’m not convinced that’s really an issue. I don’t like just using “number resources” in a place where we don’t intend IPv6 because it’s not the plain language meaning of the term.</div><div><br><blockquote type="cite"><div><div><div dir="auto">4. Where a clause only applies to “IPv4 addresses”, such as for block sizing, and the wait list, make sure they are explicitly scoped to IPv4.</div></div></div></blockquote><div><br></div>I think that’s already generally the case.</div><div><br></div><div>Owen</div><div><br><blockquote type="cite"><div><div><div dir="auto"><br></div><div dir="auto">Thanks.</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 21, 2021 at 21:06 Chris Woodfield <<a href="mailto:chris@semihuman.com" target="_blank">chris@semihuman.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">I think Joe’s got a good suggestion that I would support - define “transferable number resources” as IPv4 addresses and ASNs in Section 2, and go from there.<div><br></div><div>-C<br><div><br><blockquote type="cite"><div>On Oct 21, 2021, at 5:39 PM, Martin Hannigan <<a href="mailto:hannigan@gmail.com" target="_blank">hannigan@gmail.com</a>> wrote:</div><br><div><br><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div class="gmail_quote" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div dir="ltr" class="gmail_attr" style="font-family:Helvetica">On Thu, Oct 21, 2021 at 14:53 Chris Woodfield <<a href="mailto:chris@semihuman.com" style="font-family:Helvetica" target="_blank">chris@semihuman.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:Helvetica"><div style="font-family:Helvetica">I support this edit, for same reasons others have mentioned. <div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">If I’m recalling yesterday’s presentation correctly, it was ARIN Staff and Legal, not the AC, that determined that this language could not be implemented an editorial change, so that’s not up for debate here.<br><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">One possible adjustment that I’d like to suggest is that the term “IPv4 and/or ASN resources” seems a bit awkward, given how many times it appears in the section. Perhaps we could add a new section that incorporates David’s suggested language, but also handles the clarification of the definition of number resources in a single place, scoped to Section 8.</div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">So, a new Section 8.1.1, which I’d propose would be named “Definitions”, could read as follows:</div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica"><span style="white-space:pre-wrap;font-family:Helvetica"> </span>All references to “number resources" in this section, unless stated otherwise, refer to IPv4 addresses and/or ASN resources. </div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica"><div class="gmail_quote" style="font-family:Helvetica"><div style="font-family:Helvetica"><div style="font-family:Helvetica"><div style="font-family:Helvetica"><div style="font-family:Helvetica"><div dir="ltr" style="font-family:Helvetica"><span style="white-space:pre-wrap;font-family:Helvetica"> </span>When number resources of multiple types, including IPv6 resources, are transferred, each resource type is considered separately and independently, both for any conditions on their transferability and the application of any restrictions following a transfer.</div></div></div></div></div></div></div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">Following this, the other edits to Section 8 in the proposal can simply be changed to “number resources” to suit.</div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">Opinions?</div></div></div><div style="font-family:Helvetica"><div style="font-family:Helvetica"><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">-C</div><div style="font-family:Helvetica"></div></div></div></blockquote><div dir="auto" style="font-family:Helvetica"><br></div><div dir="auto" style="font-family:Helvetica">We’d be better off using defined terms. Easier to construct, but end up being document global. </div><div dir="auto" style="font-family:Helvetica"><br></div><div dir="auto" style="font-family:Helvetica">Warm regards,<br></div><div dir="auto" style="font-family:Helvetica"><br></div><div dir="auto" style="font-family:Helvetica">-M<</div><div dir="auto" style="font-family:Helvetica"><br></div><div dir="auto" style="font-family:Helvetica"><br></div><div dir="auto" style="font-family:Helvetica"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:Helvetica"><div style="font-family:Helvetica"><div style="font-family:Helvetica"><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica"><br><blockquote type="cite" style="font-family:Helvetica"><div style="font-family:Helvetica">On Oct 21, 2021, at 11:23 AM, Martin Hannigan <<a href="mailto:hannigan@gmail.com" style="font-family:Helvetica" target="_blank">hannigan@gmail.com</a>> wrote:</div><br><div style="font-family:Helvetica"><div dir="ltr" style="font-family:Helvetica"><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">I agree with Owen re: the editorial nature of the changes. However, I support it moving forward. I don't support the Farmer suggestion. That is possibly a material change that should undergo the rigors of "the process" on its own.</div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">Warm regards,</div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">-M<</div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica"><br></div></div><br><div class="gmail_quote" style="font-family:Helvetica"><div dir="ltr" class="gmail_attr" style="font-family:Helvetica">On Thu, Oct 21, 2021 at 11:33 AM Owen DeLong via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" style="font-family:Helvetica" target="_blank">arin-ppml@arin.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:Helvetica"><div style="font-family:Helvetica">I support this amendment.<div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">Owen</div><div style="font-family:Helvetica"><br><div style="font-family:Helvetica"><br><blockquote type="cite" style="font-family:Helvetica"><div style="font-family:Helvetica">On Oct 20, 2021, at 12:45 , David Farmer via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" style="font-family:Helvetica" target="_blank">arin-ppml@arin.net</a>> wrote:</div><br><div style="font-family:Helvetica"><div dir="ltr" style="font-family:Helvetica">I support this proposal as currently written.<span style="font-family:Helvetica"> </span><br><br>However, regarding Kevin Blumberg's comment at the ARIN 48 discussion of this policy earlier today; How about adding a paragraph like the following to section 8.1, Principles;<br><br><blockquote style="margin:0px 0px 0px 40px;border:medium none;padding:0px;font-family:Helvetica">When number resources of multiple types, IPv4, IPv6, and/or ASNs, are transferred, each resource type is considered separately and independently, both for any conditions on their transferability and the application of any restrictions following a transfer.</blockquote><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">Something like this added to Section 8.1, Principles, along with the already proposed changes should eliminate any possibility of confusion in this regard.</div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">Thanks</div><div style="font-family:Helvetica"><br><div class="gmail_quote" style="font-family:Helvetica"><div dir="ltr" class="gmail_attr" style="font-family:Helvetica">On Tue, Aug 24, 2021 at 7:52 AM ARIN <<a href="mailto:info@arin.net" style="font-family:Helvetica" target="_blank">info@arin.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:Helvetica"><div lang="EN-US" style="font-family:Helvetica"><div style="font-family:Helvetica"><p class="MsoNormal" style="font-family:Helvetica">On 19 August 2021, the ARIN Advisory Council (AC) accepted "ARIN-prop-299: Clarifications to Sections 8.3, 8.4 and 8.5.6" as a Draft Policy.</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Draft Policy ARIN-2021-4 is below and can be found at:</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica"><a href="https://www.arin.net/participate/policy/drafts/2021_4/" style="font-family:Helvetica" target="_blank">https://www.arin.net/participate/policy/drafts/2021_4/</a></p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">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:</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">* Enabling Fair and Impartial Number Resource Administration</p><p class="MsoNormal" style="font-family:Helvetica">* Technically Sound</p><p class="MsoNormal" style="font-family:Helvetica">* Supported by the Community</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">The PDP can be found at:</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica"><a href="https://www.arin.net/participate/policy/pdp/" style="font-family:Helvetica" target="_blank">https://www.arin.net/participate/policy/pdp/</a></p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Draft Policies and Proposals under discussion can be found at:<span style="font-family:Helvetica"> </span></p><p class="MsoNormal" style="font-family:Helvetica"><a href="https://www.arin.net/participate/policy/drafts/" style="font-family:Helvetica" target="_blank">https://www.arin.net/participate/policy/drafts/</a></p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Regards,</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Sean Hopkins</p><p class="MsoNormal" style="font-family:Helvetica">Senior Policy Analyst</p><p class="MsoNormal" style="font-family:Helvetica">American Registry for Internet Numbers (ARIN)</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica"> <br></div><p class="MsoNormal" style="font-family:Helvetica">Draft Policy ARIN-2021-4: Clarifications to Sections 8.3, 8.4 and 8.5.6 <span style="font-family:Helvetica"> </span></p><div style="font-family:Helvetica"> <br></div><p class="MsoNormal" style="font-family:Helvetica">Problem Statement:</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">The current language in Sections 8.3 and 8.4 is not clear regarding ASN-only transactions as well as the term “number resources”. The current language in Section 8.5.7 is not clear with regard to additional IPv4 space.</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Policy statement:</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">In Section 8.3:</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Replace</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">“In addition to transfers under section 8.2, IPv4 numbers resources and ASNs may be transferred according to the following conditions.”</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">with</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">“In addition to transfers under section 8.2, IPv4 address and/or ASN resources may be transferred according to the following conditions.”</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Replace</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">“The source entity must be the current registered holder of the IPv4 address resources, and not be involved in any dispute as to the status of those resources.”</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">with</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">“The source entity must be the current registered holder of the IPv4 address and/or ASN resources, and not be involved in any dispute as to the status of those resources.”</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">In Section 8.4:</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Replace</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">“Inter-regional transfers of IPv4 number resources and ASNs may take place only via RIRs who agree to the transfer and share reciprocal, compatible needs-based policies.”</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">with</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">“Inter-regional transfers of IPv4 addresses and/or ASN resources may take place only via RIRs who agree to the transfer and share reciprocal, compatible needs-based policies.”</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Replace</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">“The source entity must be the current rights holder of the IPv4 address resources recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources.”</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">with</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">“The source entity must be the current rights holder of the IPv4 address and/or ASN resources recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources.”</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">In Section 8.5.6:</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Replace</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">“Organizations with direct assignments or allocations from ARIN must have efficiently utilized at least 50% of their cumulative IPv4 address blocks in order to receive additional space. This includes all space reassigned to their customers.”</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">with</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">“Organizations with direct assignments or allocations from ARIN must have efficiently utilized at least 50% of their cumulative IPv4 address blocks in order to receive additional IPv4 space. This includes all IPv4 space reassigned to their customers.”</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Comments:</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">These changes were originally included in ARIN-edit-2021-1. Staff and Legal review of ARIN-edit-2021-1 on June 14, 2021 indicated that some changes were not editorial in nature. The editorial changes went forward in ARIN-edit-2021-1 and the non-editorial changes are included here.</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p><p class="MsoNormal" style="font-family:Helvetica">Timetable for implementation: Immediate</p><p class="MsoNormal" style="font-family:Helvetica"><u style="font-family:Helvetica"></u> <u style="font-family:Helvetica"></u></p></div></div>_______________________________________________<br>ARIN-PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" style="font-family:Helvetica" target="_blank">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" style="font-family:Helvetica" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact<span style="font-family:Helvetica"> </span><a href="mailto:info@arin.net" style="font-family:Helvetica" target="_blank">info@arin.net</a><span style="font-family:Helvetica"> </span>if you experience any issues.<br></blockquote></div><br clear="all"><div style="font-family:Helvetica"><br></div>--<span style="font-family:Helvetica"> </span><br><div dir="ltr" style="font-family:Helvetica">===============================================<br>David Farmer <span style="font-family:Helvetica"> </span><a href="mailto:Email%3Afarmer@umn.edu" style="font-family:Helvetica" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <span style="font-family:Helvetica"> </span><br><a href="https://www.google.com/maps/search/2218+University+Ave+SE?entry=gmail&source=g" style="font-family:Helvetica" target="_blank">2218 University Ave SE</a> <span style="font-family:Helvetica"> </span>Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>===============================================<span style="font-family:Helvetica"> </span></div></div></div>_______________________________________________<br>ARIN-PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" style="font-family:Helvetica" target="_blank">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" style="font-family:Helvetica" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact<span style="font-family:Helvetica"> </span><a href="mailto:info@arin.net" style="font-family:Helvetica" target="_blank">info@arin.net</a><span style="font-family:Helvetica"> </span>if you experience any issues.<br></div></blockquote></div><br></div></div>_______________________________________________<br>ARIN-PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" style="font-family:Helvetica" target="_blank">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" style="font-family:Helvetica" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact<span style="font-family:Helvetica"> </span><a href="mailto:info@arin.net" style="font-family:Helvetica" target="_blank">info@arin.net</a><span style="font-family:Helvetica"> </span>if you experience any issues.<br></blockquote></div>_______________________________________________<br>ARIN-PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" style="font-family:Helvetica" target="_blank">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" style="font-family:Helvetica" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact<span style="font-family:Helvetica"> </span><a href="mailto:info@arin.net" style="font-family:Helvetica" target="_blank">info@arin.net</a><span style="font-family:Helvetica"> </span>if you experience any issues.</div></blockquote></div></div></div></blockquote></div></div></blockquote></div><br></div></div>_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div></div>
</div>-- <br><div dir="ltr">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div>
_______________________________________________<br>ARIN-PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br></div></blockquote></div><br></div>_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div>