Summary

  • LACNIC enterprise legacy-holder analysis asks why banks, utilities, universities, exporters, industrial firms and inherited subsidiaries may hold scarce addresses outside ordinary ISP economics.
  • IPv4 scarcity turns historical records into capital questions around mergers, dormant blocks, sale, lease, collateral, continuity, board oversight and proof of authority.
  • A credible regional ledger should preserve title-like continuity and transferability without using paperwork or moral narratives to confiscate value from legitimate holders.

In Latin America and the Caribbean, old corporate IPv4 holdings are neither administrative relics nor moral trophies. They are scarce capital records whose value depends on a registry remaining a narrow ledger of uniqueness rather than becoming a gatekeeper over enterprise property.

The block in the data room

The discovery often begins badly. A corporate secretary is preparing a sale of a subsidiary. A chief financial officer is reviewing an asset schedule before refinancing. Outside counsel asks for a complete list of digital-infrastructure dependencies. Somewhere between land titles, software licences, domain names, spectrum leases, plant records, and long-forgotten telecom contracts, an engineer adds a spreadsheet of IPv4 prefixes that nobody in the boardroom has thought about for years. The entries may look small beside land, receivables, debt, and inventory. They are not small.

In many old companies, the addresses entered the organisation before the present scarcity economy was visible. A university connected early to research networks. A bank built wide-area computing before private addressing became ordinary. A port operator, mining group, airline, industrial exporter, public utility, manufacturer, or acquired technology subsidiary received public address space when the Internet was still treated as technical infrastructure rather than balance-sheet material. The record was placed in a registry table, contacts were named, routers were configured, and then the company changed around it. Divisions merged. Subsidiaries were renamed. Public entities were privatised. Family-controlled industrial groups professionalised. Banks consolidated. Universities split technology offices from academic departments. Utility concessions moved from state entities to private operators and sometimes back again. The address block remained.

For a long time, this did not matter much. If the block routed, it routed. If it did not route, it remained a technical curiosity. Its main risks were stale contacts, reverse-DNS mistakes, abuse mail sent to nobody, or operational confusion during network redesign. Scarcity changed that. The same entry now raises questions familiar to corporate finance. Who controls it? Can it be sold? Can it be leased? Can it support a business-continuity plan? Does a buyer of a subsidiary acquire it? Does a bankruptcy estate include it? Can it be pledged? Should it be valued in due diligence even if it has no recorded book cost? What happens when the legal name in the registry does not match the group structure that now controls the asset?

This is the enterprise legacy holder problem. It is not primarily a story about access providers, mobile networks, cloud capacity, or technical meetings. It is about companies and institutions that are not in the address business yet possess address assets because history gave them an early position in the Internet's numbering layer. In the LACNIC service region, that category is especially important because the corporate landscape includes old banks, resource exporters, industrial conglomerates, universities, state-linked utilities, family groups, infrastructure concessionaires, and subsidiaries whose legal continuity may be harder to reconstruct than their operational footprint suggests. The holder may not look like a network operator. But the address record may still sit inside operational memory, corporate value, and a future transaction.

A good board does not treat that discovery as a windfall to be stripped casually. Nor does it treat the registry as the owner of a corporate fact. It treats the block as a scarce identifier asset embedded in a chain of control, use, reliance, optionality, and risk. The first duty is not to moralise it. The first duty is to know what it is.

Enterprises that do not look like networks

The phrase "address holder" still leads many people to imagine an Internet service provider. That picture is too narrow. The address economy contains many holders whose main business is not connectivity. Some are visibly network-adjacent: hosting firms, old web portals, integration firms, enterprise outsourcing companies, payment processors, and carriers that were acquired by non-carrier groups. Others are ordinary institutions whose Internet history predates current corporate assumptions. A bank may hold blocks because secure host access, correspondent connectivity, trading platforms, branch networks, or early online services were built around public identifiers. A university may hold addresses because research connectivity made it an early Internet participant. A steel exporter, shipping company, oil-services firm, airport operator, electricity utility, hospital group, or newspaper may hold addresses because engineers once solved an operational problem in the simplest way available at the time.

These holders are not anomalies. They are evidence that the Internet entered the economy unevenly. In countries where network liberalisation, privatisation, and corporate digitisation happened in waves, addresses often attached to the institution that happened to be technically ready at the moment of connection. Later, the business could become something else. A bank might acquire a fintech and move part of its infrastructure to external providers. A state telecom might be broken into units. A university network might be reorganised under a foundation. A mining company might sell a foreign subsidiary but keep central IT. A manufacturing group might merge several legal entities while the network team preserves old numbering to avoid interrupting applications that still work.

The result is a class of holders with three traits. First, the address space may be operationally quiet without being irrelevant. A block can be lightly announced, used for specialised services, retained for migration, reserved for allowlists, or kept as a contingency asset. Second, the legal holder may be out of date while the economic controller is obvious inside corporate records. Third, the company may have no natural internal owner for the asset. The network team understands routing. The legal department understands corporate succession. Finance understands valuation.

