Summary

  • ARIN-2022-1 names Chris Woodfield and Brian Jones as co-shepherds. For an organization running multiple discrete networks, each network may be assessed individually against the 80% IPv4 utilization threshold for an additional transfer; the organization must justify that the networks are genuinely discrete under section 4.5.
  • Each network faces the section 8.5.5 projection test, and any network seeking addresses faces section 8.5.6 utilization requirements. The rule caps transfers at existing ARIN IPv4 holdings and /16; the current NRPM also specifies a /16 equivalent over any six months. ARIN adopted the policy on 19 December 2022 and implemented it on 22 March 2023.

Put three genuinely separate networks on one corporate balance sheet. Network A has almost no space left. Network B still has room. A headquarters average can tell a tidy story about the company while Network A's engineers are hunting for addresses. The network, unfortunately, cannot route an average. Brian Jones and Chris Woodfield co-shepherded the ARIN-2022-1 clarification that lets an applicant show the use of a genuinely discrete network on its own terms when seeking an additional IPv4 transfer.

The old transfer qualification language in section 8.5.7 referred to 80% utilization of currently allocated space. The policy record says the treatment of organizations with multiple discrete networks was unclear. The new wording allows each discrete network to be assessed individually against that 80% threshold. It also sends the applicant to section 4.5 to show that the networks really are separate. That second step keeps a company from drawing a line around a convenient busy corner and calling it a network.

This is a test with several checkpoints, not a one-number trick. Every discrete network must satisfy the forward-looking projection rule in 8.5.5: documentation showing use of at least 50% of the requested block within 24 months. Any network for which addresses are requested must meet the previous-block utilization test in 8.5.6. The transfer amount cannot exceed the organization's existing ARIN IPv4 holdings or a /16. The current manual adds a /16 equivalent limit in any six-month period under this route.

ARIN's staff review described the change as putting existing practice into the written policy. That matters to an operator preparing a transfer request. A practice known to staff is a poor substitute for a rule an applicant can read before spending time on evidence and network plans. The review called for staff training, public documentation and internal procedure updates. The policy history records Board adoption on 19 December 2022 and implementation on 22 March 2023.

The question Jones helped sharpen was where ARIN should point the measuring tape. At a genuinely separate network, the 80% figure can describe the pressure the operator is trying to relieve. Across an entire company, the same figure may hide that pressure behind spare capacity somewhere else. The separateness proof and the transfer caps make the tape harder to move when an applicant dislikes the answer.