A utility surrounded by tempting words
A network operator in Latin America or the Caribbean rarely meets LACNIC as a mere filing cabinet. It may need the registry to recognise an IPv4 transfer, approve or update an IPv6 allocation, issue route-origin authorisations, delegate reverse DNS, maintain public registration data, correct contacts, process a corporate change, collect fees, explain policy, support a training programme, or convene a discussion in which future rules will be written. The core task is simple to name and hard to perform: keep the recognised number-resource record reliable. Around it sits a ring of adjacent functions that can be useful, sometimes necessary, and often politically attractive.
That ring is where the mandate problem begins. LACNIC is not wrong to care about IPv6 deployment, routing security, accurate records, abuse reachability, technical capacity, open policy participation or regional development. A regional internet registry that refused all of those concerns would be an arid utility, and probably a weaker one. The registry record is not reliable if contacts are stale, authority is forged, reverse DNS is unmanaged, route-origin claims are confused or small operators cannot understand the rules that govern them. The error is different: it occurs when these surrounding missions are used to justify decisions that are not really about the record.
Mandate laundering is the conversion of a narrow registry power into a wider economic discretion through respectable language. The words are familiar: stewardship, community, development, security, compliance, inclusion, sustainability, transition. Each can describe a legitimate concern. Each can also become a jurisdictional bridge. A review said to protect stewardship may decide which buyers are morally acceptable. A security requirement may demand commercial information unrelated to route authority. A development programme may become a reason to tax or slow address-market movement. A compliance check may harden into private capital control. The vocabulary remains public-spirited; the effect is distributional.
The laundering is not necessarily conspiratorial. Institutions expand through habits as much as through plots. A staff interpretation, a form field, a fee rule, a meeting slide, a budget line, a mailing-list consensus or a risk memo starts with an accepted public purpose and ends by giving the registry more discretion over scarce IPv4 commerce than the purpose requires. No one needs to say that the registry is now regulating prices, deciding industrial policy or choosing winners. It is enough to ask one more question, take one more week, demand one more assurance or describe a private transaction as inconsistent with the community.
That distinction matters because legitimate adjacency is real. LACNIC can promote IPv6 without treating IPv4 buyers as backward. It can support training without deciding which operator deserves a scarce address block. It can administer RPKI without converting certification into leverage over business models. It can keep a policy process open without letting a narrow set of repeat participants stand in for the whole regional economy. It can require accurate records without becoming a price regulator. The institutional challenge is not to shrink the registry to a spreadsheet. It is to keep every adjacent mission subordinate to the registry utility.
The regional setting makes the problem more acute. LACNIC serves large continental economies, small island networks, public-sector systems, universities, carriers, hosting providers, content firms, financial institutions and small access networks. Some have counsel, dollar liquidity, policy staff and multilingual capacity. Others work with thin teams, currency friction, procurement delays, exposed infrastructure, concentrated transit and weak local administrative systems. In that environment a neutral phrase can move money. A rule said to defend the community may protect incumbents. A compliance delay may freeze working capital. A development preference may reduce the liquidity of a small seller's address block.
LACNIC's public description is useful background, not a mandate in itself. It is an international, non-governmental organisation established in Uruguay in 2002. It manages IPv4 and IPv6 addresses, autonomous system numbers and reverse resolution for the Latin American and Caribbean region. Its materials describe more than 13,000 network operators across 33 territories, a member-elected board and a mission that combines registry accuracy, service quality, transparency, policy participation, technical capacity and applied research. Those facts explain why the institution has adjacent roles. They do not answer where those roles must stop now that registry recognition has market value.
The question for a mature registry is therefore not whether broad values are good. It is whether they are being translated into concrete powers with a proper institutional basis. When LACNIC invokes stewardship, the next sentence should say whether it means record accuracy, fraud prevention, policy compliance, routing authority, reserve prudence or something else. When it invokes community, it should identify whose cost and whose benefit are at stake. When it invokes development, it should separate capacity building from allocation control. When it invokes security, it should show the operational interface at risk. When it invokes compliance, it should name the obligation, the breach and the proportionate remedy.
Mandate boundaries are not anti-registry. They are how a registry remains legitimate. LACNIC's authority is strongest when it protects the truth, uniqueness and usability of the number-resource record. It is weakest when it judges the economic merits of lawful use. Scarcity has made that difference expensive.
Competence, not virtue, is the boundary
The first defence against mandate laundering is institutional competence. Competence here does not mean technical intelligence, good faith or regional commitment. LACNIC plainly has all three in many areas. It means the proper relationship between an institution's function, the information it can reasonably know, the accountability it faces and the economic consequences of its decisions. A land registry is competent to record title and detect forged documents. It is not competent to decide whether the buyer will make socially optimal use of the land unless public law gives it that task. A payments utility is competent to settle transactions and manage operational risk. It is not thereby licensed to run industrial policy.
LACNIC is competent to keep the number-resource record accurate. It is competent to authenticate account holders, verify corporate authority, check whether a resource is subject to dispute, implement adopted resource policy, maintain registry services, support reverse DNS, provide RPKI infrastructure, coordinate resource changes with other registries and publish service information. It is competent to warn operators about risks that affect the number system, including stale contacts, hijacking, legacy-resource uncertainty, routing-security failures and operational effects during transfers. It is competent to facilitate a policy process whose outputs bind the registry when properly adopted.
It is not institutionally competent to decide the socially correct price of IPv4 addresses. It is not competent to decide that a bank, hosting company, cloud platform, carrier, reseller, public agency or small ISP is more deserving of addresses because its story sounds closer to regional development language. It is not competent to impose soft capital controls by delaying outbound transfers because the export of scarce IPv4 feels politically unattractive. It is not competent to make leasing unattractive merely because leasing looks financial rather than communitarian. It is not competent to convert fee policy into a levy on scarcity rents without explicit approval and transparent accounting. It is not competent to use compliance vocabulary to prefer local buyers, punish unpopular business models or turn currency friction into a test of civic virtue.
Some decisions sit near the boundary. A receiving organisation in the LACNIC region may have to justify IPv4 resources under policy before receiving a transfer. LACNIC verifies the holder and checks dispute status. In intra-regional transfers, parties submit signed legal documents. In inter-regional transfers, registries coordinate documentation. Those are real policy facts. They also show why competence is delicate. A verification step tied to identity and provenance is within the registry's lane. A need review that tests whether a stated use is coherent under adopted policy may be within that lane. A subjective judgement that the recipient's business model does not advance regional development is not.
The difference is not always visible in the form field. "How will the addresses be used?" can mean several things. It can detect a sham transfer, a forged demand claim, an impossible routing plan or an attempt to evade a holding rule. It can also become a disguised merits review. The same question can protect the record or rank business models. A narrow registry must therefore define the purpose of each inquiry. If the purpose is authenticity, say so. If the purpose is policy compliance, identify the clause. If the purpose is operational responsibility, connect it to contacts, RPKI, reverse DNS, abuse handling or routing authority. If the purpose is to decide whether the transaction is economically desirable, the registry has crossed the line.
The surrounding institutions are imperfect, but they are not irrelevant. Courts decide ownership disputes, insolvency questions, injunctions and contractual conflicts. Telecom regulators define licensing, universal-service obligations and sector competition where national law gives them power. Competition agencies examine market concentration. Central banks and finance ministries set exchange and payment rules. Tax authorities tax transactions. Legislatures decide industrial policy. Commercial parties negotiate prices, warranties, financing and risk allocation. None of these actors is always fast or technically fluent. But weakness elsewhere does not make LACNIC a substitute sovereign.
The temptation to fill gaps is understandable. If a court is slow, the registry may appear to be the only institution able to preserve stability. If a national regulator misunderstands IPv4 markets, LACNIC may seem more competent than the state. If an operator cannot obtain dollars, a flexible registry response may look like fairness. If a policy list is dominated by technical participants, it may feel like the only available forum for regional equity. Yet the more the registry uses technical competence to decide adjacent economic questions, the more it becomes least accountable in precisely the areas where its mandate is weakest.
The right distinction is between deciding record facts and deciding economic destiny. LACNIC may decide whether a signatory controls the organisation. It may decide whether a block is the subject of a documented dispute. It may decide whether a requested action would contradict an adopted resource policy. It may decide whether a route-authorisation chain is technically coherent. It should not decide whether a seller ought to keep an address block for the region, whether a buyer has enough social value, whether a lease margin is excessive, whether a foreign purchaser is too unattractive or whether IPv4 use is morally disappointing.
Legitimate adjacency and hidden discretion
Not every function around the ledger is laundering. The number-resource system would be fragile if registries did nothing except store names beside prefixes. Registry accuracy depends on training, tooling, security, policy maintenance and operational coordination. Members need to understand IPv6. Operators need ways to create and maintain route-origin authorisations. Reverse DNS has to be delegated and updated. Public registration data needs consistent stewardship within privacy and data-use limits. Policy forums need facilitation. Legacy-resource holders may need a path into modern records. A registry that refuses all adjacency would fail in practice.
The test is whether the adjacent mission improves the registry function or becomes an independent source of authority over commerce. IPv6 promotion is legitimate when it helps networks reduce long-term dependence on IPv4, trains engineers, publishes measurements and gives operators practical deployment guidance. It becomes laundering if transition rhetoric is used to make IPv4 transfers needlessly painful, to shame leasing as backward or to deny that IPv4 remains working capital. Routing-security work is legitimate when it clarifies route authority and reduces hijacking risk. It becomes laundering if security language is used to demand information unrelated to routing, punish lawful commercial delegation or pressure holders into preferred arrangements.
Development work is legitimate when it funds skills, fellowships, measurement, local technical capacity and research that members can inspect and approve. It becomes laundering if development language justifies hidden transfers of value from address-market participants to institutional projects without clear budget discipline. Community process is legitimate when affected parties can propose, oppose and refine rules. It becomes laundering if the fact that a door was open is treated as proof that absent small operators consented to burdens they had no realistic capacity to analyse. Compliance is legitimate when it prevents fraud, enforces contracts, follows applicable law and protects registry integrity. It becomes laundering if compliance language quietly imposes buyer screening, asset freezing or capital control that no public authority enacted.
The public purpose is often emotionally attractive. Inclusion, security, development, stability and stewardship are not empty ideals. That is why they are useful laundering words. A proposal framed as defending the community may reduce liquidity. A transfer delay framed as caution may shift bargaining power from a small seller to a large buyer. A fee framed as sustainability may capture scarcity value. A leasing restriction framed as responsibility may protect incumbents with owned inventory. A compliance review framed as risk management may discourage resources from leaving the region. The moral glow does not remove the economic effect.
The discipline is to disaggregate the claim. If a measure protects security, which security risk, at which operational interface, with what evidence, and why would a narrower measure not work? If the claim is development, who pays, who benefits, how was the budget approved, and does the measure change resource-market outcomes? If the claim is community, which affected groups participated, who was absent, how was consensus measured, and who receives private economic advantage? If the claim is stewardship, is the registry protecting record truth or deciding the merits of use?
Official language can collapse these categories. A mission statement can combine registry accuracy, service quality, transparency, participatory policy, technical capacity and regional development. That combination is not a scandal; it is how internet institutions often describe themselves. But once an institution controls recognition over scarce IPv4 resources, every broad phrase should be treated as a possible jurisdictional bridge. The bridge may be safe. It may also carry the registry into decisions about capital, liquidity and industrial structure that members never clearly authorised.
The laundering risk is procedural as well as substantive. A policy proposal that openly says it will restrict a class of transfers to preserve regional supply can be debated as an economic intervention. A proposal that reaches the same result through extra documentation, longer review, vague risk language or fee design is harder to contest. A registry that wants legitimacy should prefer explicitness even when explicitness is politically costly. Hidden discretion does more damage than open disagreement because it deprives the market and the community of the true issue being decided.
There is a simple diagnostic. Ask whether the registry would still need the power if IPv4 addresses had no market value. It would still need to verify signatures, prevent fraudulent record changes, delegate reverse DNS, maintain RPKI, keep contacts accurate and coordinate inter-regional uniqueness. It would not need to decide whether a buyer has enough developmental merit, whether a seller should be discouraged from exporting value, whether a lease margin is aesthetically displeasing or whether transfer fees can be designed to capture scarcity rents. If the disputed power exists only because the resource has become valuable, it deserves especially strict justification.
Scarcity turns words into prices
IPv4 exhaustion changed the price of discretion. When addresses were abundant enough for ordinary requests, a registry's broad language mostly affected allocation fairness, technical development and community legitimacy. After exhaustion, existing IPv4 holdings became capital-like resources. They support revenue, customer contracts, hosting platforms, access networks, cloud services, public-sector systems and acquisition value. They can be transferred under policy, leased through private arrangements, cleaned up after corporate changes or used as part of network continuity planning. The registry record is now part of the asset's economic life.
This does not require the crude claim that IPv4 addresses are property in the same way as land. Number resources remain embedded in registry agreements, policy and technical coordination. But economic behaviour follows usefulness and scarcity, not legal taxonomy alone. A resource that can be monetised, transferred, leased, financed indirectly, used to win customers or valued during a merger will attract capital. If registry recognition is required for clean title and operational services, registry discretion affects that capital. A narrow administrative decision can change the price of a block, the timing of a closing, the discount demanded by a buyer or the bargaining position of a small operator.
LACNIC's waitlist illustrates the change. It was created in August 2020 after the last available IPv4 address block was assigned. Public waitlist information estimates that the last request faces at least an eighteen-year wait and can receive a maximum of 1,024 addresses, with uncertainty because future recovered resources cannot be predicted. Blocks released through that phase have spent at least six months in quarantine, but reputation or filtering problems cannot be ruled out and rehabilitation falls to the recipient. This is not normal supply. It is a residual rationing mechanism.
Once the waitlist becomes a signal rather than a credible supply plan for most real demand, the burden shifts to transfers, leasing, conservation, address sharing, upstream assignment, renumbering and IPv6 deployment. Each has a different institutional boundary. Transfers require registry recognition. Leasing requires a responsibility chain between holder and user. Conservation and address sharing are operator choices. IPv6 is the long-term architecture, but not an immediate substitute for every IPv4-dependent customer. A registry that conflates these routes can launder preference. It may praise IPv6 while quietly obstructing transfers. It may demand responsibility in leasing while actually discouraging the product. It may invoke scarcity to keep resources in-region without admitting that it is restricting capital mobility.
Scarcity also makes delay expensive. A transfer waiting for documentation, need review, payment, inter-registry coordination, agreement signatures or service updates is not merely delayed in calendar time. Capital is tied up. Escrow terms remain uncertain. A seller may accept a lower price. A buyer may demand indemnities. A lessee may extend a temporary arrangement. A small provider may lose a customer. A bank may ask for new documents as exchange rates move. In countries with inflation, dollar scarcity or procurement cycles, the time value of recognition can be high.
Broad words become expensive because they can extend this uncertainty. Stewardship can mean protecting the record from fraud; it can also mean taking longer because staff dislike the transaction's economics. Security can mean validating route-origin authority; it can also mean requiring information unrelated to routing. Development can mean training operators; it can also mean holding scarce resources hostage to regional ambitions. Community can mean open consensus; it can also mean the preferences of those who had time to attend. The word does not determine the mandate. The operative effect does.
That is why post-exhaustion discretion should be analysed as a market variable. Every rule affecting transfers, legacy regularisation, account standing, certification, reverse DNS, abuse contacts or leasing visibility should be examined for liquidity effects. Who pays more? Who waits longer? Who receives bargaining power? Which costs are fixed and therefore heavier for small operators? Which actors have enough staff to navigate the procedure? Which uncertainty becomes a broker's private advantage? These are not ideological questions. They are the economics of scarcity passing through an administrative institution.
Community is a process, not an owner
LACNIC's policy-development materials describe a self-regulation model in which rules for internet resource administration are developed by the community through a public, participative and transparent process. Proposals are discussed on the policy mailing list before being presented at forums. Approval requires consensus on the list and at the forum. The process is open to anyone. These are important safeguards. They are also vulnerable to a common confusion: open participation is not the same as equal capacity to participate.
The economics of attention matters. A large carrier can assign staff to follow policy proposals, read legal text, join meetings and understand how a sentence affects a transfer, a fee, a routing-security obligation or a holding period. A broker or repeat buyer can invest because policy knowledge has commercial value. A global cloud provider can rely on specialists. A small ISP with two senior engineers may spend its week keeping customers online. A Caribbean network preparing for storm season may have other priorities. A university or public agency may understand the issue only when a transaction is already pending.
Language adds cost. LACNIC works in a multilingual region. Spanish is central. Portuguese matters, especially through Brazil. English matters for many Caribbean operators, international firms and technical documents. The legal and working-language realities of an institution based in Uruguay are understandable. They also mean that nuance, timing and informal persuasion do not travel evenly. A proposal can be formally open and still be practically easier for some actors to shape than for others.
Mandate laundering through community process occurs when a rule with economic consequences is treated as legitimate merely because no one with capacity defeated it. Silence is weak evidence. A proposal can be archived, open and formally consensual while still reflecting the interests of repeat participants more than the full regional economy. This is not an accusation of bad faith. It is a structural problem in technically complex governance. The more valuable the resource, the more attention becomes capital.
The remedy is not to abandon community policy. Staff discretion without open process would be worse. The remedy is to treat community process as necessary but not sufficient for mandate expansion. Proposals that affect scarce IPv4 commerce should carry explicit economic analysis. If a rule changes transfer eligibility, need review, account-standing conditions, holding periods, fee treatment, leasing visibility, RPKI authority or reverse DNS obligations, it should state likely distributional effects. It should identify who pays fixed compliance costs. It should ask whether legitimate activity will be pushed into opacity. It should show why the same ledger-integrity objective cannot be met with a narrower measure.
The policy list should also distinguish community rule-making from administrative accountability. Some questions are properly policy questions: minimum transfer sizes, waitlist design, holding periods, treatment of recovered resources, criteria for resource requests or principles for public logs. Other questions are service questions: processing-time metrics, reviewer consistency, explanatory letters, escalation channels, service-level commitments and anonymised publication of refusal categories. A public list can discuss both, but consensus on a list should not excuse poor administrative measurement. Open debate does not replace operational accountability.
The word community should therefore be handled with care. The community is not a single economic owner of every address block. It is a governance arena containing address holders and address seekers, buyers and sellers, lessors and lessees, large carriers and small ISPs, public bodies and private firms, Spanish speakers and English speakers, well-funded participants and absent operators. It can deliberate and set policy within the registry framework. It cannot be invoked as a mystical principal whose supposed will authorises any expansion of registry discretion.
Budgets create gravitational pull
Mandate laundering is not only a vocabulary problem. It is also a budget problem. A registry with development, training, measurement, cybersecurity, fellowship, event and research activities has institutional reasons to maintain a broader footprint. Public budget and annual-report pages are good governance practices. They let members see commitments over time. Yet budgets can blur incentives when the core ledger function funds a wider identity.
The question is not whether LACNIC should spend money outside bare registration. Some regional public goods are valuable. Training reduces errors. IPv6 support helps transition. Security work reduces routing and abuse risk. Meetings and fellowships can lower participation barriers. Applied research can expose operational problems that markets ignore. A registry with no regional investment would lose legitimacy in an uneven region. The danger appears when the budgetary appetite of the adjacent institution feeds back into the interpretation of the registry mandate.
Fees and reserves create subtle pressure. A non-profit can still prefer growth. Staff, programmes, travel, events, tooling, partnerships and reserves all need revenue. A transfer market creates fee opportunities. Scarce resources create members with valuable assets. Category changes, administrative fees, renewal invoices and service agreements tie market activity to institutional income. LACNIC's public transfer materials describe administrative fees, down payments before justification analysis, category effects, service agreements for some recipients and the requirement that parties be current with contractual obligations. These may be defensible as cost recovery and service discipline. They also make financial design part of market architecture.
The risk is not that every fee is illegitimate. The risk is that fee logic can be laundered through stewardship or sustainability. A fee may genuinely support the registry's stability. But if it is tied to block size, market timing, transfer category or renewal deadlines, it can affect transaction behaviour. A down payment that is not refunded if justification fails may discourage marginal recipients. A renewal invoice requirement can give the registry leverage over a transfer near the billing date. A category change can increase the cost of receiving resources. A high administrative fee may be immaterial for a large buyer and material for a small network. The mandate question is whether the fee reflects service cost and risk or captures scarcity value because the registry can.
Reserves add another layer. A registry serving critical infrastructure needs prudence. It should survive shocks, litigation, currency movements, technology renewal and regional crises. But reserves can become a shield for scope. The claim that a larger institutional footprint protects stability may be true up to a point; beyond that point, it can turn member fees into an endowment for projects members would not choose if costs were separated. When the ledger funds everything, it becomes harder to tell which activities are essential to registry utility and which are institutional ambition.
The discipline is functional accounting. Members should be able to see the cost of core registry operations, security infrastructure, reverse DNS, RPKI, policy support, member services, development programmes, events, fellowships, research, advocacy and reserves. They should be able to see which costs scale with members, which scale with resources, which are discretionary, and which are imposed by law or contract. They should be able to debate whether transfer fees recover processing cost, fund wider programmes or tax market movement. Without that clarity, development language can launder fee extraction.
Budget scope also affects institutional psychology. An organisation that sees itself as a regional development actor will naturally want tools to shape outcomes. If its largest practical tool is control over registry recognition, it may be tempted to use registry process to advance development ends. That is the wrong instrument. Development work should be funded transparently and evaluated on its own terms. The ledger should not become a hidden taxation or allocation mechanism for regional policy.
Transfers are examples, not the whole story
Transfer policy is where mandate boundaries become commercially visible, but it should not swallow the whole analysis. LACNIC's policy manual allows IPv4 block transfers among LIRs and end users, including intra-regional and inter-regional transfers. The minimum transferable block is a /24. A receiving organisation in the LACNIC region must justify the resources under applicable policies. LACNIC or the corresponding registry verifies the holder and checks that the resources are not involved in dispute. LACNIC maintains a public transfer log. There are restrictions after transfers and on transferring newly allocated or assigned LACNIC resources. These facts matter because they show where registry recognition meets private capital.
Some transfer rules are plainly ledger-protective. Minimum block size aligns with routing practice and operational manageability. Holder verification prevents theft. Dispute checks prevent the registry from laundering contested control into clean commercial title. Legal documents provide evidence of authority. A transfer log can reduce market opacity. Restrictions on rapid resale can be debated as anti-speculation rules. The issue is not whether transfer rules exist. It is whether implementation stays tied to their legitimate purposes.
The most vulnerable point is buyer deservingness. A transfer recipient is not asking LACNIC to hand it scarce addresses from a free pool. It is asking LACNIC to recognise a transaction with another party, subject to policy. Need review may remain in the framework, but its economic meaning has changed. During allocation from common stock, need review rationed a resource controlled by the registry. In a transfer, need review can decide whether private capital may purchase a resource from another holder. The registry becomes a gate between buyer, seller and market.
A narrow review asks whether the recipient is real, whether the request fits policy, whether the stated use is plausible enough to avoid sham transactions, whether documentation is consistent, whether prior records create a problem, whether the transfer violates holding periods and whether operational responsibility will be clear. A laundered review asks whether the recipient is the kind of buyer the registry prefers. It may dislike financial buyers, large platforms, leasing-oriented firms, foreign-controlled operators, exporters of regional address space or companies whose use does not sound developmental. If those preferences are not explicit policy, they do not belong in review.
The region's asymmetry makes this concrete. A small seller may need to monetise unused space to finance equipment, pay debt, recover after a storm, exit a market or rationalise old corporate assets. A large buyer may be the only party willing to close quickly. If LACNIC slows or complicates the transaction because the buyer is unattractive in a broad policy sense, the small seller bears the cost. Conversely, a small buyer may need addresses to win customers but cannot produce polished forecasts. If review demands corporate-planning documents suited to large firms, it may exclude the networks development rhetoric claims to protect.
Inter-regional transfers are especially prone to laundering because they look like resource flight. Scarce IPv4 leaving the region can be politically uncomfortable. There may be a legitimate debate over whether policy should restrict outbound movement. But such debate should be explicit. It should not be smuggled into delay, extra documentation, informal discouragement or moral language about stewardship. If the community wants a capital-control rule, it should say so and accept the consequences for holders' asset value. If it does not, the registry should not implement one quietly.
Leasing is another example rather than the centre of the article. It separates use from registered holdership. A holder may retain the registry record while another network originates routes, serves customers, needs reverse DNS, handles abuse complaints and pays rent. The legitimate registry question is responsibility, not rent. Who is the recognised holder? Who may create route-origin authorisations? Who manages reverse DNS? Which abuse contact can act? Is the operational user visible where material use affects third parties? Does the arrangement amount to a transfer of control that should be recorded? These questions protect coordination.
The laundered question is whether leasing is virtuous. Suspicion is understandable because leasing looks like financialisation of a resource originally allocated for network need. But a hotel group, public agency, hosting customer, cloud service or migration project may require IPv4 now. Buying a block may be too capital-intensive, slow or permanent. IPv6 may be deployed and still not solve customer dependencies. Leasing can match scarce capacity to revenue as an operating expense. It is not inherently abusive.
A registry that tries to suppress leasing without offering a workable alternative may make the record less truthful. Lessors will relabel arrangements as managed services. Lessees will avoid updating contacts. Brokers will rely on private letters of authority. Abuse desks will chase the wrong party. RPKI changes will depend on private response times. Reverse DNS will lag. The result is not a more ethical market; it is a darker one. The answer is a public responsibility chain, not rent control by another name.
Transfers and leasing therefore illustrate the same principle. LACNIC can improve markets by making recognition, authority and operational responsibility clear. It should not use those interfaces to decide price, buyer virtue, seller morality or business-model desirability. The narrower role is not weaker. It is more defensible.
Compliance must not become capital control
Compliance is an attractive laundering word because it sounds non-discretionary. Registries must comply with law. They must enforce service agreements. They must protect accounts. They must prevent fraud. They must respond to court orders and sanctions where applicable. They must guard against hijacking, false documents and abusive use of registry services. A registry that ignored compliance would damage the ledger.
The risk appears when compliance becomes a container for preferences that are not legal obligations or adopted policy. A request can be delayed because payment came from a difficult jurisdiction, because a bank asked for more documents, because exchange controls slowed settlement, because a corporate structure is unfamiliar, because a buyer is foreign, because a seller is in distress, because a lease chain looks complex or because a business model raises reputational concern. Some of these facts may require review. None automatically authorises the registry to decide capital allocation.
Latin America and the Caribbean make this especially sensitive. Operators may face currency controls, high inflation, correspondent-banking constraints, procurement delays, tax documentation, political risk, sanctions exposure or public-sector payment cycles. A registry invoice or transfer fee denominated in hard currency can be routine for a multinational and serious for a local provider. Treating every payment delay as simple delinquency can turn registry finance into an unintended capital-control device. Treating every unfamiliar corporate chain as suspicious can penalise ordinary restructuring in economies where legal forms differ.
Account standing is necessary, but it should be proportionate. A member that does not pay cannot expect unlimited elective services forever. Yet not all services are alike. New allocations, voting rights, elective transfers, emergency contact correction, abuse reachability, RPKI changes and reverse DNS continuity have different public consequences. If a curable billing issue blocks a transfer, the economic effect may be an asset freeze. If a payment dispute interrupts operational services, downstream users may suffer. If a renewal deadline forces full payment before a pending return or transfer can complete, timing becomes leverage.
The legitimate compliance question is narrow: what obligation is breached, what risk does the breach create for the registry or the public record, what remedy is proportionate, and which services must remain available to prevent broader harm? The laundered question is broader: can the registry use the breach to gain bargaining power, deter an unwanted transaction or extract payment unrelated to immediate ledger risk? The difference should be visible in policy, contracts and service procedures.
Courts and public authorities must also remain in their proper place. If a court orders a record change or freeze, the registry may have to act. If a regulator imposes a lawful requirement, the registry may need to comply. Absent such authority, LACNIC should avoid turning its own risk appetite into public law. It can refuse forged documents, insist on authorised signatories, require evidence of merger or asset transfer, and decline to recognise disputed resources until legal authority is clearer. It should not decide that addresses should stay with a locally preferred party because that feels better for regional policy.
Transparency reduces compliance laundering. Members should know which categories of compliance issues affect transfers and services. They should know whether a refusal is based on legal prohibition, missing authority, unpaid obligations, dispute, fraud risk, policy ineligibility or operational inconsistency. They should know what can be cured and how. They should have a review path that is more than an informal plea. Compliance becomes legitimate when it is bounded. It becomes power when it is opaque.
Security has to name its interface
RPKI, reverse DNS, Whois, RDAP, IRR functions, contact validation and abuse-mailbox requirements all connect the registry to security. LACNIC's resource-certification materials describe hosted and delegated RPKI modes. Its reverse-DNS materials explain that LACNIC's DNS servers handle reverse resolution for IP addresses assigned to ISPs and other organisations in the region, and that allocated address space must have an associated DNS server responsible for reverse resolution. RDAP modernises access to registration data relative to traditional Whois. These are real registry functions.
Security therefore cannot be dismissed as pretext. If route-origin authorisations are stale or wrong, relying networks may treat routes differently. If reverse DNS is broken, mail, diagnostics and customer platforms may suffer. If abuse contacts are stale, incident response weakens. If registration data is inaccessible or inconsistent, counterparties cannot assess responsibility. A registry that treats these functions as clerical afterthoughts fails its utility role.
But security language can launder control. A measure said to protect routing security may require commercial disclosure unrelated to route authority. A concern about abuse may be used to disfavor leasing generally rather than require reachable contacts. A claim about registry integrity may justify broad account reviews that delay transactions without a clear threat. A security process may become a bottleneck that lets staff approve or deny economic arrangements outside adopted policy.
The boundary is operational nexus. If a requirement affects who may create a ROA, there is a security nexus. If it affects whether a reverse-DNS delegation points to maintained name servers, there is a security and operations nexus. If it affects whether abuse complaints reach a responsible party, there is a public coordination nexus. If it asks whether a lease price is too high, whether a buyer is too large, whether a seller should retain resources or whether IPv4 use is ideologically disappointing, there is no security nexus.
This boundary matters more as RPKI becomes operationally significant. The more networks rely on route-origin validation, the more registry certification affects production service. That gives the registry practical power. It should respond by narrowing discretion, not widening it. Procedures for ROA management, delegated authority, holder changes, inter-regional movement and dispute handling should be clear and fast. If certification is unavailable or delayed during a transfer, parties should know why and for how long. If a holder-user split exists in a lease, the route-authority chain should be robust without requiring the registry to approve the economics of the lease.
Reverse DNS offers the same lesson. LACNIC operates the reverse-delegation structure for addresses in its region. That function matters for reputation, mail systems and diagnostics. A transfer or lease can fail commercially if reverse DNS is not manageable. The registry's legitimate concern is that delegations are technically correct and tied to authorised control. It is not to decide whether the customer's use of the addresses is socially optimal.
Security tools should be measured. If LACNIC wants stronger requirements, it should publish the operational problem: hijacks prevented, stale contacts reduced, ROA errors corrected, reverse-DNS failures fixed, abuse-mailbox validation rates improved, transfer-related interruptions measured. Evidence disciplines mandate. Without evidence, security becomes a magic word. It can make almost any expansion sound necessary.
IPv6 transition is not a morality play
LACNIC is right to promote IPv6. The long-term internet cannot depend on increasingly expensive IPv4 workarounds. Training, measurements, technical reports, deployment guidance and community encouragement all fit the registry's adjacent mission. IPv6 reduces future scarcity pressure and helps the region avoid being trapped by an old address architecture. A registry that ignored IPv6 would be negligent.
The mandate problem begins when IPv6 promotion turns into IPv4 moralism. Operators do not keep using IPv4 because they failed to understand a slogan. They keep using it because customers, devices, software, firewalls, enterprise integrations, mail systems, remote-access tools, hosting panels, cloud dependencies and counterparties still require IPv4 reachability. IPv6 may be deployed in the network and still not remove the need for public IPv4 at the customer edge or service interface. Dual-stack costs are real. Carrier-grade NAT has limits. Translation helps some cases and complicates others.
In economic terms, IPv6 is the strategic architecture and IPv4 is often working capital. An operator can believe fully in IPv6 and still need IPv4 to serve revenue today. A development institution, public authority or registry forum may prefer faster transition, but preference does not make customer dependencies disappear. When a registry uses transition language to slow transfers, stigmatise leasing or treat IPv4 holders as morally suspect, it launders an allocation preference through technical inevitability.
The correct stance is dual realism. LACNIC can say that IPv6 deployment is necessary for long-term growth while recognising that IPv4 remains economically useful and scarce. It can fund IPv6 training while processing IPv4 transfers predictably. It can encourage dual-stack deployment without pretending that a waitlist measured in years is adequate for present demand. It can publish IPv6 measurements without using them as a moral ranking of address-market participants. It can support transition while protecting liquidity in the legacy resource operators still need.
IPv6 promotion should therefore be budgeted and evaluated separately from IPv4 recognition. How many operators were trained? Which deployment blockers were reduced? Which measurement gaps were closed? Which technical reports improved decisions? Those are good questions. Whether a buyer in a transfer deserves IPv4 because it has a sufficiently pure transition story is a different question. It should not be smuggled into registry review.
The registry's most useful contribution to transition may be predictability rather than pressure. Operators invest in IPv6 when they can plan capital cycles, customer migration, equipment refresh and application compatibility. If IPv4 market rules are unpredictable, operators may hoard, overbuy or avoid rational restructuring because they fear losing future flexibility. Clear transfer rules and clear leasing responsibility can reduce defensive behaviour. A narrow registry can support IPv6 by making the remaining IPv4 economy less chaotic, not by moralising scarcity.
Development is capacity, not industrial policy
LACNIC's development role is part of its regional identity. Its materials speak of strengthening technical capabilities, applied research, community growth and an internet that supports inclusion and development. It supports training, events, fellowships, research and programmes such as FRIDA. In a region with uneven technical capacity, those activities can be valuable. The question is whether development language remains adjacent to the registry function or becomes a licence to shape scarce-resource markets.
Development is a broad word. It can mean more trained engineers, better routing security, stronger local internet exchanges, more IPv6 deployment, improved measurement, resilience for small networks, inclusion of underrepresented communities or support for technical research. It can also be stretched to mean preferential treatment for certain buyers, suspicion of address exports, pressure against leasing or fees designed to redirect market value into institutional projects. The first set belongs beside the ledger. The second set moves toward industrial policy.
Industrial policy is not inherently illegitimate when done by governments with legal authority, public debate and budget accountability. A country may subsidise rural broadband, regulate wholesale access, fund national research networks, tax certain transactions or restrict capital movement under law. Those choices can be good or bad, but they belong to public authorities and political accountability. A regional registry does not acquire that authority because it understands networks better than ministries do.
The distinction is clearest in resource movement. Suppose scarce IPv4 addresses are sold from a small market to a richer buyer abroad. Development language may make that movement feel wrong. But the seller may need capital. The buyer may use the block productively. The transaction may be lawful under policy. If the region wants to restrict such sales, it should say so openly and accept that holders' assets become less liquid. If LACNIC merely slows the transfer, adds uncertainty or frames foreign demand as inconsistent with stewardship, development has laundered capital control.
The same issue arises inside the region. A large operator in Brazil or Mexico may have advantages over a small Caribbean network. A local hosting firm may compete with global platforms. A public-sector network may have social value but weak procurement. A registry may sympathise with some uses more than others. Sympathy is not a mandate. LACNIC can provide information, training and participation support for smaller players. It should not secretly tilt recognition rules toward favoured sectors unless a clear policy authorises the tilt.
Development funding should avoid hidden cross-subsidy. If members want to fund regional initiatives through registry fees, the amounts, purposes and results should be clear. If transfer fees support development beyond processing cost, that should be debated as a market levy. If reserves finance programmes, members should know the rationale. What must not happen is the rhetorical conversion of every institutional ambition into registry necessity. The ledger is essential. Not every programme attached to it is equally essential.
A development-oriented registry can remain narrow if it treats development as capacity building, not allocation control. It can help operators understand transfers, leases, RPKI, reverse DNS, abuse contacts, IPv6 and risk. It can publish plain-language materials for small networks. It can collect data on barriers. It can support participation from underrepresented markets. Those actions reduce dependency without deciding winners. They strengthen the market's ability to use the ledger. That is legitimate adjacency.
Soft law is still law-like
Mandate laundering often works through official-sounding language that is not quite law, not quite policy and not merely advice. A web page, FAQ, staff interpretation, meeting slide, public statement, application form, invoice rule, training document or repeated phrase in policy discussion can shape behaviour even if it is not formally adopted policy. Operators comply because the registry controls recognition. Brokers advise clients based on expected staff reactions. Lawyers draft around perceived preferences. Small members avoid transactions they fear will be disliked.
This soft law can be useful. Clear explanatory material helps members navigate complex procedures. A FAQ can reduce error. A transfer page can tell parties what documents to prepare. A warning that inter-regional transfers may affect reverse DNS or RPKI is valuable because parties can plan escrow and service migration. Public advice about leasing responsibility can reduce abuse. But soft law becomes dangerous when it creates obligations or preferences without the accountability of formal policy.
The boundary should be explicit. If a statement is binding policy, it should identify the policy. If it is a procedure implementing policy, it should identify the operational reason and review path. If it is advice, it should say so. If staff retains discretion, the criteria should be published. If a requirement affects economic outcomes, it should not be buried in a form or informal email. The more a statement changes transaction risk, the more formal it should be.
Official vocabulary is particularly powerful around stewardship. Stewardship sounds modest, but it can mean almost anything. Does it mean preventing fraud? Yes. Does it mean promoting IPv6? Often. Does it mean restricting address sales to buyers the registry finds socially attractive? No, unless policy says so. Does it mean discouraging leasing? Not automatically. Does it mean imposing fees to fund development? Only if members approve and accounting is clear. Because stewardship is elastic, every use of the word should be translated into a concrete power.
The same applies to community. A community can deliberate policy, share knowledge, elect leaders and hold institutions accountable. But community is not a single economic interest. It contains address holders and address seekers, buyers and sellers, lessors and lessees, large carriers and small ISPs, public bodies and private firms, different languages, well-funded participants and absent operators. When a decision is said to serve the community, the next question is which part of the community bears the cost.
Soft law also interacts with fear. A large operator may challenge an informal interpretation. A small network may not. If a staff message suggests that a lease arrangement is disfavoured, the small network may restructure its business around that hint. If a transfer review asks for unusually broad information, the applicant may comply rather than risk refusal. If a public page recommends pre-approval steps, parties may treat them as mandatory. Soft law can therefore create unequal compliance burdens without formal sanctions.
The solution is not sterile legalism. It is administrative hygiene. LACNIC should keep a clean separation among policy, procedure, guidance, support and advocacy. It should avoid broad words where narrow reasons are available. It should publish changes that affect member obligations. It should maintain archives. It should let members challenge interpretations that appear to exceed policy. It should train staff to explain not merely what is requested, but why the request falls inside the registry's mandate.
The institutions outside the registry still matter
A narrow registry does not mean an unregulated internet economy. It means regulation should come from the right institution. Courts decide ownership disputes, insolvency questions, fraud claims, injunctions and contractual conflicts. Telecommunications regulators decide licensing, universal-service obligations, market access and sector-specific competition where national law provides jurisdiction. Financial authorities decide currency controls, sanctions implementation, payment rules and anti-money-laundering obligations. Tax authorities tax transactions. Competition authorities address market power. Commercial parties negotiate price and risk.
LACNIC interacts with all of these systems but should not replace them. If two companies dispute whether an asset sale included an address block, LACNIC may need to wait for sufficient legal evidence or court direction. It should not decide the corporate-law merits beyond record authority. If a national regulator worries about connectivity in a small market, it can use its legal tools. LACNIC should not create an informal export restriction unless policy clearly provides one. If a buyer and seller disagree over price, the market or courts handle it. The registry records the recognised change if policy and documentation are satisfied.
This separation is difficult because public institutions in parts of the region can be slow, politically exposed or technically weak. A registry staffed by network specialists may understand the issue better than a court clerk or ministry official. But expertise does not create jurisdiction. Indeed, the registry's technical expertise is precisely why overreach would be hard to contest. A weak court can be frustrating. A registry that becomes judge, regulator and settlement utility at once can be worse.
There are cases where LACNIC cannot avoid judgement. A court order may be ambiguous. A corporate document may be unfamiliar. A transfer may involve a jurisdiction with unreliable records. A sanction or payment issue may be unclear. The proper response is not to pretend discretion does not exist. It is to narrow the question and document the basis. Is the requester authorised? Is the resource disputed? Is there a legal prohibition? Is there a policy condition unmet? Is there an operational risk that can be cured? The registry should avoid deciding larger questions than necessary.
Markets also need space to work. IPv4 prices, lease rates, broker fees, escrow terms, warranties, geolocation remediation, reputation risk and renewal options are commercial matters. They may be imperfect. Brokers may earn spreads. Large buyers may have bargaining power. Lessors may charge high rents. Sellers may lack information. These imperfections justify transparency, education and perhaps public-law intervention in some cases. They do not automatically justify registry control.
A registry can improve markets by reducing transaction costs. Clear transfer logs, processing metrics, standard evidence categories, plain-language guidance, operational-service timelines and contact validation all reduce uncertainty. They help small operators without picking winners. They make brokers compete on service rather than secret knowledge. They make buyers and sellers price risk more accurately. This is where LACNIC can add value without laundering mandate: by making the ledger more reliable, not by deciding the market's preferred outcome.
Tests for laundering language
A narrow registry needs practical tests, not merely a temperament of restraint. The first is purpose limitation. Every request for information, delay, fee, refusal, account action, certification change or service restriction should connect to a defined registry purpose: identity, authority, provenance, policy compliance, dispute avoidance, operational security, billing, legal obligation or public-record accuracy. Broad institutional values should not be sufficient.
The second is power translation. Sacred words should be converted into concrete powers before they are used. Stewardship may translate into fraud prevention, record accuracy or conservation under an adopted policy. Security may translate into route-origin authority, reverse-DNS correctness, contact validation or abuse reachability. Development may translate into training, measurement or participation support. Inclusion may translate into lower information barriers, multilingual access or fellowship support. Transition may translate into IPv6 training and measurement. If the word translates instead into buyer screening, price influence, export discouragement, lease suppression or unexplained delay, the registry should treat it as a warning sign.
The third is operative effect. The legal form of a measure matters less than what it does. A formal rule, a fee schedule, a staff interpretation, a documentation request, a processing queue, a service suspension and a guidance page can all change the market. If the effect is to reduce liquidity, shift bargaining power, favour incumbents, burden small operators or hide economic policy inside procedure, the measure needs explicit justification. Good language does not redeem an overbroad effect.
The fourth is narrower alternative. If the problem is forged authority, ask for authority documents; do not review business virtue. If the problem is stale abuse contact, require reachable contacts; do not condemn leasing. If the problem is route hijacking, fix the ROA authority chain; do not demand unrelated commercial disclosure. If the problem is transfer speculation, debate a transparent transfer rule; do not create informal delay. The narrowest effective registry tool is usually the legitimate one.
The fifth is reasons. When LACNIC declines, delays or conditions a resource change, the affected party should receive an explanation that identifies the operative ground. "Stewardship" is not a reason. "The signatory has not been shown to control the offering organisation" is a reason. "The resource appears in a documented dispute" is a reason. "The receiving organisation has not provided policy-required justification for the requested block size" is a reason. "We dislike the buyer's intended business model" is not a reason unless the policy explicitly authorises that criterion, and if such a policy exists it should be debated as market regulation.
The sixth is proportionality. Not every defect should block every service. Missing billing information, an outdated contact, a questionable lease letter, a pending corporate clarification and a suspected forged document have different risk levels. Remedies should match risk. The registry should preserve emergency contact correction and abuse reachability even when other services are restricted. It should distinguish curable defects from disqualifying defects. It should avoid turning administrative leverage into commercial leverage.
The seventh is measurement. LACNIC should publish processing times for transfer categories, reasons for failed or withdrawn requests in anonymised form, inter-regional coordination delays, frequency of RPKI or reverse-DNS interruption during transfers, waitlist movement, recovered-resource flows, contact-validation performance and appeal outcomes. Metrics do not eliminate discretion, but they make discretion visible. They let the community see whether a rule is functioning as stated or creating hidden market costs.
The eighth is reviewability. A member or applicant should have a meaningful route to challenge interpretations that exceed policy or apply it inconsistently. The review path need not become a court for every routine ticket. But where valuable resources, transfers, certification or service continuity are affected, reviewability is part of legitimacy. A second conversation with the same reviewer is not enough for high-value discretion.
The ninth is budget separation. Core registry operations, security services, reverse DNS, RPKI, policy facilitation, training, development programmes, events, research and reserves should be understandable as separate cost centres. Transfer fees should be explained as processing cost, risk cost or explicit member-approved contribution. If a fee scales with market value rather than cost, that should be visible. If development programmes are funded from general fees, members should see why and how results are evaluated.
The final test is participation impact. Policy proposals that affect scarce IPv4 commerce should identify affected groups and likely fixed costs. They should ask whether small networks, Caribbean operators, public institutions, legacy holders, non-Spanish-speaking participants, lessors, lessees, brokers, abuse teams and routing-security operators were heard. They should not treat absence as consent. A policy process can remain bottom-up while recognising that the bottom is uneven.
None of these tests requires hostility to LACNIC. They are ordinary disciplines for a utility whose decisions affect valuable assets. They also protect the registry from being asked to solve every regional economic frustration through the one power it plainly has.
The line that keeps LACNIC legitimate
The line is not anti-registry. It is the condition of registry legitimacy. LACNIC should be strong where a registry must be strong. It should prevent fraudulent record changes. It should maintain accurate public data within lawful limits. It should coordinate with other registries. It should support RPKI, reverse DNS and operational security. It should enforce adopted policy. It should require real authority for transfers, mergers and resource changes. It should publish logs and statistics. It should keep the policy process open. It should train operators and support regional technical capacity.
It should be weak where a registry should be weak. It should not decide IPv4 prices. It should not moralise leasing. It should not decide whether a buyer is socially deserving beyond policy criteria. It should not use development language to restrict capital movement. It should not use compliance ambiguity to freeze assets. It should not let budget appetite shape mandate. It should not allow participation by a narrow set of repeat voices to cloak economic scope creep. It should not convert stewardship into industrial policy.
This line is harder to hold than to state because each overreach can be defended by a plausible adjacent purpose. A transfer restriction protects the region. A lease review protects responsibility. A fee supports sustainability. A broad compliance check protects the institution. A slow review protects security. A development preference supports inclusion. Each sentence may contain truth. Mandate laundering begins when the true part is used to hide the distributional part.
LACNIC's safest posture is credible restraint. The registry should show members, buyers, sellers, lessees, lessors, courts, banks, regulators and operators that recognition is predictable, narrow and reviewable. It should make clear that its authority is strongest when protecting the truth of the record and weakest when judging the economic merits of lawful use. It should treat scarcity as a reason for procedural discipline, not a licence for moral discretion.
The practical benefit is larger than institutional tidiness. A narrow registry lowers risk premiums. Sellers can bargain with cleaner expectations. Buyers can pay for assets rather than procedural uncertainty. Lessees can price continuity. Small operators can avoid dependence on insiders. Courts can interpret records more easily. Banks can assess transactions. Operators can deploy IPv6 without fearing that IPv4 restructuring will become a moral trial. Development programmes can stand on their own merits rather than hiding inside resource control.
There will still be hard cases. Fraud will occur. Documents will be ambiguous. Some leases will be irresponsible. Some transfers will appear to drain small markets. Some buyers will be unpopular. Some sellers will be opportunistic. Some members will fail to pay. Some policy proposals will divide the community. A narrow mandate does not make these problems disappear. It makes the registry's answer more legitimate because the answer is tied to competence.
The economics of mandate laundering is ultimately the economics of institutional temptation. Scarce IPv4 gives the ledger value. Value attracts politics. Politics attracts language broad enough to justify control. LACNIC can resist that sequence only by keeping the utility function visible. It is the registry for number resources in a complicated region. That is already important enough. Its legitimacy will be strongest if it refuses the more seductive role of deciding what the region's scarce IPv4 economy ought to become.