Summary

  • LACNIC's IPv4 reserves can serve a legitimate public-interest function by preserving limited supply for new entrants, critical continuity, recovered-resource redistribution, and emergency cases after the free pool has gone.
  • The same reserve power can also dull institutional discipline if it lets the registry ration scarcity administratively while avoiding member pressure, market signals, and the political discomfort of transfer-market dependence.
  • The governance question is not whether reserves should exist. It is whether each reserve is narrow, rule-bound, time-aware, transparent in aggregate, and exposed to periodic policy review.
  • A disciplined reserve policy should protect new networks without freezing address mobility, defend public-interest continuity without subsidising hoarding, and preserve emergency capacity without becoming a discretionary treasury.
  • LACNIC's regional context makes this balance unusually important because small economies, public networks, universities, carriers, and digital-services firms face very different abilities to buy IPv4 on the transfer market.

The last free block and the politics of the remainder

The cleanest way to understand LACNIC's reserve problem is to begin with the moment of exhaustion. In 2020 LACNIC announced that it had assigned the last IPv4 block from the region's freely available pool. After that, ordinary growth could no longer be satisfied by the familiar administrative routine: justify need, receive addresses, expand. The remaining supply came from narrower channels: recovered resources, returned space, waiting-list allocations, special pools, and transfers between recognised holders.

That shift changed the politics of registry policy. Before exhaustion, the main scarcity question was how to distribute a shrinking common stock fairly. After exhaustion, the harder question is how to govern a residual stock that is too small to satisfy demand but too valuable to leave unmanaged. A reserve can be a wise stabiliser. It can keep a first allocation possible for a small new network. It can support public-interest continuity when a university, exchange point, government service, or security function faces a genuine constraint. It can give the registry a limited buffer for cases where no normal market solution is realistic.

But a reserve can also become an institutional comfort blanket. If the registry retains a discretionary stock, even a modest one, it can soften the full pressure that scarcity would otherwise place on policy. Members may press less hard for transfer-market clarity if a waiting list promises eventual relief. Policymakers may postpone difficult debates about prices, eligibility, needs tests, and secondary-market risk. Staff may become the practical allocators of last-resort value. Incumbents may tolerate reserve rules because they limit new-entrant growth while preserving the appearance of fairness. New entrants may accept long waits because the alternative market is expensive.

This is the discipline problem. Reserves are not wrong. They are dangerous when their purpose is vague, their size is not politically legible, their waiting times are detached from reality, their opportunity cost is hidden, or their eligibility rules do not face the same scrutiny as other scarcity policies. A reserve that begins as resilience can become insulation.

LACNIC's challenge is therefore not to abolish reserve policy. The region has too many small markets, public networks, and uneven capital conditions for a purely market allocation to be satisfactory. The challenge is to make the reserve behave like a constrained public tool rather than a quiet treasury of institutional discretion.

What reserves are for

An IPv4 reserve is a promise about priority. It says that some limited portion of address space will not simply flow to the first eligible claimant or highest-value transaction. It will be held for a defined purpose. In LACNIC's setting that purpose may include new entrants, recovered-resource redistribution, continuity after exhaustion, or other public-interest cases recognised by policy.

The best case for reserves begins with entry. A new network needs some IPv4 capacity even in an IPv6 future because customers, public services, payment systems, cloud services, government portals, and legacy devices still touch IPv4. If every address must be purchased at market price, a small provider in a low-income market faces a barrier that an incumbent never faced when allocations were abundant. That is not merely a fairness problem. It is a competition problem. It can freeze the market structure that existed at the moment of exhaustion.

There is also a resilience argument. A region with many countries, islands, borders, currencies, and regulatory regimes cannot assume that a transfer market will meet every legitimate need quickly. Public-interest networks may have procurement constraints. Universities and research networks may lack the balance sheet to compete with commercial buyers. A small internet exchange or government continuity service may need a modest block for operational reasons, not speculative growth. A narrow reserve can prevent scarcity from turning into fragility.

