ARIN policy: ISP vs end user rules

Activating 2,000 IPv6 addresses within 12 months defines the minimum utilization threshold for end user justification according to ARIN data. The central thesis asserts that organizational classification as either an ISP/LIR or end user dictates the specific policy constraints applied to direct allocation requests. Lisa Liedel, Director of Registration Services at ARIN, clarifies that this distinction relies entirely on whether the organization serves external customers or manages internal infrastructure.

ARIN policy treats ISPs and LIRs as interchangeable entities that primarily assign address space to network service users. An organization requesting resources for internal tools must still apply under ISP rules if their primary business model involves customer service. Policy constraints prevent simultaneous review as both entity types due to conflicting utilization requirements.

The mechanics of direct allocation mean all IPv4 and IPv6 addresses issued since January 1, 2022, fall under this category regardless of entity type. Understanding these definitions prevents rejection during the vetting process managed by Registration Services. Strategic alignment with the correct policy framework ensures organizations meet the necessary justification standards for their IP requests.

Defining the Distinction Between LIRs and End Users in ARIN Policy

Defining LIR as ISP in ARIN NRPM Policy

A Local Internet Registry (LIR) functions as an entity that assigns address space to network service users. This technical definition equates the LIR role directly with an Internet Service Provider (ISP) within the ARIN region. The Number Resource Policy Manual specifies that these registries generally serve end users or other ISPs. Draft Policy ARIN-2025-1 seeks to remove ambiguity regarding this classification in the policy text.

Operators must distinguish this status from end-user allocations based on reassignment intent. An organization qualifies as an ISP/LIR if it justifies resources through anticipated customer use rather than internal infrastructure needs. This distinction dictates the applicable utilization metrics for resource requests. Historical policy reports noted that the manual previously lacked adequate definitions for this separation. The binary classification model prevents an organization from holding simultaneous ISP and end-user statuses for the same resources.

Entities providing connectivity must apply under ISP policies even for their own infrastructure. This requirement eliminates hybrid categorization to preserve the integrity of address scarcity management. The distinction between ISP/LIR and end user remains critical when requesting IP addresses due to different policy requirements.

Classifying Organizations by Customer Use Justification

Classification hinges on whether anticipated customer use drives the IP address request.

An entity functions as an ISP/LIR if it assigns space to network service users. Conversely, an organization acts as an end user when using addresses strictly for employees and internal systems. This binary distinction dictates the applicable policy framework regardless of the requesting entity's commercial nature. Even an ISP/LIR requiring resources solely for its own backbone must apply under ISP policies. The regulatory structure prevents simultaneous review as both an ISP and an end user due to conflicting utilization requirements.

Operational justification relies on meeting specific numerical thresholds within a 12-month window. End users must demonstrate active use of 2,000 IPv6 addresses to secure allocation. Alternatively, a contiguous network supporting a minimum of 13 active sites satisfies the resource justification criteria, or an organization can demonstrate active use of a minimum of 200 /64 subnets. These metrics ensure efficient distribution of the global pool. Some entities in other regions bypass direct membership by accessing Provider Independent space through a sponsoring LIR. This arrangement allows smaller networks to obtain necessary resources without full LIR status.

The primary implication involves the rigidity of the initial classification decision. Policy constraints do not enable having organizations reviewed as both an ISP and an end user at the same time. Operators should audit their reassignment plans before submission. Accurate self-identification prevents administrative delays and ensures alignment with ARIN's resource management goals.

Policy Constraints on Dual ISP and End User Status

ARIN policy prevents simultaneous review as both an ISP and an end user due to conflicting utilization metrics. The registry mandates that an ISP/LIR applying for its own backbone capacity must still process the request under ISP policies, not end-user guidelines. This strict binary classification ensures that utilization requirements remain consistent across the entire holdings of a single entity. While an end user justifies space via employee count, an ISP must demonstrate efficient customer reassignment. Specifically, a Local Internet Registry is permitted to reassign up to a /48 block per Point of Presence to its customers. In addition to per-PoP assignments, an LIR may reassign an additional /48 block globally for its own infrastructure needs. Any entity not clearly fitting specific end-user categories defaults to LIR/ISP treatment, triggering more rigorous auditing.

Mechanics of Direct Allocation and Utilization Thresholds

Direct Allocation Mechanics and WHOIS Classification

