The operator who needs recognition
Consider a modest network in the Caribbean, a family-owned access provider in an Andean secondary city, a municipal network that has survived several reorganisations, or a wholesale carrier serving customers across a Central American border. Its problem is not philosophical. It has a block of IPv4 addresses, perhaps some IPv6 space, an autonomous system number, customers who expect reachability, upstreams that require clean contact data, and a transaction whose value depends on whether the outside world can tell who controls the resources. A bank wants comfort before financing fibre expansion. A buyer wants to acquire an ISP and fold its address holdings into a larger platform. A cloud customer wants assurance that route-origin authorisation will survive a restructuring. An abuse desk wants a responsible party. A government procurement office wants proof that the network can keep operating after a name change.
In each case the operator is not asking the regional internet registry to bless its business plan. It is not asking for an opinion on the price of IPv4, the wisdom of leasing, the attractiveness of a buyer, the social merit of an acquisition, or the regional virtue of a particular deployment. It is asking for something narrower and more valuable: reliable recognition. The registry record should say which organisation is recognised for a resource, who is authorised to act for it, what history explains the current state, which contacts are responsible, which transfer or succession has been accepted, and which operational services can safely follow from that recognition.
That sounds administrative, almost dull. It is not. In a post-exhaustion IPv4 market, the registration record is the settlement layer for scarcity. It is the place where commercial counterparties, routing-security systems, address brokers, acquirers, lenders, upstreams, abuse reporters and other registries look when they need a fact that is more durable than a sales document or an email from a former employee. The record does not create all economic value. Networks create value by serving customers. But the record lets other people rely on claims about control. Without it, resource value becomes more expensive to finance, transfer, defend and operate.
The danger is that the same record can become a gate. Nobody needs to announce a new industrial policy for Latin American and Caribbean address resources. No one needs to say that the registry will now decide which business models deserve IPv4. It is enough for recognition to depend on unclear delay, repeated documentation requests, unresolved account standing, payment friction, compliance holds, staff discomfort with leasing, informal views about buyer deservingness, or suspicion that a price is too high. A request that begins with the question "is this the real holder?" can drift toward "should this holder be allowed to do this?" The first question is necessary recognition. The second is discretionary permission.
LACNIC sits exactly where that distinction matters. It serves Latin America and parts of the Caribbean. It is part of the global regional internet registry system, alongside the other RIRs that coordinate number-resource administration under the broad architecture of the internet's identifier system. It is not a state, a bank, a competition authority, a telecom regulator, or a court. It does not run the networks whose resources it records. It does not finance submarine cable repairs, decide retail broadband tariffs, replace storm-damaged equipment on small islands, or choose whether an ISP should buy, sell, lease or conserve IPv4. Yet because its record is treated as authoritative by markets and operational systems, its recognition can determine whether capital moves.
The region makes the power unusually sensitive. A common rule can fall very differently in Brazil, Mexico, Argentina, Chile, Colombia, Jamaica, Trinidad and Tobago, Barbados, Belize, Haiti or a small island jurisdiction with limited legal infrastructure and expensive banking channels. Some members can pay foreign invoices easily; others face exchange controls, dollar shortages, procurement delays, correspondent-banking checks or de-risking by banks that find small telecom payments more troublesome than profitable. Some have counsel on retainer; others keep records through cooperative boards, municipal offices, universities, public utilities, family companies or recently restructured carriers. Spanish, Portuguese and English all matter, and practical participation is not equally cheap in all three.
This is not an argument against registry authority. A registry without authority would be useless. LACNIC must protect accounts, reject forged requests, preserve provenance, maintain contact and abuse responsibility, support reverse DNS and resource certification, and recognise transfers only when the record can safely be changed. It remains legitimate when it uses recognition to settle those facts. It risks losing legitimacy when recognition becomes a permission system for economic choices that should belong to operators, customers, counterparties, courts, telecom regulators and markets.
The boundary that makes scarcity governable
The cleanest way to understand the issue is to separate two kinds of decision. A registry must decide whether a record can truthfully change. It should be cautious about deciding whether a market transaction is good.
Necessary recognition asks practical questions. Does the resource exist in the registry record? Is the current holder the entity that the record says it is? Has that entity changed name, legal form, ownership or control? Is the requester authorised to bind it? Is there a competing claim, a court order, a sanctions issue or a documented dispute? Does the transfer fit adopted resource policy? Are contacts accurate enough for operational use? Is reverse DNS being delegated by someone with authority? Is the RPKI certificate relationship consistent with the resource record? Is an account defect material to the requested change, or merely an ordinary billing matter that can be cured?
Discretionary permission asks a different class of question. Is the buyer the kind of buyer the registry likes? Is the price unseemly? Is the seller monetising too much? Is leasing evidence of speculation? Is the recipient too large, too foreign, too financial, too cloud-oriented, too brokered, too distant from the original allocation purpose, or insufficiently embedded in a preferred regional story? Should an operator with payment delays be prevented from moving resources even when the move would make the record more accurate? Should an acquirer have to prove that it deserves the address space rather than prove that it lawfully controls it?
The difference can be disguised because both forms of decision use the same vocabulary. "Review" can mean checking authority or judging merit. "Compliance" can mean obeying law or avoiding discomfort. "Stewardship" can mean maintaining a reliable record or substituting institutional preference for market choice. "Risk" can mean risk of fraud or risk that a transaction violates someone's economic sensibility. The words are not enough. The test is whether the concern has a direct connection to record truth, operational security, legal validity or adopted policy. If it does, the registry is doing its job. If it does not, the registry is beginning to govern the market from inside the record.
That restraint matters more after scarcity. When address space was allocated from available pools, a registry naturally asked about need. The point was to distribute new resources in a way that supported network growth and conservation. After exhaustion, much of the action shifts to resources that have already been issued. They move through mergers, acquisitions, transfers, internal reorganisations, delegated operations and leasing-like arrangements. The registry still has policy duties. It should not ignore fraud, hoarding rules, sanctions, duplicate claims or eligibility requirements. But allocation-era habits can become dangerous if they are carried into transfer-era cases as moral judgement. A party that buys scarce resources at market price is not making the same request as a party that asks for free allocation from a shared pool.
The boundary is not anti-regulatory. Public authorities may regulate telecom markets, competition, sanctions, procurement, insolvency and national security. Courts may decide ownership disputes. Lenders and customers may price uncertainty. LACNIC's special mandate is different: it keeps the number-resource record useful. The more valuable the record becomes, the more important it is that the keeper of the record does not treat every dependency as a right to decide.
What the record is for
A registry record is often described as a list of number resources and holders. That is too thin. A useful record binds several functions that would otherwise have to be recreated through private diligence every time a network changed hands, a contact failed, or a route had to be trusted.
The first function is identity. The registry must know whether the organisation in front of it is the organisation in the record, a lawful successor, an authorised representative, or an impostor. This cannot be optional. IPv4 scarcity makes theft attractive. Old address blocks can be valuable enough to justify forged signatures, hijacked email accounts, false corporate papers or opportunistic claims over defunct entities. An identity check protects the entire market. But its purpose is protection against false change. It is not a licence to review the organisation's business model each time it seeks recognition.
The second function is authority. A company may exist while the person making the request lacks power to bind it. A public body may have changed ministries. A cooperative may require board approval. A university network may have moved from a research office to a central IT department. A carrier group may have shifted assets among subsidiaries in several countries. A family ISP may have changed control after succession or sale. The registry must ask who can sign, who can update contacts, who can approve a transfer and who can maintain resource certification. Authority questions are unavoidable. They should remain questions about authority.
The third function is provenance. Scarce resources acquire history. A buyer wants to know whether a block is clean. A lender wants to know whether it is entangled in a dispute. A purchaser of a telecom asset wants to know whether the resources belonged to the target, a parent, a public body, a customer, a defunct affiliate or a predecessor entity. An upstream wants confidence that the party seeking routing changes is not relying on stale paperwork. A registry that preserves a coherent chain of recognised control reduces diligence cost. A registry that relies on personal memory, opaque practice or unexplained exceptions increases risk.
The fourth function is contact accuracy. Registration data is not decorative. It is used in abuse handling, security response, procurement, legal diligence, operational escalation and routine coordination among networks. Stale contacts can mean that phishing reports go nowhere, DDoS mitigation escalations fail, law-enforcement notices misfire, or counterparties cannot find the person authorised to correct a record. But the remedy for a contact defect should normally be correction, notice and staged cure. Treating stale contacts as an occasion to re-open the holder's entire economic relationship with its resources would turn a record problem into a permission event.
The fifth function is transfer recognition. Once ordinary new IPv4 supply has run out, address movement happens through transfers, mergers, acquisitions, reorganisations and operating arrangements that resemble leasing or delegation. The registry need not set the price or bless the financing. It does need to record the result when parties have authority, the resource is eligible, required policy conditions are met and no competing claim blocks recognition. The market value of the resource depends partly on whether this recognition is predictable.
The sixth function is account standing. A registry needs accurate account information, a billing relationship and rules for members that ignore obligations. It cannot maintain a serious record if accounts are abandoned, invoices are never paid, or records cannot be reconciled. Yet account standing is also a powerful lever. If a late payment, slow bank transfer, missing form or procurement delay can freeze unrelated record changes, administrative housekeeping becomes capital control. A disciplined registry distinguishes between a defect that undermines reliable recognition and a defect that should be cured without destabilising the record.
The seventh function is operational delegation. RPKI and resource certification translate recognised resource control into cryptographic assertions that routing systems can use. Reverse DNS gives operational meaning to address holdings. Abuse contacts identify responsibility. Publication services and routing-related data let networks automate trust. The registry is not a router, but it is a dependency in the trust chain surrounding routing and operations. The more important these services become, the more dangerous it is to use them as leverage in disputes that do not directly threaten record integrity.
The eighth function is continuity. Number resources can outlive brands, products, executives, ministries, concessions, public utilities and corporate forms. Latin America and the Caribbean contain legacy public networks, privatised telecom assets, municipal projects, university allocations, state-linked carriers, family operators, bankruptcies and cross-border acquisitions. A useful record helps lawful continuity appear. A gate treats historical complexity as an opportunity for discretion.
Exhaustion turned administration into price
LACNIC entered the exhaustion phase of IPv4 allocation in the middle of the 2010s and later reached the point where ordinary supply from its remaining pool was effectively unavailable for planning. The exact labels of the phases are less important than the economic change. Operators could no longer assume that fresh IPv4 would arrive from the registry on ordinary terms. Existing holdings became working capital.
Technical language often resists the word "asset", and for good reason. Number resources are not private land. They are globally unique identifiers administered through contracts, policy and registry recognition. But economics is less formal than legal classification. A resource that is scarce, productive, transferable under rules, relied upon by customers and recognised by a trusted record will behave like capital. Parties will pay for it. They will discount it when recognition is uncertain. They will structure acquisitions around it. They will finance expansion on the assumption that address capacity remains usable. They will litigate, bargain or walk away if they fear that the record cannot be updated.
That change alters the meaning of small administrative acts. A transfer delay is not merely a slow ticket. It can change a purchase price, extend escrow, disrupt a merger closing or force a seller to accept a discount. A documentation request is not merely a file note. It can require translations, notarisation, counsel, board action or public-sector approvals. A compliance hold is not merely caution. It can immobilise value while currency, inflation or financing conditions move. An account-standing dispute is not merely a billing inconvenience. It can become a block on liquidity at exactly the moment when a holder needs capital or an acquirer needs integration.
The market cannot easily route around this. An operator cannot choose a second LACNIC for the same Latin American or Caribbean resources. It may be able to route packets without universal admiration, but it cannot easily replace recognised registration when a bank, broker, buyer, customer, upstream, RPKI system or another registry asks for the authoritative record. That gives the registry a bottleneck position. A bottleneck can be legitimate when its function is narrow, predictable and reviewable. It becomes dangerous when the bottleneck holder uses timing and judgement to influence market outcomes.
The distributional effects are not neutral. A large carrier can survive months of uncertainty better than a small ISP. A multinational cloud platform can hire lawyers, maintain specialist registry staff and absorb working-capital delays. A cooperative access provider may have one engineer who handles peering, customer support, emergency repairs, accounting and registry correspondence. A major country with deep banking infrastructure may treat a delayed foreign invoice as routine. A small island operator may face correspondent-bank questioning, dollar scarcity, compliance checks, high wire fees and a bank relationship that does not regard telecom registry payments as a priority. Formally equal procedures can therefore favour capital-rich operators.
Liquidity in this context is a public-interest concept, not a demand for speculation. It means that resources can move toward productive use with predictable evidence, predictable timing and clear responsibility. A liquid transfer market helps new entrants that cannot obtain fresh space, sellers that need capital, networks restructuring after acquisition, public or corporate successors that must clean old records, and operators that choose leasing or delegation because ownership is too expensive. Illiquidity benefits incumbents and those already large enough to carry inefficiency.
IPv6 does not remove the problem. IPv6 is the structural answer to address scarcity, and LACNIC's work to encourage deployment and competence is legitimate. But IPv6 progress remains uneven across customer equipment, enterprise systems, public procurement, security appliances, legacy applications, foreign counterparties and consumer support. Many networks need both: IPv6 for long-term growth and IPv4 for current revenue. Treating IPv4 demand as embarrassing or morally suspect would not accelerate transition. It would merely misread the balance sheet of operators that still have to serve customers today.
This is why the registry's ordinary administration has macroeconomic significance. In a stable, low-interest environment, a three-month delay may be inconvenient. In a country with inflation, exchange controls or volatile financing, it can alter the economics of a transaction. LACNIC does not cause those conditions. But its procedures can either reduce regional transaction cost or add another unpredictable layer to it.
Delay as policy without a vote
Delay is the first administrative lever by which recognition turns into control. Every registry must take time with high-risk changes. A contested transfer, suspected fraud, compromised account, court notice or unclear public-sector succession cannot be handled like a routine email update. Speed without verification would invite theft. The issue is not whether review takes time. The issue is whether time is bounded, explained and measured.
Delay becomes gatekeeping when ordinary cases lack reliable service standards, when applicants cannot tell whether a file is waiting for staff, documents, legal review, payment, policy interpretation or a third-party response, and when long-tail cases disappear into private correspondence. Average processing time is not enough. A registry can report respectable medians while a small number of commercially important cases sit for months. In capital markets the tail matters. It is where uncertainty is priced, where sellers renegotiate, where buyers abandon, and where counterparties learn whether the record can be relied upon.
The price of delay varies by region. In a high-interest environment, every month has a financing cost. In a currency-stressed country, a quoted dollar price can move away from a buyer before recognition is complete. In a public-sector procurement process, an administrative hold may push a transaction into a new budget cycle. In an acquisition, integration plans may depend on whether addresses can be moved, certified and delegated. In a disaster-prone island market, liquidity may be needed after a hurricane or cable failure, not after an indefinite review. Delay is not merely time. It is a redistribution of bargaining power.
The institutional remedy is not a promise that every case will be fast. It is a habit of classifying and publishing time. LACNIC should be able to distinguish routine transfers, inter-regional transfers, merger updates, public-sector successions, account recoveries, disputed authority cases, legal holds, suspected fraud, payment-related holds and applicant-caused incompleteness. It should publish aggregate processing data, including long-tail cases and reasons for pauses. Confidentiality can be preserved without hiding the system's performance.
The registry should also make procedural state visible to the applicant. A holder should know whether the next step is evidence, payment, staff review, legal review, policy interpretation, third-party confirmation or appeal. It should know whether the delay is caused by its own missing material or by the registry's queue. It should know whether operational services will continue while the matter is unresolved. This is not customer-service decoration. It is the difference between a record system and an opaque permission office.
Delay is also a temptation because it avoids hard decisions. A registry that denies a transfer may have to give reasons. A registry that repeatedly asks for more material can achieve the same practical result without a formal denial. That is why repeated documentation rounds should be tracked. How many times does the registry request new evidence after the initial file? How often do applicants abandon cases? How many requests are withdrawn after long silence? These are not trivial operational statistics. They reveal whether discretion is being exercised through friction.
The most important discipline is proportionality. High-risk cases deserve time. Low-risk cases should not be dragged into high-risk treatment because the resource is valuable or the commercial context is unfamiliar. The more scarce IPv4 becomes, the easier it is to treat every change as exceptional. If every case is exceptional, the registry has stopped being a ledger and become a judge of convenience.
Documents, language and the cost of proving the obvious
Documentation is the ordinary language of a reliable record. It is also one of the easiest places for gatekeeping to hide. A demand for documents sounds neutral. Its burden depends on legal system, language, corporate form, staff capacity, access to counsel and the nature of the institution being documented.
The registry should require proof of identity, authority, succession and eligibility. It should not apologise for doing so. But proof should be organised into published evidence categories. A routine contact update should not require the file of a disputed acquisition. A corporate name change should not be treated like a suspicious transfer. A public-sector reorganisation should not be judged by the paper conventions of a private multinational. An inherited address block should not be frozen merely because the historical record is old and awkward.
The categories should be practical: contact update, change of authorised representative, corporate name change, merger, asset acquisition, insolvency or creditor restructuring, public-sector succession, state-enterprise privatisation, university or research-network reorganisation, lease-related operational delegation, account recovery, disputed authority, suspected fraud, court order and abandoned-record cleanup. For each category LACNIC should state the evidence normally required, acceptable alternatives, translation expectations, notarisation requirements where genuinely necessary, ordinary timing and escalation path.
Such guidance would not weaken scrutiny. It would make scrutiny more precise. Staff could ask for the evidence that goes to the relevant risk rather than negotiating from instinct. Applicants could prepare files before a transaction closing rather than discovering requirements after money is committed. Buyers and lenders could price registry risk more accurately. Small operators would know when counsel is needed and when a plain corporate document is enough. Regular participants would no longer possess an informal advantage simply because they have learned, case by case, what the registry tends to ask.
Language is not cosmetic. LACNIC's region runs through Spanish, Portuguese and English, and the Caribbean's English-speaking networks are not peripheral to the legitimacy of the institution. If transfer guides, payment instructions, legal evidence examples or policy explanations are clearer in one language than another, the cost of compliance becomes unequal. If informal interpretation develops in one linguistic circle, outsiders pay more. If certified translations are demanded unpredictably, a small operator may face a bill out of proportion to the change requested.
The rule should be simple: language asymmetry is governance cost. Spanish, Portuguese and English instructions should have equal practical clarity for important record changes. Translation requirements should be known in advance and limited to cases where precision matters. Staff should not rely on informal explanations in one language to fill gaps in another. Plain-language guidance should exist for members that are not policy specialists. Caribbean operators should not have to infer rules from Spanish or Portuguese meeting culture, and Portuguese-speaking members should not need to follow Spanish-language side discussions to understand a transfer practice.
Public-sector records deserve special care. Ministries split. Regulators are reorganised. Municipal networks are absorbed by national bodies. Public utilities are privatised. Universities move networks from one administrative home to another. Court registries and public gazettes may move slowly or use formats unfamiliar to private lawyers. The registry should not treat unfamiliarity as suspicion. It should state what it needs to know: legal continuity, authority to act, resource responsibility, existence or absence of dispute, and operational contacts. That protects the record without making LACNIC a judge of public administration.
Corporate succession is similar. Latin American and Caribbean telecom assets often move through mergers, fibre carve-outs, tower separations, group reorganisations, bankruptcies, creditor arrangements, share transfers and cross-border acquisitions. Address records can lag behind commercial reality. A disciplined record system helps clean them. A gate treats each cleanup as a chance to reconsider whether the new economic arrangement deserves recognition. The difference affects valuation. Buyers discount businesses whose number resources are hard to integrate.
Excessive proof can defeat the registry's own purpose. Some members will not formally fail. They will stop pursuing cleanup, delay transfers, keep stale contacts, rely on informal arrangements, or avoid updating old records because the process feels too costly. The public record then becomes less accurate. The solution is not laxity. It is evidence proportional to risk.
Account standing and the quiet power of billing
Account standing seems mundane. In practice it is one of the most powerful places where a registry can drift from recognition to leverage. A registry needs fees, updated member information and rules for non-responsive accounts. It cannot maintain services if members disregard obligations. But the account relationship must not become a broad switch that can immobilise the record whenever ordinary administration is untidy.
The hard cases are common in Latin America and the Caribbean. A member may have the money to pay but face exchange controls that delay access to dollars. A bank may require additional information before processing an international transfer. A public-sector entity may be waiting for budget release or procurement approval. A small island operator may face high wire costs, compliance questioning or a correspondent-bank chain that treats a registry invoice as suspiciously small and unfamiliar. A company may have changed name or tax registration and need its invoice corrected before payment can be approved. A hurricane, cable outage or local banking disruption can turn a routine renewal into a management problem.
None of this means fees are optional. It means account defects need categories and cure paths. A late invoice is not the same as abandonment. A payment stuck in the banking system is not the same as refusal. A missing tax document is not the same as a disputed claim to resources. An account under corporate-name cleanup is not necessarily unreliable. The registry should be firm about cure, but careful about what the defect blocks.
The most dangerous move is to use account standing as a universal hold. If a curable billing issue can block a transfer that would make the record more accurate, prevent reverse-DNS updates needed for operations, interrupt RPKI continuity or freeze contact correction, billing has become a capital-control instrument. The registry may intend only to encourage payment. The market will experience it as control over productive resources.
A better approach separates services by their connection to the defect. New discretionary services, voting rights or non-urgent requests might be limited after notice. But publication of the last verified record, critical contact correction, abuse responsibility, reverse-DNS continuity and RPKI state should not be destabilised unless the account problem directly affects authority, security or legal validity. A late payment should not make a route less trustworthy. A procurement delay should not make abuse reports vanish. A billing dispute should not force a buyer or lender to wonder whether the record itself is hostage.
This separation would also reduce perverse incentives. If members fear that admitting a payment problem will freeze unrelated functions, they may avoid communication. If the cure path is clear, they have reason to engage. If the registry can publish aggregate data on payment holds, cure timing, service treatment and exceptional hardship cases, it can show discipline without exposing private financial details.
Currency and payment friction deserve explicit recognition because they are not evenly distributed across the region. Large operators in stable financial systems can comply with international billing requirements more easily. Smaller networks in countries with exchange controls or weak banking links may spend far more effort on the same invoice. Equal treatment does not require pretending these differences do not exist. It requires a process that enforces obligations without allowing payment friction to decide who may participate in the address market.
Transfers without a theology of deservingness
Transfers are where the line between record-keeping and market judgement is most visible. A transfer record should answer whether the transferor has authority, the recipient can be recognised, the resource is eligible, adopted rules are satisfied, the parties have supplied required evidence and no superior claim prevents the change. It should not become a forum for deciding whether the buyer deserves the address block.
Deservingness can enter indirectly. A buyer may look too financial, too foreign, too large, too cloud-based, too brokered or too focused on resale. A seller may appear to be profiting from scarcity. A price may seem high. A transaction may move resources from a small local operator to a regional group. A transfer may be connected to leasing, hosting, address management or corporate consolidation. Each feature may raise questions worth asking if it touches eligibility, authority, fraud or policy. None should become a free-standing reason to slow recognition.
Post-exhaustion markets force an uncomfortable truth: IPv4 addresses will move toward parties willing and able to pay for them. That is what scarcity does. A registry can adopt clear policy constraints through its community process. It can require that records remain accurate. It can prevent false transfers and respect legal orders. But if it tries to use administrative discretion to offset market outcomes it dislikes, it will do so unevenly and opaquely. The result will not be justice. It will be uncertainty.
Need-based thinking is especially difficult after exhaustion. In the allocation era, asking whether an applicant needed space protected a shared pool. In the transfer era, the parties are reallocating already-issued resources at a price. A buyer's need may still matter if a clear adopted rule says so. But the registry should not re-create a private needs tribunal through staff judgement. It is too easy for "need" to become an impression of business virtue, local embeddedness or sympathy for one kind of operator over another.
Price judgement is equally risky. A high price may reflect scarcity, urgency, clean history, block size, routing reputation, timing, currency conditions or strategic importance. It may also reflect speculation. The registry is poorly placed to decide which. If price raises suspicion of fraud, money laundering, sanctions evasion or sham transfer, the registry should act through precise compliance categories. If price merely offends a sense of stewardship, it should not affect recognition.
Buyer identity matters only through relevant rules and risks. A carrier, cloud platform, enterprise network, public body, hosting company, security provider, content platform or address-management firm may all have operational reasons for IPv4. Their business models differ. The registry's record should make the responsible party visible. It should not rank them by institutional affection. Nor should large-country buyers receive de facto advantage because they know the process better, can produce documents faster, or have more informal access.
The same restraint should apply to intra-group reorganisations. A multinational carrier may centralise resources after a merger. A Caribbean group may move holdings among subsidiaries to match licences or customer contracts. A corporate successor may inherit resources from a brand that no longer exists. The registry should be alert to abuse, but it should not treat complexity itself as a sign that the arrangement is less deserving. The question is whether the record can truthfully recognise the new authority and responsibility.
If LACNIC wants transfer markets to be legitimate, the best tools are transparency, predictable evidence and clear responsibility. If it wants to influence the economics of who gets IPv4, it should do so only through adopted policy that members can debate, understand and challenge. Hidden deservingness tests are the worst of both worlds: too soft to be accountable and powerful enough to move capital.
Leasing suspicion and operational reality
Leasing is the issue most likely to expose the difference between moral discomfort and record usefulness. Many technical communities dislike the idea that IPv4 scarcity can generate rent. The discomfort is understandable. Addresses began as technical identifiers, not as income-producing property. Leasing can obscure responsibility, encourage speculation and produce abuse-handling problems if the record points to a passive holder while traffic comes from someone else. But refusing to see leasing does not make it disappear. It makes the record less truthful.
The registry's practical question should be: who is responsible for what? If a holder delegates operational use of a block to another network, abuse desks need contacts that work. Upstreams need to know who can request routing changes. RPKI arrangements need to reflect authorised origin. Reverse DNS may need to be maintained by a party with operational control. Contractual responsibility between lessor and lessee may be private, but the public record should not pretend that no delegation exists if the internet depends on it.
A registry can respond to leasing in three ways. It can ban or restrict it through clear policy, accepting that some activity may move outside the record. It can ignore it, leaving abuse and operational responsibility obscure. Or it can make delegated responsibility legible without treating every lease as a transfer of ultimate recognition. The third course is usually the most compatible with a useful record. It does not require the registry to endorse every contract. It requires the registry to publish what it can truthfully know.
Suspicion becomes gatekeeping when leasing is used as a smell test. A transfer is slowed because it might support leasing. A contact update is questioned because the operational party is not the historical holder. A reverse-DNS change is delayed because staff dislike the commercial arrangement. A buyer is treated as less deserving because it plans to serve customers through delegated address use. Such reactions may be framed as stewardship, but they risk making operational truth subordinate to institutional taste.
There are real risks to manage. Leasing can be used to shelter abuse, evade policy, fragment responsibility or create chains of sub-delegation that no abuse desk can follow. It can also help small networks obtain capacity without a large upfront purchase, help holders monetise surplus space, and help regional cloud or carrier platforms serve customers while IPv6 transition remains incomplete. The registry should distinguish these cases through responsibility and evidence, not through blanket suspicion.
The most useful rule is to make the public responsibility chain visible at the level necessary for operations. The recognised holder remains accountable for maintaining the relationship with the registry. Delegated operational contacts can be recorded where appropriate. RPKI and reverse DNS should be handled through authorised mechanisms. Abuse contacts should point to someone who can act. If a delegation creates persistent abuse-handling failure, the remedy should target that failure. If the issue is merely that the holder earns rent, the registry should be cautious about treating discomfort as a mandate.
Leasing also intersects with small-market finance. A small ISP may lease addresses because buying is impossible. Another may lease out unused capacity to fund upgrades, debt service or disaster recovery. In countries with capital constraints, this can be an ordinary financing choice, not a moral failing. A registry that suppresses visible leasing may unintentionally favour operators with enough capital to buy outright. That is not neutral stewardship. It is a credit-market preference disguised as technical administration.
The regional texture: large countries, small islands and concentrated carriers
LACNIC's problem cannot be imported wholesale from North America, Europe, Asia-Pacific or Africa. The region has its own economic shape. Large-country gravity, small-island fragility, multilingual participation, concentrated carrier markets, cross-border operations, public-sector records and currency friction all affect the meaning of registry power.
Large countries create gravity. Brazil and Mexico have deep technical communities, large operators, substantial internet-exchange and data-centre markets, domestic institutions and professional communities that can absorb complexity. Argentina, Chile, Colombia, Peru and other larger markets also contain sophisticated operators and counsel who understand registry procedures. In those environments, a documentation request may be inconvenient but manageable. Policy monitoring may be part of ordinary corporate affairs. Travel, translation and legal review may be budgeted.
Small-market experience is different. In an island economy, one network may combine fixed access, enterprise connectivity, hosting, public-sector service and emergency communications. Staff capacity is thin. Legal documentation may be less standardised. Storm damage, cable faults, imported-equipment delays, tourism cycles and public-sector payment timing can change cash flow abruptly. An address block may be small in global terms but central to the operator's survival. A transfer or lease may be a financing tool rather than a speculative trade. Registry friction in such a case is not background noise. It can be binding.
Concentrated carrier markets add another layer. In several countries, fixed and mobile connectivity depends on a limited number of carriers, wholesale paths or international gateways. Address resources can reinforce existing market structure. A large incumbent with clean historical files, staff capacity and policy visibility can satisfy registry demands more easily than a new entrant. If transfers are slow, leasing is suspect, or documentation demands are heavy, the cost of entry rises. A registry that imagines itself neutral may still preserve concentration if its procedures are easier for incumbents to navigate.
Large-country gravity can also shape governance. The most active voices in meetings and policy lists may come from the bigger markets because that is where staff, time and professional networks are concentrated. Their participation is legitimate; the institution needs it. But it should not be mistaken for the whole region. Silence from a Caribbean operator may mean the rules are acceptable. It may also mean that the person who would comment is repairing an outage, handling billing, or unable to follow a discussion conducted mainly in another language.
Currency conditions sharpen the divide. A Brazilian or Mexican carrier may still face complexity, but the depth of local finance and professional services can reduce the marginal cost of registry compliance. An operator in a country with exchange controls, dollar scarcity, high inflation or de-risked banking relationships may experience the same compliance step as a much larger burden. If account standing, transfer timing or evidence requirements ignore these differences, procedural equality becomes economic inequality.
The public interest is not served by weakening the record for small markets. Fraud and hijacking hurt small networks too. The point is to design evidence and timing around the actual risk. A small island operator should not have to lobby for mercy when a bank delays a payment or when a public document appears in an unfamiliar form. It should have a published cure path and continuity rules. A large carrier should not be able to use procedural mastery to turn registry friction into a competitive advantage.
Cross-border operations and succession records
Modern networks do not respect tidy jurisdictional boundaries. A company may be incorporated in one country, operate equipment in another, centralise finance in a third, serve customers across several islands and use a data centre or network-operations centre in Miami, Sao Paulo, Bogota or Panama City. A cloud provider may need IPv4 to serve customers throughout the region while routing, contracting and billing are organised through a cross-border group. A wholesale fibre or subsea operator may have subsidiaries in several jurisdictions. A strict localistic view of address use can misread how networks are actually built.
This is not an argument for ignoring regional policy. LACNIC exists because regional administration matters. It is an argument for recognising that regional use is often operational rather than corporate-formal. A Latin American or Caribbean customer may depend on infrastructure whose legal and routing path crosses borders. A carrier may centralise address management because the group is integrated, not because it is evading responsibility. A cloud platform may serve small-country customers from a regional hub because that is the only economical way to provide service. The record should identify responsible parties and operational contacts, not force business structures into a simplified map.
Cross-border operations also complicate payments and documents. The entity that receives the invoice may not be the operating subsidiary. The bank that can send dollars may be outside the country where the network serves customers. A public procurement office may require a local invoice, while the registry relationship sits with a regional holding company. A transfer may require documents from more than one corporate registry, language and legal system. These cases deserve careful review. They do not deserve suspicion merely because they look unlike a single-country ISP.
Public-sector succession is equally important. Universities, ministries, national research networks, regulators, state-owned enterprises, public utilities and municipal projects can all hold or control resources. Their records may have been created when internet administration was informal and the economic value of IPv4 was modest. Decades later, a ministry may have split, a university network may have changed legal home, a public utility may have been privatised, or a municipal project may have been absorbed. The evidence may be a statute, gazette notice, ministerial letter, board resolution, concession document or court order. It may not resemble the clean corporate file of a private telecom group.
If LACNIC treats such files as permission cases, it will either invite fraud or immobilise legitimate continuity. The better path is to publish public-sector evidence standards. What proves that one public body is the successor to another? What proves authority to sign? How should the registry handle old records where the original technical contact is gone? What happens while a ministry produces evidence? Which operational services continue? These questions can be answered without turning the registry into a constitutional court.
Corporate succession records raise parallel questions. A buyer of an ISP may acquire assets rather than shares. An insolvency process may transfer network resources through a court-approved arrangement. A creditor restructuring may place a carrier under new control. A group may separate fibre, towers, mobile operations and enterprise services into different subsidiaries. Address records may lag. If cleanup is hard, buyers will discount the assets or leave records stale. If cleanup is predictable, the record becomes more accurate and the market more efficient.
The registry should not confuse the messiness of economic life with a defect in legitimacy. Real networks are bought, split, merged, renamed, financed, rescued and reorganised. A record-keeper that can process that reality with discipline adds enormous value. One that treats each reorganisation as an opportunity to re-decide whether the business deserves its resources becomes a source of risk.
RPKI, reverse DNS and the service-continuity firewall
The most technical registry services are also the clearest reason to avoid broad gatekeeping. RPKI, reverse DNS, public registration data and abuse contacts convert recognition into operational trust. They help networks decide which routes to accept, where to send complaints, how to identify responsibility and how to maintain service continuity. If these functions are treated as discretionary rewards rather than record functions, the market will view the registry as a control point over operations.
RPKI is especially sensitive because it turns registry recognition into cryptographic statements about route-origin authority. LACNIC does not decide every routing policy; networks decide how to validate and filter. But the registry helps the recognised holder prove that it is authorised to originate or delegate origin for a prefix. If certificate continuity can be affected by a billing dispute, commercial suspicion or an unrelated documentation issue, a non-routing problem can become a routing-security problem. That is poor institutional design.
Reverse DNS is less glamorous but no less practical. Mail reputation, logging, diagnostics, monitoring systems and customer applications often rely on reverse naming. A transfer, lease or operational delegation may require reverse-DNS changes. The registry should ensure that the person requesting a change has authority. It should not make reverse-DNS continuity vulnerable to an unrelated opinion about the holder's market behaviour.
Abuse responsibility is where leasing and delegation become concrete. If a holder leases or delegates a block to another network, abuse desks need to know where to send reports. If the public record points only to a passive holder with no operational contact, accountability suffers. If the registry refuses to record delegated responsibility because it dislikes leasing, accountability suffers again. The record answer is to make responsibility visible, bounded and consistent with the recognised holder's obligations.
The same principle applies to contact updates. Inaccurate contacts harm the public value of the registry. They should be fixed. But a contact defect should not become a broad resource-status threat unless it reflects abandonment, fraud, persistent refusal or inability to maintain responsibility. The aim is to keep the operational record useful, not to turn every defect into leverage.
LACNIC would benefit from a service-continuity firewall: a published matrix explaining what happens to registration publication, contacts, reverse DNS, RPKI, account access, transfer review and support during different states. Late payment, disputed transfer, court order, suspected account compromise, incomplete documentation, sanctions concern, merger review and routine contact update should not all have the same operational consequences. Some situations require immediate locks. Others justify preserving the last verified operational state while the defect is cured.
The default should be continuity unless the specific risk requires interruption. If an account is hijacked, locking changes may be necessary. If a court order binds a resource, the relevant record may need to be frozen or annotated. If authority is disputed, the registry may need to maintain the last verified state until the dispute is resolved. But if an invoice is late because a bank transfer is stuck, or a document is missing from a corporate-name cleanup, interrupting RPKI or reverse DNS may create more harm than protection.
Such a firewall would also protect LACNIC. Staff facing pressure from complainants, competitors, governments or influential members could point to clear rules. They could say which service continues, which is paused, what evidence is required and how the decision can be reviewed. Narrow rules protect both applicants and the institution.
Compliance without private regulation
Compliance is real. LACNIC must obey applicable law, respect competent legal orders, prevent fraud, protect member accounts, screen where legally required and avoid facilitating prohibited transactions. It may need to preserve records, pause a change, request evidence or refuse recognition. None of this is optional. But compliance duties do not create a general mandate to regulate markets.
The boundary should be direct nexus. If a court order binds a resource, the registry may need to freeze or annotate the relevant record. If a request comes from a compromised account, changes should be locked until authority is restored. If a party is legally prohibited, the affected transaction may be blocked. If a corporate document is ambiguous, the specific change may wait. But a compliance concern should not automatically contaminate unrelated services. It should not become a broad judgement about a jurisdiction, business model, buyer type, lease structure or price.
This matters in a region exposed to banking de-risking and financial complexity. Banks sometimes avoid small jurisdictions, telecom clients or cross-border payments not because the transactions are illegal but because compliance cost is high. If a registry imports that bank-like caution into recognition decisions, members face a second layer of private restriction. A legal duty becomes an institutional mood. That is dangerous because it is hard to contest. The member is told only that the case is risky.
Compliance holds should therefore be named, timed and reviewable. The member should know whether the hold arises from legal prohibition, suspected fraud, missing authority, payment issue, court notice, disputed claim, sanctions screening or internal review. The registry should distinguish applicant-caused delay from registry-caused delay. It should state what evidence would cure the issue, which operational services continue, whether the hold is time-limited and what appeal path exists. Aggregate categories and outcomes can be published without exposing confidential documents.
Abuse allegations are another boundary problem. Network abuse is real, and accurate contacts matter. But a registry is not a general enforcement body for every harmful act using an address. It can require responsible contacts and preserve records. It can act under specific policy or law. It should be cautious about converting abuse complaints into resource-status decisions without a clear rule, reliable evidence and proportionate remedy. Otherwise competitors or complainants can weaponise abuse reports to create registry pressure.
Routing incidents require the same discipline. A route leak, hijack allegation or RPKI mismatch may require urgent correction. It may also involve operational error rather than bad faith. The registry's role should be tied to authority and record accuracy. If a holder's ROA is wrong, help correct it. If an account is compromised, lock and recover it. If a route dispute reflects a commercial conflict, record what the registry can support and leave the broader dispute to the proper forum.
A compliance culture that is specific, documented and bounded strengthens LACNIC. It allows the registry to act firmly when necessary while resisting pressure to become a private regulator. It also gives market participants confidence that compliance will not become a movable excuse for delay.
Governance in an open but costly community
Regional internet registries often rely on open policy processes, member participation and community legitimacy. That architecture is valuable. It gives operators and affected parties a path to shape rules rather than merely receive them. But openness in form is not the same as equal access in practice. Attention, travel, language, procedural knowledge and time are scarce resources.
This is especially important after exhaustion because policy decisions increasingly affect capital. Rules about transferability, documentation, account standing, RPKI continuity, reverse DNS, leasing visibility and fees can change valuations and bargaining power. A mailing list debate or meeting session may look open, yet the operators most affected by the cost may be absent. Silence from a small ISP is not always consent. It may mean that the owner is negotiating a bank transfer, repairing a storm-damaged link, serving public-sector customers or simply unable to follow a discussion conducted in another language.
Active participants are not the problem. They are necessary. Engineers, operators, lawyers, security experts, brokers, public-interest advocates, staff and large carriers all bring information. The danger is treating the active subset as the whole affected market. If the people who can afford to participate are also those best able to navigate complex rules, policy can drift toward procedures that appear reasonable to insiders and expensive to everyone else.
Policy proposals that affect resource liquidity should therefore include economic impact analysis. Who bears the cost? Which members will need counsel? Which documents are difficult in small jurisdictions? Which language communities face additional burden? Will the rule reduce fraud or merely reduce visible transfers? Will it push leasing into private arrangements with weaker abuse responsibility? Will it favour incumbents? How will the registry measure whether the rule worked?
Governance risk should also be understood broadly. It is not only board scandal, litigation or service outage. It is also the slow mismatch between registry authority and the ability of affected members to discipline it. If members cannot see transfer timing, denial reasons, hold categories, appeal outcomes, budget allocation, conflict disclosures and service-continuity rules, they cannot price institutional risk. If they cannot price it, they either ignore it until crisis or seek informal influence.
Conflicts of interest deserve more attention under scarcity. Board members, policy leaders, committee participants, senior staff and outside advisers may have ties to carriers, cloud firms, brokers, consultants, public bodies or development projects. In a small technical community such ties are common and not inherently improper. Scarcity makes them material. Anyone shaping transfer rules, fee policy, leasing treatment or appeal outcomes should disclose relevant interests. Disclosure does not remove bias, but it makes risk visible.
The healthiest policy evolution would make LACNIC stronger where the record needs confidence and narrower where scarcity tempts overreach. Stronger on evidence categories, fraud prevention, account security, RPKI continuity, multilingual instructions, historical record preservation and service metrics. Narrower on business-model judgement, buyer deservingness, leasing suspicion, informal regional preference and price morality.
What to watch
The first watchpoint is transfer timing. The important figure is not only the average. It is the tail: cases that take months, cases stuck in compliance review, cases delayed by payment, cases waiting for legal interpretation and cases abandoned after repeated documentation rounds. Long-tail delay is where permission hides.
The second is leasing visibility. If leasing grows while registry records remain poorly adapted to operational delegation, abuse responsibility and routing authority will become less clear. If LACNIC responds by treating leasing as suspect rather than making responsibility legible, the record will drift away from reality.
The third is account-standing leverage and documentation creep. Any move that links curable payment or paperwork defects to broad service vulnerability should be treated as a capital-control signal. Published evidence categories, multilingual examples and clear cure paths would indicate discipline. Improvised requests and broad account holds would indicate drift.
The fourth is compliance vocabulary. "Risk" should not become an all-purpose word. Legal prohibition, fraud, disputed authority, missing evidence, payment delay and internal review are different categories. The more precisely LACNIC names them, the more legitimate its caution becomes.
The fifth is rhetoric about buyers, prices and regional purpose. If transfer discussions turn on whether a buyer is virtuous, local enough, insufficiently financial, paying too much, or aligned with a preferred development story, the market should ask which adopted rule is doing the work. If there is no rule, there should be no hidden test.
The last is service continuity under stress. Members should know whether governance disputes, legal claims, financial shocks, staff turnover or system incidents could interrupt ordinary record services. When LACNIC speaks as a record-keeper, its authority is strong. When any registry speaks as if community sentiment or IPv6 advocacy authorises hidden control over IPv4 transactions, the market should ask for the precise rule. Vocabulary is not a mandate.
The conclusion: the record must settle facts, not grant economic permission
LACNIC's legitimacy does not depend on pretending that the registry is powerless. It is powerful because the record is useful. Recognition of number resources affects liquidity, transfer prices, financing, leasing markets, corporate acquisitions, routing security, reverse DNS, abuse responsibility and small-operator entry. The registry's choices can lower or raise the risk premium attached to Latin American and Caribbean resources.
That power is legitimate when it is used to keep the record accurate, secure, continuous and reviewable. It is necessary to verify identity. It is necessary to check authority. It is necessary to preserve provenance, contact accuracy, transfer history, RPKI, reverse DNS and abuse responsibility. It is necessary to block fraud, respect competent legal orders and implement adopted policy. These are not minor administrative chores. They are the functions that make the regional record worth trusting.
The same power becomes illegitimate when recognition turns into permission over economic choices. LACNIC should not decide whether a buyer is morally deserving, whether a price is attractive, whether leasing is aesthetically pleasing, whether a holder has monetised too well, whether a business model fits a preferred regional story, or whether payment friction should immobilise address capital beyond what financial discipline requires. Those choices belong to operators, customers, markets, courts and public authorities unless a clear registry rule directly applies.
The post-exhaustion internet needs registries that are boring in the best sense: accurate, narrow, fast enough, transparent enough and humble about what they do not decide. In Latin America and the Caribbean, that humility is not an academic preference. It is part of the investment climate for networks operating amid currency volatility, banking friction, public-sector complexity, concentrated carriers, island fragility, cross-border operations and multilingual participation costs.
LACNIC remains legitimate when it lets the record settle real market facts. It loses legitimacy when the record becomes a gate through which economic choices must seek institutional approval. The line is not found in slogans about stewardship or community. It is found in ordinary administration: what evidence is required, how long recognition takes, what account issues block, what services continue, what denials say, what appeals can change, and whether judgement stays tied to the integrity of the record. In a scarce IPv4 economy, those details are the constitution of trust. Legitimacy lies in letting the record settle facts, not in using recognition as permission.