The third argument is administrative cleanliness. Recovered and returned resources do not always arrive in neat quantities or with perfect histories. A registry needs rules for placing those addresses back into recognised use. A reserve framework can provide order: who is eligible, how much can be issued, what waiting order applies, what documentation is needed, and how previous recipients are treated.

These arguments are strong. They explain why reserve policy should not be dismissed as anti-market nostalgia. The Internet was not built by auctions alone. Regional registries exist because coordination, uniqueness, and public trust matter. A reserve can express those values after free-pool exhaustion.

Yet the strength of the public-interest case is also why discipline is necessary. A policy labelled "reserve" can borrow moral authority from new entrants and public-interest continuity while operating in ways that mainly protect the institution from harder choices. The word reserve should therefore trigger scrutiny, not deference.

Price signals are information, not ideology

The transfer market is often discussed as if it were a philosophical choice between community allocation and commodification. That framing is too crude. Prices are information. They tell the community where scarcity is biting, how much networks value clean title, how costly delay has become, and how much pressure exists for migration, conservation, or purchase. A region does not need to worship price signals to learn from them.

For LACNIC, price signals matter in at least four ways. First, they show the opportunity cost of reserved space. Every block held for a waiting list or special purpose is a block not sold, transferred, or otherwise moved to a buyer with immediate demand. That may be justified, but it is not free. Second, prices reveal whether reserve allocations are large enough to affect behaviour. A tiny allocation may help with bootstrapping but cannot substitute for commercial supply. Third, prices reveal whether eligibility rules create arbitrage. If a party can obtain low-cost reserved addresses and later benefit from market value, policy needs transfer restrictions, holding periods, or clawback rules that are clear and enforceable. Fourth, prices discipline institutional rhetoric. If public officials claim scarcity is manageable while market prices rise, the claim should be tested.

The problem with reserves is not that they ignore prices. Sometimes they should deliberately override price. A new entrant in a poor market may deserve a small first allocation precisely because the price signal would exclude it. A public-interest continuity case may justify non-market allocation because the social cost of failure exceeds the market price. The problem arises when the reserve hides prices from the governance conversation. If the community cannot see the cost of the reserve, it cannot decide whether the reserve is worth it.

A disciplined reserve policy should therefore treat transfer-market data as a public signal. It should ask whether waiting-list demand is rising or falling, whether recipients later seek transfers, whether reserved blocks are being used, whether the size limits make operational sense, and whether the reserve is delaying necessary IPv6 transition or merely smoothing it. These are not pro-market questions. They are governance questions.

LACNIC's region is not a single capital market. The price that is manageable for a large carrier, hyperscale buyer, or well-funded content network may be impossible for a municipal provider or small ISP. That is a reason for reserve policy. It is not a reason to ignore the market. The market is part of the evidence that tells policymakers where relief is needed and where relief may be distorting behaviour.

How reserves insulate institutions

Institutions prefer tools that reduce conflict. A reserve can do that. It lets the registry say that scarcity is being managed. It gives disappointed applicants a queue rather than a flat refusal. It allows staff to administer a finite pool under published rules. It offers the board and policy community a visible answer to the charge that exhaustion has abandoned new entrants. Those are political benefits.

The risk is that these benefits reduce member discipline. Members discipline a registry through voting, policy debate, fee pressure, public criticism, and participation in governance. Scarcity should sharpen that discipline because members must confront trade-offs: Should transfers be easier? Should needs tests survive? Should returned resources go to a waiting list or auction-like mechanisms? Should small allocations be reserved for first-time holders? Should public-interest networks receive priority? Should recipients face transfer restrictions? Should fees reflect registry workload or resource value?

If a reserve absorbs enough pressure, those questions can be postponed. The institution can point to the reserve as evidence of action while the deeper scarcity regime remains under-examined. A long waiting list can become a political sedative: everyone knows relief is remote, but the existence of a queue prevents the sharper debate that a total refusal would provoke.

