This policy seems very sound. It is codifying an undocumented practice of ARIN staff and by putting it into policy it makes it clear to entities that were only browsing the policy that this is allowable, likely expanding (even modestly) the number of entities that would seek to swap a larger block for a smaller one and potentially get those underused blocks into circulation where they can be used. I supported this policy at the ARIN 50 meeting and continue to support it during last call.
I have a more general question related to the policy, and it may have been previously discussed and I’m unaware since I’m new: - The problem statement outlines a situation where some entities have created new orgs to receive the new block and work around the existing policy language. While this policy makes that workaround “no longer needed” - there are other reasons a resource holder may create an organization to receive a secondary block or get on the waitlist. What happens when those reasons are abusive in nature? (e.g., an org built to circumvent the policy in a more nefarious way.) More of an academic question to try to understand where the limits of policy and practical implementation intersect. Thank you - Doug — Douglas J. Camin [email protected]<mailto:[email protected]> On Oct 26, 2022, at 12:53 PM, ARIN <[email protected]<mailto:[email protected]>> wrote: On 21 October 2022, the ARIN Advisory Council (AC) sent the following Recommended Draft Policy to Last Call: * ARIN-2020-6: Allowance for IPv4 Allocation “Swap” Transactions via 8.3 Specified Transfers and 8.4 Inter-RIR Transfers Feedback is encouraged during the Last Call period. All comments should be provided to the Public Policy Mailing List. Last Call will expire on 9 November 2022. The Recommended Draft Policy text is below and available at: https://www.arin.net/participate/policy/drafts/2020_6/ The ARIN Policy Development Process is available at: https://www.arin.net/participate/policy/pdp/ Regards, Sean Hopkins Senior Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2020-6: Allowance for IPv4 Allocation “Swap” Transactions via 8.3 Specified Transfers and 8.4 Inter-RIR Transfers AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Draft Policy 2020-6 is fair, impartial, and technically sound. The intent of this policy is to eliminate confusion by codifying existing processes for downsizing IPv4 allocations and assignments within the written policy of the NRPM. It has the apparent support of the community. Problem Statement: Organizations wishing to “swap out” a larger block for a smaller one in the interest of avoiding deaggregation (as opposed to breaking up their existing block and transferring only a part of it) are forbidden by existing 8.3 policy from being the source of the transfer for their larger block after receiving a smaller one for 12 months after receiving the smaller block. In practice, ARIN staff has been allowing orgs to transfer out blocks after receiving smaller ones inside of the 12-month window, but many ARIN resource holders are not aware of this. Some resource holders have worked around the restriction by creating a new org to receive the smaller block, but this practice has implications on waitlist policy, as the new org is now technically eligible to apply for wait-list space while the original org cannot. Similar language is present in NRPM Section 8.4, as such, the practice should be sanctioned for those types of transfers as well. Policy Statement: Clarify the conditions under 8.3 and 8.4 that explicitly allows transfer of a larger block in exchange for a smaller one as part of a renumbering plan by making the following changes in 8.3, 8.4, and 8.5: 8.5.5. Block Size Organizations may qualify for the transfer of a larger initial block, or an additional block, by providing documentation to ARIN which details the use of at least 50% of the requested IPv4 block size within 24 months. An officer of the organization shall attest to the documentation provided to ARIN. Add: 8.5.5.1- Transfer for the Purpose of Renumbering Organizations with larger direct allocations or assignments than they require may receive transfer of a smaller block for the purpose of renumbering onto the smaller block if they transfer the entire larger block to a qualified recipient under section 8 within one year of receipt of transfer of the smaller block. If the larger block is not transferred within one year of receipt of the smaller block, the organization will be ineligible to receive any further transfers under this section until the larger block is transferred. 8.5.5.1.1 Smaller Block Size Organizations may qualify to receive transfer of a smaller block by providing documentation to ARIN which details the use of at least 50% of the smaller block size within 24 months. Current use of the larger block may be used to satisfy this criteria. Current text: 8.5.6. Efficient Utilization of Previous Blocks 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. Add: 8.5.6.1 Transfer for the Purpose of Renumbering Organizations receiving transfer of a smaller block under section 8.5.5.1 may deduct the larger block they are transferring to a qualified recipient when calculating their efficient utilization of previous blocks under section 8.5.6. Current Text: Sections 8.3 and 8.4, under “Conditions on Source Of the Transfer”: “The source entity must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request. This restriction does not include 8.2 transfers. Change to: With the exception of M&A transfers under section 8.2, the source entity must not have received a transfer, allocation, or assignment from ARIN for the past 12 months. This requirement may be waived by ARIN for transfers made in connection with a renumbering exercise designed to more efficiently utilize number resources under section 8.5.5.1. Timetable for Implementation: Immediate _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]<mailto:[email protected]>). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected]<mailto:[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.
