Draft Policy ARIN-2024-5

Rewrite of NRPM Section 4.4 Micro-Allocation

Status: Under Discussion
Shepherds: Chris Woodfield, William Herrin

Current Text (7 July 2025)

Problem Statement:

The current NRPM Section 4.4 language hasn’t aged well. As the ARIN 53 policy experience report demonstrated, 4.4 has also become difficult to implement by ARIN staff. The growth and use of Internet Exchanges have also changed. The overhaul seeks to improve technical soundness, respect the privilege of a dedicated pool and to more closely observe conservation principles using clear, minimum and enforceable requirements and underscoring the value of routability of allocated prefixes as required.

Policy Statement:

4.4 Critical Internet Infrastructure (CII) Allocations

ARIN will reserve a /15 equivalent of IPv4 address space for critical Internet infrastructure (CII) within the ARIN RIR service area. Allocations from this pool will be no smaller than a /24. Sparse allocation will be used whenever practical. CII includes Internet exchange points (IXPs), core DNS service providers (e.g. ICANN-sanctioned root and ccTLD operators) ARIN, and IANA.

ICANN-sanctioned gTLD operators may justify up to the equivalent of an IPv4 /23 block for each authorized gTLD, allocated from the free pool or received via transfer, but not from the above reservation. This limit of a /23 equivalent per gTLD does not apply to gTLD allocations made under previous policy.

Previous allocations under this policy must continue to meet the justification requirements of this policy.

Use of this policy for CII is voluntary; address holders that qualify for CII allocations may use allocations obtained via other means for CII resources. ARIN will publish a record of all addresses allocated under this section for research purposes.

4.4.1 Internet Exchange Allocations

Internet exchange operators must justify their need by providing a minimum of three initial participants not under common control connected to a shared, physical switching fabric to be used for the purpose of the exchange of data destined for and between the respective networks. This justification must include participant names, ASNs and contact information for each named participant. The applicant’s Internet exchange-affiliated ASNs are not eligible to be included in meeting the participant requirement.

Allocated addresses may be publicly reachable at the operator’s discretion but must be assigned only to resources directly related to the operation of the IXP.

4.4.2 TLD Allocations

TLD operators will provide justification of their need and certification of their status as currently active zone operators.

4.4.3 Additional Requests

A recipient may request up to a 24-month supply of IPv4 resources under this section. Requests for additional resources under this section will be evaluated using Section 4.2.4.1’s usage requirements.

In cases where fulfilling the request by expanding the existing allocation is not possible, a single prefix sized to accommodate both the prior and additional requested allocation will be issued to facilitate renumbering. The original allocation must be returned to ARIN within 12 months of the new allocation.

Timetable for Implementation: Immediate.

Staff and Legal Review (17 March 2025)

Staff Understanding: Staff understands that this draft policy seeks to address certain ambiguities in the current policy language and formalize existing ARIN practices.

Under current practice, Internet exchange points (IXPs) are typically allocated a /24. Requests for allocations larger than a /24 are evaluated based on other policies outlined in Section 4, including utilization requirements. The draft policy clarifies that IP addresses issued under Section 4.4 are intended exclusively for operational use directly related to the IXP and not for other purposes.

The policy resolves any ambiguity regarding the routing of IXP space and specifies that IP addresses allocated under this policy may be made publicly reachable at the operator’s discretion. The draft also establishes that a qualified recipient may request up to a 24-month supply of IPv4 addresses for the IXP. Any justifications for allocations beyond a /24 will be reviewed in accordance with the relevant policies in Section 4.

Staff notes the change of “the RIRs” to “ARIN” in the list of examples of critical infrastructure providers of the Internet. This aligns with ARIN’s current business practice.

In section 4.4, staff suggests removing “Only Section 8.2 transfers are allowed” since this text is a duplication of the transfer requirements in section 8.3. Transfers Between Specified Recipients Within the ARIN Region and Section 8.4. Inter-RIR Transfers to Specified Recipients. Both section 8.3 and 8.4 already state “Address resources from a reserved pool (including those designated in Section 4.4 and 4.10) are not eligible for transfer.”

In section 4.4, staff suggests replacing, “Addresses allocated from this pool may be revoked if they are no longer in use or not used for approved purposes,” with, “Previous allocations under this policy must continue to meet the justification requirements of this policy.” This is consistent with other policy requirements for reserved pools, such as section 4.10.

In section 4.4.3, staff recommends removing the / in front of “/24-month”.

In section 4.4.3, staff suggests referencing section 4.2.4.1 for utilization requirement instead of duplicating the text in the NRPM.

Implementable as Written?: Yes

Impact on ARIN Registry Operations and Services: None

Legal Review: No material legal issue

Implementation Timeframe Estimate: 3 Months

Implementation Requirements:

• Staff Training
• Updates to public documentation
• Updates to internal procedures and guidelines

Proposal/Draft Policy Text Assessed: 6 March 2025

History and Earlier Versions

Related Meetings