Insulation can also work through complexity. Reserve rules, recovery rules, transfer rules, eligibility tests, and waiting-list rules can become difficult for ordinary members to monitor. Staff then become the practical interpreters of value. Even when staff act in good faith, the community's ability to discipline the institution weakens if the rules are too intricate to contest.

A third form of insulation is reputational. Reserve policy sounds public-minded. A critic who questions it can be made to look hostile to new entrants or poor markets. That is why the criticism must be precise. The question is not whether LACNIC should preserve some space for entry and continuity. The question is whether each reserve instrument has a defined purpose, a visible opportunity cost, a limited scope, and a review path that can change it when conditions change.

The final form is fiscal and strategic. A registry with a reserve retains relevance in allocation decisions after exhaustion. That may be healthy if the reserve is narrow. It may be unhealthy if the institution uses reserve administration to preserve a central role that should gradually shift toward registry accuracy, transfer integrity, IPv6 support, and accountability. The registry should remain central because the ledger matters, not because it controls a residual stock of scarce assets.

New entrants and the fairness of small allocations

The strongest argument for LACNIC reserves is the new entrant. An incumbent received addresses in a different era. A newcomer arrives after the door has closed. If the newcomer must buy everything while the incumbent holds historical or pre-exhaustion resources, the registry has helped crystallise an old market structure. Small first allocations can partially correct that.

But the fairness case has limits. A reserve cannot make a new entrant equal to an incumbent with large historical holdings. It can give the entrant a bootstrapping block. It can support transition mechanisms, customer onboarding, and basic reachability. It cannot provide indefinite growth. If policy pretends otherwise, it creates false expectations.

That means LACNIC should be candid about what a reserve allocation does and does not do. It should not be sold as a substitute for IPv6 deployment, efficient addressing, carrier-grade translation where appropriate, or market purchase where commercial growth requires more space. It should be understood as a start-up aid in an exhausted market.

Eligibility matters. A new entrant reserve should not become a way for affiliates of existing holders to multiply claims. It should not reward paper companies created to obtain low-cost blocks. It should not let recipients flip addresses quickly into the transfer market. It should not prefer applicants who are better at paperwork over applicants with genuine operational need. These risks argue for documentation, relationship checks, holding periods, public statistics, and enforcement.

At the same time, the policy must avoid making compliance so expensive that only sophisticated firms can use it. A reserve for new entrants that requires costly legal submissions, complex corporate proof, or long uncertainty can reproduce the same exclusion it is meant to soften. The administrative burden should be proportionate to the block size and risk.

This is where regional realities matter. Latin America and the Caribbean include markets where a modest allocation can materially affect local competition and public connectivity. They also include sophisticated commercial actors capable of structuring around rules. A disciplined reserve policy must be simple enough for small applicants and strong enough to resist gaming by large ones. That balance is difficult, but it is the job.

Transfers as discipline, not merely escape

Transfers are sometimes described as an escape from registry scarcity: if the free pool is gone, buy from another holder. But transfers also discipline registry policy. They reveal whether the registry's rules permit resources to move, whether title records are trusted, whether delays are costly, and whether regional policy is aligned with operational demand.

A reserve-heavy system can dull that discipline if it treats transfers as a morally suspect secondary option rather than a normal scarcity tool. LACNIC does not need to let the transfer market decide everything. It does need to recognise that transfers are now part of the address economy. A reserve policy that works against transferability can trap resources, encourage informal workarounds, and make the official ledger less useful.

The transfer market also disciplines reserve sizing. If reserve allocations are small and waiting times are long, commercial buyers will still need transfers. If transfer rules are too restrictive, those buyers may defer investment, buy corporate shells, lease addresses in opaque ways, or shift activity outside the region. If transfer rules are too loose, reserved allocations may leak into the market and undermine the new-entrant rationale. The policy problem is a triangle: reserve fairness, transfer mobility, and anti-arbitrage protection.

A disciplined LACNIC approach would let transfer evidence inform reserve rules. If many reserve recipients soon seek transfers, eligibility or holding periods may be wrong. If the waiting list grows while transfers are blocked by procedure, the region may be rationing scarcity inefficiently. If prices rise sharply while reserve allocations remain symbolic, policymakers should admit that the reserve is not solving growth demand. If transfer disputes increase, title and review rules need attention.

