[arin-ppml] LAST CALL - Recommended Draft Policy ARIN-2020-6: Allowance for IPv4 Allocation “Swap” Transactions via 8.3 Specified Transfers and 8.4 Inter-RIR Transfers
owen at delong.com
Wed Oct 26 22:46:24 EDT 2022
> 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.
> 126.96.36.199- 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.
It’s unclear to what extent “ineligible to receive any further transfers under this section” refers. This section could refer to section 188.8.131.52, or any or all of its parents and/or just that lineage or all of the subordinates of any level of parent section.
As such, I propose replacing “this section” with “section 8”.
IMHO, there should also be a process by which ARIN can reclaim at least one of the two blocks in question after (e.g. 3 years of failing to transfer the larger block). That’s more than ample notice for the organization which failed to meet its obligations to address any customer impact given that they originally agreed to a 1-year time horizon.
> 184.108.40.206.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.
This appears to allow an organization with a larger block than it needs to transfer a smaller block based solely on utilizing a portion of their larger block that is more than 50% of the desired smaller block, yet does not require any renumbering. If I read this correctly, it would
allow an organization using 25% of their existing /16 to transfer in up to a /17 of additional space essentially no questions asked and without committing to renumbering.
If that is the case, then I strongly oppose as written. If I am misreading this provision, then I look forward to a public education. ;-)
I realize that since this paragraph is subordinate to 220.127.116.11 one might argue that the requirement to renumber is implicit, but if that’s the case, I fail to understand how 18.104.22.168.1 is significantly different from 22.214.171.124 and/or why it is necessary.
> 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.
> 126.96.36.199 Transfer for the Purpose of Renumbering
> Organizations receiving transfer of a smaller block under section 188.8.131.52 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.
For clarity, this paragraph should explicitly state that that deduction is only valid during the 1 year grace period allowed prior to transferring said block.
> 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 184.108.40.206.
I object to the use of the word may here and propose “shall”. ARIN should not be blocking entities from complying with their obligations under 220.127.116.11, so there is no reason to make this at the discretion of ARIN staff.
> Timetable for Implementation: Immediate
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net <mailto:ARIN-PPML at arin.net>).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml <https://lists.arin.net/mailman/listinfo/arin-ppml>
> Please contact info at arin.net <mailto:info at arin.net> if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ARIN-PPML