This produces predictable mistakes. Engineers may assume that an unused prefix is merely technical clutter. Lawyers may assume that a registry record is just an administrative record. Accountants may ignore it because it was never purchased and therefore appears at no cost. M&A teams may overlook it because it is not named in a plant schedule or software inventory. Boards may hear about it only when a buyer, lessor, broker, creditor, or registry asks for proof of authority.

The LACNIC region adds its own texture. Many enterprises operate across borders. Corporate groups may have holding companies in one jurisdiction, operating subsidiaries in another, and network assets originally assigned to a predecessor whose name survives only in old filings. Public institutions may have changed legal form through privatisation, concession contracts, or administrative reform. Family-owned exporters may have informal control continuity but incomplete paper continuity. Universities may carry historical names, foundations, institutes, and technology arms whose relationship is intelligible locally but not cleanly expressed in a registry contact table. None of this makes the holder undeserving. It makes the ledger's job more important and more limited.

The registry should record who is recognised, what evidence supports a change, what dispute exists if evidence conflicts, and what public contacts must work. It should not decide that an enterprise holder is suspect merely because it is not an access network or because the asset is not being consumed in the morally preferred way. An old bank holding address space is not a policy embarrassment. It is a corporate fact. A university retaining addresses is not hoarding by default. It is historical continuity. An acquired subsidiary with a block is not an invitation to administrative discretion. It is a chain-of-title question.

Scarcity turned memory into capital

IPv4 scarcity did not create the addresses, but it changed the meaning of holding them. The shift is similar to what happens when an old industrial site becomes urban land. The factory may have been built for production, not speculation. Its land may have sat on the balance sheet at a historical cost that says little about current market value. When the city grows around it, the land becomes a capital fact. The company does not become immoral because geography changed. It becomes responsible for managing an asset whose economic meaning has changed.

Enterprise IPv4 blocks have undergone a comparable transformation. A record that once helped packets find their way now sits within a market for scarce, globally useful identifiers. The holder may lease unused portions, sell a block, retain it as a strategic reserve, use it as part of a larger corporate transaction, or keep it because the cost of renumbering hidden applications is higher than outsiders imagine. The asset may not be recognised at fair value in statutory accounts. It may not have been purchased. It may have no depreciation schedule. Yet it can still affect enterprise value, buyer negotiations, tax analysis, lender questions, cyber-insurance review, operational resilience, and board oversight.

This creates an awkward accounting gap. Internally generated or historically assigned assets are often poorly reflected in accounts because no acquisition price was paid. That does not mean they have no economic value. In an acquisition, a buyer may identify address space separately. In a carve-out, the parties may argue about whether the block belongs with the sold operation, the parent, or a service agreement. In insolvency, creditors may discover that an apparently technical entry can become realisable value. In a family succession, heirs may inherit a company whose old network resources are more valuable than some visible assets. In a public body, an auditor may ask whether a state-linked holder can transfer or lease address space without a clear public mandate. These questions are not made easier by pretending the registry owns the value.

Scarcity also changes incentives. When addresses had little market value, a firm could ignore stale registration records. Today, stale records create discounts. A buyer prices uncertainty. A lessor worries about interruption. A creditor hesitates if transfer recognition depends on discretionary interpretation. A board becomes cautious if the asset is valuable but its control trail is messy. If the registry record cannot be made legible through clear, evidence-based processes, the asset suffers a governance discount. That discount is paid by the holder, by potential users who might otherwise obtain capacity, and by the regional economy that could have turned dormant identifiers into productive inputs.

The correct response is not to thicken administrative power. It is to make capital legible. A scarce address block should be capable of being documented, transferred, leased, disputed, corrected, and relied upon without requiring the registry to pronounce on the virtue of the holder's business model. The ledger should answer narrow questions. Is the block unique? Who is the recognised holder? What evidence supports that recognition? Has control changed? Is a transaction being recorded? Are there active disputes, security assertions, or publication dependencies? Are contacts reachable? Those questions protect the Internet. They also protect the market.

The opposite approach converts scarcity into bureaucratic leverage. If every monetisation decision becomes a chance to ask whether a holder deserves value, the registry is no longer maintaining a ledger. It is allocating capital. It may not call itself a capital-control body, but the economic effect is the same. A decision to delay, deny, condition, or stigmatise transferability changes the asset's value. If the institution exercising that power does not carry proportionate liability, the result is a familiar asymmetry: control over value without exposure to the loss caused by control.

Enterprise holders are a useful test because they expose the weakness in moral language. A small network requesting more addresses can be discussed in terms of operational need. An old exporter, bank, university, or utility holding legacy space forces a harder question. Does historical holder status continue to matter once the resource becomes valuable, or may a registry recast the holder as a guest whose rights depend on current fashion? The economically coherent answer is that the record describes an existing claim. It does not create a perpetual licence for the bookkeeper to reallocate value.

The LACNIC proof problem

In mature asset markets, proof is boring by design. Land registries, securities depositories, shipping registries, patent offices, company registries, and title offices exist because markets need a stable way to verify claims. They do not eliminate disputes. They reduce the number of disputes that become existential. IPv4 needs the same discipline, but its records often grew out of technical administration rather than asset governance. Enterprise legacy holders therefore face a proof problem that is more mundane than ideological and more important than many registries admit.

