Request IPv4 Addresses

Policy: NRPM 4.4

ARIN will make IPv4 micro-allocations to critical infrastructure providers of the Internet, including public exchange points, core DNS service providers (e.g., ICANN-sanctioned root and ccTLD operators) as well as the RIRs and IANA. These allocations will be no smaller than a /24. Multiple allocations may be granted in certain situations.

Policy: NRPM 4.10

As part of the community-adopted policy, a contiguous /10 IPv4 block has been set aside and dedicated to facilitate IPv6 deployment. Allocations and assignments from this block must be justified by immediate IPv6 deployment requirements. Examples of such needs include: IPv4 addresses for key dual stack DNS servers, and NAT-PT or NAT464 translators. ARIN staff will use their discretion when evaluating justifications.

A /24 will be allocated. In order to receive an allocation or assignment under this policy:

• the applicant may not have received resources under this policy in the preceding six months;
• previous allocations/assignments under this policy must continue to meet the justification requirements of this policy;
• previous allocations/assignments under this policy must meet the utilization requirements of end user assignments;
• the applicant must demonstrate that no other allocations or assignments will meet this need;
• on subsequent allocation under this policy, ARIN staff may require applicants to renumber out of previously allocated / assigned space under this policy in order to minimize non-contiguous allocations.

Policy: NRPM 4.2.2

All ISP organizations without direct assignments or allocations from ARIN qualify for an initial allocation of up to a /22, subject to ARIN’s minimum allocation size.

All ISP organizations without direct allocations, direct assignments, re-allocations or reassignments automatically qualify for a /24. These organizations are exempt from requirements of showing the efficient utilization of previously held IPv4 space. These organizations may qualify for a larger than a /24 by documenting how the requested allocation will be utilized within the request size specified in NRPM 4.2.4.3.

ISPs holding re-allocations and/or reassignments must show the efficient utilization of their resources consistent with the requirements in sections NRPM 4.2.3 and NRPM 4.2.4.

Documentation typically required for initial requests:

• List of CIDR prefixes/ranges assigned to dynamic pools with service type (e.g., DSL, wireless), city/region served, peak utilization percentage, and number of customers served for each pool
• List of IP addresses/subnets statically assigned to customers along with the corresponding customer name for each IP address/subnet
• List of IP addresses used for web hosting along with at least one customer domain name hosted on each IP address
• List of IP addresses/subnets assigned to internal equipment/infrastructure along with the corresponding hostname/device name for each IP address/subnet

Policy: NRPM 4.2.4)

• Demonstrate at least 50% of each of your allocations is efficiently used
• Demonstrate at least 80% of the sum of all allocations is efficiently used
• Provide reassignment information for all customer reassignments of eight or more contiguous IP addresses via SWIP or RWhois
• Provide reassignment information in text or spreadsheet format for all customer assignments less than 8 contiguous IP addresses
• List of CIDR prefixes/ranges assigned to dynamic pools with service type (e.g., DSL, wireless), city/region served, peak utilization percentage, and number of customers served for each pool
• List of IP addresses used for web hosting along with at least one customer domain name hosted on each IP address
• List of IP addresses/subnets assigned to internal equipment/infrastructure along with the corresponding hostname/device name for each IP address/subnet

Policy: NRPM 4.5

• Demonstrate your organization is a single entity and not a consortium of smaller independent entities
• Provide verification your organization has two or more discretely routed networks
• Provide detailed records on how you’ve allocated space to each discrete network, including the date of each allocation
• Demonstrate 50% utilization of both your last allocation and of all allocations (overall) OR demonstrate all free blocks are smaller than ARIN’s minimum allocation

Policy: NRPM 4.2.3.8

IP addresses reassigned by an ISP to an incumbent cable operator for use with Third Party Internet Access (TPIA) will be counted as fully used once they are assigned to equipment by the underlying cable carrier provided they meet the following requirements:

• Initial assignments to each piece of hardware represent the smallest subset reasonably required to deploy service to the customer base served by the hardware
• Additional assignments to each piece of hardware are made only when all previous assignments to that specific piece of hardware are at least 80% used and represent a 24-month supply
• IP allocations used through 4.2.3.8 are non-transferable via section 8.3 and section 8.4 for a period of 36 months. In the case of a section 8.2 transfer the IP assignment must be utilized for the same purpose or needs-based justification at a rate consistent with intended use.

Size: /24 minimum
Policy: NRPM 4.3.2

• End-user organizations without direct assignments or allocations from ARIN qualify for an initial assignment of ARIN’s minimum assignment size
• Provide data demonstrating at least a 50% utilization rate of the requested block within 24 months

Size: /24 minimum
Policy: NRPM 4.3.6.1)

Requirements:

• Provide data showing efficient utilization of at least 50% of each previous assignment
• Provide data showing at least 80% of the sum of all assignments is efficiently used
• Provide data demonstrating a 50% utilization rate of the requested block within 24 months

Documentation typically required for additional requests:

• A subnet mapping for each of your previous ARIN assignments listing each logical subnet created within the block with the following data for each subnet
  • A brief description of its purpose
  • The number of IP addresses currently used
• A subnet mapping showing each logical subnet you plan to create within the requested block with the following data for each subnet:
  • A brief description of the subnet’s purpose
  • Number of IP addresses that will be used within 12 months
  • Number of IP addresses projected to be used within 24 months