Since 1 January 2022, ARIN issues all IPv4 resources as direct allocations, yet policy distinctions between provider and consumer roles remain rigid. This administrative shift did not alter the fundamental utilization requirements that govern address space distribution. Operators must still justify requests based on whether addresses support customer reassignments or internal infrastructure. The technical enforcement of this status appears in WHOIS data through specific allocation type flags. Blocks assigned for Local Internet Registries appear as Allocated PA, signifying Provider Aggregatable space intended for further distribution to clients. Conversely, space assigned to organizations for their own operational use is classified as end-user space, denoting Provider Independent status that prohibits sub-allocation. This binary classification in the registry database acts as a hard constraint on network topology; an entity holding end-user space cannot legally reassign blocks to third parties without violating policy. While the fee structure now treats all recipients as direct allocatees, the structural distinction between LIR and end user persists in the reassignment capabilities granted to each. Misclassifying an organization during this direct allocation process creates immediate compliance gaps when future expansion requires customer-facing subnets. Operators must verify their intended use case against these registry markers before finalizing network design.

Applying the 200 /64 Subnet and 13-Site Contiguous Network Metrics

Technical validation for IPv6 requests requires proving active use of 200 /64 subnets or a contiguous network spanning 13 active sites within a 12-month period. Organizations must select one of these distinct paths to satisfy registration criteria without ambiguity. The ARIN Quick Guide codifies these specific numerical justifications as the baseline for resource approval. This distinction prevents inflation of utilization requirements through vertical scaling alone. The following table contrasts the two primary metrics for end-user justification:

The rigid 12-month window creates a planning tension where operators must deploy infrastructure before securing the very addresses needed for that deployment. InterLIR assists networks in modeling these deployment scenarios to ensure compliance before submission. Strategic planning around these fixed numbers avoids the administrative burden of re-application. Precise adherence to these metrics simplifies the audit process for all parties involved. Network architects should map their active sites against this checklist early in the design phase. Compliance depends on accurate forecasting rather than retrospective justification of existing traffic.

Enforcement Risks of Assigned Resource Sub-allocation Limits

The WHOIS database technically enforces policy by marking "Assigned" resources as not sub-allocatable, preventing end users from distributing blocks to third parties. This constraint creates immediate operational friction for organizations misclassified as end users that later attempt to offer services. While LIRs enjoy flexibility to reassign up to a /48 block per Point of Presence, end users face a hard ceiling on distribution.

Operators attempting to bypass this by requesting excessive space for "future growth" risk audit findings if customer reassignments appear without prior LIR qualification. The registry validates these claims against utilization requirements. If an organization classified as an end user is found to be reassigning space to third parties, they may be required to re-apply as an ISP/LIR, potentially altering their fee structure and reporting obligations. Unlike the flexible Sponsoring LIR models found in other regions, the local framework demands strict adherence to the initial classification. Unauthorized reassignment violates policy constraints. The technical attribute "Assigned" restricts further division of blocks to third parties. This binary enforcement ensures efficient IPv4 resource distribution but offers no middle ground for hybrid business models.

Strategic Classification for Organizational IP Requests

ISP versus End User Classification by Justification

Classification hinges strictly on whether anticipated customer use or internal employee needs drive the address request. An organization acts as an ISP/LIR if it assigns space to service users, whereas it functions as an end user when using addresses for its own infrastructure. This distinction remains binding even if an ISP requests space for internal backbone elements; policy mandates applying under ISP rules regardless of the immediate technical application. A hard constraint prevents simultaneous review as both entity types due to conflicting utilization requirements. Operators cannot split their legal status to bypass stricter reassignment reporting expected of providers. Justifying space via employee counts while planning customer reassignments creates immediate procedural friction. The ARIN blog clarifies that this binary choice dictates the entire validation path. Misclassification risks future audit failures when WHOIS data reveals unauthorized sub-allocation attempts. End users marked as "Assigned" lack the technical flag permitting further distribution to third parties. Organizations aiming to redistribute addresses must secure ISP/LIR status initially, as retroactive conversion complicates direct allocation histories. Selecting the wrong category forces a complete re-application rather than a simple status update.

Applying IPv6 Utilization Thresholds for End Users

Organizations must validate internal infrastructure needs against the strict 2,000 IPv6 addresses active use metric within a 12-month window. This quantitative baseline, codified in the ARIN Quick Guide, serves as the primary filter for distinguishing end-user requests from provider allocations. Applicants failing this volume test may alternatively demonstrate eligibility by documenting 200 /64 subnets or a contiguous network spanning 13 active sites. These discrete thresholds prevent entities serving external customers from masking as end users to avoid stricter reassignment reporting obligations. A common operational error involves counting device density rather than distinct logical locations, which inflates perceived readiness without meeting the site count requirement.