The proof problem has several layers. The first is identity. The name in the registry may correspond to a predecessor, a trade name, a university department, a government agency that was reorganised, or a subsidiary later absorbed into a group. The second is authority. The listed contacts may have retired, left, died, or moved to a supplier. The third is corporate succession. A merger, acquisition, spin-off, privatisation, bankruptcy, or statutory transfer may have moved rights and obligations without anyone separately updating the address ledger. The fourth is operational use. Some addresses may be routed by a service provider, some used internally, some reserved, some abandoned, and some unknown. The fifth is economic intention. The holder may wish to retain, lease, sell, subdivide, or transfer as part of a corporate transaction.

LACNIC's region is not unique in facing these issues, but the variety of legal and institutional histories makes them acute. Latin American companies often operate through groups whose formal control may pass through holding companies, trusts, family vehicles, state entities, pension funds, foreign parents, or concession structures. Caribbean companies may have cross-border corporate arrangements shaped by tourism, finance, shipping, telecom, and offshore services. Universities and public research institutions may not fit a simple corporate model. Utilities may combine public-service obligations with private capital. A registry process that assumes every holder looks like a contemporary access provider will misread this landscape.

Stale contacts should be treated as a repairable evidence problem, not as moral failure. A bank whose registry contact is a retired engineer is not thereby less entitled to the historical block. A university whose department changed name is not a suspect claimant. A public electricity company whose legal form changed after sector reform should not be treated as though continuity vanished because a record field lagged behind reality. The question is evidentiary: what documents, corporate filings, board resolutions, court orders, contracts, public laws, or operational records establish continuity or change of control?

That evidentiary work must be rigorous. Fraud is real. Address hijacking is real. Corporate disputes are real. A block may be claimed by an old subsidiary, a successor, a liquidator, a parent, a former service provider, or a buyer who misunderstood the sale agreement. The registry cannot simply accept the loudest party. It must preserve uniqueness and prevent false changes. But rigor is not the same as discretion. The registry should test evidence against clear rules. It should record disputes when proof is incomplete. It should require authority from legal principals. It should maintain audit trails. It should not use ambiguity as an opportunity to impose a theory about what kind of holder deserves to control scarce addresses.

The difference matters. In an evidence regime, a holder can cure defects. It can find incorporation documents, merger approvals, asset-transfer agreements, powers of attorney, court filings, board minutes, or public decrees. It can show that a predecessor became a successor. It can document that a subsidiary sold everything except the address space, or that the address space followed the network assets. In a discretionary moral regime, the holder can never be certain what will satisfy the institution because the real test is not proof but institutional approval. That uncertainty is value-destructive.

For enterprise legacy holders, the practical lesson is clear. Treat addresses as part of corporate housekeeping before a transaction forces the issue. Map prefixes, current use, historical assignments, legal holder names, contact authority, routing dependencies, reverse-DNS arrangements, security records, customer dependencies, and transaction restrictions. Place responsibility with an executive owner, not only a network engineer. Include address holdings in M&A diligence, bankruptcy planning, internal controls, and succession records. An old block should not be found for the first time by a buyer's consultant.

For the registry, the lesson is narrower. The more valuable the resource, the more disciplined the ledger must become. Discipline means transparent evidence requirements, predictable recognition of lawful succession, quick correction of stale records, dispute notation, and operational continuity while conflicts are resolved. It does not mean making the registry a judge of corporate virtue.

Dormant capacity is not dead capital

The most misleading word in this debate is "unused". An address may be absent from the routing table today and still carry real value. It may be a reserve for disaster recovery. It may support old services that appear only during failover. It may be embedded in customer allowlists or supplier firewalls. It may be intentionally dark because the holder is planning a sale, lease, migration, or consolidation. It may be held by a subsidiary whose operational environment has been frozen after acquisition. It may be dormant because the legal authority to move it has not yet been reconstructed. Dormancy is a state to investigate, not a confession.

Enterprise holders are especially prone to hidden use. Banks and payment firms are conservative because external dependencies can be costly to change. Universities may host legacy services, research equipment, alumni resources, library platforms, or science projects with long replacement cycles. Industrial firms may have plant networks, remote sites, vendor links, and monitoring platforms whose addressing decisions were made by engineers who have since left. Utilities may have conservative change windows because continuity matters more than elegance. Exporters may maintain old B2B services that still serve a small number of important counterparties. The fact that an outsider cannot see heavy public routing does not prove the block is valueless or socially wasted.

At the same time, dormant capacity has an opportunity cost. If a holder no longer needs a block for operations or contingency, the address space can support others. Leasing can turn idle capacity into recurring revenue while preserving strategic control. A sale can fund modernisation, debt reduction, research, network upgrades, or shareholder returns. A transfer inside a corporate group can align records with operational reality. A temporary lease can reduce pressure on the market by bringing capacity into use without forcing a final disposition. The socially useful outcome is movement under clear rules, not freezing under suspicion.

