Summary
- ARIN reclamation is economically attractive because scarce IPv4 addresses should not remain trapped in dead records, abandoned files or voluntarily returned inventory, but recovery becomes legitimate supply only when the prior state has ended through clear authority, defined breach, proven fraud, non-payment after cure, genuine abandonment or voluntary return.
- Returned, revoked, abandoned, bankrupt, legacy and reputation-impaired resources do not have the same risk profile. Gross recovered addresses are not the same as clean usable supply, especially when dirty reputation, route-security changes, reverse-DNS repair, successor claims or small-block fragmentation affect reuse.
- Reclamation and transfers should complement each other: voluntary markets move recognised resources by consent, while reclamation removes dead or invalid states after fair process. If waiting-list pressure or anti-hoarding rhetoric broadens recovery into judgement over reserves, leasing, pricing or business models, the result is capital control by procedure rather than ledger hygiene.
- ARIN's strongest role is narrow: preserve uniqueness, authority, contactability, dispute state, service continuity and clean reuse. Its weakest role would be pretending that scarcity gives it a general mandate over address capital.
The attraction of idle numbers
The easiest story about IPv4 reclamation begins with a moral intuition. The address space is finite. Some organisations hold addresses they no longer use, cannot identify, forgot during a merger, inherited from a failed business, or stopped paying to maintain. Other organisations need addresses now. If a regional registry can recover dormant space and return it to productive use, the system appears to gain efficiency without building anything new.
That intuition is not wrong. It is incomplete. A recovered IPv4 block is not like a box of spare cables found in a storeroom. It may be tied to an old legal entity, a bankrupt estate, a university department, a dormant subsidiary, a security allowlist, a routing registry entry, a reverse-DNS delegation, an abuse reputation history, a lender's file, a customer contract, a firewall rule, or a company whose operations are quiet but not dead. The apparent idle address may be idle because it is abandoned. It may also be idle because it is reserved for continuity, litigation, migration, disaster recovery or a slow procurement process. Scarcity makes recovery attractive; operational dependence makes it hazardous.
ARIN is a useful setting for this problem precisely because the region has a mature IPv4 market. The free pool has long since stopped being the normal source of address supply. New demand is met through transfers, limited waiting-list distribution, reserved-policy channels, IPv6 deployment, provider inventory, leasing arrangements and network redesign. In that environment, reclamation is not a side matter. It affects transfer pricing, small-provider planning, legacy-holder confidence, bankruptcy recoveries, broker diligence, lender assumptions and the credibility of ARIN's registry records.
The policy question is therefore not whether unused or abandoned resources should ever return to circulation. A registry that never corrects dead records would degrade the ledger. It would let false contacts, dissolved holders and unmaintained registrations block efficient use. The harder question is when recovery is real recovery and when it becomes confiscation by procedure. The same act - removing a holder from the registry and making the block available again - can be legitimate ledger hygiene in one case and economically destructive overreach in another.
The distinction matters because IPv4 is now capital. It is bought, leased, financed, collateralised in practice, integrated into mergers, priced by brokers, assessed by auditors and embedded in running networks. A revocation that once might have looked like an administrative endpoint now touches asset value. A return that once might have been a gesture of civic thrift now changes market supply. A waiting-list distribution that once might have looked like routine allocation now reallocates scarce capital to new users. Reclamation has become a market intervention whether or not it is described that way.
That is why a disciplined ARIN reclamation system should begin from modesty. It should recover what is genuinely abandoned, returned, fraudulently obtained, non-responsive after fair process, or no longer covered by an applicable service relationship. It should not become a general licence to judge whether a holder has used capital well, whether a reserve is socially pleasing, whether a sale should occur sooner, whether leasing is morally acceptable, or whether a legacy position should be weakened because scarcity has made it valuable. The registry's task is to keep the record trustworthy. It is not to become the central planner of address capital.
Reclamation is a state change, not a moral verdict
The vocabulary around reclaimed addresses often blurs several different situations. Returned resources are surrendered by a holder, usually because the organisation no longer needs them, no longer wants the fee or record burden, or has completed a restructuring that makes the addresses surplus. Revoked resources are removed by the registry after some breach, non-payment, fraud finding, failure to execute required agreements, or prolonged non-response. Abandoned resources sit in a more ambiguous middle: the registered holder may have dissolved, contacts may have failed, fees may be unpaid, successors may be unclear, or the resources may be quiet enough that outsiders assume no one cares.
Those categories should not be compressed into one moral class called "unused." Returned space is comparatively clean because the holder has chosen exit. Even then, the registry must check authority: the person returning the resource should actually be empowered to do so, and any transfer, creditor, successor or customer claim should be considered before the record is closed. Revoked space is more dangerous because the holder has not consented. It requires stronger process, clearer grounds and a record capable of surviving later challenge. Abandoned space is the most treacherous because silence is not always waiver. A defunct mailbox does not prove a defunct right. A stale point of contact does not prove that no successor exists.
Treating reclamation as a state change helps discipline the analysis. The question is not whether the old holder is admirable. The question is what has to be true before the public registry can safely change the recognised state of a scarce number resource. The answer requires evidence of authority, notice, opportunity to cure, dispute handling, preservation of last verified operational state and a reissue path that does not create duplicate claims. A registry may discover that the old state is no longer valid. It should not assume invalidity merely because the record is untidy.
That higher-risk class is where economics enters. A block that looks idle to ARIN may have market value to the holder, option value to a lender, sale value to an estate, lease value to a provider, or continuity value to customers. Destroying or redistributing that position without proper process transfers wealth. It may transfer wealth to a waiting-list applicant. It may transfer wealth to the market by increasing supply. It may transfer wealth to ARIN's institutional reputation by allowing the registry to claim active stewardship. But a transfer of wealth by administrative action is not neutral simply because it occurs inside a registry.
The legitimate version of reclamation is narrow and valuable. It removes dead records, reverses fraud, returns voluntarily surrendered space to use, cures non-payment endpoints after warning, and lets scarce addresses serve networks rather than ghosts. The illegitimate version treats old holdings as suspicious because they are old, reserves as suspect because they are valuable, and quiet operational states as invitations to seize. ARIN's institutional challenge is to make the first version predictable enough that it does not slide into the second.
ARIN's mature market makes the stakes visible
The ARIN region is not a final-fragment frontier where every reclamation decision is mainly a question of immediate allocation relief. It is a mature scarcity market. Address brokers understand ARIN paperwork. Buyers ask for chain-of-registration evidence. Sellers price blocks by size, reputation, transferability and timing risk. Mergers and reorganisations can move number resources as part of broader corporate transactions. Bankruptcy estates may treat IPv4 as value that creditors can see. Cloud, hosting, access, enterprise, public-sector and Caribbean operators all encounter IPv4 scarcity through different operating constraints.
The North American legal and financial setting also makes ARIN's role more visible. The Nortel bankruptcy sale to Microsoft remains the canonical example of market and court reality overtaking older registry theory. Nortel's IPv4 addresses were treated as valuable assets in a proceeding, and ARIN's position had to adjust to a world in which courts, buyers and creditors treated number resources as economically meaningful. The lesson is not that a registry record is irrelevant. It is the opposite: the record matters so much that markets need it to align with legal and operational reality rather than deny them.
Reclamation sits directly on that fault line. If a bankrupt company holds address space, the efficient outcome may be transfer, sale, return, consolidation, or continuation by a successor. Creditors may reasonably expect the estate to preserve value. Customers may need continuity while a buyer is found. The registry needs to know who has authority to sign, whether fees are current, whether fraud is present, and whether the successor can be recognised. But the registry should not treat insolvency as automatic abandonment. Bankruptcy is a legal process for preserving and distributing value. It is not an invitation for an administrative body to pull scarce assets out of the estate because the holder looks weak.
The same applies to dormant corporations and old institutions. Many early Internet allocations sit inside organisations whose structure has changed. A university may have renamed departments. A hospital system may have merged. A manufacturer may have spun off divisions. A local ISP may have been sold twice. A legacy contact may have retired. Reclamation can clean real debris from these records, but careless recovery can also punish the exact historical depth that makes the ARIN market complex. Old files are not automatically false files.
Market maturity therefore changes ARIN's burden. The registry does not need to guarantee every private bargain. It does need to maintain a public record that allows serious parties to rely on state changes. A reissued block should not carry unresolved title fog. A revoked block should have a review history that explains why the prior state ended. A voluntarily returned block should have authority evidence. A dormant-file cleanup should distinguish a lost mailbox from a dissolved holder with no successor. In a mature market, predictable state transition is supply.
Abandoned, returned and revoked supply have different yields
Reclamation is often discussed as if recovered addresses immediately become usable supply. In practice, supply has yield. A returned /20 is not automatically equivalent to a clean, market-ready /20. A revoked /24 with a history of spam, hijacking or customer disputes may require months of quarantine and reputation repair before a small provider can safely use it. A block recovered from a dormant holder may be subject to later successor claims if the record was not carefully closed. A fragmentary set of small blocks may help waiting-list applicants but may not fit the demand profile of networks waiting for contiguous space.
Usable-yield accounting should therefore become part of any serious reclamation discussion. Gross recovered addresses are the headline number. Net usable addresses are the economic number. The gap between them includes legal uncertainty, operational quarantine, route-filter acceptance, reverse-DNS repair, RPKI and routing-security assertion changes, abuse-desk history, geolocation corrections, stale allowlists, block-size fragmentation, reinstatement windows and staff time. A registry that announces recovery without accounting for yield may overstate relief and understate risk.
Different recovery sources produce different yields. Voluntary returns from known holders tend to be the cleanest if the holder has maintained records and cooperates with transition. Non-payment revocations may be administratively clear but still require reinstatement windows and reputational checks. Fraud recoveries can be necessary but messy because the registry must unwind false authority while preserving legitimate downstream reliance. Abandoned resources may produce large nominal numbers but low immediate yield if successors are hard to identify. Legacy cleanups may create usable supply only after slow work with organisations that have not thought about number resources for years.
Yield also depends on the intended reuse channel. A waiting-list applicant may accept a small clean block for immediate access-network or hosting needs. A cloud provider may need larger contiguous space and stronger reputation assurances. A public agency may need exceptionally clean history for security allowlists. A brokered transfer buyer may value documentation more than speed. An email-heavy service may treat dirty reputation as a price discount or a rejection reason. A rural ISP may not have the staff to remediate a block that large operators could clean with dedicated teams.
This is why reclamation is not a substitute for transfer-market design. Reclaimed space can relieve scarcity, but it cannot recreate abundance. It arrives in irregular sizes, with uncertain histories and administrative cost. The waiting list can distribute some of it, but the waiting list is a rationing device, not a market-clearing mechanism. Transfers remain the main way value moves from lower-valued to higher-valued use in the ARIN region. Reclamation improves the public stock; transfers allocate across private demand. Confusing the two leads to overclaiming.
The goal is not to burden ARIN with theatrical transparency. It is to let the market understand whether reclamation is meaningful supply or mostly a symbolic comfort. In a scarce asset market, the difference matters. Operators plan budgets, purchases and network builds around expected supply. If recovered addresses are slow, dirty or legally uncertain, they should not be counted as if they were clean supply. Honest yield accounting protects both applicants and incumbent holders.
Due process is the price of legitimate reuse
The strongest economic argument for due process is not sentimental. It is that due process lowers the cost of relying on the registry. If holders, buyers, creditors and applicants believe that ARIN will change resource state only through defined grounds, clear notice, fair opportunity to cure, documented review and appeal or reconsideration paths, they can price registry risk more cheaply. If they believe state can change through opaque discretion, they price fear.
Due process begins before the first threat. The holder should know what conduct can lead to reclamation, what evidence ARIN will consider, who may respond, how long the response period lasts, what happens if the holder is in bankruptcy or corporate transition, what counts as cure, when services may stop, when resource status may be revoked, when a revoked block may be reinstated, when it may be reissued, and how disputes are recorded. The details may differ by category, but the architecture should be legible.
Notice is not only an email. In number-resource administration, notice must account for the reality that contacts become stale for reasons that are negligent, innocent or structural. A small ISP's founder may die. A university contact may retire. A corporate domain may change. A bankruptcy trustee may not know how to read ARIN correspondence. A holding company may control the resource through records that were not updated after a merger. The registry cannot chase every ghost forever, but serious notice should use layered methods before drawing severe conclusions: listed contacts, known billing contacts, officer information, public corporate records where appropriate, counsel in active proceedings, and clear public or account-level status markers that create an incentive to respond.
Cure is equally important. A holder that missed fees should have a defined path to restore good standing before reissue. A holder with stale contacts should be able to update authority. A holder with ambiguous successor documentation should be told what authority evidence is missing. A holder with resources it no longer needs should be able to return or transfer them without being treated as suspect. A holder whose block has been hijacked should be able to work through correction without losing the legitimate claim. Cure turns reclamation from punishment into record repair.
Appeal or independent review matters most where the consequence is irreversible. Once a block has been reissued and a new network has built on it, later correction becomes painful. The safest system isolates disputes before reissue. It can mark the resource as under review, pause transfer, restrict nonessential changes, or preserve last verified state while authority is examined. It should not rush to redistribute merely because redistribution is popular. In scarce markets, speed can be a form of taking.
Due process also protects ARIN. A registry with clear procedures is less vulnerable to accusations that recovery is being used to favour insiders, punish unpopular holders, relieve institutional pressure, or manufacture supply for political optics. ARIN's legitimacy in reclamation will not come from saying that unused resources should be reused. Most market participants already accept that. Legitimacy will come from proving that the registry can end a recognised state without becoming a commercial judge, creditor, prosecutor or asset allocator beyond its mandate.
Notice-and-cure separates cleanup from confiscation
Notice-and-cure is the practical line between ledger hygiene and expropriation. A ledger-hygiene system says: the record appears defective, here is the defect, here is the evidence, here is the rule, here is the cure path, here is the deadline, here is the consequence and here is the review channel. A confiscatory system says: the holder has failed to satisfy the registry's judgment, therefore the holder's position can be ended and redeployed. The difference is not cosmetic. It is the difference between correcting a record and appropriating an asset-like position.
The ARIN region contains many holders for whom notice-and-cure is not a formality. Rural broadband cooperatives, Caribbean networks, small hosting providers, family-owned ISPs, municipal networks and small enterprises may not have full-time number-resource counsel. They may treat ARIN correspondence as technical administration until the language becomes severe. They may have accurate operational use but weak paperwork. They may be slow to answer because the person who knows the address history is also running the network. A fair cure period does not reward negligence. It recognises fixed-cost asymmetry.
Legacy holders need the same protection for a different reason. Some early allocations were made under older expectations and later brought into modern agreement structures through negotiation, continuity arrangements or service relationships. A legacy holder may have relied for decades on the stability of its registration. The registry may reasonably ask for current contacts, authority and accurate records. It should not use modern cleanup as a way to erode legacy continuity by surprise. Legacy certainty is not merely private nostalgia. It supports market confidence in old space that continues to route, support customers and anchor institutional networks.
Notice-and-cure also reduces defensive behaviour. If holders fear that admitting a defect will expose them to immediate reclamation, they will hide defects. If they believe defects can be cured proportionately, they will update records, return surplus, clean customer assignments, identify successors and negotiate transfers before the problem becomes severe. A harsh system may recover some blocks quickly but poison cooperation. A cure-oriented system may recover fewer blocks at first but increase voluntary correction and return over time.
The remedy should fit the defect. A stale point of contact calls for an update. Non-payment calls for payment, service-status warnings and defined revocation steps. Dissolution calls for successor inquiry. Fraud calls for stronger intervention. A returned block calls for authority verification. A quiet but valid reserve calls for documentation, not seizure. A block with abusive traffic history calls for quarantine and reputation remediation. A holder in bankruptcy calls for estate coordination, not impatience. Matching remedy to defect is what keeps the registry in its lane.
In a market where an address block can be worth millions of dollars, cure is not a courtesy. It is an economic control. It ensures that the registry's administrative power cannot be used as a cheap substitute for purchase, court order, creditor process or negotiated transfer. If society wants unused capital to move, markets and legal processes exist for that purpose. The registry can support them by maintaining accurate records. It should not replace them by declaring that untidy capital is available for administrative redistribution.
Bankruptcy and dormant holders test the boundary
Bankruptcy exposes the difference between abandonment and value preservation. A company in insolvency may be unable to respond quickly, may have unpaid invoices, may lack active operations and may have confusing contacts. But its assets do not vanish because it is distressed. Creditors, trustees, receivers, purchasers and courts exist precisely because value must be preserved, sorted and transferred in an orderly way. IPv4 addresses complicate that process because the registry record is not identical to ordinary title, yet the economic value is real enough that the estate may depend on it.
ARIN's experience after the Nortel transaction showed that registry policy cannot be insulated from insolvency reality. Courts and market participants may treat number resources as value that can be sold, assigned or carried into a successor arrangement. ARIN remains relevant because the registry record must be updated, agreements may need to be signed, transfer rules may apply and operational continuity must be preserved. But relevance is not ownership. The registry is a necessary interface, not the estate's superior creditor.
Dormant holders raise the same issue without the formality of a court case. A corporation may have been dissolved by mistake and reinstated later. A subsidiary may have merged into a parent. A business may have stopped serving retail customers but retained infrastructure. A former university project may have been absorbed into a central IT unit. A provider may have sold customer assets but not the original registration. A holding company may be waiting for a buyer. In each case, silence can have several meanings. It may mean abandonment. It may mean administrative decay. It may mean a valuable asset lacks a caretaker.
The reclamation temptation is strongest when the holder looks weak. That is also when process should be strongest. A registry that can recover from the absent, insolvent or confused without careful inquiry creates a predatory incentive. It tells the market that number resources are safest in the hands of large professional actors with permanent compliance departments. Small and distressed holders then become supply mines. That may increase short-term redistribution, but it undermines the idea that registration is a stable basis for investment.
A better approach treats bankruptcy and dormancy as continuity problems. The registry should preserve the last verified state while identifying the authorised party. If a court-appointed representative exists, deal with that representative. If a successor can be proven, update the record. If no successor appears after layered notice and a defined period, reclamation may be legitimate. If a dispute exists, record it and isolate it. If the holder voluntarily returns space through proper authority, accept it. If fees are unpaid, apply the published service and revocation path. The point is not endless delay. It is sequenced legitimacy.
The market benefits from this discipline. Buyers prefer blocks whose prior holders were not steamrolled. Lenders prefer collateral whose registry status cannot be ended by administrative impatience. Bankruptcy estates can realise value rather than lose it. Small operators can reorganise without fearing automatic disappearance. Applicants waiting for recovered space receive addresses with cleaner histories. ARIN's record becomes more credible because it shows that state changes were earned.
Legacy continuity is market plumbing
Legacy address space often provokes impatience. Some early holders received large blocks when IPv4 looked abundant. Later entrants now pay market prices or wait for limited distributions. The distributional unfairness is real enough to create political pressure. But reclamation is a poor tool for rewriting history. A legacy registration may be old, generous by modern standards and economically valuable. It may also be the foundation for real networks, customer systems, research infrastructure, public services, enterprise security designs or a transfer that can move supply through lawful market channels.
Legacy continuity performs market plumbing. It allows old space to remain legible, transferable where policy permits, financeable in practice and connected to responsible contacts. If legacy holders believe that engaging with ARIN exposes them to weakened expectations, they will stay quiet. If they believe engagement improves continuity without turning every old reserve into a confiscation risk, they will update records, sign appropriate agreements, clean authority files, return unneeded space or sell space into the market. Stability encourages movement. Threat encourages hiding.
The right objective is not to freeze legacy space outside modern discipline. It is to make legacy status compatible with accurate records and predictable change. ARIN can require current contacts for services. It can verify authority for transfers. It can prevent fraud. It can document disputes. It can support returns. It can make clear which services depend on agreement status. What it should not do is let scarcity convert old reliance into a presumption of guilt. A university's quiet /16 is not automatically a moral offence. A corporation's old allocation is not automatically abandoned because its current network architecture uses only part of it. The policy question is evidence and continuity, not resentment.
Legacy certainty also affects non-legacy markets. When buyers compare addresses, they look for clean history. A legacy block with clear authority can be valuable supply. A legacy block with ambiguous status, unclear services, missing contacts or unresolved registry questions carries a discount. If ARIN's approach to legacy cleanup is predictable, the market can price and process those differences. If the approach is discretionary, every legacy block becomes a negotiation with institutional mood.
Legacy holders also form an important potential source of voluntary returns and transfers. Some have genuinely surplus space. Others could monetise unused capacity and reinvest in networks, security or institutional missions. The recovery path that unlocks this supply is not coercive rhetoric. It is confidence: clear authority rules, predictable transfer processing, fair tax and accounting treatment where applicable, clean reputation data, manageable agreement terms and assurance that returning part of an estate will not invite attack on the rest.
In that sense, legacy continuity and reclamation are not opposites. Good legacy continuity can produce better reclamation because it draws old holders into the light. Bad reclamation policy can freeze legacy space because holders fear that visibility is the first step toward loss. ARIN's economic interest, if it is understood as ledger quality rather than institutional control, should be to make the honest path less dangerous than silence.
Waiting-list relief is not the same as abundance
The waiting list gives reclamation its most visible constituency. A provider waiting for IPv4 addresses is easy to sympathise with. It may have customers, network plans, equipment, financing and a genuine need for public numbers. When ARIN distributes recovered space to waiting-list requesters, the act has a pleasing sense of fairness: unused numbers move to someone who can use them. In a depleted region, that signal matters.
But waiting-list relief should not be confused with abundance. Reclaimed supply is irregular. It depends on returns, revocations, cleanup, block sizes and policy constraints. A quarterly distribution can help some applicants while leaving the structural scarcity unchanged. The market price of IPv4 does not disappear because a limited number of blocks are reissued. Operators will still buy, lease, conserve, deploy IPv6, use NAT, negotiate with upstreams and redesign products. Reclamation softens scarcity at the margin; it does not abolish it.
This distinction protects against political overreach. If recovered space is framed as the path to fairness, pressure will grow to find more of it. That pressure can be healthy when it drives better contact cleanup, anti-fraud work and voluntary returns. It becomes dangerous when it encourages the registry to define "unused" expansively, shorten cure periods, treat old holdings as suspect, or convert reserve capital into administrative supply. Waiting applicants deserve fairness, but fairness to applicants cannot be purchased by unfairness to existing holders.
Usable-yield accounting is especially important for the waiting list. Applicants care about usable addresses, not gross recovery. If a block is encumbered by reputation problems, geolocation errors, route-filter doubts or potential successor claims, handing it to a small operator may export cleanup cost to the party least able to bear it. A large platform can remediate dirty space with dedicated teams. A local ISP may discover that customers cannot send mail, access services, pass fraud checks or satisfy security filters. Reuse is not complete when the registry record changes. Reuse is complete when the recipient can operate the block without inheriting unpriced damage.
The waiting list also creates incentive questions. If recovered addresses are distributed at administrative cost while market prices remain high, a waiting-list position has option value. Rules that limit speculative behaviour are therefore necessary. But those rules should focus on preventing abuse of the distribution channel, not on expanding reclamation power over unrelated holders. The registry should be strict about applicant eligibility, holding periods, transfer restrictions where applicable and accurate need statements. It should not treat the existence of waiting demand as proof that someone else's quiet address space should be taken.
For small and new operators, the waiting list can still be important. It offers a non-market route to some public IPv4, even if limited. It signals that ARIN is not only a transfer-recording institution for incumbents and large buyers. It gives political legitimacy to the post-exhaustion regime. But that legitimacy depends on clean inputs. If waiting-list relief is built on questionable revocations, it will damage the very trust it is meant to preserve.
Dirty addresses are not clean supply
The phrase "dirty address" is imprecise but economically useful. It describes an IPv4 block whose registry status may be clean enough to assign, yet whose operational history makes use costly. The block may appear on spam blocklists, fraud-scoring systems, threat-intelligence feeds, geolocation databases, payment-risk models, hosting-abuse records, country or region mappings, enterprise allowlists, denied lists, stale reverse-DNS assumptions or old customer documentation. None of these systems is identical to ARIN's registry. All can affect whether a reissued block works.
Reputation cleanup should therefore be part of reclamation economics. When a block returns to ARIN, the registry can update the public record, remove or change contacts, support reverse-DNS transition, allow new routing-security records and publish the new holder. It cannot directly force every mail provider, fraud platform, geolocation vendor or enterprise firewall to forget the past. Time, documentation and active remediation are needed. The cost may fall on the new recipient unless the reuse process acknowledges it.
This matters most for waiting-list distributions and small-holder reuse. A sophisticated buyer in a transfer can diligence reputation, negotiate price, demand warranties, require cleanup covenants or choose a different block. A waiting-list recipient may receive what is available. If the block arrives with serious reputation damage, the recipient has effectively received less than the nominal address count. The distribution may look fair on ARIN's books while imposing hidden cleanup labour on a small network.
Quarantine periods can help, but they are not magic. A recovered block that sits unrouted for a period may lose some bad traffic association. But reputation systems vary. Some update quickly; others lag. Some depend on third-party reports; others preserve old classifications. Geolocation may point to the old holder or region. Reverse DNS may be stale. RPKI and IRR state may need rebuilding. Abuse contacts may receive old complaints. Customers may encounter blocked services without understanding why. The block is reusable only after the recipient can establish a new operational identity.
ARIN should not become the global reputation regulator. That would repeat the mandate problem in another form. But ARIN can support cleaner reuse by maintaining accurate state transitions, ensuring old authorisations are removed or superseded, allowing new security assertions, preserving transition evidence, and making the prior-status category visible enough that recipients understand risk. The market can do the rest through diligence, price and remediation. The registry's role is to make history legible, not to erase it.
The broader lesson is that IPv4 scarcity attaches value to continuity, not just numbering. A clean block is a bundle of registry recognition, routeability, reputation, reverse-DNS control, security-object clarity, legal confidence and customer acceptability. Reclamation recovers only the first piece unless the rest is considered. The most efficient recovery system will therefore be conservative before reissue and helpful after reissue. It will treat recovered space as inventory needing preparation, not as magic abundance appearing from administrative action.
Transfers and reclamation are complements, not enemies
The transfer market and reclamation are sometimes discussed as rival philosophies. Transfer advocates emphasise price signals, voluntary exchange and movement from lower-valued to higher-valued use. Reclamation advocates emphasise fairness, anti-hoarding and returning dormant resources to applicants who need them. In practice, the two mechanisms should complement each other. A mature address economy needs voluntary movement and involuntary cleanup, each confined to its proper domain.
Transfers are best for resources whose holders are known, legitimate and willing to sell, lease or reorganise. They preserve value by compensating the holder and moving the block to a buyer that expects higher use. They create price discovery. They let legacy and incumbent holders convert surplus into capital. They support M&A, cloud expansion, hosting demand, access-network growth and lender recovery. They are imperfect because policy friction, need requirements, holding periods, broker quality, reputation issues and legal uncertainty can raise transaction costs. But their core virtue is consent.
Reclamation is best for resources whose recognised state has ended or should end after fair process: voluntary returns, proven fraud, prolonged non-payment under agreement after cure, no eligible successor after serious notice, unauthorised registration changes, or abandoned resources that cannot be tied to any continuing claim. Its virtue is ledger correction. Its danger is that it can move value without compensation if the process is too broad.
When reclamation is too aggressive, it harms transfers. Holders become reluctant to engage. Buyers fear later challenge. Brokers spend more on registry-risk management. Lenders discount collateral. Legacy holders avoid cleanup. Small operators view ARIN not as a predictable recordkeeper but as an institution that may reinterpret silence. The result is less voluntary movement and more administrative fog. A registry may recover a few blocks while freezing a larger pool that would otherwise have moved through the market.
When reclamation is too weak, transfers also suffer. Dead records remain in the system. Fraudulent claims contaminate diligence. Buyers cannot distinguish real sources from ghosts. Waiting-list pressure grows because idle space appears locked away forever. Honest holders pay a reputational price for the perception that incumbents can warehouse without consequence. The market becomes less trusted because the registry fails to remove debris.
The efficient balance is narrow reclamation plus liquid transfer. ARIN should be tough on dead, false and unresponsive records. It should make voluntary returns easy and safe. It should make legacy authority repair predictable. It should support transfer clarity and avoid converting transfer review into business-model judgment. It should not use reclamation as a substitute for market pricing or as a way to suppress the economic value of IPv4. Scarcity should be allowed to express itself through price where legitimate holders exist, and through recovery where no legitimate holder remains.
Small holders need clocks, not discretion
Large address holders can manage uncertainty. They hire counsel, maintain dedicated registry contacts, use experienced brokers, run internal IPAM, retain outside consultants, monitor policy lists and negotiate with lenders or counterparties. Small holders experience the same rules as fixed costs. A rural ISP, independent hoster, municipal network, tribal broadband provider, Caribbean operator, small enterprise or school network may have legitimate address use but limited administrative capacity. For them, predictable clocks matter more than elegant doctrine.
A small holder should know how long it has to answer a notice, how to update authority, when non-payment becomes service risk, when service risk becomes revocation risk, when a revoked resource can be reinstated, when reissue can occur, how to show successor authority, how to return unneeded space without endangering retained space, and how to challenge a mistake. If those clocks are visible, the holder can plan. If the process depends on discretionary escalation, the holder behaves defensively or pays intermediaries it can barely afford.
The distributional risk is subtle. A reclamation system may be formally neutral and practically regressive. The same notice that a large company routes to a compliance team may land in a small operator's general mailbox. The same documentation demand that a national provider answers in a week may take a cooperative a month. The same reputation cleanup that a cloud provider absorbs as routine may overwhelm a local hoster. If ARIN measures only whether the rule is written equally, it will miss whether the cost of surviving the rule is unequal.
Scale-sensitive process does not mean lower standards. It means first asking for the least complex action that cures the defect. Update the contact. Identify the officer. Pay the invoice. Provide the merger document. Confirm return authority. Show that the network still exists. Explain the reserve. Correct reverse DNS. Remove stale routing records. Escalate only when the answer is absent, contradictory or suggests fraud. Small holders should not be forced into acquisition-grade evidence production to answer a housekeeping problem.
For small holders, ARIN's best contribution is a boring one: templates, examples, defined statuses, clear emails, account dashboards, plain-language cure steps, real closure and reasonable response windows. These tools are less dramatic than policy debate, but they decide whether reclamation feels like infrastructure maintenance or threat. When the process is legible, small holders can correct records. When it is obscure, they either ignore it until late or depend on larger actors.
Small-holder predictability is not charity. It protects competition. If independent address holding becomes too risky or administratively complex, small networks will depend more heavily on upstreams, cloud platforms or large brokers. IPv4 scarcity already favours incumbents. Reclamation discretion can deepen that effect if it makes small ownership feel unsafe. A narrow, clock-driven process keeps the registry from becoming an accidental consolidation force.
Member power should constrain the registry
ARIN's member-governance setting is often presented as a legitimacy source. Members participate in policy, elect leadership and influence the organisation's direction. That structure matters, but it should be understood carefully. Member power is most legitimate when it constrains the registry's discretion, improves transparency, disciplines costs, clarifies process and protects the reliability of the ledger. It is less legitimate when a participating subset uses policy language to redistribute value from less organised holders to more organised applicants.
The "community" cannot be treated as a magic source of public authority. In practice, participation is uneven. Large operators, policy specialists, consultants and repeat attendees have more capacity than small firms, dormant holders, legacy institutions, distressed companies, public bodies and future applicants. A consensus process may be useful without being sovereign. It can set procedures for a shared registry service. It should not be allowed to convert into a legislature over asset-like positions held by parties who may not be present in the room.
In reclamation, this distinction is vital. The registry's authority should come from narrow administrative function: maintaining uniqueness, accurate records, service continuity, transfer recognition, fraud correction and fair reuse after valid state termination. Member policy can define procedures around those functions. It should not create a moral mandate to seize value because active participants dislike how inactive or legacy holders use scarce resources. A member-governed registry is still a registry. It does not become a state.
The economics of member power are also conflicted. Applicants waiting for space may favour aggressive recovery. Incumbent holders may favour restraint. Brokers may favour clarity that supports transactions. Large buyers may tolerate process costs that small holders cannot. Legacy holders may avoid participation because visibility feels risky. Public-sector users may have constraints that private operators underestimate. No single "community" preference automatically equals public interest. Good process recognises these conflicts rather than hiding them.
The dangerous version of member power is majoritarian impatience. Scarcity creates constituencies for redistribution. If the registry hears mostly from those who want more supply, it may mistake demand for mandate. If it hears mostly from incumbents, it may neglect dead records. The solution is not to romanticise either side. It is to tie recovery to objective state-transition rules. A resource should be reclaimed because defined facts have occurred, not because a political temperature has changed.
That approach would make ARIN's governance more credible. Members can and should debate the rules of cleanup. But the rules should produce a ledger that outsiders can trust: courts, lenders, operators, customers, security teams, counterparties and future applicants. A registry that serves only the loudest part of its membership will weaken the market it administers. A registry that lets member governance discipline its own power will strengthen it.
The capital-control trap
Capital control does not always announce itself. In a market like IPv4, it can appear as delay, uncertainty, discretionary review, broad definitions of non-use, unclear revocation grounds, selective enforcement, transfer friction, reputation ambiguity or fear that a registry may reinterpret old facts. A holder may still "own" its business in ordinary language and still find that the most valuable network identifier cannot move, be financed, be leased, be sold or be maintained without institutional permission. That is capital control by administrative dependency.
Reclamation can fall into this trap when the registry treats scarcity as justification for broader authority. The argument begins innocently: addresses are scarce, some holders are not using them efficiently, therefore ARIN should recover them for better use. But "better use" is not a registry invariant. The registry can know whether a holder is recognised, whether contacts are current, whether fees are unpaid, whether documents are false, whether a return is authorised, whether a transfer can be processed and whether a block can be reissued without duplicate claims. It cannot reliably know the socially optimal capital plan for every holder.
The line between ledger hygiene and expropriation is therefore functional. Ledger hygiene protects the record: uniqueness, authority, contactability, service status, fraud resistance, transfer state, delegation state and conflict metadata. Expropriation begins when the registry uses control over the record to take or immobilise value because it dislikes the holder's reserve, business model, timing, price, customer mix, leasing plan, financing structure or silence absent a defined abandonment process. The remedy may be described as policy compliance, but the economic effect is taking.
This distinction is particularly important because ARIN's formal language, like other registry systems, may resist calling number resources property. That language does not eliminate reliance. Buyers pay. Networks build. Courts notice value. Creditors underwrite. Customers depend. If an administrative system can destroy or redistribute that reliance while denying that it is touching property, it creates the worst of both worlds: property-like value without property-like protection, public-infrastructure effect without public-law accountability, market prices without market security.
A serious reclamation framework should avoid that contradiction by limiting itself. It need not settle metaphysical ownership. It only needs to recognise that number-resource positions have high reliance value and that ending them requires a process proportionate to that value. The higher the consequence, the stronger the notice, cure, review and reissue discipline should be. The registry does not have to call the resource property to behave as if arbitrary loss would be harmful.
This is why ARIN's best institutional posture is restrained. It should say less about moral stewardship and more about specific state defects. It should recover returned resources, close abandoned records after serious process, revoke only on defined grounds, preserve dispute state, clean reputation where it can, and publish usable-yield categories. It should leave pricing, leasing, financing, customer strategy and capital timing to operators, contracts, courts and markets. That is not weak governance. It is the governance appropriate to a registry.
A disciplined reclamation compact
A disciplined ARIN reclamation compact would not begin with the question "how much space can be recovered?" It would begin with "what state transitions can the market trust?" From that premise, several operating principles follow.
First, classify recovery sources. Voluntary return, non-payment revocation, fraud correction, abandoned-holder closure, legacy-file repair, bankruptcy transfer, merger succession and reputation quarantine should not be collapsed. Each class has different evidence, cure, risk and yield. Public category reporting would help applicants understand supply and help holders understand risk.
Second, separate gross recovery from usable yield. The meaningful metrics are not only addresses recovered, but addresses reissued, addresses still in quarantine, addresses disputed, addresses reinstated, addresses returned voluntarily, average time to reuse, average block size, reputation issues identified, and the share of recovered supply that went to waiting-list applicants. This would make reclamation an inventory discipline rather than a slogan.
Third, preserve layered notice and cure. Severe remedies should follow documented grounds and failed cure, not impatience. Notice should account for stale contacts, corporate changes, insolvency representatives and legacy records. Cure should be proportionate to the defect. Reinstatement windows should be clear enough that a holder can act before reissue makes correction costly.
Fourth, isolate disputes. If authority is contested, the resource should not be rushed into reuse. The registry can pause changes, mark status, preserve service where appropriate and require independent resolution. Dispute metadata is part of ledger accuracy. Destructive action before adjudication is not.
Fifth, prepare recovered addresses for actual use. Before reissue, old delegations, security assertions and authorisations should be cleaned or superseded where possible. Recipients should receive enough status information to anticipate reputation, geolocation and abuse-history work. ARIN cannot cleanse the Internet's memory, but it can avoid pretending that memory does not exist.
Sixth, protect small-holder legibility. Reclamation notices should be written for real operators, not only counsel. The account interface should show status, deadline, defect and cure step. Templates should help holders return surplus, update contacts, document succession and ask for review. Predictability is a competition policy in disguise.
Seventh, keep registry administration separate from market judgment. A reclamation compact should state what ARIN will not do: it will not reclaim merely because a resource has high market value, because a holder could sell but has not, because a reserve looks inefficient absent defined policy, because a business model is unfashionable, because a transfer price is high, or because waiting demand is politically sympathetic. Those may be debates for markets, boards or legislatures. They are not enough for registry seizure.
Such a compact would not satisfy everyone. Applicants will say recovery remains too slow. Holders will say any revocation power remains dangerous. Brokers will complain about complexity. Some policy participants will want stronger anti-hoarding tools. But the point of institutional design is not to remove conflict. It is to make conflict survivable without degrading the ledger. A compact built on state transition, yield accounting and restraint would let ARIN recover real supply while lowering the risk premium attached to its power.
The final test is simple. After a reclaimed block is reissued, a serious outsider should be able to understand why the old state ended, why the new state is valid, what cleanup occurred, what risks remain and why the process did not function as uncompensated taking. If that answer is available, reclamation has strengthened the registry. If the answer is "ARIN decided," the market will hear something else: the gatekeeper can move capital by declaring the ledger dirty.
The modest power that matters
The best ARIN reclamation policy would be modest and consequential. It would not promise to solve IPv4 scarcity. It would not pretend that recovered space can replace transfers, private supply arrangements, network redesign or address-market finance. It would not define registry virtue by how aggressively old holders are pressured. It would instead keep one narrow promise: when the recognised state of a number resource changes, the change will be accurate, reviewable, proportionate and safe enough for networks and markets to rely on.
That promise is more valuable than it sounds. A clean ledger lowers transaction costs. It lets waiting-list applicants receive supply without inheriting avoidable disputes. It lets buyers pay for addresses rather than political-risk insurance. It lets lenders understand collateral risk. It lets legacy holders engage without fearing surprise confiscation. It lets small operators maintain independent address positions. It lets bankrupt estates preserve value long enough for lawful resolution. It lets ARIN correct fraud and dead records without becoming a capital allocator.
The institutional temptation will always be to make reclamation sound larger. Scarcity rewards strong language. "Unused" sounds wasteful. "Community" sounds legitimate. "Stewardship" sounds moral. "Reuse" sounds efficient. Yet the registry's legitimacy comes from the opposite habit: boring precision. Who held the resource? Under what authority? What changed? Who was notified? What cure was offered? What defect remained? What dispute exists? What was returned voluntarily? What was revoked? What was quarantined? When was it reissued? What does the new holder need to know?
That is the economics of reclamation in the ARIN region. The recovered address has value only if the state transition is trusted. The waiting-list applicant benefits only if the block is usable. The market benefits only if recovery removes dead records without frightening live holders. The registry benefits only if its power remains narrow enough that participants continue to treat its ledger as infrastructure rather than as leverage.
Reclamation is therefore a test of institutional character. A registry that can recover abandoned, returned and properly revoked resources without turning scarcity into discretionary control has adapted to the post-exhaustion world. A registry that uses scarcity to stretch its mandate has not. ARIN's advantage is that the region already has market depth, legal sophistication, member capacity and long experience with transfers. Its risk is that those same features make every ambiguous recovery more consequential.
The correct line is neither permissive neglect nor administrative expropriation. It is disciplined reuse: recover what has truly left the holder's valid control, protect what remains operationally and legally alive, account honestly for usable yield, clean dirty space before celebrating supply, give small holders predictable clocks, and remember that the ledger is valuable because networks rely on it. The registry should protect the address book. It should not mistake the address book for a deed to the economy written on top of it.