The end of the freely available IPv4 pool did not make a regional internet registry less important. It changed the source of its authority. In the allocation era, the central bargain was easy to describe even when it was hard to administer. A registry held a common stock of unique numbers. Networks needed those numbers. Policy set rationing rules. Staff reviewed need, identity, efficient use, and compliance. Members could disagree about line-drawing, but the basic justification was intelligible: scarcity required a neutral institution to prevent waste, hoarding, and conflicting claims.
That bargain has largely expired for IPv4. LACNIC still administers a waiting list, recovered space can reappear, and IPv6 remains the long-term addressing architecture. But no serious network in Latin America or the Caribbean can plan its IPv4 future around timely fresh supply from the registry. For ordinary commercial, public-sector, and infrastructure planning, the old pool is gone. The registry's legitimacy therefore can no longer rest mainly on the fair distribution of new addresses. It now rests on a different institutional function: recognition.
Recognition sounds less dramatic than allocation. It is not. After exhaustion, the registry's most valuable public good is the maintenance of a record that others can rely on. A buyer wants to know that a transfer can settle. A seller wants to prove that a block is not trapped in documentary uncertainty. A lessee wants a visible responsibility path. A university or public agency wants old holdings regularised without being forced into a fictional modern origin story. An access provider wants route-origin certification and reverse DNS to survive account recovery, merger, payment friction, or a change of upstream. A bank, court, acquirer, customer, or counterparty wants to know that the official record is not merely a database entry but a dependable settlement layer.
This is the economics of post-exhaustion legitimacy. When a registry is no longer the principal source of new IPv4 supply, its unavoidable power comes from being the institution whose records make existing resources usable. That power is still real. It can raise or lower the cost of capital. It can make a transfer ordinary or uncertain. It can make a lease visible or push it into private ambiguity. It can protect a small operator from fraud or impose a documentation burden that only large firms can absorb. It can preserve operational continuity during a dispute or turn account administration into leverage over routing trust. It can help members move toward IPv6 while recognising that IPv4 dependence has not disappeared.
The legitimacy test is therefore narrower and harder than the old one. LACNIC must be strict about truth, identity, authority, security, and continuity. It should verify who controls a resource, whether a transferor is authorised, whether a recipient satisfies a clear rule, whether a block is disputed, whether an account defect is curable, whether a lawful order requires action, and whether RPKI or reverse DNS can safely continue. But it should be restrained about broader economic preference. It should not use registry discretion to express dislike of leasing, discomfort with high prices, nostalgia for original use, suspicion of foreign counterparties, impatience with IPv4 demand, or a general wish that the market had moved faster to IPv6.
That distinction matters more in the LACNIC service region than a generic model suggests. Latin America and the Caribbean are not one economy. Brazil and Mexico bring scale, legal capacity, domestic professional networks, and large operator communities. Smaller Caribbean markets bring limited redundancy, small banking corridors, hurricane exposure, thin technical teams, and acute dependence on cross-border connectivity. Rural networks and small access providers may have little spare capacity for long evidence cycles. Public-sector and university networks may hold resources whose historical legitimacy is real but whose paperwork is scattered across reorganisations, public decrees, retired contacts, or old institutional names. Some members receive local-currency revenue while paying registry charges, equipment suppliers, transit providers, and transfer counterparties through foreign-exchange or correspondent-bank channels. Legal systems, languages, procurement rules, corporate forms, and administrative capacity vary widely.
A formally neutral registry rule can therefore become economically unequal if the institution does not watch how the rule behaves. The cost of proving authority, curing payment defects, translating documents, responding to staff questions, or waiting through a review is not the same for a national carrier and a small island provider. A large buyer can hire counsel and brokers. A rural operator may learn the rules only when a transaction is already urgent. A public university may be able to prove continuity, but not in the documentary style of a private company. The post-exhaustion registry must be neutral in outcome and attentive to unequal fixed costs.
This is not mainly a story about scarcity, transfer markets, mandate expansion, audit mechanics, reserves, or governance recovery. Those questions matter, but the narrower point is that exhaustion changes the economic foundation of registry legitimacy itself. LACNIC's income, power, member expectations, and public-interest claims now sit on recognition, continuity, settlement, due process, transfer and lease reality, and restraint of discretionary gatekeeping. That necessity is precisely why its authority must be more disciplined.
The allocation bargain cannot carry the post-exhaustion economy
The allocation-era bargain was built on the existence of a common pool. Because IPv4 addresses had to be unique and because demand exceeded supply, somebody had to decide which organisations received space, in what quantity, and under what conditions. Need-based review was not an arbitrary intrusion in that setting. It was the vocabulary of rationing. If every applicant had received whatever it requested, scarcity would have arrived faster and hoarding would have been rewarded. If price alone had allocated the pool, early cash-rich applicants could have outbid smaller networks, research institutions, public users, and new entrants. Need review, conservation, and community policy were the compromise.
LACNIC's exhaustion milestones changed the meaning of that compromise. The region entered late-stage IPv4 constraint years ago, and LACNIC announced in August 2020 that its last available IPv4 block had been assigned, moving the remaining supply problem into a waiting-list regime. That list remains administratively important. It is also economically modest. LACNIC's public explanations have described long waits for late applicants, small maximum assignments, and recovered blocks that may require quarantine or reputational cleaning before they can be used with confidence. Those facts do not make the waiting list pointless. They show that it is a remnant of allocation, not a replacement for a functioning supply system.
Once the free pool disappears, the word "need" does not do the same work in every context. When LACNIC distributes recovered space from a waiting list, need review still has a rationing function. The registry is deciding who receives a scarce fragment of common stock. But when two private parties seek recognition of a transfer of already-issued space, the institutional question is different. The recipient is not asking LACNIC to give away remaining inventory. It is asking the registry to recognise a transaction subject to adopted policy, authority checks, dispute controls, payment rules, and operational-responsibility requirements. Importing the whole psychology of allocation into the settlement function risks turning verification into a market veto.
This shift is institutional as much as economic. In the old model, LACNIC could say that it was stewarding a limited pool for regional development. In the new model, much of its power comes from being the only regional recognition layer for resources that members already hold, buy, sell, lease, certify, delegate, recover, and regularise. The registry has become a bottleneck around records. A bottleneck can be legitimate when it is narrow, predictable, reviewable, and tied to the function that makes it necessary. It loses legitimacy when the bottleneck holder begins to judge the broader worthiness of transactions that markets, contracts, courts, customers, and public law are better placed to evaluate.
The point is not to romanticise the market. IPv4 transfers and leases can carry forged authority, compromised accounts, dirty reputations, shell entities, undisclosed disputes, mismatched responsibility, and outright fraud. A registry that recognised every request quickly would not be a settlement utility. It would be a weak control point. The post-exhaustion legitimacy test is not speed alone. It is whether LACNIC can distinguish risks that threaten the truth and continuity of the record from preferences that merely express an allocation-era view of how scarce addresses ought to be used.
That distinction should be the governing theory. The registry is legitimate when it asks whether the holder is real, the signer is authorised, the resource is eligible, the block is disputed, the account is recoverable, the payment problem is material, the public contacts are accurate, the operational services can continue, and a clear adopted rule applies. It is on weaker ground when it asks, explicitly or by implication, whether the buyer deserves the addresses, whether the seller is too financial, whether the price is unattractive, whether a lease is morally suspect, whether the space should remain in a preferred geography, or whether IPv4 dependence should be discouraged by making recognition harder.
The old allocation vocabulary becomes especially dangerous because it is morally comfortable. Conservation, fairness, regional development, and stewardship are good words. They helped explain why private institutions could administer resources with public infrastructure effects. But good words can outlive the economic setting that gave them discipline. After exhaustion, the registry's moral authority depends less on deciding who receives new supply and more on ensuring that existing supply can be identified, transferred, certified, delegated, and disputed under rules that members can understand. The legitimacy of rationing cannot simply be carried over into the legitimacy of settlement.
There is also a revenue implication. In the allocation era, membership growth, address holdings, and service fees could be explained partly by the costs of managing distribution. After exhaustion, members still pay because the official record remains necessary. The relationship becomes more like a utility relationship: members fund uniqueness, recognition, certification, reverse DNS, support, policy administration, and continuity. Utility income is legitimate when it funds reliable service and prudent resilience. It becomes suspect when compulsory recognition is treated as broad economic planning authority.
The post-exhaustion bargain is therefore not a smaller version of the old bargain. It is a different bargain. LACNIC should be stricter about evidence where evidence protects the ledger, and less discretionary where discretion merely re-enacts allocation morality. It should make the record more complete, not more judgmental. It should make formal settlement easier to trust, not harder to approach. The registry remains a steward, but the object of stewardship has changed: not a stock of free addresses, but the reliability of recognition after the stock has gone.
Recognition is the new scarce public good
In a post-exhaustion registry, finality is a productive input. A block whose holder is recognised, whose contacts are current, whose account is in good standing, whose reverse DNS is stable, whose RPKI authority is clear, whose transfer history is coherent, and whose documentary chain can survive diligence is worth more than the same block caught in uncertainty. The address count may be identical. The economic resource is not.
Recognition lowers transaction costs. A buyer can close with fewer conditions. A seller can resist a discount. A lender can understand what the borrower controls. A public body can prove continuity after reorganisation. A university can move a network from one administrative unit to another without losing the history of its holdings. A hosting company can tell customers that reverse DNS and routing authority will not collapse during a corporate change. A Caribbean operator can restore service after a storm without discovering that an old contact problem has become a certification problem. A foreign counterparty can accept a Latin American or Caribbean block without needing private knowledge of local registry practice.
Finality does not mean irrevocability. Fraud, forged documents, court orders, account compromise, duplicate claims, and clear policy violations must be addressed. The point is that, once LACNIC recognises a state of the record, participants should be able to rely on it until a defined and reviewable reason changes that state. In markets for scarce resources, open-ended uncertainty is priced aggressively. Parties demand wider warranties, hold back payment, use brokers with specialised knowledge, or avoid formal settlement. A registry that preserves the last verified operational state except where a specific risk requires intervention lowers the fear premium.
The finality problem is especially acute in the LACNIC region because the evidence base is diverse. Some members can produce sophisticated corporate files, board resolutions, notarised documents, legal opinions, and experienced counsel. Others may be cooperatives, universities, municipal networks, family-owned access providers, public agencies, Caribbean carriers, rural wireless firms, privatised telecom assets, or cross-border infrastructure groups. A record may be legitimate even when its documentation does not look like a clean file from a large private company. Finality requires evidence discipline, not evidence monoculture.
One danger is that finality becomes available only to repeat players. A large operator that has completed previous transfers knows the timing, staff questions, payment details, documentation style, operational handoff risks, and informal expectations. A broker knows which documents tend to satisfy review and how to structure a request. A small holder transferring a block once in a decade learns under pressure, often while a commercial deadline is running. If LACNIC's requirements are not public enough, recognition becomes a private good sold by procedural specialists. The official ledger still exists, but knowledge about how to make it move becomes a source of rent.
Recognition finality should also apply to negative decisions. A denial that states the rule, the missing fact, the evidence considered, the cure path if one exists, the service consequence, and the review route improves the market. It lets future participants prepare. A vague denial multiplies risk beyond the rejected file. It makes every similar case harder to price. If LACNIC wants members to trust discretion, it should turn discretion into reasons.
The same principle applies outside transfers. Legacy records, waiting-list assignments, recovered space, account recoveries, RPKI authority, reverse DNS delegations, mergers, insolvencies, name changes, and public-sector succession all need settlement logic. Each category should have defaults: what is preserved, what can be changed, what evidence is needed, what service state continues, what is marked as disputed, and what can be appealed. Without such defaults, the registry asks members to trust case-by-case judgement. In a scarce-resource environment, that is too weak a public good.
Recognition also changes the moral status of old records. In an allocation economy, a poorly documented holding may look like an inefficient use of common stock. In a post-exhaustion recognition economy, the same holding may be an operational fact that customers, public services, research networks, and local infrastructure have depended on for years. The registry's task is not to pretend the past was perfectly documented. It is to make truthful continuity easier than neglect, while preventing hijack, forgery, and opportunistic claims. A rigid demand for modern title-style proof can punish institutions whose legitimacy is historical and public; an overly forgiving approach invites theft. The middle ground is published evidence categories and reasoned judgement.
Recognition is also where legitimacy meets regional capital constraints. An address block can be a means of raising cash, financing growth, supporting collateral discussions, or enabling consolidation. If settlement is unpredictable, the block is discounted. If account standing can freeze a transaction without a proportionate cure path, liquidity falls. If transfer timing varies widely without explanation, buyers price risk into the contract. If leases cannot be made visible through responsibility records, small networks may rely on private arrangements that the registry cannot see. In each case, the registry's process changes the economic value of the resource without allocating a single new address.
The strongest version of LACNIC's post-exhaustion legitimacy is therefore not that it can still allocate the last fragments fairly. It is that it can make recognition boring. Boring finality is valuable. It reduces the price of legal advice, the spread charged by brokers, the discount demanded by buyers, the fear of old records, and the temptation to hide operational use. A boring ledger is not a small thing. It is the settlement layer of a region's internet-number economy.
A regional ledger with unequal fixed costs
"Latin America and the Caribbean" is a useful institutional phrase and a misleading economic shortcut. A single registry serves large continental markets, small island economies, rural networks, national carriers, public-sector systems, universities, local hosters, data centres, research networks, global infrastructure groups, cooperatives, family-owned providers, and operators with very different access to law, finance, language, and technical labour. The record may be regional; the cost of using it is not uniform.
Brazil and Mexico illustrate the force of scale. Large markets tend to produce dense operator communities, domestic counsel, policy participants, technical associations, data-centre demand, cloud investment, and repeated interaction with the registry. Scale gives members more chances to learn the system and absorb mistakes. That is not improper. The risk is that procedures shaped around large-country capacity become the assumed norm. A document requirement that is routine for a major carrier may be burdensome for a small Caribbean provider. A policy discussion regular participants can follow may be expensive for operators outside the main language or meeting circuits.
The Caribbean presents a different map of dependence. Many island networks operate in small markets with limited upstream diversity, expensive redundancy, exposure to hurricanes and other disruptions, and banking paths that may depend on correspondent relationships outside the country. A modest address block can support hotels, public offices, clinics, schools, local hosting, emergency communications, and small-business customers. The block may be small by global market standards and central to local continuity. A delay in account recovery, transfer recognition, reverse DNS update, or RPKI change can become a service problem rather than a paperwork inconvenience.
Rural and smaller access providers face another set of fixed costs. They may have a small engineering staff, limited legal support, and little experience with transfer documentation. They may depend on upstream providers that can change terms quickly. They may use CGNAT, leased space, or small acquisitions to bridge customer demand. The cost of a long evidence cycle is not just the staff time spent answering questions. It is the customer growth deferred, the capital locked in escrow, the equipment plan delayed, and the bargaining power lost to larger firms that already hold addresses.
Public-sector and university networks add historical complexity. Early internet capacity in the region often involved universities, research bodies, public utilities, ministries, national telecom structures, and publicly linked projects. Over decades, ministries split, state enterprises were privatised, university departments changed names, research functions moved, and original contacts retired. The current operator may be legitimate, yet the proof chain may be scattered across public notices, rectorate decisions, government acts, old letters, procurement files, and institutional memory. A registry that lacks evidence categories for such cases will either under-verify, inviting fraud, or over-verify, imposing a discount on public-interest infrastructure.
Currency and payment friction are also part of the record economy. Some members receive revenue in local currencies while paying registry charges, transfer costs, transit, equipment, software, and foreign services in dollars or through cross-border banking channels. Inflation can change the burden between invoice and payment. Foreign-exchange rules can delay a wire. Intermediary banks can deduct charges, leaving a short receipt even when the payer intended to pay fully. Public procurement cycles can make a late invoice different from private delinquency. A disaster can shift cash toward immediate repairs. LACNIC cannot eliminate these conditions. It can avoid treating all payment friction as the same moral category.
Legal diversity matters as well. Corporate succession, mergers, insolvency, public ownership, non-profit governance, municipal authority, cooperatives, trusts, and regulated telecom obligations may look different across jurisdictions. A standard form can help, but it cannot replace a theory of acceptable evidence. Registry staff should not be asked to become judges of every national legal question. Nor should members be forced to translate every local legal reality into a narrow corporate template. The institution needs enough legal discipline to prevent fraud and enough regional adaptation to avoid punishing legitimate forms.
Language is not only a matter of politeness. Spanish, Portuguese, and English are part of due process. A transfer instruction, fee rule, account-standing warning, RPKI notice, reverse DNS procedure, evidence guide, or policy proposal can be formally translated and still practically unequal if examples, timing, informal explanations, or operational nuance cluster in one language. English-speaking Caribbean members should not have to infer registry consequences from Spanish or Portuguese debate culture. Portuguese-speaking members should not be treated as an appendage to Spanish-language discussion. Spanish-speaking members should not discover English-only market practice after the fact.
These regional differences do not imply that LACNIC should lower standards. They imply that standards should be intelligible, proportionate, and adaptable to real evidence. A small operator should not get a pass on authority proof because it is small. But it should know exactly what proof will satisfy the registry and how to cure a defect. A public university should not be allowed to rely on vague institutional memory. But it should have a recognised path for showing public continuity. A Caribbean firm should not be exempt from fees. But a bank-fee shortfall should not be treated like abandonment. Equal rules require unequal attention to how proof, payment, language, and delay costs land.
The economic lesson is simple. A registry can impose fixed costs without noticing because each requirement looks reasonable on its own: a signature, notarisation, translation, waiting period, renewed invoice, supplemental explanation, cautious legal review, service handoff, or appeal path. For a large member, the bundle is administration. For a small or historically complex member, it can be a tax on formalisation. Post-exhaustion legitimacy depends on making the formal path cheaper than avoidance; otherwise members route around it through private leases, stale contacts, unrecorded operating arrangements, and dependence on larger counterparties.
Waiting lists preserve fairness, not supply
The waiting list is the most visible remnant of the allocation era. It deserves careful administration because it is still a channel through which LACNIC distributes recovered IPv4 space. It also deserves a modest theory. A waiting list does not recreate the old free pool. It cannot justify broad discretionary control over the existing address economy.
LACNIC's late-stage IPv4 arrangement illustrates the point. The last available block was assigned in August 2020, and the waiting-list regime began. The remaining possibility is recovered or returned space, generally rationed in small quantities and subject to conditions. LACNIC's public materials have described small maximum assignments and very long waits for those near the end of the list. Recovered blocks may have spent time in quarantine, yet recipients can still face reputation problems if addresses have been filtered, blacklisted, or misused before. These details show the waiting list's economic character. It is a fairness mechanism for scarce fragments, not a growth strategy.
A wait measured in many years cannot be the main supply plan for a network. A small maximum block cannot support a major access expansion, a serious hosting platform, a carrier consolidation, or a broad public-service digitisation programme. Recovered space may require cleaning, which adds technical cost and uncertainty. The waiting list can help a new member, a transition need, a small operational gap, or a symbolic access principle. It cannot carry the full legitimacy of a regional registry after exhaustion.
This matters because residual allocation can preserve old authority narratives. If LACNIC still allocates tiny amounts of recovered space, it may be tempted to treat all IPv4 administration as if it were still rationing a common pool. That temptation is understandable and wrong. The waiting list should be managed with fairness, transparency, and discipline. It should not become the conceptual tail that wags transfer recognition, lease responsibility, account recovery, or legacy regularisation.
Recovered-space policy also creates reputational questions. An address block is not simply a number range. It carries history in filters, blacklists, reputation systems, abuse records, customer memories, and operational assumptions. A recovered block may be formally available and still costly to use. If recipients are warned that cleaning is their responsibility, then the registry should be clear about what it does and does not know. Quarantine is useful. It is not a warranty. Post-exhaustion legitimacy requires honest disclosure of usability, not merely formal allocation.
Queue administration should therefore be auditable. Members should be able to see, in aggregate, how many approved requests wait, how long different parts of the queue have waited, what sizes are assigned, how much space is recovered, how much is held back for review, how often recipients decline or fail to complete, how often reputation issues are reported, and what eligibility problems recur. Such reporting does not need to expose private member files. It would help the community understand whether the waiting list is a working fairness channel or mostly a symbolic remnant.
The waiting list also interacts with member expectations. A small network may join the queue because it has no better path. A public institution may treat the possibility of recovered space as evidence that the registry can still support growth. A policymaker may point to the list as proof that equitable allocation remains alive. If the practical wait and usable supply are very limited, LACNIC should say so plainly. Clear expectations are part of legitimacy. Hope is not a supply policy.
Nor should recovered space become a reason to discourage transfer liquidity. It may be appealing to say that the registry should keep addressing needs inside a public queue rather than rely on a market. But the volumes and timing do not support that ambition. If the market is where most usable IPv4 capacity can move, the registry's public-interest role is to make settlement safer and more transparent, not to pretend that a residual allocation channel can substitute for it. Weakening formal transfers in the name of residual fairness would hurt the very operators that need usable capacity soon.
The same point applies to returned space. Members may return resources for public reasons, because they no longer need them, because of consolidation, or because old records are cleaned up. The registry should welcome and administer returns. It should not build a general theory of institutional power on the hope that returns can reverse exhaustion. The economics of IPv4 after exhaustion are dominated by already-issued space. The legitimacy of LACNIC must be built where the addresses actually are.
The proper theory is narrow. Waiting lists preserve a principle of fair access to recovered fragments. They support transparency about the last bits of common stock. They can prevent recovered space from being allocated through favouritism. They can help small needs where luck and timing allow. They do not revive the allocation-era mandate. After the well runs dry, a fair bucket line is valuable, but the main institution becomes the land registry around wells already dug.
Transfers, leases, and the line between verification and veto
Transfers are the clearest test of post-exhaustion legitimacy because they expose the difference between recognition and allocation. In a transfer, LACNIC is not deciding whether to issue fresh space from a common pool. It is deciding whether the official record should recognise a change involving already-issued resources. That decision still requires policy. It still requires authority checks, payment rules, eligibility conditions, fraud controls, and operational handoff. But the direction of scrutiny should be different.
The registry should verify that the seller or transferor is the recognised holder, that the signer is authorised, that the block is eligible, that the recipient is a real organisation or otherwise meets the applicable rule, that no unresolved dispute prevents settlement, that account standing issues are classified, and that RPKI, reverse DNS, public contacts, and abuse responsibility can be aligned. Those are registry questions. They protect the truth and continuity of the record.
The registry should be wary of questions that turn settlement into economic preference. Is the buyer's business model attractive? Is the price too high? Is the seller monetising a resource too aggressively? Is the transfer moving space out of a favoured geography? Is leasing involved? Does the transaction reveal that IPv4 remains commercially important? Those may be topics for market participants, governments, competition authorities, tax agencies, customers, or public debate. They are not natural grounds for discretionary registry veto unless an adopted policy clearly makes them relevant.
Leasing is more uncomfortable than transfers because it separates recognised holding from operational use. It can make responsibility less visible. It can support speculation, short-term arbitrage, or evasive behaviour. It can also solve real problems. A small operator may need addresses for a period but lack capital to buy. A customer project may require IPv4 during a transition. A hosting provider may need burst capacity. A holder may monetise unused space while retaining long-term plans. A lessee may be more willing to formalise if the registry provides a responsibility path than if the only official message is disapproval.
Post-exhaustion legitimacy does not require LACNIC to celebrate leasing. It requires the registry to recognise the record problem leasing creates. If operational use is separated from registered holding, abuse contacts, RPKI authority, reverse DNS, and accountability can become unclear. Ignoring leasing because it is untidy does not make the internet safer. It makes responsibility harder to see. The registry's comparative advantage is not moral commentary. It is making authority and responsibility legible.
The right approach is a responsibility model anchored in the recognised holder. The holder should remain accountable to the registry for the resource relationship. The operational user should be visible enough for abuse handling, reverse DNS coordination, routing-security practice, and emergency contact where appropriate. The registry should not become a rent judge or private contract enforcer. It should define what information is needed so that delegated use does not undermine the public record. That approach preserves accountability without forcing the registry into price control or business-model approval.
Transfers and leases also reveal the danger of hidden need review. If recipient justification is required by adopted policy, it should be narrow, objective, and predictable. A recipient should know what evidence satisfies the rule. Review should not become a broad inquiry into whether the recipient's growth plan is virtuous. The more subjective the standard, the more valuable insider knowledge becomes and the more cautious buyers will be. Subjective need review does not eliminate demand. It converts demand into procedural risk.
Inter-regional transfers add another layer. LACNIC must coordinate with other registries, each with its own policy environment and operational practice. Cross-regional movement can raise concerns about regional development, foreign buyers, and resource outflow. Those concerns should be handled through clear community policy, not staff improvisation. If the region wants to restrict certain movements, it should say so openly and accept the economic costs. If the policy allows movement, settlement should not be burdened by informal discomfort.
Small transfers deserve special attention. A fixed documentation burden falls harder on a /24 than on a large block. A fixed fee, legal review, translation requirement, or timing uncertainty can make a small transaction uneconomic. Yet small transactions may matter most to small operators. If formal settlement is too costly, parties may rely on upstream arrangements, private leases, stale records, or informal routing. The ledger becomes less complete exactly where the registry should want more truth.
Transfer handoff is not complete when the registry updates the holder field. RPKI authority, reverse DNS, public contacts, abuse records, account credentials, and operational responsibility all have to move or be preserved in a predictable state. Buyers should know whether route origin authorisations can be created immediately, whether old authorisations must be removed, whether reverse DNS changes require a separate review, and what happens if the seller is slow. Sellers should know when their responsibility ends. Lessees should know what the holder retains. A settlement utility publishes these consequences.
The market will not be made virtuous by making official settlement opaque. Fraudsters and speculators can exploit uncertainty. Legitimate small operators are the ones most likely to be deterred by cost and delay. The registry's best defence is to make formal recognition the safest path: strict authority checks, clear responsibility, predictable service handoff, proportionate fees, reasoned denials, and aggregate reporting. If participants trust the formal path, more of the address economy becomes visible. If they fear discretionary gatekeeping, the address economy moves into shadows the registry cannot govern.
Due process for asset-like records
Internet number resources are not ordinary property. They arise from a specialised coordination system, are subject to registry policy, and depend on uniqueness rather than physical possession. But after exhaustion, IPv4 holdings have asset-like economic effects. They can be bought, sold, leased, valued, financed, disputed, inherited through corporate succession, and priced into acquisition decisions. When registry decisions affect such interests, due process becomes part of legitimacy.
Due process need not mean court-like procedure for every file. A registry is not a judiciary. It must be able to move quickly against fraud, account compromise, forged documents, clear policy violations, or immediate security risks. But high-impact decisions should have a recognisable structure: notice, classification, evidence expectations, reasons, cure paths, service-state rules, and review. The more a decision affects transfer value, operational continuity, certification, reverse DNS, or account standing, the stronger the process should be.
Classification is the first discipline. A file should be understood as an ordinary transfer, inter-regional transfer, merger, acquisition, legacy regularisation, public-sector succession, account recovery, payment cure, suspected fraud, legal hold, dispute notation, RPKI authority change, reverse DNS delegation, lease-related responsibility update, contact correction, or enforcement action. Classification prevents a file from becoming a general referendum on a member's worthiness. It also tells the member what evidence applies.
Proportionality is the second discipline. A routine contact correction should not trigger transfer-level proof. A payment shortfall caused by bank fees should not have the same effect as abandonment. A disputed transfer should pause the disputed action, not unrelated resources, unless the risk spreads. A legacy regularisation should ask for continuity evidence, not a fresh allocation justification. A lease responsibility signal should improve abuse and operational accountability, not invite a broad judgment on rent. Proportionality is how caution avoids becoming capital control.
Preservation of the last verified state is the third discipline. When uncertainty appears, the registry should not rush to rewrite operational reality. It should preserve what is currently verified, restrict only what the risk requires, and create a path to resolution. This principle is essential for RPKI and reverse DNS, but it also applies to public registration data, account access, transfer review, and dispute notations. Preservation does not mean passivity. It means avoiding collateral damage while the contested fact is examined.
Reason giving is the fourth discipline. A denial, hold, restriction, or materially adverse decision should explain the rule applied, the decisive or missing fact, the evidence considered at a useful level of generality, the service consequence, the cure path if any, and the review route. Reasons can protect confidential detail and security-sensitive information. They should still be usable. If a member cannot tell what fact would change the outcome, accountability has failed.
Review is the fifth discipline. Revocation, long transfer holds, broad account restrictions, certification interruption, denial of legacy regularisation, or a decision that materially affects an operator's continuity should not rest only on the same staff chain that made the initial decision. Review need not be expensive or theatrical. It must be independent enough that members do not view litigation as the only remedy. For small operators, cheap review is more important than formal elegance.
Due process also protects staff. Published categories, evidence expectations, and service-state rules give employees a defensible basis for resisting pressure from governments, creditors, competitors, influential members, or angry customers. Staff can point to the rules: this is a legal hold, a disputed authority claim, a payment cure, a fraud lock, or a service preservation state. Procedure is a shield as well as a constraint.
The Latin American and Caribbean context makes due process more than a legal abstraction. Members operate under different legal systems, languages, currency conditions, and administrative capacities. Some can escalate quickly through counsel. Others cannot. Some can obtain corporate documents in days. Others depend on public agencies, historical files, or foreign banks. A process that relies heavily on informal staff judgement may work for members that know the institution and fail for members that do not. Published procedure is a substitute for insider familiarity.
Due process should extend to account standing. Fee collection is legitimate and necessary. But account consequences should distinguish bad faith, abandonment, ordinary lateness, bank-fee short receipt, foreign-exchange delay, public procurement cycles, disaster hardship, disputed invoice, and administrative error. The service effect should be proportionate to the category. A registry that treats all arrears as equivalent may be simple to administer, but it will not be economically neutral in a region with uneven payment channels.
The point is not to slow everything down. Good process can speed settlement because parties know what is required. It reduces back-and-forth, surprise, escalation, and fear. It also makes the registry's discretion smaller and more trusted. Post-exhaustion legitimacy depends on the ability to say: the institution is powerful, but it is powerful through defined categories, not personal judgement; it can stop fraud, but it cannot improvise market policy; it can enforce rules, but it must explain how the rule reached the result.
RPKI, reverse DNS, and continuity as institutional capital
The registry's record is not only a list of holders. It is connected to operational trust. RPKI, reverse DNS, public contacts, and abuse responsibility turn recognition into routing confidence, naming continuity, and accountability. After exhaustion, these services make registry decisions more consequential. A dispute or account defect may not merely delay paperwork. It may affect how networks decide whether a route is authorised, whether mail systems trust a host, or whether abuse complaints reach the right party.
RPKI illustrates the stakes. Route origin authorisations help other networks decide whether a route is legitimate. Hosted RPKI lets members manage certification through the registry's system; delegated RPKI lets more sophisticated members operate their own certification authority under the hierarchy. These services reduce routing risk, but they also tie operational confidence to account status, authority verification, and service continuity. If a payment issue, disputed signature, merger review, or account recovery problem affects certificate management, the consequence may reach beyond the member's administrative file.
Reverse DNS is less fashionable and still economically important. Mail reputation, hosting platforms, diagnostics, security systems, customer logs, public-sector applications, and compliance processes can depend on reverse naming. A transfer that leaves reverse DNS unclear is not operationally complete. A lease that depends on slow cooperation from a holder creates service risk. A public network whose old contact has retired may discover that a technical delegation is tied to an obsolete account relationship. Reverse DNS is part of settlement, not an afterthought.
Abuse and operational contacts are equally central. Scarcity and leasing separate legal recognition from operational use more often. If the public record points to a holder that is not handling the traffic, abuse reports may fail. If a lessee has no visible responsibility path, the holder may face reputation risk for conduct it does not control directly. If LACNIC refuses to accommodate responsibility signals because delegated use is uncomfortable, it weakens the record. If it accommodates them without accountability, it invites evasion. The middle ground is a responsibility model that preserves holder accountability while making operational use visible enough to protect the internet.
These services require a continuity firewall. Members should know what happens to RPKI, reverse DNS, contacts, account access, transfer review, and public registration data under different states: suspected fraud, compromised account, forged transfer attempt, court order, competing authority claim, curable payment defect, merger review, legacy regularisation, public-sector succession, disaster recovery, and ordinary administrative correction. Each state should have a default service consequence. Without defaults, operational trust depends on ad hoc judgement.
The default should be continuity of the last verified operational state, with defined exceptions for fraud, security, law, and genuine competing claims. A compromised account may require immediate locks. A forged transfer attempt may require suspension of the request and preservation of evidence. A court order may require specific restraint. A disputed authority claim may require maintaining the last verified state while authority is checked. A curable payment shortfall caused by bank fees should not have the same blast radius. An incomplete document in a merger file should not destabilise existing route-origin trust unless the document directly affects authority.
Transfer handoff deserves special attention. A recognised transfer is not fully settled for the market until operational services are aligned. Buyers should know when they can create ROAs, whether existing ROAs remain valid during transition, how old certificates are withdrawn, whether reverse DNS changes are immediate or staged, what contacts are visible, and how abuse responsibility changes. Sellers should know when their operational responsibility ends. Lessees should know whether the holder retains certificate control. The registry does not need to guarantee every private outcome. It should publish the service consequences of the recognition it provides.
Disaster resilience gives the continuity firewall moral weight. Caribbean operators may need rapid routing or contact changes after hurricanes, facility damage, cable cuts, or upstream failure. Rural networks may need emergency adjustments during outages. Public-sector systems may need continuity during administrative transition. In such moments, the registry should not discover its service-state rules for the first time. It should already know who can act, how authority is verified, what is logged, what continues, what is restricted, and how customers are protected from collateral damage.
Continuity also protects LACNIC from external pressure. If a government, competitor, creditor, complainant, or influential member asks for broad action, staff can point to the service-state rules. They can implement lawful and policy-based restraints without turning a narrow dispute into a regional confidence event. This is particularly important after exhaustion because the value of operational trust objects is larger than their direct technical footprint. RPKI and reverse DNS are part of the economic constitution of the ledger.
There is a temptation to use operational services as leverage because they are powerful. A registry that can restrict certification, delay reverse DNS, or hold account changes has practical influence over members. That leverage should be used only where it is tied to the service risk itself. RPKI should not become a tool for expressing discomfort with a transfer. Reverse DNS should not become collateral for an unrelated fee dispute unless the account state genuinely signals abandonment or loss of authority. Public contacts should not be frozen to punish a member for a policy disagreement. Operational trust is too important to be used as a general enforcement stick.
The post-exhaustion registry earns legitimacy by making continuity predictable. It can still act decisively against security threats and false records. But when the risk is documentary, curable, or unrelated to the operational service, preservation should be the bias. Networks need to keep routing, naming, diagnosing, and responding while the record is corrected. A registry that understands this will be trusted not because it never intervenes, but because it intervenes with narrow purpose.
Fees, reserves, and captive-member restraint
A registry utility must be solvent before it can be neutral. LACNIC needs secure systems, staff, member support, legal capacity, translation, RPKI and DNS infrastructure, transfer review, account recovery, incident response, audits, governance support, and reserves. A fragile registry would be bad for every member, especially small ones that cannot route around institutional failure. The post-exhaustion critique is not that fees are illegitimate. It is that compulsory fee power requires clearer restraint after the registry's role shifts from allocation to recognition.
Members cannot choose a competing LACNIC for the same regional number-resource relationship. That practical exclusivity makes fees resemble utility charges more than ordinary vendor prices. A fee may be modest compared with the market value of IPv4 and still large compared with a small operator's cash flow. A reserve may be prudent for continuity and still excessive if its target is not explained. A legal budget may be necessary to defend the record and troubling if it defends expansive discretion. A meeting, training, or development budget may support regional capacity and still require evidence that it reaches those whose fees fund it.
The region's payment conditions make restraint concrete. A member may pay from a volatile local currency into a foreign account. Intermediary banks may deduct charges. A public university may wait for budget approval. A municipal network may not understand why a registry invoice has operational urgency until a service consequence appears. A Caribbean firm may face de-risking, slow wire paths, or correspondent-bank friction. A disaster may shift cash toward immediate repairs. None of this means LACNIC should tolerate chronic nonpayment. It means account-standing consequences should distinguish bad faith, abandonment, short receipt, bank delay, foreign-exchange friction, public procurement, disaster hardship, disputed invoice, and ordinary error.
Account standing is a powerful lever because it can affect recognition. If both parties to a transfer must be current, a curable payment problem can freeze a transaction. If a renewal deadline interacts with a transfer, billing timing can alter bargaining power. If a small holder must pay before it can monetise a block, the registry's calendar affects liquidity. If an invoice shortfall caused by bank fees creates a service restriction, payment plumbing has become an operational risk. These outcomes may be acceptable in some cases. They should be classified and proportionate.
Fee schedules can also influence formalisation. Transfer fees recover cost and deter frivolous filings. Initial payments can signal seriousness. Category changes can align fees with holdings. But a cost stack that is trivial for a large buyer can deter a small transfer or legacy cleanup. If a /24 transaction faces a fixed administrative burden, the percentage cost is far higher than for a large block. If a recipient fears losing a payment because review standards are uncertain, it may avoid the official route. If formal settlement is too expensive or unpredictable, the market moves toward leases, upstream dependence, and stale records.
Reserves should be treated like insurance. Members should understand the target, the risks covered, the drawdown rules, the replenishment logic, and the line between core continuity and broader ambition. A continuity reserve for cyber incidents, service interruption, legal shocks, bank problems, vendor failure, and disaster response is sensible. An unexplained accumulation looks like compulsory saving by a captive membership. The difference is disclosure and member control.
Legal costs need the same category discipline. Counsel used to prevent fraud, preserve the last verified record, respond to lawful orders, protect data, and maintain RPKI or reverse DNS continuity protects the utility. Counsel used to defend broad discretion, resist useful reasons, or stretch the registry's role into market preference is a different cost. Confidentiality can protect active matters without hiding aggregate categories. Members should be able to see whether legal spending is reducing registry risk or entrenching institutional power.
The development mission complicates the budget. LACNIC has legitimate regional functions beyond a narrow database: training, IPv6 support, routing-security capacity, research, participation, and technical development. These may be valuable, particularly where national resources are limited. But broad mission language should not blur the fiscal distinction between core recognition services and optional or strategic programmes. If members fund capacity-building, the budget should show it. If reserves protect continuity, the reserve policy should show it. If legal costs defend the ledger, the category should show it. Fiscal clarity is a limit on mission creep.
Payment restraint does not require softness. A serious registry must collect fees, prevent abandonment, and ensure that members carry their share of common costs. Restraint means visible categories, cure paths, proportional consequences, and a presumption that operational services should not be destabilised by defects unrelated to authority, security, law, or record truth. A late invoice is not a false record. A bank-fee shortfall is not a hijack. A public procurement delay is not abandonment. The remedies should reflect those differences.
In the legitimacy transition, fees and reserves are not a side topic. They show whether LACNIC understands itself as a settlement utility funded by members or as an institution entitled to expand because its work is important. Importance is not a blank cheque. The more unavoidable the registry relationship, the stronger the case for fiscal humility. Members are more likely to trust a registry that can explain not only what it charges, but why the charge is tied to continuity rather than institutional appetite.
Member trust in a multilingual, unequal region
Community process was easier to defend when the main problem was fair access to new supply. Members and participants debated allocation policy, conservation, eligibility, and technical coordination. After exhaustion, the same community process governs questions with direct effects on existing resource value: transfers, waiting lists, recovered space, need review, account standing, fees, RPKI, reverse DNS, lease responsibility, legacy regularisation, and dispute handling. Participation has become economic infrastructure.
LACNIC has a broad region and a multilingual community. Open lists, meetings, assemblies, elections, policy forums, and board oversight matter. But openness is not enough. Participation has fixed costs. A large operator can assign staff to track policy. A small Caribbean provider may read messages after outages, billing, and customer support. A Brazilian or Mexican participant may have local peers and national channels. A rural operator may have no comparable context. English-speaking members may find that much practical nuance lives elsewhere. Portuguese and Spanish communities may not receive identical cues at identical speed. Silence is not always consent.
Member trust after abundance should therefore be measured by more than the existence of a forum. It should ask who participates, who is absent, which categories of members bear the cost of a proposed rule, and whether implementation data returns to the community. A policy that affects transfer finality should be accompanied by metrics on timing, denials, evidence requests, payment holds, appeals, and long-tail cases. A fee change should report incidence on small members, payment friction, and reserve movement. A rule affecting RPKI or reverse DNS should report service effects. A waiting-list rule should report queue behaviour and recovered-space quality. Policy should have aftercare.
Elections and board oversight also change meaning after exhaustion. Directors are not merely association stewards. They oversee an institution whose record affects asset-like holdings, transfer settlement, certification, reverse delegation, budget restraint, legal posture, and service continuity. They should understand the difference between a member community and an affected market, between policy implementation and staff discretion, between core ledger utility and broader development activity, and between security enforcement and commercial morality. A board that cannot ask those questions will default to institutional comfort.
Conflicts of interest should be treated as normal and managed, not denied. In a small expert community, people may be operators, consultants, brokers, large holders, public officials, vendors, policy advocates, or employees of firms affected by transfer and leasing rules. Expertise often comes from exposure. The legitimacy problem is not that interested people speak. It is that interests may be undisclosed when decisions affect scarce-resource economics. Disclosure and recusal rules protect both the individuals and the institution.
Member control also requires reasoned administration. If staff can delay, deny, or restrict high-value actions without usable reasons, elections and policy lists cannot fully discipline the institution. Members need aggregate evidence of how rules behave: transfer timing, account holds, payment classifications, denial reasons, appeal outcomes, service restrictions, RPKI incidents, reverse DNS delays, legacy regularisation queues, and public-sector succession cases. Without these, members debate the text but not the cost.
Multilingual equality should be operational, not symbolic. Critical materials should be equally clear in Spanish, Portuguese, and English: transfer instructions, evidence categories, account-standing consequences, payment guidance, RPKI and reverse DNS service states, appeal procedures, fee changes, reserve policies, and policy summaries. Meeting records should capture trade-offs, not only decisions. Members should not need informal access to regular participants to understand what changed. The cost of comprehension is part of the cost of control.
Regional adaptation should not be confused with regional exceptionalism. LACNIC does not need a different standard of truth for every country. It needs a shared standard that can recognise different kinds of proof. It does not need to subsidise every small operator through registry discretion. It needs to know when fixed procedural costs make formal compliance less likely. It does not need to turn public universities into a privileged class. It needs a defensible path for public continuity evidence. Adaptation is not softness; it is accuracy.
Trust also depends on the registry's willingness to state limits. Members are more likely to accept strict verification when they know the registry will not use the same file to judge their business model. They are more likely to accept fees when they can see reserve targets and programme categories. They are more likely to accept delay when delay reasons are measured and reviewable. They are more likely to participate when language and timing do not make them outsiders. Trust is not produced by institutional reputation alone. It is produced by repeated proof that power has boundaries.
Post-exhaustion member control is therefore not nostalgia for a town meeting. It is a set of checks that make registry power legible: clear rules, usable reasons, conflict disclosure, cost reporting, multilingual access, implementation metrics, and a board that reduces the prize of discretion. The more LACNIC behaves like a utility, the less dramatic governance needs to be. The more it behaves like a market planner, the more valuable control of the institution becomes.
Auditability without exposure
Transparency is often invoked too easily. Posting documents is useful, but auditability is harder. Auditability means a member, counterparty, board, or community participant can reconstruct how a recurring decision type moves from fact to rule to result without breaching legitimate confidentiality. In a post-exhaustion registry, auditability is part of the value of the resource. It lowers the discount attached to uncertainty.
LACNIC should not publish private contracts, identity documents, security details, confidential legal files, or sensitive fraud indicators. That would damage trust. But confidentiality does not justify opacity about categories, timing, reasons, and outcomes. The market does not need to know the price in every transfer. It does need to know how long different types of transfers take, why they are denied or delayed, how many are paused for payment, how many require additional documents, how many involve inter-regional coordination, how often RPKI or reverse DNS handoff is delayed, and how appeals change outcomes.
The denominator matters. A public transfer log shows completed transactions. It does not show requests withdrawn because evidence burden was too high, cases that failed recipient justification, files delayed past commercial deadlines, transfers blocked by account standing, or applicants deterred by uncertainty before filing. Without a denominator, the market prices risk from rumour. Repeat players may know more. Small operators know less. Opaque systems create private spreads.
Timing should be reported in distributions, not only averages. Median processing time is useful, but the long tail is where capital freezes. A transfer that usually closes in weeks but sometimes takes months is a different economic object from one whose outer bound is clear. LACNIC should separate applicant response time, registry review time, payment time, inter-registry time, legal hold time, document supplement time, and post-recognition operational handoff. A slow applicant and a slow institution are not the same problem. A payment delay and a policy hesitation are not the same risk.
Denial and delay reasons should be categorised. Authority not proven. Corporate succession incomplete. Public-sector evidence insufficient. Recipient justification failed. Resource disputed. Account not current. Payment short. Intermediary bank issue. Court order. Suspected fraud. Account compromise. Translation issue. Legacy chain unclear. RPKI handoff pending. Reverse DNS delegation pending. These categories can preserve confidentiality while giving members and counterparties a map of the system.
RPKI and reverse DNS need operational metrics. How often are certificate actions delayed by account states? How many authority recoveries occur? How many reverse DNS updates lag after transfer? How many emergency changes are made? How often are services preserved during disputes? How often are they restricted? These metrics need not expose security-sensitive detail. They should show whether operational trust objects are stable.
Payment categories should be visible as categories. Late payment is too crude. Members should know how often arrears are cured, how often short payment results from bank fees, how often foreign-exchange or public-procurement issues appear, how often disaster hardship is invoked, and how often payment states affect transfer or service actions. Such reporting would not excuse nonpayment. It would show whether fee policy is funding continuity or creating avoidable friction.
Legacy and public-sector regularisation should also be measured. How many old-record cases are pending? How many involve universities, public bodies, mergers, dissolutions, unavailable contacts, or competing claims? What evidence gaps recur? How long do they take? Which cures work? Regularisation improves the ledger, so the registry should know whether its own evidence design encourages or discourages it.
Auditability has a deterrent effect inside the institution. Staff are less likely to drift into subjective market judgement if decision categories must later be reported. Boards are less likely to approve vague policies if implementation effects will return. Members are less likely to rely on accusation and rumour if aggregate evidence exists. Courts and regulators are more likely to trust a registry that can show narrow, consistent action. Auditability is not anti-registry. It is institutional insurance.
The standard should be simple: every high-impact recognition decision should leave a traceable explanation, and every recurring category of such decisions should produce aggregate statistics. Trust should not depend on whether members like the people currently in office. It should depend on whether the system can be inspected without exposing what should remain private.
IPv6 development without IPv4 moralism
IPv6 is the long-term answer to address expansion. It is not a short-term escape from the post-exhaustion legitimacy problem. LACNIC should promote IPv6 deployment, training, operational knowledge, public-sector adoption, and routing security. It should also be honest that dual-stack operation, carrier-grade NAT, legacy customer equipment, enterprise systems, government applications, hotel networks, payment platforms, and global reachability keep IPv4 economically relevant. Treating IPv4 demand as a moral embarrassment will not make it disappear. It will make registry decisions less realistic.
Carrier-grade NAT illustrates the point. CGNAT lets operators stretch limited IPv4 space across many customers. It can delay purchases, reduce immediate scarcity, and support transition. It also imposes equipment costs, logging burdens, troubleshooting complexity, abuse attribution problems, application issues, and customer dissatisfaction. For small operators, the capital and operational burden can be serious. For public-sector networks, procurement and compliance can be awkward. For law-enforcement and abuse response, shared addresses complicate identification. CGNAT is a tool, not a free substitute for recognised address capacity.
IPv6 deployment is similarly uneven. A backbone may support IPv6 while customer devices, enterprise firewalls, industrial systems, government applications, or foreign counterparties remain IPv4-dependent. A network may carry IPv6 traffic and still need IPv4 for customer acquisition. A country may improve IPv6 statistics while small operators remain constrained by equipment, training, upstream practice, or customer premises devices. Regional averages can hide local bottlenecks. A registry that uses IPv6 progress as a reason to discount IPv4 settlement problems confuses horizon with present reality.
Development language is attractive because LACNIC's region contains real development gaps. Rural connectivity, public services, small-island resilience, technical capacity, routing security, IPv6 readiness, local hosting, and regional infrastructure all matter. But development language is elastic. It can justify training and measurement. It can also justify hidden preferences over who should obtain, sell, lease, or monetise IPv4. The first use is legitimate. The second is mandate expansion.
The boundary should be explicit. LACNIC can support IPv6 education without punishing lawful IPv4 transfers. It can improve routing security without using RPKI as leverage in unrelated disputes. It can help small operators without making every buyer's business model a public-interest hearing. It can publish research and hold meetings without turning broad regional goals into staff discretion over settlement. It can encourage recovered-space fairness without discouraging existing-space liquidity. It can be developmental in public goods and narrow in recognition.
This distinction matters because broad discretion tends to hurt the members it claims to protect. If transfers are slowed to prevent addresses leaving poorer markets, small sellers may receive lower prices and small buyers may find fewer counterparties. If leasing is stigmatised to discourage speculation, small operators may lose the only financing path they can afford. If IPv4 demand is shamed to promote IPv6, customers still needing IPv4 may move to larger incumbents that already hold enough space. If need review becomes subjective to protect regional values, repeat players with policy staff learn to speak the right language and smaller firms pay the uncertainty cost.
Development policy belongs in visible programmes, measured support, transparent subsidies if members approve them, and public law where governments choose it. It should not be smuggled into recognition decisions. The registry's comparative advantage is the ledger: uniqueness, authority, provenance, certification, reverse delegation, account standing, and continuity. If it performs that function well, it lowers the cost of network development indirectly. If it expands into moral allocation, it raises the cost of development by making scarce inputs harder to use.
The IPv6 transition strengthens the case for settlement discipline. The transition period is long, uneven, and expensive. Operators need predictable IPv4 recognition while they deploy IPv6. They need leases, transfers, CGNAT, customer migration, and dual-stack strategies to coexist. LACNIC's legitimacy lies in keeping those choices recordable and safe, not in pretending the architectural answer has already solved the commercial problem.
The settlement utility test
The next phase of LACNIC's legitimacy will not be decided by one statement, election, fee schedule, or policy proposal. It will be decided by repeated behaviour in the places where allocation-era authority can quietly reappear as post-exhaustion discretion. The practical question is whether LACNIC behaves as a settlement utility or as a moral allocator.
A settlement utility verifies narrowly. It asks whether identity, authority, eligibility, payment, dispute status, and operational responsibility are clear enough to update or preserve the record. It defines the service consequences of each state. It publishes evidence expectations. It gives reasons. It preserves the last verified operational state unless fraud, security, law, or genuine competing claims require narrower restraint. It reports its own delays and denials. It funds continuity with restraint. It lets operators make economic choices within clear rules.
A moral allocator uses the same administrative points to express preference over who should hold, buy, sell, lease, or depend on IPv4 after the free pool has disappeared. It turns transfer review into a business-model hearing. It treats leasing as a moral defect rather than a responsibility problem. It lets payment friction become broad leverage. It uses RPKI or reverse DNS as collateral in disputes unrelated to operational trust. It hides delay inside case-by-case judgement. It invokes regional development without showing the rule, cost, or evidence. It may speak the language of stewardship, but the economic effect is discretionary gatekeeping.
The first watchpoint is waiting-list treatment. LACNIC should show whether the list is a fair rationing channel for recovered fragments or a symbolic device that lets old allocation language dominate the whole IPv4 economy. Queue age, assignment size, removals, recovered-space categories, reputation warnings, and eligibility failures should be visible in aggregate. If the wait is measured in many years and assignments are small, members deserve plain language about what the list can and cannot do.
The second watchpoint is recovered-space policy. Recovered blocks should be quarantined, classified, and reintroduced with honest warnings about reputation and usability. A recipient should know whether it is receiving clean working capacity or a block that may require rehabilitation. Recovered space should not become an excuse for discretionary control over already-issued resources.
The third watchpoint is transfer and lease recognition. Transfers should be settled through clear authority, eligibility, dispute, payment, and operational-service rules. Leasing should be treated as a responsibility problem, not a moral failing. The registry should make abuse contacts, RPKI authority, reverse DNS, and holder accountability more legible rather than pushing delegated use into private obscurity.
The fourth watchpoint is the scope of need review. Need review for recovered allocation is one thing. Need review for private transfers is another. LACNIC should keep recipient justification narrow, objective, and tied to adopted rules. If staff judgement begins to rank business models, prices, foreignness, leasing, or IPv4 dependence, the registry will have crossed from settlement into allocation-style permission.
The fifth watchpoint is legacy regularisation. Old public-sector, university, family-company, privatised, reorganised, and otherwise historically complex networks need a recognisable evidence path. LACNIC should make truthful records easier than neglect while preserving strict controls against forged successors and dormant-block theft. Regularisation should be a confidence service, not an open-ended reallocation hearing.
The sixth watchpoint is RPKI and reverse DNS continuity. The default should be preservation of the last verified operational state unless fraud, security, law, or a genuine authority conflict requires a narrower restriction. Transfer handoff, account recovery, lease responsibility, and dispute holds should have published service consequences. Operational trust should not be collateral for unrelated institutional discomfort.
The seventh watchpoint is fee and reserve restraint. Members should see what they are funding: core ledger services, security, RPKI and DNS continuity, translation, support, policy participation, legal defence, development programmes, and reserves. Payment states should distinguish nonpayment from bank friction, public procurement, short receipt, disaster hardship, and disputed invoices. Account standing should discipline members without becoming private capital control.
The eighth watchpoint is auditability of denial and delay. LACNIC should report timing distributions, delay categories, denial reasons, appeal outcomes, payment holds, legal holds, legacy cases, transfer handoff problems, RPKI restrictions, reverse DNS delays, and small-operator effects. Completed transfer logs are not enough. The region needs to understand the queue, not only the exits.
The ninth watchpoint is multilingual participation. Spanish, Portuguese, and English materials must be equally useful where rights, payments, transfers, account standing, RPKI, reverse DNS, or policy consequences are involved. Policy aftercare should test whether small Caribbean, rural, public-sector, and less frequent participants actually understand and can use the rules. Absence from a list is not consent if participation costs are high.
The tenth watchpoint is small-operator hardship. Caribbean and rural providers, small hosters, municipal networks, universities, and public-service networks should not face a hidden surcharge through fixed documentation, translation, payment, and delay costs. Hardship does not mean exemption from truth or fees. It means proportionate evidence, cure paths, service continuity, and measurement of how rules land on thin capacity.
These watchpoints reduce to the same institutional economics. When free addresses disappear, authority no longer comes primarily from fair distribution of new supply. It comes from disciplined recognition: final, narrow, auditable, continuous, and humble about what a registry does not decide. LACNIC's best future is deliberately modest. It should be strict where the ledger needs truth. It should be fast enough where delay prices capital. It should be multilingual enough that participation is real. It should be solvent enough to survive stress and restrained enough that solvency does not become expansion.
It should promote IPv6 without moralising IPv4 dependence. It should record leases and transfers without becoming a rent judge or market planner. It should preserve RPKI and reverse DNS continuity without using them as leverage. It should make old records legible, give members reasons rather than asking for personal trust, and make formal recognition cheaper, safer, and more dependable than avoidance.
That is not a small programme. It is the institutional economics of legitimacy after the well runs dry. If buyers, sellers, lessees, small operators, public networks, universities, courts, banks, and members treat the LACNIC ledger as a low-risk settlement layer, the institution will have earned the post-exhaustion bargain. If they treat it as a discretionary gate, they will price a discount into every block, contract, and continuity plan that depends on it. The choice is not between strong registry authority and weak registry authority. It is between authority that protects the record and authority that tries to govern the market through the record. Only the first can remain legitimate after exhaustion.