This is where a narrow registry ledger supports both enterprise value and access. A registry that makes transfers and leasing legible encourages holders to bring dormant capacity to market. A registry that treats monetisation as suspect encourages silence. If a university fears that acknowledging unused space will invite confiscatory pressure, it will avoid the conversation. If a utility believes leasing will expose it to moral review, it will keep the block dark. If an industrial group thinks a proposed sale may be delayed by subjective criteria, it will price that risk into the transaction or abandon it. Illiquidity protects no one except the gatekeeper.

Dormant capacity also disciplines boards. Once an address block has a visible market value, directors and executives must decide whether retention is justified. The answer may be yes. Continuity, security, contractual dependence, and strategic optionality can justify holding. But the answer should be documented. A board that ignores a valuable block because it is technical is not being prudent. A board that sells without understanding hidden dependencies is also not being prudent. The task is capital stewardship by the holder, not moral stewardship by the registry.

The better regional outcome is a liquid, well-documented, low-friction market in which old enterprise holders can make rational choices and newer networks can obtain capacity. That requires confidence that a recorded holder can lease, sell, or retain without being treated as a supplicant. It also requires confidence that buyers and lessees receive clean records. Both needs point to the same design: the registry as accurate ledger, not economic priesthood.

Corporate events expose the registry boundary

Mergers and acquisitions are the place where address theory meets adult supervision. A buyer of a business wants to know what it is buying. A seller wants to avoid giving away assets unintentionally. A lender wants collateral and continuity to be intelligible. A receiver wants to maximise value for creditors. A public authority wants to ensure that an essential service does not fail during restructuring. In each case, the registry record is important, but it is not the whole legal reality.

Consider a manufacturing group that acquired a software subsidiary in the late 1990s and later absorbed it. The subsidiary held a block. Its name remains in the registry. The group now uses only part of the block, and the subsidiary no longer exists as a separate operating entity. If the group sells the software product line, does the address block go with it? The answer depends on corporate documents, transaction agreements, operational dependence, and the law governing the merger. The registry should record the result when properly evidenced. It should not invent a separate entitlement because the old line in the ledger looks untidy.

Or consider a bank merger. Two banks combine. One brand disappears. The surviving entity inherits platforms, customers, licences, and technology. Years later, a fintech buyer wants a carve-out that includes servers and certain prefixes. If the registry process is clear, the parties can allocate the address asset in the sale agreement, provide authority, and record the transfer. If the process is uncertain, the address block becomes a negotiating risk. The buyer demands a discount. The seller hesitates. Counsel escalates. A transaction that should be commercial becomes hostage to administrative interpretation.

Bankruptcy raises harder issues. Creditors may see value in a block held by a distressed enterprise. An insolvency officer may seek to sell it. Employees may worry that a sale could disrupt remaining operations. Customers may depend on services still tied to the addresses. A court may need evidence of value and control. The registry's job is not to decide whether creditors deserve the asset more than future networks, or whether the old holder used the block efficiently enough. Its job is to preserve the ledger, recognise lawful authority, prevent fraud, maintain continuity, and record transfers that do not create conflicting claims.

Public-sector transformations are equally important. A state-owned utility may have received address space under one legal form, then been corporatised, partly privatised, concessioned, or merged into a new public holding company. The addresses may support services tied to electricity, water, transport, health, education, or public administration. These are not abstract policy objects. They are identifiers embedded in public reliance. A registry that treats organisational change as an opportunity for discretionary review can create public risk. A registry that treats it as a documentation question can preserve continuity while updating the record.

Family-company succession is a quieter version of the same problem. Latin American enterprise history includes many firms whose control passes through families, trusts, holding companies, or informal group structures before formal governance catches up. The death of a founder, a shareholder dispute, or a generational split can leave digital assets poorly documented. Address space may be held by an operating company that no longer matches the group's business reality. The right answer is not confiscation by neglect. It is disciplined reconstruction of authority.

Acquired subsidiaries create a further trap. A parent may have acquired the business but not the corporate shell; a buyer may have taken customers and software but not the numbering asset. A merger agreement may have transferred "all technology assets" without making clear whether addresses with no book value were included. The registry should not resolve such ambiguity by instinct. It should require title-like proof and record only the conclusion supported by law, contract, and corporate authority.

These examples expose the boundary. The registry is not the corporate court, the tax authority, the bankruptcy judge, the securities regulator, the family council, or the board of the enterprise. It is a specialised ledger for number uniqueness and related publication. It can require evidence. It can reject defective evidence. It can record a dispute. It can refuse to create duplicate recognition. It can keep services stable while parties resolve ownership elsewhere. What it must not do is convert paperwork difficulty into a claim of superior moral control over the asset.

If LACNIC is to serve enterprise legacy holders responsibly, this boundary is not optional. The richer the corporate history, the more tempting administrative discretion becomes. Yet the richer the history, the more damaging discretion is. Capital needs a ledger that can survive complexity without turning complexity into permission.

Lease, sell, retain: the real menu

Enterprise holders face three basic choices: retain, lease, or sell. Each is legitimate.