The registry's role in transfers should be clear: protect the ledger, verify authority, apply policy, maintain history, and prevent fraud. It should not use transfer discretion to impose hidden industrial policy. If the community wants to favour certain uses, sizes, or recipients, it should say so in policy. Scarcity policy is too consequential to be made through opaque transfer friction.

The waiting list as a public signal

A waiting list is more than an allocation queue. It is a public signal about the credibility of reserve policy. If the queue is short and allocations move at a visible pace, the reserve is functioning as a modest relief valve. If the queue is long, opaque, or effectively indefinite, it becomes something else: a promise whose political value may exceed its operational value.

The first discipline is plain measurement. How many applicants are waiting? What is the typical wait? How much space is entering the pool? How much space is leaving? What share of applicants eventually receive usable blocks? How many leave the queue because they bought addresses, merged, failed, or changed plans? A reserve cannot be judged without these facts. A queue that is not measured is not a governance instrument; it is a story.

The second discipline is expectation management. A small first allocation can be meaningful, but it must not be presented as if it solves growth scarcity. If waiting times are measured in years, applicants should know that before they make business plans. A small ISP deciding whether to enter a market, buy addresses, partner with an incumbent, or accelerate IPv6 deployment needs honest scarcity information. False hope is a subsidy to indecision.

The third discipline is queue design. First-come-first-served rules are simple, but they are not always fair if documentation burdens differ across countries or applicant types. Priority categories can be fairer, but they invite lobbying and complexity. Randomisation can reduce gaming, but it may seem arbitrary. Size limits can spread benefits, but they may produce allocations too small for practical use. Every queue design is a theory of fairness. LACNIC should make that theory visible.

The fourth discipline is exit. A waiting list should have rules for applicants that no longer qualify, do not respond, change control, affiliate with existing holders, or obtain addresses elsewhere. Without exit rules, the queue can accumulate stale demand and distort the apparent need. With overly harsh exit rules, small applicants can be punished for administrative weakness. Again, the answer is proportion.

The fifth discipline is feedback into policy. If the waiting list becomes very long, the policy community should not treat that as a mere administrative backlog. It may mean reserve inflows are too small, eligibility is too broad, transfer markets are too hard to use, or the reserve promise is too ambitious. A disciplined institution lets the waiting list embarrass policy when policy deserves it.

Fees, incentives, and the cost of comfort

Reserve policy also intersects with registry finance. LACNIC, like other RIRs, must fund staff, systems, security, training, policy meetings, legal capacity, and member services. Its fee model is not the same as selling addresses, and that distinction is important. Still, exhaustion changes institutional incentives. When free-pool allocation declines, the registry's relevance must rest more on ledger quality, transfer integrity, IPv6 support, member services, and governance legitimacy. A residual reserve can preserve a visible allocation role, and that visibility can be comforting.

The risk is not crude self-enrichment. The more subtle risk is mission inertia. Institutions built around allocation do not easily become institutions built around scarcity governance. Staff expertise, member expectations, meeting agendas, public communications, and performance measures may remain organised around who receives resources even when the core public need has shifted toward accurate records and trusted transfers. Reserve policy can slow that institutional adjustment because it keeps allocation at the centre of attention.

Fees can sharpen or dull the issue. If fees are perceived as unrelated to service value, members may ask why the registry retains broad discretion over scarce assets. If fees are too tightly tied to resource holdings, the registry can appear to benefit from historical concentration. If transfer-related fees are too high or procedures too costly, the market signal is distorted. If small new entrants face fees that make reserve allocations hard to use, the public-interest rationale weakens.

A disciplined reserve regime should therefore be discussed alongside service expectations. What does the registry owe a holder after exhaustion? Accurate records, reliable RDAP and WHOIS services, reverse DNS support, secure portals, fair transfer handling, policy coordination, transparent reporting, training, and regional engagement. These services are valuable even if no free IPv4 remains. If members understand that value, the institution does not need reserve mystique to justify itself.

