Plenty of IT managers request IPv4 space directly from ARIN without realizing there are two separate review frameworks at play: the needs assessment<\/strong> and the appropriate usage<\/strong> policy (section 4.4 of the Number Resource Policy Manual). Which one applies to you? Honestly, often both. And knowing how reviewers actually evaluate your paperwork can save you months of back-and-forth emails. This guide walks through both pathways and offers some practical advice on getting through each one.<\/p>\n The needs assessment is ARIN’s standard utilization-based review. Simple idea behind it: when you ask for address space directly\u2014whether an initial allocation, an additional allocation, or an assignment under certain policies\u2014ARIN staff check whether your demonstrated utilization actually justifies the size of the request. What do they look at?<\/p>\n Take NRPM 4.1 (basic allocations to ISPs) as an example. There, an 80% utilization justification is required. If your documentation shows you’re using 40% of your existing \/22, ARIN will generally approve only what your demonstrated need supports. Not necessarily the block size you asked for. That distinction trips people up more than you’d think.<\/p>\n Appropriate usage, defined in section 4.4 of the Number Resource Policy Manual, has nothing to do with utilization percentages. It’s a judgment about how<\/em> the addresses will be used. ARIN grants space only for legitimate, technically justified purposes, things like:<\/p>\n Under this kind of review, ARIN staff may dig into your network architecture and routing plans with detailed questions. There are strings attached, too. Space acquired under NRPM 4.4 carries a holding period\u2014typically 24 months\u2014during which it can’t be transferred without being returned first. And here’s the part that matters most: space assigned under 4.4 to end users is treated as non-portable<\/strong>. It stays with the organization it was assigned to, not with whoever happens to hold a service relationship.<\/p>\n Say an ISP requests a \/22. That single request might trigger a needs assessment (can you justify the size?) and<\/em> an appropriate usage review (will the space serve legitimate routing needs?). Requests tied to cloud or CDN environments get particular scrutiny under 4.4, by the way\u2014virtualized addressing can often be handled with private space or shared infrastructure instead.<\/p>\n Direct ARIN requests make sense when your growth is steady and well documented. But the free pool has been exhausted since 2015, and many organizations simply can’t afford to sit around waiting for their utilization to mature. The IPv4 transfer market offers another route: immediate acquisition of portable, transferred address blocks under ARIN’s M&A\/transfer policies (NRPM 8.2 and 8.3), with no utilization thresholds or holding periods beyond what policy already requires.<\/p>\n When pursuing transfers, the marketplace you work with matters. IP4 Market<\/em> offers a trusted platform for IPv4 transactions with verified sellers, competitive pricing, and full support for the ARIN transfer process\u2014pre-transfer due diligence, RIR paperwork handling, escrow-protected payments, the whole chain. For a lot of IT managers, buying a \/22 or \/23 on the market closes in weeks. A contested needs assessment can eat up months.<\/p>\n Most direct requests get evaluated for appropriate usage on top of the specific policy’s needs criteria, but the depth of review varies by request type and block size.<\/p>\n Not during the 24-month holding period, and end-user assignments under 4.4 are non-portable regardless. After the holding period, transferred allocations follow standard transfer policies.<\/p>\n Straightforward requests with complete documentation are often processed within one to two weeks. Complex ones with documentation gaps? Considerably longer.<\/p>\n<\/div>\n Knowing the difference between the needs assessment and appropriate usage policies puts you in a much better position to pick the right acquisition path\u2014direct request or market transfer\u2014and to prepare documentation that clears review without friction. Whether you’re putting together your first allocation request or weighing transfer options, plan your addressing strategy with both policies in mind.<\/p>\n\n
What Is the ARIN Needs Assessment?<\/h2>\n
\n
Understanding Appropriate Usage (NRPM 4.4)<\/h2>\n
\n
Key Differences at a Glance<\/h2>\n
\n\n
\n \nAspect<\/th>\n Needs Assessment<\/th>\n Appropriate Usage (4.4)<\/th>\n<\/tr>\n<\/thead>\n \n Primary question<\/td>\n How much space do you justify?<\/td>\n What will the space be used for?<\/td>\n<\/tr>\n \n Evaluation basis<\/td>\n Utilization data, growth projections<\/td>\n Technical justification of use case<\/td>\n<\/tr>\n \n Typical thresholds<\/td>\n 80% utilization of existing space<\/td>\n No percentage; purpose-based review<\/td>\n<\/tr>\n \n Portability<\/td>\n Per allocation policy<\/td>\n Non-portable for end users<\/td>\n<\/tr>\n \n Holding period<\/td>\n Per policy section<\/td>\n 24-month transfer restriction<\/td>\n<\/tr>\n \n Common requests<\/td>\n ISP additional allocations<\/td>\n End-user assignments, small blocks<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n Why Both Can Apply to the Same Request<\/h3>\n
Documentation Tips That Pass Review<\/h2>\n
\n
When the Wait Isn’t Worth It: The Transfer Market<\/h2>\n
Does every ARIN IPv4 request require an appropriate usage review?<\/h3>\n
Can I transfer space I received under NRPM 4.4?<\/h3>\n
How long does a needs assessment take?<\/h3>\n