Retention is rational when addresses remain operationally embedded, support security and continuity, or provide strategic optionality. A bank may keep a block because renumbering old applications would introduce risk disproportionate to the cash value of a sale. A utility may retain capacity for continuity planning. A university may preserve address space for research autonomy, future hosting, or institutional independence. An exporter may keep addresses because important partners still rely on old allowlists. Even if a block is not fully used, retention can be prudent where the holder understands and documents the reason.

Leasing is rational when the holder has surplus capacity but does not want to surrender long-term control. It can turn a dormant asset into income, allow other networks to use scarce space, and preserve the holder's ability to recover capacity later. Leasing also fits firms that are unsure how future restructuring will unfold. An old industrial group may not want to sell a block before a larger divestiture. A university may prefer periodic revenue to permanent alienation. A public utility may have authority to contract for use but not to dispose of the asset outright. A lease can accommodate those constraints if the ledger recognises the difference between operational use and recorded control.

Sale is rational when the holder has no continuing need, can establish authority, and wants to realise capital. For some companies, the proceeds may be modest relative to the group. For others, especially distressed firms or institutions with large historical holdings, the value may be material. Sale can clean up records, reduce administrative burden, and place addresses with operators that need them. It can also expose hidden disputes if the holder waited too long to document control. That is why sale preparation should begin with housekeeping, not with a buyer.

The registry should not prefer one option as a matter of moral theory. It should require that the transaction preserve uniqueness, protect relying parties, avoid fraud, maintain required publication data, and reflect lawful authority. Beyond that, commercial choice belongs to the holder. An enterprise that leases is not necessarily speculating. An enterprise that sells is not necessarily abandoning public duty. An enterprise that retains is not necessarily hoarding. The same observable fact--a lightly used block--can support different rational decisions depending on hidden dependencies, legal authority, risk tolerance, and capital needs.

A discretionary registry undermines all three choices. It weakens retention by making the holder fear later reinterpretation. It weakens leasing by making lessees doubt continuity. It weakens sale by making buyers price administrative risk. It also encourages informal workarounds, opaque contracting, and reluctance to update stale records. When recognised records become uncertain, markets do not become pure. They become murky.

The better approach is to reduce transaction costs. Clear transfer recording increases supply. Clear lease recognition increases productive use. Clear holder recognition increases board confidence. Clear dispute notation protects buyers and courts. Clear portability reduces the monopoly discount imposed by a single registry relationship. This is not a demand for deregulation in the lazy sense. It is a demand for correct regulation of the registry function: precise, narrow, and reliable.

For LACNIC-area enterprises, this matters because corporate address assets often sit outside the usual network-operator conversation. A telecom company already knows that addresses are part of its production machinery. A bank or exporter may not. If the path to monetisation is uncertain, the asset remains invisible. If the path is clear, a CFO can evaluate the block like any other scarce intangible: what is it worth, what does it support, what risks attach to disposal, and what governance is needed to act responsibly?

Board oversight and the cost of ambiguity

The economics of enterprise legacy holdings eventually reach the boardroom because ambiguity has a price. A valuable asset with unclear control is not a full-value asset. A transfer right subject to unpredictable administrative judgment is not a clean right. A block with stale contacts and unknown dependencies is not simply hidden value; it is also hidden risk. Directors do not need to become routing experts. They do need to ensure that management knows what the company holds and who can act on it.

A sensible board inventory begins with fact-finding. Which prefixes are associated with the group? Which legal entity appears in the registry? Which entity actually uses them? Are they announced? Who originates them? Are there reverse-DNS dependencies? Are any certificates, security assertions, customer contracts, vendor access rules, or regulatory obligations tied to them? Are old subsidiaries, dissolved entities, or predecessor names involved? Are contacts current? Has the company ever leased, assigned, delegated, or permitted another party to use part of the block? Has any block been informally transferred without a clean record?

The second step is authority. The company should identify who can instruct changes, sign transaction documents, respond to registry questions, and approve leasing or sale. This cannot be left to a generic technology mailbox. Address assets sit at the intersection of legal, finance, security, and operations. A CFO may own valuation, but not routing. A general counsel may own authority, but not technical continuity. A chief information officer may own use, but not disposal. A mature governance model assigns a cross-functional owner and keeps the board informed when value is material.

The third step is valuation. Not every block deserves a full independent valuation every year. But material holdings should be visible in risk registers and transaction planning. Even where accounting rules do not permit recognition at market value, management can maintain an internal estimate for decision-making. In an acquisition, sale, refinancing, restructuring, or insolvency, that estimate can become important quickly. The absence of a book entry should not be mistaken for absence of value.

The fourth step is policy. A holder should decide when it will retain, lease, sell, or reserve. It should define acceptable counterparties, continuity protections, security obligations, notice periods, and internal approvals. It should document why unused capacity is retained if the value is material. It should avoid informal side arrangements that blur control. It should keep enough technical evidence to prove operational state and enough legal evidence to prove authority.

Ambiguity is expensive because counterparties capitalise it. A buyer who worries that the registry may not recognise a transfer will demand protections. A lessee who worries about interruption will pay less. A lender who sees unclear control will ignore the asset or discount it. An auditor who discovers a valuable, unmanaged resource may escalate. A regulator reviewing a public utility or bank may ask why management failed to supervise a material digital asset. These costs are not theoretical. They are the natural result of letting old administrative records become valuable without updating governance.

