Summary

  • ARIN-2025-8 entered Last Call on 28 October, ending 11 November 2026. It would add “within the ARIN service area” to the sentence reserving IPv4 allocation for IPv6 deployment under NRPM §4.10.
  • ARIN staff say they already require addresses from that pool to be used inside the region. The draft instead expressly locates the IPv6 deployment. An Advisory Council shepherd has acknowledged the public objection that the two tests need not coincide.

The reserved pool is a bridge built from scarce IPv4. Section 4.10 of ARIN's policy manual holds a contiguous /10 for immediate IPv6 deployment needs, including dual-stack DNS servers and translation gateways; an eligible request normally receives a /24. The existing sentence says that IPv4 allocation is dedicated to facilitating IPv6 deployment. It does not put a geographic adjective on either the IPv4 equipment or the IPv6 result.

Staff do put a border on applications. At ARIN 55, ARIN's Chief Experience Officer said requests for the special §4.4 and §4.10 pools to be used beyond the service region are currently refused. The proposal's own problem statement agrees that §4.10 lacks an express territorial restriction beyond general §9, and its staff review says the new sentence would codify existing processing practice without changing outcomes. This is how an unwritten interpretation becomes a written rule.

But read the proposed sentence literally. It would dedicate the IPv4 allocation to “facilitate IPv6 deployment within the ARIN service area.” That describes the location of the deployment being helped. The rule staff describe concerns where the IPv4 addresses are operated. A gateway outside the region serving a rollout inside it and a gateway inside the region serving users outside it could receive different answers depending on which location ARIN actually means to test. The draft provides no test for such mixed cases.

The ambiguity is already on ARIN's own Public Policy Mailing List. A participant asked whether facilitating deployment within the service area necessarily means the IPv4 allocation is used there. Kaitlyn Pellak, an Advisory Council shepherd, replied that staff have historically interpreted §4.10 strictly in-region and the proposal seeks to make that practice explicit. She acknowledged the wording concern and invited a clearer formulation. The official proposal page later says follow-ups brought no replacement wording. Last Call has arrived with the grammatical question intact.

General §9 does not solve it by itself. That provision allows out-of-region use of ARIN-registered resources when a real and substantial connection and same-type in-region use are shown, including a /22 IPv4 threshold. Staff say special §4.10 applications follow a narrower in-region practice. The proposal would put that narrower practice into the manual. It should identify the operational object of the restriction before becoming binding text: where are the allocated IPv4 addresses used, where is the transition equipment run, or where does the IPv6 deployment take effect?

The draft also says the new restriction is not intended for §4.10 allocations made before implementation. Its implementation timetable says “Immediate,” while the staff review estimates three months for training and documentation. Those details require an effective-date instruction, especially for a holder planning a network move. One sentence can both formalize an old practice and create a new dispute over its wording.

ARIN-2025-8 remains a proposed policy until the policy process and Board act. The Last Call ends 11 November. The missing fact is a published eligibility test for a mixed-location deployment: which side of the service-area line must the IPv4 allocation occupy for staff to approve the request?

Sources