There is also a political economy of comfort. A reserve lets everyone avoid an unpleasant truth: the region cannot administratively allocate its way back to abundance. New entrants will still face IPv4 costs. Incumbents will still hold advantages. Transfers will still matter. IPv6 will still be necessary. Public-interest networks will still need funding and planning. The reserve can soften the edge, but it cannot repeal scarcity.

That truth should be stated often because it keeps policy honest. A reserve is a bridge, buffer, or relief valve. It is not an economic strategy for the region. LACNIC's legitimacy after exhaustion will depend less on the fact that it still has some addresses to distribute and more on whether it can help the community govern a market that no longer has enough old resources for everyone.

Regional asymmetry and the temptation of quiet rationing

The Latin America and Caribbean region has an additional complication: scarcity is not evenly experienced. A multinational carrier can buy expertise, search the transfer market, evaluate title, manage geolocation problems, and absorb price movement. A rural provider, research network, small hosting firm, municipal service, or non-profit connectivity project may not have those options. Even where money is available, cross-border payment, procurement rules, currency volatility, tax treatment, and legal review can slow a transfer until the operational need has passed.

This asymmetry gives reserve policy a strong moral claim. It also creates a temptation for quiet rationing. If policymakers conclude that markets are too unequal, they may prefer to distribute small blocks through administrative judgement while avoiding the harder question of how to make the market safer and more transparent for weaker participants. A reserve can then become a substitute for transfer-market reform.

That would be a mistake. The weaker the buyer, the more it needs a trustworthy market. Small operators benefit from clear title standards, predictable transfer timing, published fees, understandable documentation, and visible dispute paths. They also benefit from reserve allocations where the market is genuinely inaccessible. These tools should reinforce each other. Reserve policy should not let the community neglect transfer hygiene, and transfer policy should not be used to argue that reserves are unnecessary.

There is a regional development point as well. Address scarcity can shape where digital services are built. If growing firms in the region cannot obtain clean IPv4 capacity at predictable cost, they may host elsewhere, rely more heavily on foreign intermediaries, or delay services that still need IPv4 reachability. A reserve will not solve that structural problem, but opaque reserve and transfer rules can make it worse. The registry cannot create abundance, yet it can reduce uncertainty.

The Caribbean dimension is especially sensitive. Smaller island markets may have limited provider choice, disaster-recovery constraints, and public-sector continuity needs that do not resemble the needs of a large continental market. A reserve rule that looks neutral on paper may not capture these constraints. But discretion to recognise them should be bounded. The better answer is not unlimited case-by-case judgement; it is a policy vocabulary that can name continuity needs, small-market constraints, and emergency limits without opening a broad door to favouritism.

Regional asymmetry therefore strengthens both sides of the argument. It supports reserves because equal treatment in a wildly unequal market can entrench old advantages. It demands discipline because unequal markets are also easier to govern through opaque patronage. The registry should be able to help the small applicant without becoming the invisible allocator of last-resort economic opportunity.

Emergency supply and moral hazard

Emergency reserves are attractive because they promise preparedness. A region may need capacity for unforeseen continuity cases: a public network failure, a recovery from fraud, a critical infrastructure transition, a natural disaster response, or another urgent situation where the market is too slow. The argument is sensible. The risk is moral hazard.

If operators believe emergency supply will be available, some may underinvest in planning, IPv6 deployment, conservation, or market acquisition. If policymakers believe emergency reserves exist, they may defer hard decisions about transfer reform or public-interest funding. If staff control emergency judgement with limited visibility, emergency allocation can become discretionary value distribution.

The answer is not to eliminate emergency capacity. It is to define emergency narrowly. The recipient should face a real continuity risk. The need should be temporary or bounded. The allocation size should be the minimum needed. The decision should be documented. The community should receive aggregate reporting. Repeat use should trigger policy review. Emergency addresses should not become growth capital.

