An old IPv4 block does not look like a financial instrument. It appears in a registry as a span of numbers, a holder name, a contact, a routed prefix, a reverse-DNS delegation and, in better cases, a small history of changes that once seemed administrative rather than economic. It may have begun inside a university network, a public research project, a state telecommunications body, a city carrier, a family-owned internet provider or a regional group that connected customers before the commercial internet had settled into its present institutions. It may have survived a name change, a ministry reorganisation, a privatisation, a merger, an inheritance, a sale of network assets or a long period during which nobody updated the record because the addresses continued to work.
Then scarcity arrived. The old entry stopped being merely an archive. It became something a buyer might diligence, a seller might price, a lessee might depend on, a bank might ask about, a lawyer might qualify, an upstream network might treat with caution and a registry might be asked to regularise. What had once been administrative memory became a claim on confidence.
That is the central fact in the economics of legacy allocation title. The question is not whether internet number resources should be described as ordinary property. They are not land, and a regional internet registry is not a land office. Nor is the question whether the operator currently routing the prefix can use it this week. The harder question is what makes an old recognition durable enough for others to rely on it: to route, transfer, lease, certify through RPKI, delegate in reverse DNS, receive abuse reports, survive a dispute, pass through escrow or appear on a balance sheet without a heavy discount for uncertainty.
Title in this setting is best understood as a chain of recognition. It begins with an original allocation or assignment. It then passes through institutional survival, corporate succession, contact authority, service relationship, registry regularisation, operational continuity and dispute evidence. A chain can be strong even if its documents are old, local, uneven or written before IPv4 became scarce. It can be weak even if a present-day claimant produces polished paperwork that does not prove the relevant link. The economic value of the block rests less on a slogan about ownership than on whether the chain is good enough for a market to trust.
LACNIC makes this issue unusually vivid because its region contains several kinds of institutional memory at once. Latin America and the Caribbean include old universities, public bodies, national research networks, former state carriers, privatised telecommunications companies, municipal networks, cooperatives, family ISPs, island operators, subsidiaries of global groups, regional holding companies and cross-border acquisitions whose documents were not written for an IPv4 transfer market. Some records are clean. Some are stale. Some are legitimate but poorly archived. Some may be exposed to opportunistic claims. Some may be dormant because the holder no longer exists, while others only look dormant because the holder never needed to ask the registry for anything new.
The registry's task is therefore neither to romanticise history nor to erase it. LACNIC has to respect historical allocation, because much of the region's early connectivity was built by institutions that did not receive their numbers under present membership habits. It also has to refuse undocumented market claims, because scarcity gives old records a price and a price attracts fraud. The narrow middle is disciplined recognition: a way of saying which facts must be proven, which evidence can prove them, which services may continue while proof is being gathered and which claims are too uncertain to support a sale, lease or change of holder.
IPv4 scarcity has turned weak title into a visible cost. A clean block can support a transfer application, an escrow instruction, an RPKI route-origin authorisation, reverse-DNS continuity, customer migration and acquisition diligence. A block with weak succession or stale authority commands less confidence. Buyers ask for stronger warranties. Escrow periods lengthen. Counsel asks for local opinions. Brokers trade on private knowledge. Leasing becomes more opaque, because parties prefer informal assurances to a registry-facing test they fear might fail. A legitimate holder with poor documentation may lose value to a better-resourced counterparty. An illegitimate claimant may try to monetise the fog.
This is why LACNIC's legacy allocation question is not another routine transfer-market essay. Transfers are the visible closing event. Legacy title is the confidence layer underneath. It determines whether the market believes that the old record can be trusted before anyone negotiates price, need, fees or timing. It is institutional memory converted into liquidity.
The chain of recognition
The first link is the original allocation. LACNIC has described legacy resources as internet number resources assigned by InterNIC or IANA before the current regional registry arrangements existed and not later brought under an ordinary LACNIC membership agreement. That origin matters because it places the resource inside a different historical bargain. The allocation may predate modern portals, RDAP habits, routine point-of-contact validation, standard service contracts, RPKI, familiar transfer procedures and the commercial practice of treating a number block as an asset whose history must survive a closing table.
The original allocation does not answer every later question, but it anchors the chain. Without it, the present record floats. A later claimant may control a route, possess an old domain, know a retired engineer or display a letter of authorisation, but those facts mean little unless they can be tied back to the allocation that created recognition in the first place. A title review should therefore begin by asking what the historical holder was, what range was allocated, when and in what context the allocation was made, and whether the current record still reflects that root.
The second link is institutional survival. Many old holders still exist, but not necessarily under the same name or administrative form. A university may have changed its legal style, consolidated campuses or moved its network operation from a research unit to a central technology office. A ministry may have absorbed a predecessor body. A public enterprise may have become a regulated carrier. A private operator may have incorporated, merged, split or become a subsidiary. A title review that stops at the displayed name misses the point. It must ask whether the entity requesting action is the same institution, a lawful successor, an authorised representative or a claimant that merely stands near the old record.
The third link is corporate succession. This is where Latin American and Caribbean variety matters. A privatisation may be evidenced by legislation, concession documents, regulator approval and asset schedules rather than by a single purchase agreement. A family ISP may change control by inheritance, share transfer, local notarial acts or practical continuity of the business. A municipal network may move into a new public body. A telecom group may transfer network assets among subsidiaries in different countries. A Caribbean company may rely on common-law corporate filings while a continental public body relies on administrative resolutions. LACNIC does not need to become a court for every jurisdiction. It does need to know what fact each document is meant to prove.
The fourth link is contact authority. A stale contact is not a harmless inconvenience in a scarce-address market. It is a fraud surface. A retired engineer's mailbox, an expired domain, an old role account or a forgotten personal address can be used by a legitimate holder trying to recover a record, but also by someone trying to impersonate one. Conversely, a current contact may be an operator, consultant, lawyer or broker rather than the holder. Contact control is evidence, not destiny. It must be joined to institutional authority.
The fifth link is the service relationship. A legacy holder may have relied on registry services without having a conventional membership relationship. Bringing the block into a modern relationship can improve certainty, but it can also feel to the holder like a conversion of historical reliance into new obligations. That tension is economic, not merely legal. If the path is predictable, regularisation raises value. If the path is opaque, expensive or frightening, holders may avoid contact, leaving records stale and the market more dangerous.
The sixth link is dispute evidence. A block may be claimed by a successor company, an asset buyer, a former affiliate, a creditor, a founder's estate, a government body or an operator that has routed it for years. The registry should not decide every private-law dispute. Yet it must protect the ledger from false finality. A disputed block should not become clean merely because one side reaches the registry first. Nor should an unsupported objection become an indefinite veto. Confidence requires categories for competing claims, evidence, review and resolution.
The final links are operational. RPKI, reverse DNS, WHOIS or RDAP data, abuse contacts and routing continuity do not prove ownership in a courthouse sense. They show whether the recognised holder can translate registry recognition into useful network authority. An old block whose route authorisation, reverse delegation and contacts remain coherent is economically different from one whose services are broken, stalled or controlled by a party whose authority is unclear. Operational continuity is not a substitute for succession proof, but it is part of the market's confidence in the chain.
Scarcity made old memory expensive
IPv4 scarcity did not create legacy records. It changed their price. Before exhaustion, an awkward historical entry could often be treated as a cleanup problem. A network that needed more addresses might request new space, use upstream assignments, renumber with pain or continue quietly with inherited addresses. After exhaustion, that background assumption changed. LACNIC created its IPv4 waiting list after the last available block was assigned on August 19, 2020. Public material around the waitlist has described the last request as facing a wait measured in many years and limited to a small maximum allocation from recovered space. For most real demand, that is not a supply plan. It is a signal that marginal IPv4 demand must be met through another holder, a transfer, a lease, a merger, old inventory or engineering around shortage.
When new supply stops being ordinary, old stock starts to behave like capital in commercial decisions. The phrase should be used carefully. An IPv4 block is not a factory, a licence to operate a monopoly or a parcel of land. But if a scarce resource is useful, recognisable, transferable under rules, required by customers and capable of supporting revenue, it begins to affect enterprise value. It appears in acquisition diligence. It is leased. It is pledged in the language of business plans even if not always formally pledged as collateral. It becomes something whose weakness can be discounted.
The discount is not theoretical. In a sale, a clean record allows the seller to approach the market without asking the buyer to reconstruct the 1990s before closing. A stale legacy record forces the seller to sell uncertainty along with addresses. A buyer may respond with a lower price, a longer escrow period, an indemnity, a local legal opinion, a condition that the seller regularise first or a right to walk away if LACNIC refuses recognition. The numerical block is not the whole asset. The asset is the recognised ability to move or use the block without a foreseeable challenge.
Leasing exposes the same problem. If the lessor's authority is uncertain, the lessee inherits risk. It may receive a letter of authorisation but lack a reliable way to test the chain behind it. It may depend on the lessor to create route-origin authorisations, keep reverse DNS working or answer abuse notices. It may later discover that the lessor is a broker, not the holder, or that another party disputes the record. Leasing can be a rational tool for temporary demand or small networks. It becomes dangerous when title is weak and the public record cannot tell the market who is accountable.
Scarcity also changes the behaviour of strong and weak parties. A large carrier, cloud group or experienced address-market participant can absorb proof costs. It can hire counsel, translate documents, trace corporate events and wait through review. A small island operator selling a /24 to finance equipment, or a university attempting to clean an old entry, may face the same title problem without the same surplus. The party able to prove history cheaply captures value from the party that cannot. Documentation becomes bargaining power.
This is why market confidence cannot rest on mythology. It is not enough to insist that number resources are not ordinary property. That statement is true but incomplete. It is also not enough for holders to say that history gives them absolute dominion. The practical question is whether LACNIC can define and apply a recognition standard that lowers transaction costs while preventing fraud. In a scarce market, that standard is part of the value of the resource.
The economics are especially sharp because the registry's recognition is not a mere private certificate. It is the coordination signal on which many other actors rely. A buyer wants assurance that the transfer will settle. A lessee wants usable authority. An upstream provider wants confidence in route legitimacy. A mail operator wants reverse DNS to remain coherent. A bank wants diligence that does not dissolve into old anecdote. A public institution wants continuity. LACNIC wants accurate records and secure services. These interests can coexist when the chain is clear. They collide when recognition becomes a matter of discretionary comfort.
The regional texture of proof
LACNIC's region is not a single legal or administrative environment. It contains large economies with sophisticated carriers and counsel. It contains countries with inflation, exchange controls and foreign-payment friction. It contains English-speaking Caribbean jurisdictions whose company records may look unfamiliar to Spanish- or Portuguese-speaking participants elsewhere in the region. It contains public bodies whose continuity is shown by official acts rather than private merger documents. It contains island networks for which a small block may be a meaningful item of enterprise value rather than an accounting footnote.
That variety changes what title evidence looks like. A Brazilian or Mexican operator may produce national filings, regulator records and a long domestic commercial history. A Chilean university may show institutional continuity but have patchy memory of an allocation made inside an early research environment. An Argentine company may have real continuity while facing currency and documentary complications around a sale. A Caribbean provider may have solid local corporate records, a small staff and a high cost for certified translations or foreign legal opinions. A public body may have inherited a network from a predecessor ministry and need to prove continuity through decrees, budget allocations and service responsibility rather than a purchase contract.
The registry's evidentiary task is not to demand one universal document shape. It is to demand proof of underlying facts. Who was the historical holder? Does that institution still exist? If it does not, what legal or administrative event created the successor? Who can sign for the successor today? Were the addresses included in the transaction, reorganisation or continuity being claimed? Is there a competing claimant? Has the resource been used continuously, and by whom? Are contacts, routing and reverse DNS consistent with the chain? These questions travel across legal systems even when the documents do not.
The danger lies in mistaking elegance for truth. A large company can often produce a polished closing file. A small operator may produce local filings, tax receipts, invoices, routing history, officer statements and a shorter paper trail. The second file may be harder to read but still true. Conversely, a polished acquisition document may be irrelevant if it proves acquisition of a company but not acquisition of the network assets or the resource relationship. LACNIC's discipline should reward relevance, not paper volume.
Universities and public institutions require special care. Early internet allocations often landed in academic or public networks because they were building connectivity before commercial demand matured. Over decades, a university may rename itself, reorganise campuses, centralise technology, create a research network or separate network operations from other functions. A public network may move from one ministry to another. A state telecom may be privatised, merged and later restructured again. It would be unfair to punish these holders for not preserving a transfer file before addresses had market value. It would be unsafe to allow any present official to market a block without proving institutional continuity. Respect for history and proof discipline are not opposites.
Family-owned and small regional providers create another pattern. A founder may have received or administered resources in a period when the business was informal by current standards. The company may have grown, changed tax form, brought in relatives, sold a customer base or moved operations into a new corporation. The network may be continuous, but formal records may be fragile. A narrow proof rule should ask whether the resource relationship survived and who can act for it now. It should not force a small holder to reproduce the documentary habits of a multinational group.
Caribbean cases add scale and resilience issues. Many island networks operate with small teams, foreign suppliers, correspondent-banking friction and exposure to hurricanes or other disruptions. The value of address continuity may be high relative to firm size. If a legacy regularisation file requires repeated cycles of documents, translations and long uncertainty, the process may deter cleanup. Deterrence then makes the ledger worse. LACNIC should want legitimate small holders to come forward before a buyer, broker or dispute makes the issue urgent.
Cross-border groups add a different risk. A regional holding company may have acquired a local ISP, merged several networks, moved customers across brands and centralised technical operations. The chain may be genuine, but the entity using the addresses may not be the one that owns the legacy relationship. An acquisition of shares may leave resources where they are; an asset purchase may or may not include them; a merger may extinguish a company while a successor remains. The registry does not have to decide every commercial allocation of value within the group. It must decide who may speak for the recognised holder and what change is being requested.
This regional texture is not an argument for lower standards. It is an argument for standards written around facts rather than around a preferred style of paperwork. A registry can be strict and still accept that proof from a university, a public body, a privatised carrier and a family ISP will not look the same. The question is whether each file proves the relevant link in the chain.
Regularisation as a market event
In June 2026 LACNIC issued a call to organisations holding or using legacy IPv4 resources. It asked them to contact the registry within six months, from June 16 to December 16, to formalise the relationship, update associated information and justify the right to use the resources. LACNIC also said that if a holder did not contact it within that period, or if after analysis it could not justify its right of use, LACNIC would cease providing registration services to those organisations. Related guidance says legacy resources can be transferred once the right to use them is justified and legal documentation supports the change of holder; after transfer they are no longer legacy and become subject to current policies and obligations.
That is more than an administrative campaign. It is a market event. Done well, it can clean stale records, reduce hijacking risk, identify abandoned space, clarify contact authority and give future buyers or users a stronger basis for diligence. A block that emerges with a recognised holder, current contacts and coherent operational services is easier to value than one surrounded by institutional fog.
Done poorly, the same exercise can feel like a cliff. A legitimate holder may fear that contacting the registry will trigger demands it cannot satisfy quickly, obligations it did not expect or loss of services because old archives are incomplete. A holder that does nothing may preserve the status quo for a while but reduce marketability and increase exposure to hijacking. A buyer may refuse to close until the record is regularised. A broker may charge for navigating the process. A small holder may sell at a discount because it cannot bear uncertainty.
The right standard is patient finality. It must be patient because legacy files come from a period before current documentation expectations. It must be final because valuable resources cannot remain marketable on undocumented stories. Patience without finality rewards fog. Finality without patience punishes history. The balance should be visible in evidence categories, service treatment and reasons given when a claim fails.
Regularisation should not become confiscation by paperwork. Some claims will fail. Some resources may be abandoned. Some parties may be unable to connect themselves to the original holder. Some files may reveal fraud. LACNIC must be able to say no. But the refusal should identify the missing link: original holder not connected, successor evidence insufficient, signer authority unproven, competing claim unresolved, contact control inadequate, service relationship absent or transaction documents not showing the resource. A refusal that names the missing fact improves confidence. A refusal that feels discretionary discounts the whole class.
Nor should regularisation become a quiet conversion of legacy history into ordinary membership on terms holders did not foresee. LACNIC has real reasons to bring records into current service arrangements: security, contact validity, dispute handling, RPKI, reverse DNS and accurate registry data. But if holders believe the only way to preserve services is to accept unclear obligations without a reasoned recognition path, they will delay. The result will be worse data, not better discipline.
The distinction between status and service matters. A legacy block may remain legacy for some purposes while the holder updates contacts or proves authority. A transferred block may lose legacy status and enter current obligations. A disputed block may need service continuity for customers while high-risk changes are paused. Treating every interaction as if it were a transfer creates needless fear. Treating every legacy holder as immune from present obligations creates needless risk. The design should match the action.
The regularisation period also creates a signalling problem. If a block has been reviewed, the market will want to know what that means. Has the holder merely responded? Has contact information been updated? Has authority been accepted for routine services? Has succession been accepted for transfer? Has a dispute been recorded? Has legacy status changed? A single public label will not carry all of these meanings. A disciplined title file can.
The best outcome would be a virtuous circle. Legitimate holders come forward because the path is clear. LACNIC cleans records without erasing history. Fraudulent claims become harder. Buyers and lessees price resources with less private guesswork. Small operators retain more of the value created by their historical continuity. The market still bears scarcity costs, but not the unnecessary premium created by obscurity.
Services are part of title, not afterthoughts
Registry services often appear technical, while title appears legal or commercial. For legacy IPv4, that division is misleading. RPKI, reverse DNS, contact data, transfer logs, abuse reachability and routing history are the operational face of recognition. They are how a chain of title becomes useful on the network.
RPKI is the clearest example. A route-origin authorisation does not by itself settle who owns a resource. It does, however, express registry-backed authority for a route origin. If a legacy holder's authority is uncertain, the creation or change of ROAs may become sensitive. If a dispute exists, changing RPKI state can alter practical control even before a formal holder change occurs. If a legitimate holder cannot access RPKI because old authority is unclear, the resource may be less secure and less valuable. The title file therefore has to connect proof status to certification status.
Reverse DNS is similarly important. For mail, hosting and network operations, reverse delegation is not ornamental. A block with broken or contested reverse DNS is less useful. In some cases, continuity of reverse DNS may be evidence that the same operational chain has persisted. In others, it may show only that an old technical contact retained control after corporate authority changed. The service must be treated carefully: neither proof of title by itself nor irrelevant to title confidence.
Contact data has the same dual character. Accurate contacts improve accountability, but changing contacts may shift the practical ability to request other actions. A low-risk correction, such as updating an abuse contact for a recognised holder, should not be burdened like a high-risk change of holder. Yet a request to replace all contacts before a sale may deserve stronger proof. Registry design should distinguish contact accuracy from commercial control.
Routing history should also be handled with care. Long use of a block by the same network can support a claim of continuity, especially where older paperwork is incomplete. It can show that the claimant is not a stranger. But route history is not enough on its own. A network may have routed a customer assignment, a leased block, a hijacked prefix or space controlled by an affiliate. The economic point is that operational evidence supports the chain; it does not replace the chain.
Service continuity is most delicate during disputes. A registry that instantly breaks services because a document is incomplete may harm customers, downstream networks and innocent users. A registry that allows value-moving changes while a credible dispute exists may reward speed over truth. The sensible default is preservation of the last verified operational state for continuity-preserving services, paired with locks on irreversible or value-moving changes until authority is clearer. Fraud and security incidents require stronger action, but ordinary documentary gaps should not casually disrupt working networks.
Transfers require the strictest joining of service and title. When a block moves to a new holder, the market expects the registry record, contacts, RPKI authority, reverse DNS posture and policy status to move in a coherent sequence. If the transfer strips legacy status, that change should be clear before closing. If reverse DNS will be preserved only temporarily, the parties need to know. If ROAs must be rebuilt, networks need a migration plan. A transfer that settles legally but breaks operational continuity is not a clean market event.
Leasing is less formal and therefore riskier. A lessee may have no holder change in the registry, yet it depends on registry-recognised authority to route, receive reverse DNS support and answer abuse. Where the lessor's title chain is weak, leasing can become a shadow market in stale records. LACNIC does not need to approve every commercial lease to reduce this risk. It can make holder authority, service access and contact accountability clearer, so lessees and upstream networks do not depend entirely on private assurances.
The service layer also protects LACNIC's legitimacy. A registry that says title is uncertain but keeps customer-impacting services stable where appropriate looks like a careful steward. A registry that allows undocumented changes because a commercial transaction is ready looks captured by the market. A registry that withdraws services abruptly from plausible historical holders looks punitive. The economics of confidence are visible in these operational choices.
Dormant records and contested stories
Scarcity makes dormant records tempting. An old entry with stale contacts and little visible activity may be an abandoned resource, a quiet institutional holding, a block used behind old routing arrangements, a forgotten university asset, a resource stranded by corporate dissolution or a target for fraud. The registry has to sort these possibilities without assuming that silence means abandonment or that every old story deserves market recognition.
Dormancy should be approached through notice, inquiry and proportionate consequences. The registry should try to reach the named holder, known successor, associated domains, historical contacts and visible operational users. It should review prior registry interactions, routing evidence, reverse-DNS history and any current use. It should ask for proof of continuity rather than a document selected only because it is convenient for current procedure. If no one can justify the right to use the resource after reasonable notice and review, withdrawal of services may be defensible. The legitimacy of that result depends on the process being visibly about record truth, not institutional convenience.
False claims need a firmer response. A party relying on forged documents, irrelevant corporate filings, misused contacts, hijacked mailboxes, misleading asset stories or bought access to old accounts should not receive a clean record. The registry should preserve evidence and block the change. It should also learn from the attempt. Common fraud patterns can be summarised in anonymised public guidance so legitimate holders know what risks to avoid. Fraud control and market confidence strengthen each other when the rules are precise.
The hardest cases are incomplete but plausible. A university can prove continuity but cannot find the original allocation letter. A family ISP can show decades of operation but not every shareholder document. A public body can show current responsibility but not a private transfer contract. A successor can show acquisition of a network business but not an address-specific schedule. These files should not be treated as either clean or worthless. The registry should be able to grant recognition for lower-risk services while requiring stronger proof for transfer, sale, split or high-value change.
Competing claims require particular discipline. A founder may say the block was personal. A company may say it was corporate. A successor may say a merger included all network assets. A seller may say an asset purchase transferred the address relationship. A creditor may assert rights after insolvency. A government body may assert public ownership of a resource used by a privatised carrier. The registry cannot resolve every underlying dispute. It can say what actions are frozen, what facts are missing, what evidence would matter and whether an external decision is needed.
A dispute flag should protect the record without destroying value unnecessarily. An unsupported complaint should not create a hidden veto. A credible competing claim should not be ignored because a buyer is ready. A court order should be respected within its scope. A corporate dispute should not automatically break reverse DNS for customers who have nothing to do with the conflict. The flag should describe consequence: no holder change, no transfer, no split, no RPKI change, routine abuse-contact update allowed, current reverse DNS preserved, review pending, external decision required. Precision turns a dispute from rumour into risk that can be managed.
Dormant and contested records also test the relationship between public transparency and confidentiality. Market participants need to know that a resource is not clean if a real dispute exists. They do not need to see private contracts, personal data or security-sensitive evidence. A public history log can record status changes, transfer dates where applicable and standardised dispute or review labels without exposing the file. The aim is not spectacle. It is to prevent false confidence.
The temptation in scarce markets is to seek finality at closing speed. A buyer wants the block. A seller wants proceeds. A broker wants completion. A quiet or contested old record becomes a problem to be pushed through. LACNIC's role is to resist that pressure when the chain is weak and to move with confidence when the chain is proven. The market will accept strictness more readily than caprice. What it cannot price is a record that looks clean until a rival appears or a service breaks.
The proof premium falls hardest on small holders
Legacy title proof is a fixed cost, and fixed costs are regressive. A local legal opinion costs roughly the same whether the block is a /24 or a /16. Translation costs do not fall neatly with address count. Staff time consumed by a registry file may be minor for a national carrier and significant for a small provider. Historical reconstruction may require the same archive search, officer certificate or courthouse record whether the resource supports a regional network or a local hosting business.
This proof premium affects who can monetise old resources. A well-capitalised holder can regularise first, then negotiate from strength. A small holder may need sale proceeds to fund the proof work and therefore negotiate before regularisation. That weakens its position. The buyer demands a discount for taking process risk. Escrow holds back funds until recognition occurs. Counsel narrows warranties. A broker becomes essential. The holder's claim may be valid, yet part of its value moves to parties with cash and procedural knowledge.
The same premium affects use rather than sale. A small network that depends on an old block may avoid updating contacts because it fears opening a file it cannot finish. It may delay RPKI adoption because it does not know whether a service request will trigger a title review. It may preserve old reverse DNS because change feels dangerous. It may rely on a retired founder's memory instead of formalising authority. These behaviours are bad for the registry, but they are rational if the cleanup path is unclear.
The answer is not weaker proof for small operators in high-risk cases. That would invite fraud and create a second-class ledger. The answer is clearer proof. LACNIC can identify ordinary evidence categories for common patterns: unchanged holder, name change, university reorganisation, public-body succession, privatised carrier, family succession, merger, asset purchase, insolvency, long-routed operational use, stale-contact recovery and disputed claim. For each category it can explain the fact to be proven and the kinds of evidence that may prove it.
Staging would help. Some actions are low risk and improve the record: updating an abuse contact, adding a current administrative contact after authority is shown, correcting a name spelling, recording a current domain, preserving existing reverse DNS while proof is reviewed. Some actions are high risk: transferring a block to an unrelated party, changing RPKI authority during a dispute, splitting a resource or changing the recognised holder after a contested succession. Proof should match consequence. A current holder trying to make the record more accurate should not be treated like a stranger trying to sell a disputed asset.
Language and local fit matter. Spanish, Portuguese and English guidance should be equally practical. Caribbean operators should not have to infer rules from continental assumptions. Brazilian and Mexican operators should understand how national channels interact with regional recognition. Public-sector holders should see examples relevant to official acts. Universities should see examples relevant to institutional continuity. Plain language is not simplification. It is transaction-cost reduction.
Small-operator-safe proof also means accepting evidence that proves the fact even if it is not the most elegant evidence. Longstanding invoices, old service records, tax registrations, domain history, routing continuity, board minutes, notarial statements, regulator correspondence and officer certificates can all help when stronger documents are unavailable. None should be accepted blindly. But a rule that recognises only the paper habits of large corporate transactions will transfer value away from legitimate small holders and toward repeat players.
There is also a timing issue. If regularisation windows are too short for small holders to gather records, they may fail not because their claims are weak but because their archives are thin and their staff scarce. LACNIC can require engagement within a fixed period while allowing phased evidence for plausible files. Early contact should be rewarded when the holder is cooperative, the claim is credible and services are not being changed in a way that transfers value. The market benefits when legitimate holders come forward early rather than wait for a sale.
The proof premium will not disappear. Scarce assets require diligence. But unnecessary premium is a design failure. A registry cannot change the economic fact of IPv4 exhaustion. It can reduce the avoidable cost created by unclear categories, inconsistent service treatment and fear that asking for cleanup will endanger the resource.
What the title file should contain
The title file is not one magic document. It is a structured memory of why the registry recognises the current state of a resource. For a legacy block, it should begin with original allocation facts: the historical holder, resource range, date or period if known, allocation context, predecessor registry and any early correspondence or public record supporting the entry. The purpose is not nostalgia. It is to preserve the root of recognition.
The file should then record identity evolution. Name changes, corporate continuations, mergers, public reorganisations, privatisations, asset transfers and successor relationships should be captured as categories, with the relevant proof type noted. Confidential documents can remain private. The registry still needs enough durable structure that future staff do not have to guess why a change was accepted. A later buyer should not rely on the memory of one employee or one lawyer.
Authority should be separated from identity. The fact that an organisation exists does not prove that a particular person can transfer its resources. The file should record who can act for the holder, how authority was verified and whether that authority is limited to a particular action. A technical contact may be authorised for reverse DNS but not for sale. A lawyer may be authorised for a transfer but not for routine operations. A subsidiary may operate the network while the parent remains the recognised holder. Precision prevents future conflict.
The service relationship should be explicit. Is the resource still legacy? Has it entered a membership or service agreement? Was status changed by transfer? Which policies and obligations now apply? Which services are available? What happens to RPKI, reverse DNS and contact management? If a transferred legacy resource loses legacy status, the file should show that event clearly. Market participants can price changes they understand. They fear changes that appear only after trouble.
Dispute status should be recorded without turning every complaint into permanent contamination. A title file can distinguish an unsupported objection, a credible competing claim, a court order, a pending corporate dispute, a resolved conflict and an ordinary documentary gap. It can record which actions are paused and which services continue. A dispute flag should protect the record, not destroy value unnecessarily.
Operational continuity should be included. The file should reflect whether contacts are current, whether reverse DNS is delegated appropriately, whether RPKI authority exists or is unavailable, whether route history supports the claimed operational chain and whether abuse responsibility is reachable. These details are not substitutes for legal continuity, but they are evidence of live responsibility. They also tell future reviewers whether a proposed change preserves or disrupts existing operations.
The title file should also separate evidence strength. Original allocation records, current legal existence, formal succession documents and authorised-signatory proof may be primary evidence. Routing history, invoices, old domains, technical correspondence and long service use may support the chain. A local officer statement may be useful where archives are incomplete, but it should not carry the same weight as a clear merger document for a high-value transfer. Marking evidence strength avoids both credulity and unfair rejection.
Reasons matter. When LACNIC accepts regularisation, denies it, requests more proof, limits a service, records a dispute or changes status after transfer, the reason category should be preserved. This is not a call to expose private documents. It is a call for the ledger to be auditable. A trusted registry is not one that never uses judgment. It is one whose judgment leaves a trail that a later reviewer can understand.
Public history should be used where appropriate. The public record need not reveal contracts, personal data or sensitive security methods. But it can show holder, resource range, status, current contacts, public transfer entries, regularised status where useful, dispute or review labels where proportionate, and service posture when it affects reliance. A market cannot price what it cannot see. A public history log is not a substitute for the private title file. It is a confidence signal derived from it.
The title file must also survive staff turnover. Legacy cases can span decades. The person who understands why a public university's file was accepted, why a carrier succession was treated as continuous or why a Caribbean family ISP received conditional recognition may leave. If the reasoning is not recorded, the next review begins again. That raises cost and weakens confidence. Institutional memory has to be made institutional.
Review, appeal and restraint
Review is often treated as a safeguard for disappointed applicants. In a legacy title market, it is also a price stabiliser. A buyer, seller or holder can accept a strict evidence rule if the rule has a reason and a review path. The deepest discount is created not by strictness but by uncertainty over whether a decision reflects policy, law, missing evidence, staff preference, payment status, a dispute hold or unresolved identity.
A meaningful adverse decision should identify the missing link. If LACNIC cannot connect a successor to the original holder, it should say so. If the signer lacks authority, it should say so. If an asset purchase excludes the relevant network or fails to mention resources, it should say so. If a court order prevents action, the legal basis should be identified to the extent possible. If a competing claim exists, the parties should know which actions are frozen and what evidence could change the status. The aim is not to litigate in public. It is to make the path knowable.
Review should be proportionate to stakes. A routine support request does not need a heavy process. A denial that prevents a legacy holder from receiving registration services or transferring a high-value block deserves a stronger path. The reviewer should not merely ask whether the same staff remains comfortable. It should ask whether the action was properly classified, whether the evidence standard was applied correctly, whether alternatives were considered and whether service continuity was treated narrowly.
Appeal paths protect the registry as well as the holder. Staff reviewing a valuable legacy block may face pressure from a buyer, seller, broker, government body, creditor, former employee or competitor. Clear categories and review procedures give staff a shield. They can point to the evidence needed, the services that can continue, the changes that are blocked and the route for reconsideration. A registry that leaves these questions to informal discretion makes every hard case more personal than it should be.
Aggregate reporting would reinforce review without exposing private files. LACNIC could report counts of regularised resources, unresolved files, common documentation defects, transfer delays, dispute categories, appeal outcomes and service-continuity incidents. Such data would help the market distinguish ordinary friction from structural risk. If most cases resolve quickly and a small percentage require deeper proof, confidence rises. If delays cluster around public-sector records, Caribbean corporate forms or family succession, guidance can be improved. If denials are rare but unexplained, rumour fills the gap.
Restraint is the other side of review. A registry should protect uniqueness, accuracy, security and policy compliance. It should not become the commercial arbiter of every bargain attached to an old resource. If a holder with a clean chain wants to sell under the rules, the registry's concern is whether the recognition can change safely and correctly, not whether the price is attractive. If a holder leases space, the registry's concern is accountability and service integrity, not the private economics of every lease. The more LACNIC limits itself to record truth and service reliability, the more legitimate its strictness will appear.
Restraint also means preserving continuity during uncertainty. Where authority is incomplete but plausible, the registry can avoid irreversible change while maintaining continuity-preserving services. Where fraud appears, stronger interruption may be necessary. Where a dispute is credible, value-moving changes can be frozen. Where a holder merely needs time to collect public-sector documents, the record should not be treated as if a fraudster had appeared. The discipline is to distinguish risk types.
The market does not need LACNIC to promise that every old block is clean. It needs to know how dirt is identified, contained and cleaned. It needs to know when a dispute matters, when a documentary gap matters and when operational continuity will be preserved. It needs reasoned outcomes rather than mystery. Review turns discretion into institution.
Lessons from other registry histories
Other RIR histories are useful as warnings, not templates. ARIN's experience with legacy resources shows how early allocations can sit uneasily beside later service agreements, transfer rules and security services. The RIPE NCC's legacy environment shows that mature registries still face the line between historical reliance and present obligations. APNIC's diverse region shows how varied legal systems and national channels complicate evidence. These comparisons help describe the structure of the problem. They do not decide LACNIC's answer.
AFRINIC is the sharper warning because institutional stress and litigation have shown how confidence in the registry itself can become a market risk. The point is not that LACNIC faces the same path. It does not. The point is that when resource holders begin to doubt whether registry records, services and decisions are insulated from institutional conflict, every title question becomes more expensive. Transfers slow. Buyers discount. Litigation becomes part of risk management. Ordinary requests are interpreted as power moves. The ledger may continue to function technically while confidence in the gatekeeper weakens.
The lesson for LACNIC is preventive. Keep the title standard narrow before a crisis tests it. Preserve last verified operational state during disputes unless law or security requires otherwise. Separate fraud control from business judgment. Maintain public history where appropriate without exposing confidential evidence. Make regularisation outcomes visible in aggregate. Ensure that RPKI and reverse DNS continuity are not collateral damage in a documentary disagreement. Provide review before one weak file becomes a market panic.
Global experience also warns against institutional self-description as proof. Official materials are indispensable for facts: service region, policy text, transfer conditions, RPKI services, reverse DNS, waitlist status, regularisation calls and governance procedures. But an institution's statement that it is open, community-based or a steward does not settle the economic issue. The market asks whether records are reliable, proof rules are proportionate, services are predictable and discretion is constrained enough for old resources to be valued without fear of arbitrary treatment.
LACNIC's region needs its own settlement. A North American legal habit may be too expensive for smaller Caribbean holders. A European service practice may not translate neatly to markets with different currency constraints and public-sector records. An Asia-Pacific analogy involving national channels may fit Brazil or Mexico only in part. The useful comparison is not imitation. It is diagnosis: which practice lowers the cost of trust in this region?
That cost is not abstract. It appears in legal fees, escrow terms, delayed transfers, broken reverse DNS, withheld ROAs, leasing opacity, lower sale prices and cautious customers. It also appears in the willingness of legitimate holders to contact the registry before a crisis. If the process is seen as a trap, the registry will learn less. If it is seen as disciplined and fair, holders have an incentive to clean records before a market transaction forces them to.
A practical settlement for legacy title
The first element is title-file discipline. LACNIC should preserve the evidence categories behind each material legacy decision: original allocation, institutional continuity, corporate succession, authorised signer, current contact, service relationship, dispute status, operational delegation and status change. The file should be auditable and durable across staff changes. It should not depend on informal memory or private relationships.
The second element is an evidence map. LACNIC should publish common paths for universities, public bodies, privatised telecoms, corporate mergers, asset purchases, family succession, insolvency, name changes, stale-contact recovery and national-channel interaction. The map should state what each document type proves and what substitutes may be acceptable. It should distinguish primary evidence from supporting evidence. This would reduce the advantage of repeat players and discourage opportunistic claims.
The third element is action-based proof. The burden should match consequence. Updating an abuse contact should not require the same proof as transferring a block to an unrelated buyer. Preserving reverse DNS while proof is reviewed should not be treated like splitting a resource. Changing RPKI authority during a dispute should require more care than adding a current contact for a recognised holder. A narrow proof rule is not a weak rule; it is a rule aimed at the relevant risk.
The fourth element is dispute-flag discipline. A real dispute should block value-moving changes until authority is clearer. It should not automatically destroy operational continuity. The registry should state which services remain, which changes are frozen and what evidence or external decision can resolve the flag. Unsupported objections should not become hidden vetoes. Credible conflicts should not be brushed aside because a transaction is ready.
The fifth element is appeal and review. Material denials, service withdrawals, transfer holds and regularisation failures should be reasoned and reviewable. The holder or claimant should know which fact failed. The review path should be practical for a small operator, not only for a large company with advisers. Reviewability is not hostility to staff judgment. It is how staff judgment becomes institutionally credible.
The sixth element is public history where appropriate. Not every document belongs in public. Many files include confidential contracts, personal data or security-sensitive evidence. But the public record can show enough to support reliance: holder, resource range, transfer date where applicable, status, current contacts, public transfer-log entries, relevant service posture and standardised labels for regularised or disputed resources where proportionate. Markets price visible risk better than rumour.
The seventh element is RPKI and reverse-DNS continuity. Regularisation and transfers should be measured not only by record changes but by whether certification, reverse resolution, contact data and abuse responsibility remain coherent. During ordinary disputes, the default should be preservation of the last verified operational state for continuity-preserving services, with locks on irreversible or value-moving changes. Fraud and security incidents may require interruption, but documentary uncertainty should not casually break customer service.
The eighth element is small-operator-safe proof. A public university should not be penalised because its continuity appears in administrative acts rather than private acquisition contracts. A family ISP should be able to use local succession evidence. A Caribbean provider should not face unnecessary translation and opinion costs for a low-risk correction. A registry that defines proof by fact rather than paper style can be strict and fair at the same time.
The ninth element is communication. Legacy holders should be told why regularisation improves value, what documents to gather, what happens if evidence is incomplete, which services may be affected and how to seek review. Fear of the registry is bad for the registry. It keeps records stale. Clear communication is a security tool because it brings legitimate holders into the open before fraudsters do.
The final element is institutional humility. LACNIC should protect the ledger, not make itself the author of legacy value. Old holders, networks, customers and market demand created much of that value. The registry supplies the confidence layer that lets others rely on it. The more valuable the resource, the more important it is that registry intervention stay tied to record truth, authority, uniqueness, security and clear policy compliance.
Conclusion: title as market confidence
Legacy allocation title is not a demand that LACNIC abandon its registry duties. It is a demand that those duties be understood economically. Old IPv4 records now support scarce assets. The value of those assets depends on confidence that the recognised holder can be identified, that succession can be traced, that contacts are real, that services continue, that disputes are marked, that transfers can settle and that regularisation distinguishes weak archives from false claims.
LACNIC's legacy environment is especially sensitive because the region's history is diverse. Universities, public institutions, privatised carriers, family ISPs, regional groups, island operators and cross-border acquisitions do not leave identical document trails. A proof rule that ignores this variety will punish legitimate holders and reward the best-resourced counterparties. A proof rule that accepts every old story without discipline will invite fraud and weaken the market. The narrow middle is a title-confidence system.
The June 2026 call makes the issue immediate. It can clean the ledger and raise the value of legitimate old resources. It can also create fear if holders see it as a cliff. The difference will lie in evidence categories, proportional service treatment, review paths, operational continuity and aggregate transparency. Regularisation should improve title, not turn history into a paperwork trap.
Transfers, leasing, RPKI, reverse DNS and contact data are all downstream of the same chain. A buyer wants finality. A lessee wants authorised use. An upstream wants reliable route authority. A mail operator wants reverse DNS. A bank wants diligence. A public institution wants continuity. A registry wants accurate records. These interests can coexist if the ledger is disciplined. They collide when recognition becomes discretion over commercial choice.
The correct conclusion is modest. LACNIC does not need to declare IPv4 ordinary property to respect legacy title. It does not need to approve every commercial arrangement to make leasing and transfers safer. It does not need to treat old allocations as untouchable to respect historical reliance. It does need to make the chain of recognition clear enough that market participants can price risk without guessing the registry's mood.
In a scarce-address economy, institutional memory is part of the asset. The old allocation, the surviving institution, the successor document, the authorised contact, the service relationship, the dispute record, the ROA, the reverse-DNS delegation and the public holder record together form the confidence layer. Strengthen that chain, and LACNIC strengthens both the market and its own legitimacy. Let the chain remain foggy, or turn proof into gatekeeping, and the market will respond with discounts, escrow, private opacity and avoidable conflict.
The old IPv4 block in the opening scene is therefore not merely an artefact of early internet history. It is a test of whether a regional registry can preserve memory without freezing it, demand proof without erasing history, support markets without regulating every bargain and protect the ledger without becoming the gate. That is the economics of legacy allocation title.