The registry can reduce or increase those costs. It reduces them by providing predictable evidence standards, timely record updates, clear dispute handling, and stable publication services. It increases them by preserving discretionary ambiguity. Every unclear rule becomes a spread between the asset's theoretical value and its realisable value. In capital-market language, registry discretion raises the asset's cost of capital.

This is why enterprise legacy holders should care about registry boundaries even if they never attend a policy meeting. A bank board, university council, or utility oversight committee may not speak the language of Internet governance. It understands title risk, counterparty risk, continuity risk, and impaired asset value. The address ledger should make those risks easier to manage. It should not add a layer of institutional theology to an already complex corporate record.

The temptation to police value

Once an administrative record sits above valuable assets, institutional temptation appears. The recordkeeper begins to feel that because transactions require its recognition, it is the source of value. This is false. Value comes from scarcity, utility, reliance, and market demand. It comes from networks, customers, enterprise operations, and the capital decisions made around them. The registry contributes a necessary coordination function: uniqueness, accuracy, publication, and trust in the record. Necessary is not the same as sovereign.

Enterprise legacy holders are particularly vulnerable to the temptation to police value because they do not always fit the preferred story of network need. If a broadband provider requests addresses to connect customers, the operational narrative is easy. If an old bank leases unused space, a moral vocabulary can be assembled against it. Why should a bank profit from addresses? Why should a university sell a block? Why should a dormant subsidiary hold scarce identifiers? Why should a utility retain capacity not visible in public routing? These questions sound public-spirited. They are often capital control in ethical dress.

The answer is not that every holder is wise or every transaction benign. Some holders neglect records. Some intermediaries overpromise. Some blocks have dirty histories. Some transactions require careful fraud checks. Some use may create reputational or security concerns for the holder. But none of that gives the registry a general mandate to decide who deserves economic value. It gives the registry a duty to keep the ledger accurate, require authority, support reachability, record transfers, and isolate disputes.

The distinction between enforcement and recording is essential. If a company commits fraud, violates sanctions, breaches contracts, abuses customers, or breaks national law, the relevant authorities and courts have tools. A registry should cooperate where lawful and maintain accurate records. It should not become police, prosecutor, judge, and execution layer by threatening the identifier itself unless a lawful order or clearly defined technical necessity requires action. The address book is too important to become a punishment device.

The phrase "community policy" does not solve the problem. A meeting, mailing list, consultation, or association vote may produce useful input. It does not become a mandate over absent corporate principals. A registry contact is not a power of attorney. A technical participant is not the board of a bank. A service region is not a shareholder. A policy discussion can define operational procedures for the common ledger. It cannot legitimately convert enterprise capital into discretionary institutional property.

The risk is mandate laundering. A narrow service role is wrapped in community language, regional language, continuity language, and stewardship language until the institution appears to have authority far beyond the technical function that justified it. For enterprise legacy holders, the economic effect is clear. The registry acquires a veto over liquidity, leasing, transfer, and recognition. The holder bears the loss if value is impaired. The registry does not. That asymmetry is not stewardship. It is leverage.

LACNIC should be most credible when it is modest. The region needs accurate records, resilient publication, fraud resistance, transfer clarity, and continuity. It does not need a private administrative layer deciding whether an industrial group's historical block is morally acceptable capital. It does not need a registry to turn corporate housekeeping into a loyalty test. It does not need scarcity to become a reason for institutional rent.

The hardest discipline for any registry is to remember that it did not create the world it records. Enterprise legacy holders existed because the Internet entered companies, universities, and public institutions through practical engineering. The ledger followed that reality. It should not now claim to stand above it.

The public-interest argument points toward liquidity

Defenders of restrictive control often invoke the public interest. The claim is familiar: scarce IPv4 resources should not be treated as ordinary assets because markets may reward early holders and leave newer networks worse off. In the abstract, the concern is understandable. Scarcity can produce rents. Early position can matter. Markets can be unequal. But the conclusion does not follow. Restricting enterprise holders from moving, leasing, or selling dormant capacity does not create more addresses. It traps them.

Liquidity is not the enemy of access. Illiquidity is. A bank that can lease unused capacity increases supply. A university that can sell a surplus block releases addresses to someone that values them more. A utility that can transfer a block to a successor after reorganisation preserves continuity. An industrial group that can monetise dormant space may fund upgrades while another network obtains capacity. None of these outcomes is guaranteed, but they are possible only when movement is allowed. A frozen ledger protects neither users nor new entrants.

Administrative rationing has its own inequality. Large firms can hire counsel, consultants, and technical staff to navigate complex processes. Small networks and smaller buyers pay the friction more painfully. Insiders understand process better than outsiders. Delay favours those with cash. Unclear standards favour those with relationships. A moralised anti-market regime often claims to protect the weak while imposing high transaction costs on them. Price is not always kind, but it is visible. Discretion is opaque.