There should also be a sunset logic. If emergency reserves are never used, the community should ask whether they are too large. If they are used often, the community should ask whether the underlying policy environment is failing. Either pattern contains information. A reserve that is never questioned becomes a hidden assumption.

Moral hazard also applies to incumbents. Large holders may support reserves for new entrants because the reserve is too small to threaten them and because it channels newcomers into a limited allocation path rather than a more aggressive transfer or redistribution debate. In that sense a reserve can be both progressive and conservative: progressive in helping a few new networks, conservative in preserving the larger distribution of address wealth.

That is not a reason to reject it. It is a reason to describe it honestly. A small reserve is not redistribution. It is a bootstrapping and continuity device. If the region wants deeper redistribution, it must debate recovery, fees, transfer rules, and possibly public funding. Hiding that choice inside a reserve policy is bad governance.

Recovery and returned space

Recovered and returned IPv4 space carries special legitimacy. Unlike a reserve carved out before exhaustion, recovered space often returns because a holder no longer needs it, cannot justify it, abandoned it, violated policy, or voluntarily gives it back. Redistributing such space can feel less like rationing and more like restoration.

Even here discipline matters. Recovery powers can become too broad if the registry treats underuse as simple forfeiture without regard to reliance, documentation, or transition plans. Returned resources can be allocated in ways that reward patience, favour certain categories, or create small windfalls. The community needs to know how much space returns, how long it waits, who is eligible, and whether outcomes match the policy's stated purpose.

Returned space is also a test of transparency. Because the quantities may be small and irregular, it is easy for the public to lose track. Yet these small blocks can matter greatly to small networks. Aggregate reporting can show whether the reserve is meaningful or mostly symbolic. It can also reveal whether recovery creates enough supply to justify maintaining a queue.

There is a further issue of cleanliness. Recovered blocks may have reputation problems, routing history, geolocation errors, or abuse-list baggage. A reserve policy that treats all returned addresses as equal may underestimate the cost to recipients. A small ISP receiving a tainted block may face deliverability or reachability problems. The registry cannot cleanse the whole Internet's memory, but it can disclose what it knows, provide history, and avoid presenting recovery as costless abundance.

The constitutional point is that recovery and reserve policy should be joined by review. If recovered space is scarce, slow, dirty, or uneven, the policy should adapt. If it creates useful new-entrant support, the policy should say so with evidence. If it mainly creates a long queue and occasional symbolic allocations, the region should be honest about that too.

Member discipline and LACNIC's governance burden

LACNIC's members are not merely customers. They are part of the governance structure that legitimises registry policy. In a scarcity regime, that role becomes harder. Members have divergent interests: holders of large historical blocks, networks trying to buy, small new entrants hoping for first allocations, public-interest operators, governments, universities, brokers, and firms whose IPv6 plans differ widely. Reserve policy sits in the middle of those interests.

Member discipline works only if members can see the trade-offs. A reserve policy should therefore expose the main facts in a form ordinary members can understand: reserve size, inflows, outflows, waiting time, recipient categories, transfer restrictions, returned-space volume, emergency uses, and policy exceptions. This does not require naming every recipient in every sensitive case. It does require enough public information to let members decide whether the policy is still justified.

Voting and assemblies are blunt instruments for technical scarcity questions. Policy forums are more precise, but they can be dominated by repeat participants. Staff know the details, but staff should not be the only practical interpreters of the rules. The registry's burden is to connect these layers: staff administration, policy debate, board oversight, and member accountability.

Reserve policy is especially vulnerable to deference because it sounds technical and benevolent. Members may assume that a small pool is being handled properly. That assumption is not governance. Good institutions make benevolent tools auditable. They invite the question: has this reserve outlived its original purpose, become too small to matter, become too large to justify, or begun to distort transfers?

The most useful discipline may be periodic automatic review. A reserve rule should not survive indefinitely simply because nobody has the time to reopen it. Review can be triggered by dates, depletion thresholds, waiting-time thresholds, market indicators, or repeated emergency use. The goal is not constant churn. It is to prevent exhaustion-era rules from becoming fossilised.

