Recommended Draft Policy ARIN-2020-6
Allowance for IPv4 Allocation “Swap” Transactions via 8.3 Specified Transfers and 8.4 Inter-RIR Transfers
Status: Pending Implementation
Shepherds: Rob Seastrom, Amy Potter
Current Text (2 May 2022)
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.
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.
18.104.22.168- 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.
22.214.171.124.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.
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.
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.
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.
Timetable for Implementation: Immediate
Staff and Legal Review (7 December 2021)
ARIN-2020-6 would allow organizations, by request, to receive a smaller IPv4 block to renumber into prior to conducting a specified transfer under NRPM 8.3. or 8.4. Further, it seeks to prevent organizations from creating new Org IDs just to receive a smaller block so that the larger block may be transferred.
This Draft Policy would effectively codify the practice of obtaining and renumbering into a smaller block prior to conducting a transfer as a source, preventing the need for workarounds.
Staff recommends changing the verbiage of:
If the larger block is not transferred within one year of receipt of the smaller block, the smaller block will be ineligible for transfer under sections 8.3 and 8.4, and the organization will be ineligible to receive any further transfers under this policy.
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.
With regard to proposed 8.3 and 8.4 “Conditions on Source of the Transfer” text, there is potential ambiguity; staff suggests consideration of more direct language that states for transfers made to fulfill the requirements of 220.127.116.11 rather than a general reference to transfers in connection to other requirements.
Finally, it is notable that the officer attestation requirement stated in 18.104.22.168.1 (carried over from current 8.5.5 language) has been deprecated for IPv4 requests. Staff suggests removing this language, either as a part of this Draft Policy or in a future change for consideration.
Implementable as Written?: Yes
Impact on ARIN Registry Operations and Services:
In concept, the proposed policy does not have any material legal issue; however, legal suggests considering the clarifications proposed in Staff Understanding as it may avoid confusion in terms of interpretation and implementation.
Implementation Timeframe Estimate: 3 months
- Staff training
- Updates to public documentation
- Updates to internal procedures and guidelines
- Restricting waitlist space from use in these scenarios
Proposal/Draft Policy Text Assessed: 26 August 2021 Version
History and Earlier Versions
|Proposal||31 May 2020|
|Draft Policy||23 June 2020|
|Revised||26 August 2021|
|Revised||5 February 2022|
|Recommended||2 May 2022|
|Last Call||26 October 2022|
|Advanced to Board of Trustees||17 November 2022|
|Adopted||19 December 2022|
- 21 May 2020
- 18 June 2020
- 16 July 2020
- 20 August 2020
- 17 September 2020
- 15 October 2020
- 19 November 2020
- 17 December 2020
- 22 January 2021
- 18 February 2021
- 18 March 2021
- 15 April 2021
- 20 May 2021
- 17 June 2021
- 15 July 2021
- 19 August 2021
- 16 September 2021
- 21 October 2021
- 18 November 2021
- 16 December 2021
- 20 January 2022
- 25 February 2022
- 17 March 2022
- 27 April 2022
- 19 May 2022
- 16 June 2022
- 21 July 2022
- 18 August 2022
- 15 September 2022
- 21 October 2022
- 17 November 2022