The public interest is better served by rules that bring capacity into productive use while protecting the ledger from fraud. That means clear recognition of lawful holders, predictable transfer recording, support for leasing structures that preserve accountability, transparent dispute flags, and portability if a registry relationship becomes structurally unsafe. It also means accepting that some holders will profit from historical scarcity. That is not a defect unique to IPv4. It is a feature of scarce assets whose supply cannot be recreated.

The alternative is not equality. It is administrative power. If a registry can decide that an enterprise holder's historical block is not being used in the preferred way, it can decide which business models, geographies, buyers, lessors, or uses are acceptable. That is a capital-allocation role. Once the registry occupies that role, it becomes a gatekeeper over value created by others. If it also limits its own liability and preserves institutional discretion, it becomes the worst kind of allocator: powerful, underexposed, and procedurally insulated.

A region with many old enterprise holders should be especially wary of this path. Latin America and the Caribbean do not need an arrangement that frightens old companies into hiding address assets. They need a record environment that makes those assets legible enough to move when movement is rational. Address space held by an exporter, bank, university, or utility can become a regional resource in the practical sense only if the holder can transact. It cannot help anyone while trapped by uncertainty.

There is also a continuity dimension. Forced or pressured movement can be dangerous. If a registry treats low visible use as justification for aggressive intervention, holders may rush to create artificial use, hide information, or resist updating records. Real public interest lies in careful, voluntary, documented movement. The holder should decide whether a block is operationally necessary. The registry should ensure that any resulting record remains unique and reliable. That division of labour is more stable than moral control.

Public interest is not served by turning a ledger into a planning ministry. It is served by lowering the cost of truthful information, lawful transfer, and operational continuity.

Portability is the discipline behind trust

A registry relationship is safer when exit exists. Without portability, even a narrow service can become power. If a holder cannot move its registration away from a failing, conflicted, or overreaching registry, the registry's control over recognition becomes lock-in. Lock-in changes the psychology of administration. A service provider that cannot be replaced becomes less disciplined. A holder that cannot leave must price every disagreement as existential. That is unhealthy for ordinary operators and especially unhealthy for enterprise legacy holders whose address assets may be one part of a much larger corporate estate.

Portability should not be confused with disorder. It does not mean duplicate claims, casual transfers, or a free-for-all. It means that the holder's recognised claim can be maintained through a different registry service if the current one becomes unreliable or if a legitimate transfer of administrative service is permitted. The common layer should preserve uniqueness, evidence, publication, transfer history, security state, and dispute metadata. It should not bind a holder forever to one institution merely because history placed the record there.

For LACNIC-area enterprise holders, portability matters for several reasons. First, many do not have the time or expertise to fight registry overreach as their main business. A bank wants banking continuity. A utility wants service continuity. A university wants research and education continuity. A shipping firm wants logistics continuity. If the registry relationship becomes unstable, they need a structural remedy, not a political campaign. Second, corporate transactions often move across borders. A buyer or parent in another region may need administrative alignment without losing continuity. Third, portability introduces market discipline into registry service quality. If holders can leave, the registry must compete on accuracy, responsiveness, neutrality, and trust.

Portability also clarifies the difference between ledger and gatekeeper. A ledger can be replicated, audited, and transferred while preserving the facts it records. A gatekeeper insists that the facts depend on its own continuing control. The first model treats the registry as a service to the asset. The second treats the asset as captive to the registry. Enterprise capital cannot mature under the second model because every valuation includes an institutional hostage discount.

The continuity argument is often used against portability. The claim is that changing registry service could threaten stability. This confuses continuity of the ledger with continuity of the incumbent gatekeeper. What must be protected is uniqueness, publication, security coherence, contactability, transfer history, dispute integrity, and running-code primacy: services that keep working should not be sacrificed to institutional theory. Those functions require careful transition rules. They do not require institutional immortality. Indeed, the absence of transition mechanisms makes the arrangement less stable, not more. A bridge is safer when it has maintenance access and emergency plans, not when engineers declare it sacred.

Portability is also a governance signal. It tells holders that the registry recognises itself as a service provider with a bounded mandate. It tells markets that the asset is not trapped inside a single administrative monopoly. It tells courts and boards that continuity can survive institutional failure. It tells old enterprise holders that updating records will not increase their vulnerability by placing all power in one relationship.

The Number Resource Society's positive model is built around this intuition: exit rights instead of enforced permanence, portability instead of lock-in, redundancy instead of monopoly, and mechanisms instead of moral narratives. That is not anti-registry chaos. It is the only serious way to preserve trust in a voluntary order once the recorded resources become capital.

Without portability, every promise of stewardship asks holders to trust the benevolence of a gatekeeper. With portability, trust is supported by structure. Enterprise legacy holders should prefer structure.

What LACNIC should be in this market

The best version of LACNIC in the enterprise legacy market is not a more ambitious governor. It is a more reliable ledger. That role is demanding enough. It requires accurate records, consistent evidence standards, fast correction of stale contacts, careful treatment of succession, transparent transfer recording, reliable publication services, secure handling of authority, and dispute notation that protects all parties without interrupting running services.