A disciplined reserve standard

LACNIC's reserve policy can be judged by a practical standard.

First, purpose. Each reserve should name the problem it solves: new entrant access, public-interest continuity, emergency need, recovered-resource redistribution, or another defined category. Vague fairness is not enough.

Second, size. The community should know whether the reserve is large enough to serve its purpose and small enough not to distort the broader market. If the quantity is unknowable because inflows depend on recovery, the uncertainty should be stated.

Third, eligibility. Applicants should be screened for genuine need and independence without creating barriers that exclude the small networks the reserve is meant to help. Affiliation rules, anti-flipping rules, and holding periods should be clear.

Fourth, opportunity cost. The policy should acknowledge what reserved space cannot do while it is held: it cannot be transferred to current demand, priced by the market, or used by another waiting applicant. This is not an argument against the reserve. It is the cost that justifies review.

Fifth, transfer interaction. Reserve recipients should know when and how they may transfer resources. Transfer restrictions should be tied to the anti-arbitrage purpose and should not immobilise addresses longer than necessary.

Sixth, emergency limits. Emergency allocations should be narrow, temporary where possible, minimally sized, reasoned, and reported in aggregate.

Seventh, public reporting. The community should see reserve balances, inflows, outflows, waiting times, and categories of allocation. The report should be simple enough for a small operator and detailed enough for serious scrutiny.

Eighth, review. The reserve should face automatic policy reconsideration when conditions change. A waiting list that effectively promises relief after many years is not the same institution as a waiting list that can satisfy applicants in months.

This standard is not hostile to LACNIC. It is protective of LACNIC's legitimacy. Scarcity makes every registry more powerful and more exposed. The way to preserve trust is to make the remaining discretion smaller, clearer, and easier to contest.

The regional case for restraint

Latin America and the Caribbean need a registry that can see beyond the balance sheets of the largest address buyers. The region includes markets where a small allocation can support local competition, remote connectivity, education, public services, and regional autonomy. A purely price-led scarcity regime would risk entrenching incumbents and exporting address control to whoever can pay most.

But the same regional case also demands restraint. Small networks are harmed by opaque rules as much as by high prices. They need predictable eligibility, honest waiting-time information, clean transfer rules, and confidence that the registry is not rationing scarcity to preserve its own authority. Public-interest language should not become a substitute for member control.

The mature position is therefore mixed. LACNIC should defend narrow reserves for new entrants and public-interest continuity. It should maintain clear transfer markets so addresses can move where need and willingness to pay exist. It should publish enough aggregate data for members to see whether reserves are working. It should treat price signals as evidence. It should review reserves automatically. It should keep emergency power small.

That combination is harder than slogans on either side. Market purists will dislike the reserve. Administrative rationers will dislike price discipline. Incumbents will dislike scrutiny of historical advantage. New entrants will dislike hearing that a small first allocation is not a growth plan. But the registry's job is not to make scarcity painless. It is to make scarcity governable.

Governable scarcity also requires humility: every reserved block is a temporary compromise, not proof that the institution has solved the region's address problem.

The 2020 exhaustion moment was a boundary. Before it, policy could still imagine that conservation and need-based allocation were managing a declining pool. After it, LACNIC entered the constitutional economy of remainders. Every address held back has an opportunity cost. Every waiting-list promise has a political effect. Every transfer rule creates winners and losers. Every emergency reserve invites the question of who decides.

That question should be asked in the language of evidence rather than virtue. How much space is reserved, how quickly it moves, what applicants do after receiving it, and whether transfer rules are improving or worsening access are all answerable questions. A reserve defended only by good intentions will lose legitimacy as scarcity hardens. A reserve defended by visible trade-offs can remain a public tool even among members who disagree about its size.

Reserve policy is defensible when it answers those questions in public and under limits. It is dangerous when it hides them behind benevolent language. LACNIC's discipline problem is not that it has reserves. It is that reserves must continually prove they are serving the region rather than insulating the institution from the full consequences of scarcity.

Sources and Further Reading