Summary
- ARIN's waiting list converts IPv4 scarcity from a posted market price into a bundle of hidden prices: time in queue, uncertainty about returned supply, eligibility limits, documentation work, fee readiness, block-size fit and the opportunity cost of not buying or leasing elsewhere.
- The list is defensible as a residual fairness mechanism because it limits access to smaller or less-endowed organizations, caps the maximum qualifying aggregate at a modest size, restricts immediate resale and uses returned or revoked inventory rather than pretending that abundance remains.
- The same rules create strategic behavior. Applicants must decide when to file, what minimum block they will accept, whether to wait, whether to enter the transfer market, and how much administrative capacity to spend before the business case is urgent.
- ARIN's legitimacy depends on keeping the queue narrow, auditable and modest: it should ration a residual pool without turning waiting-list relief into industrial policy, transfer suppression or discretionary capital allocation.
The queue is the price ARIN does not charge
When ARIN announced in September 2015 that its free IPv4 pool had been depleted, the old allocation bargain ended but the demand did not. Networks still needed public IPv4 addresses for customers, servers, remote access, security appliances, payment systems, public-sector sites, compatibility with older equipment and the long tail of software that assumes IPv4 reachability. What changed was not the usefulness of the address. What changed was the institution through which a qualified operator could hope to obtain it.
The waiting list became one of ARIN's post-exhaustion instruments. It does not recreate the free pool. It does not set a market price. It does not promise that a qualified network can obtain the block it wants when it wants it. It is a queue for approved requests, fed by addresses that become available, typically through revocations for non-payment and other returns to inventory. That makes it more than an administrative list. It is a rationing mechanism for scarce infrastructure capital.
Rationing is never free. If a price is not allowed to clear the market, some other currency does the clearing. Sometimes the currency is political influence, personal connection, eligibility scoring, paperwork, lottery chance or the ability to stand physically in line. In ARIN's case, the currency is time plus qualification. The applicant pays by proving eligibility, selecting an acceptable block range, maintaining fee standing, monitoring the list, absorbing uncertainty, and deciding whether to wait or buy elsewhere. The price has not disappeared. It has moved from the invoice to the calendar.
This hidden price is easiest to miss because the waiting list can look morally cleaner than the market. No applicant is bidding against a richer cloud platform. No broker is collecting a spread. No legacy holder is monetizing historical inventory. A smaller operator may have a route to addresses that would be painful to buy in the open market. Those are real virtues. But institutional economics starts where moral contrast ends. The queue gives one applicant a scarce input at administrative terms while others wait, lease, purchase, redesign or lose business. That is an allocation of value, even if no auctioneer calls it one.
The correct question is not whether ARIN should have a waiting list. A residual public queue can be legitimate when a registry receives returned or revoked space and must distribute it without favour. The question is what the queue costs, who pays that cost, and whether those costs match the policy's stated purpose. If the cost falls on speculative applicants, the queue disciplines gaming. If the cost falls on small networks that lack administrative capacity, the queue becomes regressive while sounding fair. If the cost is uncertain enough that rational applicants buy addresses earlier than necessary, the queue can raise market demand rather than relieve it.
That is the economics of waiting-list rationing. It is not a story about benevolence or obstruction. It is a story about a registry converting one scarce thing, IPv4 addresses, into several other scarce things: calendar priority, eligibility status, staff attention, documentation capacity and planning certainty.
The waiting list turns scarcity into a timetable
ARIN's public waiting-list material is useful because it describes the mechanics plainly. A request that meets current policy requirements may be placed on the IPv4 Waiting List for the approved block size. The qualifying organization must state the smallest block it would accept. Available addresses are then used to fill requests on a first-approved basis, subject to the size of each block ARIN has available. The list is chronological, but ARIN warns that chronological position is not identical to fill order because fulfillment depends on the order, size and quantity of blocks that enter inventory.
That caveat is the whole political economy of the queue. A conventional line suggests that the person ahead is served first and the person behind is served later. ARIN's waiting list is more complicated because supply arrives in irregular shapes. A /24 that becomes available may satisfy one request and be useless for another. A larger request may remain visible while smaller requests behind it can be matched to available inventory. The queue is therefore not only a sequence. It is a matching problem.
This matters because time becomes uncertain capital. A small operator may know that it has been approved. It may know what size it requested. It may know how much it is willing to accept. It may even know where it sits in a public status table. What it cannot know with certainty is when a suitable block will return to ARIN, whether the returned block will match its approved size, whether other requests will fit more easily, whether its own minimum acceptable size is strategically too high, or whether accepting a smaller block will solve enough of its business problem to justify leaving the line.
Before exhaustion, timing risk was largely a matter of processing. After exhaustion, timing risk is the allocation device. The applicant does not merely wait while ARIN performs an ordinary review. It waits for an uncertain supply event. That event depends on non-payment revocations, returns, recovered space, administrative timing and inventory composition. The registry can publish the queue; it cannot manufacture the blocks.
The timetable also changes internal planning. An operator considering a new access network, hosting node, regional expansion or enterprise service cannot write "ARIN waiting list" into a launch plan as if it were a supplier purchase order. It must create contingencies: lease addresses for the first customers, buy a smaller transfer block, redesign around private addressing, postpone marketing, reserve capital for a future purchase, or prepare to accept a smaller allocation if the list matches one. Each contingency has cost.
The list is therefore a clock with irregular ticks. The public process creates order, but not certainty. That distinction should be central to any assessment of ARIN's post-exhaustion legitimacy. A fair queue can still impose unpredictable delay. A transparent list can still produce costly mismatch. A first-approved rule can still reward applicants whose business can tolerate waiting more than those whose need is immediate. Time is not a neutral substitute for price.
Eligibility is an economic filter
ARIN's waiting-list eligibility rules are designed to keep the residual pool from being absorbed by large address holders. Organizations that already hold more than a /20 equivalent of IPv4 space in aggregate, excluding certain special-use space, are not eligible to apply. The maximum aggregate an organization may qualify for at one time is a /22. An organization may have only one request on the waiting list. Receipt of IPv4 space through the waiting list, or through specified transfer routes, removes the organization from the list.
These conditions are easy to defend in a scarcity setting. A residual pool that can hand out only small quantities should not become another acquisition channel for already well-resourced incumbents. A one-request rule limits queue stacking. A /22 ceiling keeps the prize modest. Removal after receipt of space prevents applicants from treating the list as an endless subsidized refill. Restrictions on transferring waiting-list space for 60 months, except in merger, acquisition or reorganization cases, prevent immediate resale and protect the moral logic of allocation.
The economic effect is more complex. Eligibility does not merely decide who qualifies. It creates categories of firms. A network below the /20 aggregate threshold sees the waiting list as a possible relief valve. A network just above it must look to transfers, leasing, provider inventory, internal efficiency or IPv6 transition. A growing operator that receives any qualifying amount must consider whether the gain is worth losing its queue position. A holder that might sell or transfer space while on the list must consider whether transfer activity changes its list status. The rules shape strategy before the application is filed.
The /20 threshold is especially important. It encodes a distributional view: organizations with more than that level of aggregate IPv4 space should not compete for residual returned supply. That may be fair. But it also means the queue is not a general growth mechanism. It is a narrow access channel for smaller or relatively less-endowed organizations. A company can have real demand, real customers and real financing while still being ineligible because it already holds enough addresses to cross the threshold. The queue is not measuring desire. It is imposing a public scarcity discipline.
The /22 maximum has a similar dual character. At 1,024 IPv4 addresses, a /22 can be meaningful for a small hoster, rural broadband provider, regional enterprise network, Caribbean access operator, local security firm or specialized infrastructure service. It is not enough to transform the balance sheet of a large carrier or cloud provider. This is a fairness design. It is also a planning constraint. A firm whose business case requires a /20 cannot use the waiting list as its main supply plan. It must either split strategy across sources or enter the market.
Eligibility also raises the value of administrative precision. How aggregate holdings are counted, how special-use space is excluded, how related organizations are treated, how recent transfers affect status, how fees and agreements are handled, and how receipt of "IPv4 space in any amount" is applied all have economic consequences. The more valuable IPv4 becomes, the less these questions can be treated as clerical details. They decide who may wait for underpriced scarce inventory and who must buy or lease at market terms.
The best defense of eligibility is restraint. ARIN should maintain clear public criteria and apply them mechanically where possible. It should avoid turning eligibility into a broader judgement about an applicant's business model, moral worth, market position or future strategy. The queue is legitimate when eligibility protects a residual fairness channel. It becomes dangerous when eligibility becomes a substitute for economic planning by the registry.
Block-size mismatch is the hidden geometry
IPv4 scarcity is often discussed in aggregate numbers, but the waiting-list problem is shaped by block size. A thousand addresses in one block are not economically identical to four scattered /24s. A /22 may fit a small ISP's immediate expansion but not a hosting provider's contiguous infrastructure plan. A /24 may be routable and useful for one applicant, yet too small to justify leaving the queue for another. ARIN's waiting list requires applicants to state the smallest block they are willing to accept because matching depends on this geometry.
That requirement creates a strategic choice. If an applicant sets its minimum acceptable size too high, it may wait longer because fewer returned blocks fit. If it sets the minimum too low, it may receive a block that does not solve the actual business problem and, by doing so, may be considered fulfilled and removed from the list. ARIN's guidance makes clear that an organization declining an available block is treated as fulfilled and removed. This is a strong anti-gaming rule. It is also a sharp planning knife.
The applicant must therefore translate business uncertainty into a prefix-size threshold. A rural broadband provider may not know whether the next subsidy award will add 300 households or 1,200. A regional hoster may not know how many customers will require dedicated public addresses rather than shared services. A managed-security provider may need clean public endpoints for appliance fleets, but customer onboarding may arrive unevenly. A Caribbean operator may face a sudden enterprise, tourism or public-sector demand that cannot be forecast with neat CIDR arithmetic. The waiting-list form asks for a number. The business reality is a distribution.
Block-size mismatch also affects fairness. Smaller applicants can sometimes accept smaller blocks and therefore match returned inventory sooner. That appears fair because smaller blocks serve smaller needs. But it can disadvantage firms with lumpy but legitimate growth. A new entrant building a proper network may need a block large enough to avoid immediate fragmentation, routing complexity, renumbering or customer segmentation. If it asks for that block, it waits. If it accepts less, it may lock itself into a more expensive architecture.
Fragmentation creates another cost. Multiple small blocks can be routed, but they require more operational care. They can complicate aggregation, reputation management, geolocation correction, reverse DNS, routing-security assertions, abuse handling and customer communication. The cost is not dramatic for a sophisticated operator. It can be meaningful for a small one. A queue that mostly produces small fragments may relieve address scarcity while increasing management cost.
There is no perfect solution. A registry cannot choose block sizes that returned inventory does not contain. It cannot always reshape recovered supply into ideal pieces. It should not let applicants hold out indefinitely for a dream block while smaller blocks sit unused. But it can improve the economics by publishing aggregate inventory signals, explaining how minimum acceptable size affects matching, showing historical fulfillment by prefix size, and making clear how declining a block affects future eligibility. The applicant should understand the trade before the moment of offer.
The hidden geometry of block size is where the queue stops looking like a line and starts looking like a matching market without prices. The registry is not selling addresses, but it is matching scarce shapes to heterogeneous demand. In such a system, transparency about shape is as important as transparency about order.
Returned supply is volatile inventory
The waiting list depends on supply that ARIN receives back into inventory. Official material identifies revocations due to non-payment as a typical source, and the broader policy environment includes returns, revocations and special reserved pools for particular purposes. This inventory is economically different from a procurement stockroom. It is irregular, administratively conditioned and sometimes operationally burdened by history.
That volatility matters more than the headline number of addresses. A quarter with many small revocations may satisfy several /24-level requests and do little for applicants waiting on larger approved blocks. A later period may produce a larger block but leave small applicants behind if matching logic points elsewhere. A block may return with reputation issues, stale reverse-DNS traces, old routing registry records, geolocation memory, abuse history or legacy contacts that need cleanup. Recovered supply is supply, but it is not always clean supply at the moment it re-enters the system.
This is where the waiting-list article must not become a reclamation article. The main issue here is not the due-process mechanics by which a block returns to ARIN. That is a separate institutional problem. The waiting-list issue is what happens after returned or revoked space becomes the feedstock for a queue. Applicants experience it as uncertain inventory. The volatility of that inventory determines whether the queue is a credible planning tool or a lottery with paperwork.
Volatile supply changes behavior. An applicant that trusts a steady stream of suitable blocks may wait longer before entering the transfer market. An applicant that sees irregular and size-mismatched distributions will hedge earlier. It may lease addresses for immediate customers, buy a small transfer block, redesign services around address sharing, or spend capital on NAT infrastructure. The waiting list then ceases to be merely a public allocation channel. It becomes one signal among several in a procurement decision.
ARIN can reduce uncertainty without promising abundance. It can report the timing of distributions, the quantity of blocks cleared for waiting-list use, the sizes distributed, the number of requests fulfilled, the number of requests bypassed because of block-size mismatch, the count of offers declined, and the volume of inventory waiting on administrative readiness. None of this requires publication of sensitive applicant details. It requires recognition that inventory volatility is part of the economic cost of the queue.
Volatile inventory also reveals why the waiting list cannot be judged by a simple fairness slogan. If a /22 goes to a small operator that can use it productively, the list has performed a useful function. If ten applicants remain unable to plan because the next suitable block is unknowable, the same list remains costly. Rationing institutions are not only judged by whether they hand out scarce units without corruption. They are judged by whether participants can make rational plans while scarcity continues.
The queue's credibility therefore rests on an honest admission: returned supply is helpful, but it is not a channel of abundance. It is a stochastic inventory stream. Treating it as such would make ARIN's waiting-list communications more economically useful and less vulnerable to disappointment.
The applicant's strategy begins before the ticket
A waiting-list applicant is not passive. The existence of the queue changes behavior before the application begins. An organization that knows ARIN's residual pool is limited will prepare documentation earlier, clean up contacts, settle billing questions, decide how to describe need, model acceptable block sizes, and compare the expected value of waiting against the cost of transfer or leasing. It may also time its request around expected growth, internal approvals or capital budgets. The queue is therefore a strategic environment.
Strategic behavior is not automatically abuse. A well-run network should plan ahead. It should know its address inventory, future customer commitments, IPv6 posture, NAT architecture, upstream dependencies and transfer options. If the waiting list encourages applicants to maintain better records and think carefully about address use, that is a public benefit. But the line between prudent planning and gaming is thin when the residual pool is valuable.
The one-request rule, maximum-size cap and removal rules are ARIN's principal anti-gaming tools. They prevent an organization from multiplying claims, asking for a very large subsidized block, taking any waiting-list space and remaining in line, or immediately converting waiting-list space into transfer inventory. These rules protect the queue's moral claim. They say, in effect, that residual space is for demonstrated operational need, not for arbitrage.
The same rules create defensive planning. An applicant must decide whether to request the maximum it can justify or request less in order to match inventory more quickly. It must decide whether receipt of a small block is worth the loss of queue position. It must consider that a transfer obtained through specified routes may remove it from the waiting list. It must keep fee standing current because fee problems can make it ineligible at the moment a block becomes available. It must be ready to sign the required agreement and pay applicable fees when ARIN Financial Services calls. The file may be approved, but the organization still needs operational and financial readiness.
This is a rational actor problem, not a moral failing. A firm facing uncertain public rationing and expensive market alternatives will optimize around both. It may hold more internal reserve because future access is uncertain. It may buy a transfer block earlier than needed because waiting is too risky. It may lease while waiting and then use waiting-list space to reduce lease exposure. It may split customers across address pools in ways that are technically inefficient but financially prudent. The queue affects the network architecture even before it delivers an address.
The economic danger is that compliance skill becomes a competitive advantage separate from operational need. Firms with experienced registry staff, consultants, counsel and capital can manage the waiting-list decision better than a small regional provider whose expertise is in serving customers. The official price of the block is lower than the market price, but the unofficial price includes expertise. If ARIN wants the list to serve smaller networks, it should make that expertise less necessary.
Plain documentation, examples, predictable status codes, applicant-facing timelines, clear fee reminders and transparent consequences for accepting or declining blocks would reduce the premium on insider knowledge. Anti-gaming discipline should be firm. It should not depend on applicants needing a professional interpreter for every strategic choice.
Small networks pay in planning cost
The waiting list is most important for the networks that cannot easily buy their way around it. A large cloud platform, national carrier or well-capitalized enterprise can purchase addresses, acquire a company, lease capacity, build more elaborate address-sharing systems, or use provider inventory while it waits. A small ISP, independent hoster, municipal network, tribal broadband project, Caribbean operator or regional managed-service firm may have fewer options. For them, a /24 or /22 can be meaningful, and uncertainty around that block can shape commercial survival.
Planning cost is not only the cost of paperwork. It is the cost of not knowing whether a business plan has an address basis. A small access provider may have a customer waiting for service but not enough public IPv4 capacity to support clean deployment without more sharing. It can promise service and hope the queue moves. It can buy or lease and weaken margins. It can add address sharing and accept support and reputation risk. It can delay the customer. None of these choices appears in ARIN's fee schedule, but all of them are caused by scarcity.
This is where a fair queue can still be regressive. The rule is formally the same for every eligible applicant. The effect is not. A delay that a large operator treats as a procurement inconvenience may be a financing problem for a small one. A fee reminder that a large operator routes to a finance department may sit in the inbox of an owner-manager. A block-size decision that a large operator models in software may be made by a small provider using rough customer forecasts. A 60-month transfer restriction that a large operator treats as acceptable may be a significant lock-in for a startup whose business model may change.
The waiting list also affects bargaining power. If a small network can credibly expect a block from ARIN, it enters lease or transfer negotiations with an outside option. If the queue is unpredictable, that outside option weakens. Brokers, lessors and upstream providers know that waiting may not solve the problem. They can price urgency. The queue's uncertainty therefore leaks into private contracts.
Small-network planning is also exposed to lumpy demand. A rural broadband build may depend on grants, construction schedules, tower availability, school contracts or anchor tenants. A Caribbean network may face demand from tourism, finance, government services or disaster recovery. A local hoster may win a customer whose compliance rules require public address stability. These events do not always align with waiting-list distributions. The smaller the firm, the less able it is to carry unused paid supply in advance.
ARIN cannot eliminate this planning cost. It cannot make IPv4 abundant. It cannot guarantee that a returned block will fit a small network's launch date. But it can reduce avoidable uncertainty. It can keep the rules simple, the status visible, the fee consequences clear, the matching logic understandable and the applicant interface usable by organizations without dedicated policy staff. In a queue meant partly to protect smaller networks, usability is not a courtesy. It is the policy's distributional core.
The economic test is practical: can an eligible small network look at the waiting list and make a defensible business decision? If yes, the queue supports competition even when it cannot provide abundance. If no, the queue may preserve formal fairness while leaving small networks to buy certainty at a price they can least afford.
Fairness and liquidity pull in opposite directions
ARIN's waiting list embodies a tension that cannot be solved by rhetoric. Fairness pushes toward eligibility limits, small maximum blocks, one-request rules, anti-resale restrictions and removal after receipt. Liquidity pushes toward transferability, larger block availability, freedom to adjust strategy, easier market movement and the ability to convert addresses into capital when business conditions change. The queue protects one value partly by limiting the other.
The 60-month transfer restriction on waiting-list space illustrates the trade-off. Without such a restriction, the waiting list would be vulnerable to arbitrage. An organization could qualify for a block at administrative terms and quickly sell it into a higher-priced market. That would turn a fairness channel into a subsidy capture channel. The restriction helps ensure that waiting-list allocations serve operational need.
Yet the restriction also reduces liquidity. A recipient that later merges, changes direction, loses customers, restructures, exits a service line or discovers that the block is less useful than expected cannot freely move the space for five years, except through specified reorganization channels. The block remains valuable, but its value is locked into use rather than ordinary transfer. This may be a justified policy cost. It is still a cost.
The /22 ceiling has a similar effect. It spreads opportunity and limits capture, but it also means that the waiting list cannot meet larger legitimate demand. Larger demand must go to the transfer market, leasing arrangements, provider-held space or network redesign. The queue thus supports fairness at the margin while leaving the main address economy to market mechanisms. That is not a defect if everyone understands it. It becomes a defect only if the queue is presented as a broad answer to scarcity.
Fairness also interacts with incumbency. Large legacy and incumbent holders cannot generally use the list if their aggregate holdings exceed the threshold. Smaller applicants can. That sounds pro-entry. But incumbents already hold the scarce resource. They may not need the list. New entrants and smaller networks depend more on the residual channel, yet receive only small, uncertain blocks. The policy reduces one form of inequality but cannot reverse the structural advantage of historical holdings.
Liquidity advocates sometimes argue that any waiting-list logic is a distortion because market price should move addresses to the highest-valued use. That is too simple. A residual pool controlled by a registry is not identical to already-issued private inventory. ARIN has a legitimate reason to distribute returned space under rules that prevent immediate capture by the richest bidder. At the same time, fairness advocates sometimes imply that market price is morally suspect. That is also too simple. Transfers and leasing are how much of the post-exhaustion economy obtains usable IPv4 capacity. Suppressing liquidity can harm the same small networks the queue is supposed to help.
The better view is institutional separation. The waiting list should be a narrow fairness instrument for residual inventory. The transfer market should remain the main mechanism for moving already-issued addresses between recognized holders and qualified recipients. The registry should protect uniqueness, authority, fraud resistance and record accuracy in both. It should not let waiting-list morality contaminate all market movement, and it should not let market liquidity destroy the credibility of the residual queue.
ARIN's challenge is not choosing fairness or liquidity once and for all. It is preventing each from becoming a justification for excess. Fairness without liquidity becomes rationed stagnation. Liquidity without anti-gaming discipline becomes capture. A mature registry keeps both within their proper domains.
The transfer market is the outside option
The waiting list cannot be understood without the transfer market. ARIN's own public materials present transfers as one of the other available IPv4 options after free-pool depletion. A network that cannot wait, is ineligible, needs a larger block, needs certainty or cannot accept the 60-month transfer restriction will look to market transfers, leasing or provider-supplied addresses. The queue and the market are connected vessels.
The transfer market disciplines the waiting list by giving applicants an outside option. If waiting becomes too uncertain, the applicant can buy or lease. If transfer review becomes too costly or uncertain, the waiting list becomes more attractive. If market prices rise, the implicit value of a waiting-list allocation rises. If the waiting list issues more predictable small blocks, it may reduce some marginal demand for transfers. Neither institution is isolated.
This connection produces a subtle price signal. ARIN does not auction waiting-list space, but every applicant knows that the alternative has a market value. A /22 received through the queue is not merely a technical allocation. It is relief from buying or leasing 1,024 addresses, subject to policy restrictions. The greater the market price, the greater the incentive to qualify, file early, maintain status and accept a suitable block. The waiting list's administrative rules are therefore under economic pressure even when ARIN does not set a sale price.
Transfers also reveal the limits of the queue. A firm needing a /20, a /18 or a carefully selected reputation-clean block cannot rely on residual inventory. It must find a seller, satisfy transfer requirements, sign the required agreement, pay fees and manage routing, reverse DNS, RPKI and reputation transition. This is expensive but more certain if supply is available and the registry process is predictable. For larger or time-sensitive needs, market purchase may be the rational choice even when waiting-list space is cheaper.
The outside option also constrains ARIN's legitimacy. If ARIN made the waiting list opaque, slow or discretionary, applicants would shift more demand to transfers and leasing. If ARIN made transfers too burdensome, applicants would cling to the waiting list, hoard eligibility and treat small allocations as windfalls. A healthy post-exhaustion regime requires both channels to function honestly: the queue as residual rationing, transfers as market movement, leasing as temporary or strategic access, and IPv6 deployment as long-term compatibility relief rather than a magical substitute for current demand.
The risk is that rationing logic migrates from the waiting list into the market. Need-based review has a historical rationale when a registry distributes scarce free-pool or residual inventory. It is more contentious when a buyer and seller have agreed on a market transfer and the registry is being asked to record a movement of already-issued space. The more valuable IPv4 becomes, the more any discretionary need review feels like capital control. That does not mean ARIN should abandon anti-fraud, authority and record checks. It means the policy should be precise about which controls protect the ledger and which controls suppress liquidity.
The waiting list is strongest when it stands beside a credible transfer market, not above it. It should relieve some small-scale pressure without pretending to replace price discovery. It should discipline speculative capture without becoming a universal moral theory of address movement. Its outside option is not a threat. It is part of the system that keeps the queue honest.
Anti-gaming discipline has a price
Every rationing institution fears gaming. If ARIN permitted unlimited waiting-list requests, applicants would stack claims. If it allowed quick resale, the list would invite arbitrage. If it allowed applicants to decline blocks without consequence, they could hold out for ideal matches while inventory sat unused. If it allowed large holders into the residual pool, small applicants would rightly suspect capture. Anti-gaming rules are therefore essential to the waiting list's legitimacy.
The price of discipline is reduced flexibility. One request at a time prevents stacking but also prevents a complex organization from expressing several legitimate needs across business units. The /22 maximum prevents bulk capture but cannot fit some efficient deployments. The rule treating a declined block as fulfillment prevents strategic cherry-picking but can punish an applicant that receives a technically unsuitable offer. Removal after receipt of space through the waiting list or certain transfers prevents double dipping but forces applicants to choose among imperfect channels. The 60-month transfer bar prevents resale but limits future business adaptation.
These are not arguments against the rules. They are reasons to keep the rules transparent and narrow. A rationing system that does not discipline gaming will lose legitimacy quickly. But a rationing system that treats every request for flexibility as gaming will impose unnecessary deadweight loss. The hard work is distinguishing opportunism from operational reality.
Consider the smallest acceptable block size. Allowing applicants to adjust the minimum acceptable size after joining the list gives them some flexibility as business needs and inventory expectations change. But the maximum approved size cannot simply be increased without closing the existing ticket and filing a new request, which then enters the list by approval order. This prevents applicants from preserving old priority while expanding the claim. It also means that an applicant whose need grows legitimately may face a painful choice: stay in line for a smaller block or reset the process.
Fee standing provides another example. ARIN requires organizations to be current on fees at the moment a block becomes available. That is reasonable; a registry should not distribute scarce inventory to an account in financial default. But for small organizations, billing and eligibility status must be communicated plainly and early. Losing a waiting-list opportunity because an invoice problem was noticed too late converts a financial administration issue into an address-supply shock.
Anti-gaming discipline also protects the membership from distrust. Members and applicants will tolerate scarcity more readily if they believe no one can turn the queue into a private trading strategy. That belief matters for ARIN's authority. A waiting list that appears exploitable would invite demands for tighter controls, which could make the system even less flexible. Good anti-gaming rules can therefore preserve a lighter overall regime.
The institutional lesson is that discipline should be rule-bound rather than discretionary. The registry should not rely on staff intuition to identify gaming case by case if objective rules can do the work. Objective rules may sometimes be blunt, but blunt published rules are generally preferable to hidden suspicion. Where exceptions are necessary, they should be rare, documented and available on equal terms.
The queue needs anti-gaming rules because the resource has value. It needs restraint because the applicants have real businesses. A mature waiting-list regime treats both statements as true.
New entrants learn expectations from the queue
For a new entrant, the waiting list is not only a possible source of addresses. It is an education in the political economy of IPv4. The entrant learns that public IPv4 space is scarce, that registry qualification is limited, that block sizes are small, that timing is uncertain, that market transfers are the real source of larger supply, and that address planning must be part of business strategy from the beginning. The queue shapes expectations even when it never delivers a block.
This expectation-setting function can be constructive. It prevents naive business plans built on the assumption that ARIN can provide old-style growth allocations. It tells a startup hoster, access provider or infrastructure operator that IPv4 must be budgeted, justified, conserved, shared and supplemented. It encourages IPv6 deployment where feasible, more disciplined address management, realistic customer contracts and earlier attention to routing and registry records. Scarcity is painful, but accurate expectations are better than false abundance.
The danger is that the expectation becomes fatalistic. If new entrants conclude that the waiting list is too uncertain, transfers too expensive, leasing too dependent on counterparties and incumbent holdings too entrenched, they may avoid independent network ownership altogether. They may depend on upstream providers, cloud platforms or large address holders for public identity. That can be efficient in some cases. It can also consolidate power and reduce competition.
The queue therefore sends a legitimacy signal. A visible, bounded and usable waiting list says that ARIN has preserved at least a modest route for smaller organizations to obtain residual space without entering the highest-priced market immediately. An opaque or frustrating list says that the registry can no longer provide meaningful access and that entrants must buy certainty from incumbents. The difference matters for member trust.
New entrants also learn how ARIN understands its own role. If the waiting list is framed as a limited residual mechanism, entrants can plan accordingly. If it is framed as stewardship that will somehow protect fairness broadly, entrants may overestimate what the registry can do. Under post-exhaustion conditions, honest modesty is better than comforting overstatement. A /22 cap is not industrial policy. A one-request rule is not competition policy. A 60-month transfer restriction is not a substitute for a liquid market. These are rationing tools, not an address economy.
Expectation-setting is especially important in the North American and Caribbean context. The ARIN region contains sophisticated capital markets, large incumbents, cloud providers, rural and remote access needs, Caribbean island networks, public agencies, universities, local hosters and entrepreneurs. Their planning horizons differ sharply. A waiting-list rule that is sensible for one may be marginal for another. The common denominator should be clarity, not a promise that one queue can solve every growth path.
The next generation of operators will judge ARIN less by whether it can provide abundant IPv4, which it cannot, than by whether it tells the truth about scarcity. A registry that accurately describes the residual queue, supports transfer clarity and keeps its own authority limited will help entrants plan. A registry that overstates the queue's fairness function will teach entrants the wrong lesson until the bill arrives.
Member legitimacy depends on restraint
ARIN's member-based governance is a source of procedural legitimacy, but it is not a blank cheque. The waiting list affects applicants, holders, transfer parties, future entrants and customers who may not participate equally in policy discussions. A rule can emerge from a legitimate process and still impose uneven costs. That is why the waiting-list question should be treated as institutional economics rather than community sentiment.
Members have competing interests. Small eligible networks may want residual space protected from large incumbents. Large holders may want clarity that their existing holdings will not be undermined by anti-hoarding rhetoric. Brokers and transfer participants may want predictable interaction between queue status and transfer activity. Operators dependent on leases may want a market that remains liquid. Public-sector and rural networks may want special recognition of social value. Future applicants are not yet in the room. No single "community" preference can collapse these interests into one moral mandate.
The registry's strongest legitimacy comes from doing less than some members might ask. Scarcity creates pressure for intervention. Applicants waiting for space may want stricter anti-hoarding policy. Incumbents may want less review. Market participants may want looser transfer conditions. Staff may want broader discretion to handle edge cases. Board members may want visible fairness. Each demand can sound reasonable from inside its constituency. The registry's task is to protect the narrow function that all constituencies need: an accurate, predictable and non-duplicative record.
In the waiting-list context, restraint means several things. ARIN should not treat the list as evidence that it can centrally allocate IPv4 capital. It should not use the list to judge business models beyond published eligibility and need criteria. It should not let member impatience turn residual allocation into pressure on legacy holders or market sellers. It should not let transfer-market ideology determine who receives returned space. It should not reward the loudest applicants with informal acceleration. It should not hide behind community process when the economic effect is unequal.
Restraint also means acknowledging the limits of consent. An eligible applicant may accept waiting-list restrictions because the alternative is costly. That does not make the restriction economically weightless. A holder may avoid the list entirely because it is ineligible or because it needs liquidity. That does not make the list irrelevant to market expectations. Governance legitimacy is not measured only by whether rules are published. It is measured by whether the rules remain proportionate to the registry function.
The best member-governed registry is not the one that finds the most popular rationing slogan. It is the one that can explain, in operational terms, why each waiting-list rule exists: uniqueness, fair residual distribution, anti-gaming, inventory matching, fee integrity, record accuracy, or transfer-market separation. If a rule cannot be tied to one of those purposes, it should be suspect.
ARIN's maturity is an advantage here. It has public materials, published policy, transfer mechanisms, legacy-resource experience and a community accustomed to process. That maturity should be used to narrow power, not to rationalize it. A waiting list earns legitimacy through restraint precisely because scarcity makes overreach tempting.
What ARIN should measure over the next 12 to 24 months
The waiting list should be assessed by metrics that reflect its economic function. Counting addresses distributed is useful but insufficient. A rationing institution should be measured by predictability, fit, delay cost, transparency, anti-gaming effectiveness and interaction with the market. Over the next 12 to 24 months, ARIN's most useful public reporting would be less dramatic than policy debate and more valuable to applicants.
The first metric is queue movement by block size. Applicants need to know whether /24, /23 and /22 requests move differently, how often returned inventory fits each class, and how many requests are bypassed or remain unmatched because of size. This would not reveal confidential business plans. It would help firms choose realistic minimum acceptable sizes.
The second metric is timing. ARIN could publish median and percentile time from approval to fulfillment by approved block size, plus the age of the oldest waiting request in each relevant category. Averages alone can mislead if a few requests move quickly because they fit small inventory. Percentiles would show the tail risk that matters for planning.
The third metric is inventory source and readiness, in aggregate. Addresses entering waiting-list inventory from non-payment revocation, voluntary return or other channels should be reported as categories where possible, with the caveat that operational readiness may differ. The purpose is not to relitigate recovery. It is to show applicants whether inventory is steady, irregular, clean, fragmented or delayed.
The fourth metric is offer outcome. How many offers are accepted, declined, timed out or made ineligible because fees are not current? How often do applicants adjust minimum acceptable size? How often are requests removed because the organization received space through another route? These figures would illuminate the hidden price of the queue.
The fifth metric is small-network usability. ARIN could report applicant-facing process improvements: clearer checklists, status explanations, billing alerts, deficiency categories, help-desk response times and examples of acceptable documentation. The point is not public relations. It is reducing fixed process cost for the organizations the queue is meant to help.
The sixth metric is market interaction. ARIN need not publish private prices to show whether waiting-list dynamics are pushing applicants to transfers or whether transfer receipt is removing applicants from the list. Aggregate flows among waiting-list receipt, 8.3 transfers and 8.4 transfers would help the community understand how residual rationing and market supply interact.
The seventh metric is dispute and exception handling. If eligibility decisions, declined offers, fee-standing issues or status changes are contested, ARIN should have a clear way to count and categorize them without exposing private files. A queue without reported disputes may be functioning well, or it may be pushing disputes into private frustration. The distinction matters.
Metrics will not create addresses. They will improve the price signal that a non-price rationing system otherwise suppresses. Better information lets applicants decide when to wait, when to buy, when to lease, when to redesign and when to accept a smaller block. That is a real economic gain.
The registry's modest bargain
The waiting list is a modest institution with high stakes. It cannot restore IPv4 abundance. It cannot eliminate the transfer market. It cannot erase the advantage of historical holdings. It cannot provide perfect block-size matches. It cannot make a small operator's launch date align with the return of suitable inventory. Its value is narrower: it can distribute residual IPv4 space under published rules without letting the richest or fastest private buyer capture every returned address.
That narrow value is worth preserving. A mature address economy should have room for a residual fairness channel. The existence of a market does not mean every piece of returned registry inventory should be auctioned or absorbed into private bargaining. But the existence of a fairness channel does not mean the registry has a mandate to manage address capital generally. The waiting list is legitimate as rationing. It is not legitimate as a theory of control.
The best description of ARIN's role is therefore restrained. It should maintain the queue, publish its mechanics, guard against gaming, match inventory to approved requests, enforce fee and agreement requirements, prevent immediate resale of residual allocations, and tell applicants the truth about uncertainty. It should also preserve a predictable transfer market as the outside option and avoid importing waiting-list morality into every movement of already-issued space.
This restraint is not weakness. It is the institutional discipline required when a private registry sits above valuable infrastructure assets. The more scarce IPv4 becomes, the more every timestamp, eligibility threshold and block-size decision can affect capital. That does not mean ARIN should stop making decisions. It means the decisions should be mechanical where possible, reviewable where necessary and modest in their stated purpose.
The queue turns price into time. It turns market demand into eligibility. It turns inventory volatility into planning cost. It turns small blocks into strategic choices. It turns anti-gaming rules into liquidity limits. It turns member legitimacy into a test of restraint. These transformations are not failures by themselves. They are the normal economics of rationing.
The failure would be pretending that the transformations do not occur. If ARIN speaks honestly about the hidden prices of waiting-list rationing, applicants can make better choices and members can debate policy with fewer illusions. If ARIN treats the queue as proof of broad stewardship authority, it will invite the suspicion that the registry is using scarcity to preserve power over capital it did not create.
The North American address market is mature enough to understand the difference. Operators know that IPv4 has value. They know that timing has value. They know that a /22 is not abundance. They know that transfers, leases, provider inventory and network redesign remain part of the economic landscape. What they need from ARIN is not a promise that rationing can be made painless. They need a rationing institution whose limits are clear.
That is the modest bargain: a fair queue for residual supply, a liquid outside market for larger movement, and a registry disciplined enough to know where one ends and the other begins.