The narrowness is the virtue. A registry that knows its boundary can be trusted by many kinds of holders. A bank can update records without fearing that disclosure of underused space invites moral review. A university can document succession without being treated as a political resource pool. A utility can preserve continuity through restructuring. An exporter can lease or sell capacity under commercial terms. A buyer can trust that a recorded transfer means what it says. A court can look to the ledger for evidence without accepting the registry as the source of superior economic authority.

The wrong version is also clear. LACNIC should not convert historical holder status into discretionary control. It should not treat enterprise holders as second-class because they are not network operators. It should not use scarcity as a reason to review business models. It should not use regional rhetoric to restrict capital movement beyond what is technically necessary to preserve uniqueness and lawful record integrity. It should not turn stale contacts into leverage. It should not treat leasing as suspect merely because value flows to a non-network enterprise. It should not confuse its service region with political ownership of the resources recorded there.

The distinction between service and sovereignty is not decorative. LACNIC is an institution established in a particular legal environment to perform a registry function for a service region. It is not Latin America. It is not the Caribbean. It is not the collective owner of every address whose holder happens to be located within its footprint. Its legitimacy is strongest when it performs the function that running networks and holders actually need: a dependable, neutral, evidence-based ledger.

The economics are straightforward. If LACNIC reduces uncertainty, enterprise address assets become more liquid and more valuable. If assets become more liquid, dormant capacity is more likely to reach users who need it. If records become more accurate, fraud risk falls. If succession rules become predictable, corporate transactions become cleaner. If portability exists, registry trust becomes less dependent on institutional self-restraint. Each of these outcomes strengthens the region.

If LACNIC expands discretion instead, the opposite happens. Holders avoid disclosure. Buyers discount. Lessees hesitate. Old records remain stale. Corporate counsel treats the registry as a risk factor. Boards defer rational decisions because the administrative path is unclear. Scarcity then remains trapped not by lack of need but by lack of trust. That would be a poor outcome for a region whose enterprises may hold useful capacity precisely because they were early, important participants in the digital economy.

The ledger should not punish history for becoming valuable. It should make history usable.

The NRS future for enterprise holders

The enterprise legacy holder problem points beyond one region. It shows why the future of number governance cannot be built on thicker institutional discretion. Once IPv4 is capital, the registry layer must become thinner, more portable, more auditable, and less moralised. The point is not to romanticise markets or deny public concerns. The point is to place authority where it belongs. Holders manage assets. Courts and regulators enforce law. Operators run networks. Registries preserve uniqueness and record truth. No one layer should quietly absorb the functions of all the others.

The Number Resource Society offers the only positive direction because it begins from structure rather than reassurance. It does not ask enterprise holders to trust that a registry will remain modest forever. It asks for exit, portability, redundancy, and mechanisms that make modesty enforceable. It treats decentralisation not as a slogan but as a way to remove single points of failure from a voluntary global arrangement. For old banks, universities, utilities, exporters, industrial groups, and acquired subsidiaries, that matters. Their address assets may be small compared with their main business, but the principle around them is large. A corporate asset should not depend on the continuing self-restraint of a single administrative gatekeeper.

An NRS-oriented model would make several practical differences. Historical holder claims would be documented through verifiable records rather than institutional favour. Transfers would be recorded to preserve uniqueness and auditability, not to ask whether commerce deserves permission. Leasing would be treated as a contractual use of scarce capacity, with accountability attached to parties, not as a moral defect. Succession would be handled as evidence. Disputes would be isolated rather than converted into threats against running networks. Registry service would become replaceable. The common layer would contain what all participants need and no more.

That model is better for enterprise holders because it makes assets portable and legible. It is better for operators because it increases supply and reduces gatekeeping risk. It is better for users because continuity is protected in running networks and services, not in institutional prestige. A registry that confines itself to a narrow ledger can remain useful. A registry that tries to govern capital without the legitimacy and liability of a capital governor will eventually be challenged by the value it seeks to control.

The LACNIC region should take enterprise legacy holders seriously because they reveal the economic truth beneath the registry debate. The old Internet is not separate from the old economy. It is embedded in banks, ports, universities, manufacturers, utilities, exporters, airlines, hospitals, media groups, and public bodies. Some of those institutions hold address space because they were early. Some hold it because they acquired someone who was early. Some barely know they hold it. But the blocks are there, and scarcity has made them matter.

The question is not whether these holders fit a preferred narrative. The question is whether the ledger can tell the truth about them without trying to own them. A serious registry can. It can protect uniqueness, require evidence, publish reliable records, maintain continuity, and support lawful movement. It can refuse to become the moral landlord of history.

That is the economics of enterprise legacy holders. They are not ghosts in an administrative record. They are corporate actors holding scarce digital capital, often imperfectly documented, often operationally entangled, and increasingly visible to boards and markets. They need clarity, portability, and a ledger that respects the difference between recording value and controlling it. LACNIC's legitimacy in this market will depend less on what it says about stewardship than on whether it can preserve that difference when the value becomes too large to ignore.

Sources and further reading

These references provide the article's public doctrine and background context. They are used for institutional-economic framing, not for adopting any registry or official-sector narrative.