Validation Steps for Direct Allocation Requests

Correcting a misclassified IP request begins by confirming whether anticipated customer use drives the need for address space. Organizations functioning as ISPs must apply under ISP policy even when requesting blocks strictly for internal backbone infrastructure. This legal definition overrides the immediate technical application, a nuance detailed in recent policy interpretations. Failure to recognize this distinction triggers processing delays because utilization requirements differ fundamentally between provider and end-user categories.

All resources issued since 1 January 2022 are direct allocations, yet the fee structure and validation logic still bifurcate based on this organizational type. A critical operational tension exists here: an entity cannot split its account to satisfy both sets of metrics simultaneously. Attempting to justify a portion of space via customer demand and another via internal headcount violates the single-status constraint. The registry system cannot process mixed-justification requests under one organizational ID. Applicants must select the classification that governs the majority of their strategy or restructure their legal holding entities accordingly. Registry staff review each submission against these fixed parameters to maintain data integrity across the region.

Executing the IP Address Application and Justification Process

Implementation: Direct Allocation Mechanics and Fee Schedule Changes

Applying for IP addresses as an ISP requires submitting justification based on anticipated customer use rather than internal employee counts. Since 1 January 2022, the fee schedule mandates that all IPv4 and IPv6 resources issue as direct allocations, yet this administrative shift preserves the strict policy boundary between providers and end users. Operators must recognize that requesting space for internal backbone infrastructure still necessitates an ISP/LIR application status if the organization serves external customers.

1. Identify whether the address space supports customer reassignment or strictly internal operations.
2. Prepare utilization data demonstrating demand from service users rather than device density.
3. Submit the request through the portal, acknowledging that fee structures differ for registry functions supporting third-party management.

The distinction dictates not eligibility but the entire validation workflow, as policy constraints prevent simultaneous review under both classifications.

End users paying for direct allocation maintenance face a different cost obligation structure than ISPs supporting reassignment capabilities. If an organization classified as an end user is found to be reassigning space to third parties, they may be required to re-apply as an ISP/LIR, potentially altering their fee structure and reporting obligations.

Contacting the ARIN Registration Services Help Desk.

For assistance with questions about ARIN resources and services, including applying for IP addresses, organizations can contact the Registration Services Help Desk at +1.703.227.0660. The help desk supports these inquiries Monday through Friday from 7:00 AM to 7:00 PM ET, providing a window for real-time resolution of complex justification scenarios. Lisa Liedel's responsibilities include management of registration requests for Internet number resources (IPv4, IPv6, and ASNs) and maintenance of registration. Applicants often misunderstand that requesting space for internal backbone components still requires an ISP/LIR application status if the organization serves external customers, a nuance that demands precise verbal articulation during the call.

1. Call the provided number during Eastern Time business hours to reach a live analyst.
2. Declare whether the request supports customer reassignment or strictly internal employee devices.
3. Accept that policy constraints prevent simultaneous review as both an ISP and an end user.

The operational risk lies in vague descriptions; clearly distinguishing between customer-facing and internal usage ensures the correct policy framework is applied from the start. Resource analysts cannot guess the intent behind a request, so the caller must explicitly define the utilization requirements governing their specific case type. Failing to distinguish these categories during the initial contact can complicate the application, as the supporting evidence required for an ISP differs fundamentally from end-user proofs.

This direct engagement model eliminates ambiguity early, forcing operators to align their technical needs with the correct policy framework before the submission begins.

Validating IPv6 Utilization Metrics for End User Requests

Execute a pre-submission audit against the strict 12-month utilization window before filing justification data. Applicants must document active use of 2,000 addresses, 200 /64 subnets, or 13 active sites to satisfy the ARIN Quick Guide thresholds.

1. Tally assigned addresses to verify the 2,000 unit minimum within the set period.
2. Count deployed subnets to confirm the 200 /64 subnet alternative metric.
3. Map physical topology to prove the 13 active site contiguous network requirement.
4. Ensure counts reflect active utilization rather than anticipated growth or customer reassignment plans.

Operators frequently miscalculate eligibility by including reserved blocks intended for future expansion. Policy mandates actual deployment, rendering forward-looking projections invalid for initial end user classification. This constraint forces organizations to right-size requests based on immediate capacity rather than theoretical maximums.

InterLIR recommends verifying these counts against live WHOIS data to prevent classification errors. Organizations that do not meet these specific numerical baselines for direct allocation may need to seek space from an upstream ISP/LIR instead. Submitting applications without proven need based on these metrics can result in delays or rejection.