Summary

  • LACNIC public-sector address-dependency analysis asks how government portals, courts, hospitals, schools, utilities, contractors and procurement cycles turn IPv4 continuity into civic infrastructure.
  • Scarcity and renumbering risk matter because public systems carry allowlists, VPNs, certificates, incident-response procedures, archived endpoints and citizen trust that cannot be replaced quickly.
  • A credible regional ledger preserves evidence, portability and continuity without turning the registry into a public-policy gatekeeper or a rationing authority over scarce address value.

In the LACNIC region, IPv4 is not only a network input for companies; it is part of the continuity file behind tax collection, customs clearance, court access, hospital operations, public utilities, schools, procurement, archives and emergency services.

A public service is an address dependency before it is a policy question

The most revealing Internet policy document in a government is often not a strategy paper. It is a continuity file: a list of addresses, names, vendors, firewall rules, remote-access circuits, backup portals, DNS records, certificates, contacts and fallback procedures that keeps a public service reachable when the ordinary day becomes an abnormal one. A tax portal may be presented to citizens as a website. Inside the state it is a chain of dependencies: application servers, identity services, payment gateways, bank links, customs databases, audit trails, help desks, mail relays, monitoring probes and third-party contractors. A court-filing platform may appear as a procedural convenience. In practice it becomes a time machine for rights, because filings, deadlines, summonses and evidence submissions depend on being able to reach exactly the same service when a clerk, lawyer or citizen needs it. A hospital network may look like a medical technology issue. It is also an address management issue once appointment services, laboratory results, telemedicine gateways, insurance validation and emergency coordination depend on known endpoints.

This is the correct starting point for public-sector address dependency in the LACNIC region. The interesting question is not whether governments possess a rhetorical claim over digital space. It is whether public institutions can preserve service continuity when a scarce addressing layer becomes capital, a registry record becomes operational evidence, and the cost of changing a number is paid in bureaucracy rather than in a neat engineering sprint. A government may speak in the language of sovereignty, inclusion and digital transformation, but the service that citizens touch usually rests on an older and more prosaic foundation: addressability.

The state is a heavy user of old technology because the state is a heavy user of old obligations. Tax debts do not vanish because a service is being modernised. Court records remain reviewable long after the vendor that built the platform has disappeared. Customs platforms must exchange data with ports, airports, brokers, warehouses, banks and foreign agencies that do not update in the same quarter. Public utilities run operational networks that were procured under one political cycle, integrated under another and still expected to work under a third. Schools often sit at the edge of bandwidth, budgets and technical staffing. Municipal portals may be run by a contractor whose network design was inherited from a previous contractor whose documentation was partial even when it was new.

That accumulation makes IPv4 different in the public sector. In a private firm, a failed migration can damage revenue, customer retention and reputation. In a government service, it can also damage legal certainty, social trust and the ordinary rhythm of the state. A late tax filing caused by a portal outage is not merely an inconvenience. A lost customs connection can hold physical goods at a border. An inaccessible court docket can affect due process. A hospital routing problem can become a clinical problem if it interrupts access to patient records, referral services or emergency coordination. A school-network failure can cut students off from exams, records or remote learning. A water or electricity utility that cannot coordinate field operations may discover that an address dependency has become a public-order dependency.

The point is not that IPv4 is magic. It is that stable addressing is a layer of institutional memory. When a public service has been reachable at a set of addresses for years, those addresses become embedded in contracts, diagrams, incident playbooks, supplier configurations, help-desk scripts, audit reports, allowlists, certificates, VPNs, reverse DNS, monitoring dashboards and user habits. The longer a service exists, the less the address is merely a technical locator. It becomes part of the evidence that a public institution can still find itself.

Public-sector networks age differently from companies

Government networks do not age like enterprise networks, because governments do not buy, operate or retire technology estates in the same way. A large private enterprise may be slow, political and full of legacy estates. It still has a clearer economic language for replacement: cost, risk, margin, customer churn, compliance exposure, valuation, integration burden. A ministry, municipality, court, hospital network or public utility has a more awkward set of incentives. Its estates are funded through budget cycles, appropriations, donor programmes, multilateral loans, procurement rules, emergency waivers, regional development initiatives and political promises. It may have a formal owner, a technical operator, a policy sponsor, a finance controller, an audit authority and several contractors, none of whom can unilaterally approve the whole change.

That structure matters for addresses. A private operator that discovers it needs to renumber a service can assign a project manager, price the disruption and ask whether the migration is worth it. A public body has to navigate procurement law, vendor scopes, public-notice requirements, cyber-security review, archive obligations, service-level obligations, political scrutiny and the simple fact that citizens cannot be treated like optional customers. A tax authority cannot tell taxpayers that filing will be inconvenient this year because the address plan is being rationalised. A court cannot tell litigants that deadline risk is their problem because the case management platform is being moved. A health ministry cannot assume that every clinic, laboratory, ambulance service and insurance gateway will update its dependencies on schedule.

Public-sector dependency is therefore not only technical debt. It is procedural debt. The address record is tied to tender documents, service catalogues, inter-agency memoranda, regulator notices, cyber-insurance forms, audit recommendations and supplier obligations. In many administrations, the original integrator is no longer present. The current contractor may maintain a platform it did not design. The ministry may know the visible domain name but not the complete dependency map behind it. Documentation may be split between a central technology agency, a line ministry, a hosting provider, a telecom operator and an application vendor. Even when the state owns the obligation, the operational knowledge may sit outside the state.

Latin America and the Caribbean add further asymmetry. Public digitalisation is uneven not only between countries but inside them: capital-city agencies may run modern portals while smaller municipalities rely on hosted templates, shared service providers or arrangements negotiated years earlier. A national customs platform may be highly professional while local government procurement sits on fragile infrastructure. A public hospital in a major city may have technical staff, redundant connectivity and security operations; a rural clinic may rely on a provincial network, a telecom bundle and a support number that is busy during a storm. The same address-policy decision may therefore be absorbed as paperwork by one institution and as a crisis by another.

This is why public-sector address dependency should not be analysed as a morality play about who deserves addresses. It is an institutional economics problem. Scarce inputs are embedded in organisations with different switching costs. Those with professional teams, budget autonomy and clear asset registers can adapt more easily. Those with fragmented ownership, contractor-run networks and legal obligations to serve everyone have less room to experiment. The public sector often sits in the second category. It is expected to modernise like a technology firm while being constrained like a bureaucracy and judged like a constitutional actor.

The practical consequence is that registry policy, transfer friction and address uncertainty do not land on a neutral surface. They land on real administrative estates. A slow or discretionary transfer process may be a transaction delay for a private buyer. For a public agency, it may extend dependence on an expiring vendor, delay a data-centre move, complicate a disaster-recovery design or force a ministry to keep paying for a bundled network service because the addresses are entangled with the contractor's infrastructure. The public problem is not always the absence of addresses. Sometimes it is the absence of clean separability.

Procurement rules make that separability difficult to recover after the fact. A tender may specify uptime, hosting location, support hours, data ownership, cyber-security obligations and disaster-recovery targets, while leaving address control implicit. The omission is understandable: procurement officers buy services, not address theory. But the missing clause later becomes expensive. If the incumbent vendor holds the operational address path, a rebid may not produce true competition. New bidders must price migration risk, duplicated infrastructure and uncertainty over whether the old supplier will cooperate. The state may appear to have a competitive market while the address dependency quietly narrows the field. In that sense IPv4 continuity is not only a network issue. It is a procurement-market issue.

The hidden cost of renumbering a state

Renumbering is often described as if it were a technical chore. Replace old addresses with new ones, update DNS, adjust firewalls, test services and move on. That description is too thin for any serious network. For the public sector it is almost fictional. A state does not consist of one network team and one change window. It consists of agencies, courts, schools, hospitals, utilities, police, border offices, public archives, citizen-service portals, suppliers, payment processors, telecom carriers, consultants, auditors, development partners and legacy applications that may not have been designed to be moved.

The visible work is only the top layer. Public-facing endpoints must be changed without breaking citizen access. DNS records must be updated while preserving old expectations. Certificates must be reissued or revalidated. Monitoring must learn the new endpoints. Firewalls must be rewritten. Load balancers, reverse proxies and web application firewalls must be checked. Mail services, API gateways, identity providers and payment interfaces must be tested. Logging and incident-response tools must preserve continuity of evidence across the migration. Public instructions, forms, user manuals and call-centre scripts may need revision. If the service interacts with banks, customs brokers, legal firms, hospitals, laboratories, schools, utilities or international partners, the external allowlists and static configurations become part of the project.

The deeper work is worse because it is not always visible. Many public services contain hard-coded addresses, undocumented dependencies or vendor-managed connections that are discovered only when they fail. A customs platform may have broker software that phones home to an address range that no one has reviewed for years. A court platform may have e-filing integrations with law-firm case management software. A hospital platform may have laboratory machines, imaging platforms or pharmacy applications that were installed under a service contract and never fully documented. A school service may depend on a content-filtering or identity product configured by a third party. A utility may have operational technology separated on paper but still linked through management jump hosts, remote support platforms or vendor VPNs.

The cost of finding these dependencies is part of the cost of address scarcity. It is also part of the economic meaning of a registry record. A number resource is valuable not only because it can be routed. It is valuable because it sits inside a web of reliance. The older the public service, the more that reliance accumulates. IPv4 addresses become like old land parcels under public buildings: the title document is short, but the value lies in the roads, pipes, wires, easements, records and habits built around it.

For states in the LACNIC region, renumbering costs may be amplified by geography and administration. Border agencies require connectivity across ports, airports, free zones, bridges and customs offices. Island states and territories may have fewer redundant routes and a higher dependence on a small number of providers. Smaller municipalities may lack in-house engineers and therefore depend on vendors who charge for discovery work. Public utilities may have regional operating centres and field networks whose change windows are dictated by service continuity rather than by central IT. Education networks may have hundreds or thousands of endpoints distributed across schools with unequal local support. Health networks may have clinical applications where downtime has a different moral and legal weight from an ordinary website outage.

In that setting, the advice to "just migrate" or "just use IPv6" can become an evasion. IPv6 may be desirable for new deployment, and dual-stack operation may be rational in many environments. But public-sector reality is not rewritten by aspiration. The citizen's transaction, the customs broker's declaration, the court filing, the hospital referral, the school exam platform and the water utility's operations centre must work through the infrastructure that actually exists. Running-code primacy means that the live service disciplines the policy sentence, not the other way round. A rule that assumes clean migration has not solved continuity; it has merely exported the cost to institutions that may be least able to absorb it.

The fiscal problem is that renumbering money is rarely visible as a single appropriation. It appears as consulting time, extended support, emergency procurement, parallel hosting, staff overtime, delayed transformation, extra testing, duplicated security review and unexplained risk premiums in vendor bids. Finance ministries may see technology projects exceeding budgets without recognising the address layer as one cause. Legislatures may criticise agencies for slow modernisation while approving procurement frameworks that make network identity hard to move. The true cost is therefore partly hidden in administrative delay. IPv4 scarcity becomes a public-finance issue not because addresses consume the largest line item, but because address rigidity can make every adjacent reform more expensive.

Security controls turn addresses into institutional memory

Security makes public-sector address dependency more rigid. The more sensitive the service, the more likely it is to depend on address-based controls in addition to modern identity, encryption and monitoring. Governments are full of allowlists because governments are full of inter-organisational trust problems. A tax portal may accept traffic from banks, payroll providers, large employers and accounting applications. A customs service may accept connections from brokers, port operators, inspection agencies, warehouses and foreign platforms. Courts may restrict administrative interfaces to known networks. Hospitals may permit remote support from equipment vendors through tightly defined ranges. Utilities may restrict operational dashboards and management interfaces. Procurement services may connect to payment, identity and audit platforms that treat known addresses as part of risk scoring.

Security architects can correctly say that addresses are a weak identity factor. Attackers can compromise hosts, abuse tunnels or exploit trusted paths. Yet the practical conclusion is not that address controls do not matter. It is that they are often one layer in a layered control design, and changing them carries operational risk. A public institution may use certificates, tokens, multifactor authentication, device posture and logging; still, its counterparties may keep old allowlists. A vendor may maintain a support tunnel that was approved under a specific range. A bank may require written approval before changing a connection source. A court or tax agency may need to preserve audit evidence that only registered endpoints could perform certain actions at certain times.

The incident-response layer deepens this dependence. When an attack occurs, responders work from logs, netflows, source addresses, destination addresses, timestamps, certificates, user accounts and service events. Stable address records help investigators connect activity to institutions, contractors and service owners. If addresses are moved, leased, transferred or renumbered without transparent records, the response function becomes more expensive and less reliable. If registry data are incomplete, politicised or subject to discretionary reinterpretation, the evidentiary value of the record declines. That affects not only operators but prosecutors, auditors, cyber-insurance reviewers, public accountability bodies and citizens trying to understand why a service failed.

Emergency services make the problem sharper. A public network used for ordinary administration may become an emergency network under stress: disaster payments, evacuation notices, hospital coordination, water restoration, electricity repair, police dispatch support, emergency procurement, border control, social benefits and public-health reporting. In a hurricane, flood, earthquake, cyberattack or political emergency, the address plan is not an abstract registry object. It is part of the state's ability to coordinate. The services that work in normal time are the services that will be leaned on in abnormal time.

The Caribbean dimension is especially important. Islands and coastal territories face storms, cable cuts, power instability and logistics constraints that can turn a minor network dependency into a continuity issue. A municipality that depends on a small provider, a hosted portal and a contractor-run firewall may have little spare capacity when a disaster forces services online. A hospital or utility may need remote support precisely when physical access is difficult. A registry framework that treats addresses mainly as policy tokens misses the fact that public resilience often depends on boring continuity: known addresses, reachable services, accurate contacts and records that remain useful when other services are under pressure.

Security allowlists also create a political economy of lock-in. If a vendor controls the network path, the address block or the operational documentation, the public agency may become dependent on the vendor for changes that should be under public control. This is not necessarily corruption or bad faith. It is the predictable result of outsourced complexity. Address portability, transparent transfer records and clear holder rights reduce that lock-in. A registry that preserves evidence and facilitates clean movement helps the public agency regain operational independence. A registry that treats movement as a privilege to be rationed can strengthen the incumbent contractor by accident.

The LACNIC region makes continuity uneven and therefore valuable

The LACNIC region is not one market, one administrative culture or one level of network maturity. It includes large economies with national digital estates, small states with limited technical labour pools, island administrations exposed to environmental shocks, land borders with heavy customs flows, public utilities with uneven modernisation, and municipalities where a small IT office is expected to support services that citizens now regard as essential. That variation is the central regional fact for public-sector address dependency. A uniform policy vocabulary can hide unequal switching costs.

In larger administrations, public-sector address dependency may be distributed across central agencies, national data centres, sectoral networks and major telecom relationships. The challenge is complexity: many services, many contractors, many integrations and many accountability layers. In smaller administrations, the challenge may be concentration: a few providers, a few engineers, a few vendors and a small number of address decisions that affect a large share of public service. In island or geographically exposed environments, the challenge may be resilience: keeping services reachable through storms, submarine-cable incidents, power problems or emergency relocations. In border economies, the challenge may be interoperability: customs, immigration, agriculture, health inspection, logistics and taxation services need to coordinate across institutional and sometimes national boundaries.

This unevenness means that public-sector address scarcity is not a single budget line. It is a collection of frictions. A central tax authority may have the purchasing power to buy addresses or negotiate provider arrangements, but a municipality may inherit whatever a vendor provides. A health ministry may understand the need for continuity, but a hospital may be constrained by old equipment contracts and clinical change-control rules. A school network may benefit from national connectivity programmes, but a rural school may experience the policy world through a single broadband circuit. A public utility may have engineering talent but old operational estates that are risky to touch. The same regional registry environment meets each of these institutions differently.

The region's history of outsourced and contractor-run public networks matters. Many public bodies procure applications and connectivity together. A vendor delivers the portal, the hosting, the firewall, the maintenance and sometimes the address plan. That arrangement can be efficient at the start because the public agency buys a functioning service rather than building capability from scratch. Over time it can create dependency. The agency may not know whether the addresses are held by the ministry, the contractor, the hosting provider or an upstream network. It may not know whether they can move with the service. It may not know whether a future transfer, lease or registry update will be straightforward. The contract may say the state owns the data, but not the network identity through which the data is reached.

This is why LACNIC-region public-sector dependency should be analysed through institutional continuity rather than through abstract fairness. If address movement is slow, discretionary or unclear, the winners are not always the poor, the local or the public. The winners may be incumbents who already control the path. The losers may be smaller public bodies that cannot afford long transition projects. A scarcity regime that claims to protect weaker actors can harm them if it traps them in old arrangements, raises transaction costs or forces every continuity problem through a procedural gate.

There is also a trust dimension. Citizens may not know what IP addresses are, but they know whether a portal works. They know whether a tax receipt can be downloaded, a public-service appointment can be booked, a court notice can be checked, a school service can be accessed or a utility outage can be reported. The legitimacy of digital government is built from these small confirmations. Address continuity is therefore not a back-office topic. It is one of the quiet foundations of citizen trust.

The region's dependence on remittances, tourism, commodity logistics, cross-border trade and public-utility reliability also gives address continuity a macroeconomic edge. A customs outage can delay exporters. A public-health portal failure can damage travel confidence. A procurement-service interruption can slow public works. A tax-service incident can affect cash collection. A utility coordination problem can lengthen recovery after storms or grid failures. These are not arguments for treating every address as a national monument. They are arguments for recognising that public-sector address dependency sits inside ordinary economic circulation. The registry layer may look remote from ports, clinics and municipal offices, but its recordkeeping and portability rules can influence the cost of keeping those services reachable.

The registry's proper job is evidence, not permission

The registry layer should be understood as a narrow uniqueness ledger. Its indispensable function is to record who is the holder of a number resource, preserve uniqueness, maintain accurate contactability, support routing-related assertions, record transfers and disputes, and make the information operationally useful. That is already important work. It does not require the registry to become an allocator of moral worth, a regulator of business models or a political gatekeeper over public-service continuity.

The distinction between ledger and gatekeeper is central. A ledger preserves evidence. A gatekeeper decides who may act. A ledger reduces transaction costs by making control, history and conflict state legible. A gatekeeper increases dependency when it can delay, condition or refuse movement according to broad discretion. In the public sector, this distinction has immediate practical consequences. If a ministry must move a service away from a failing contractor, the registry should make the record clear and portable. If a public utility needs addresses for a disaster-recovery design, the registry should help the continuity file remain accurate. If a hospital network has inherited a range through a complex vendor history, the registry should preserve the chain of evidence rather than turn the case into a morality hearing about deserved use.

This is not an argument for disorder. The uniqueness layer must be strict. Duplicate registration would break coordination. False records would harm operators, investigators and citizens. Contact data should be usable. Transfer history should be auditable. Security assertions should be tied to the holder's authority. Disputes should be recorded without allowing one party to erase the other's evidence. Fraud should be dealt with by the institutions that have the authority and process to deal with fraud. But narrow discipline is different from broad discretion. The more valuable IPv4 becomes, the more important it is to keep the common layer thin and reviewable.

The danger is mandate laundering. A registry can begin with a modest administrative function and then borrow the language of community, region, inclusion or public interest to justify broader control. In the public-sector context, that move is especially tempting because governments and citizens are morally attractive nouns. A rule can be presented as protecting public interest while actually increasing institutional power over scarce assets. A registry can describe itself as serving the region while making itself less replaceable. It can speak of stability while denying portability. It can speak of fairness while rationing transactions through discretionary process.

Public-sector continuity gives no justification for that expansion. On the contrary, public dependency is a reason to limit registry ambition. The state needs stable records, not another policy actor inserted into every continuity problem. Courts need evidence, not administrative folklore. Hospitals need reliable contact and routing information, not symbolic stewardship. Schools and municipalities need low-friction access to usable resources, not a theory of regional virtue. Public utilities need resilience and clean handover mechanisms, not a registry that can become an additional point of failure.

Neutrality is not passivity. A narrow registry can still be rigorous. It can reject duplicate claims, demand sufficient authority for record changes, require usable contacts, preserve historical entries, maintain signed routing information, mark disputes, publish operationally meaningful data and cooperate with lawful process. What it should not do is convert that rigor into a general discretion over address value. The more valuable the resource, the more mechanical and reviewable the registry function should become. Public bodies can plan around strict rules. They cannot plan around a clerk who may become a policymaker after the budget has been approved and the service contract has been signed.

Registries must not become enforcers because enforcement changes their nature. An enforcer chooses sanctions, interprets behaviour and uses dependency as leverage. A ledger records rights, control, contact and history so that operators, courts, markets and public authorities can do their own jobs. When a registry turns scarcity into enforcement power, it moves from coordination into capital control. That is the wrong direction for a layer on which public services depend.

Scarcity is a capital fact even when the user is a citizen

IPv4 scarcity is sometimes treated as if it were a commercial issue that becomes morally suspect when discussed near government services. That is a mistake. Scarcity is a capital fact before it is a political slogan. A limited, globally useful input with embedded operational demand will acquire price, liquidity problems, financing structures, hoarding incentives, leasing markets, transfer disputes and balance-sheet significance. Public institutions do not escape that reality because they serve citizens. They face it through procurement, budgets, vendor contracts, service continuity and opportunity cost.

The public sector often experiences capital facts indirectly. A ministry may not buy addresses on a spot market. It may buy a managed service whose price includes address scarcity. A municipality may not lease addresses in its own name. It may pay a hosting provider or telecom operator that prices scarcity into the contract. A hospital may not think of IPv4 as an asset. It may still discover that moving from one network provider to another requires a renumbering project whose cost exceeds the apparent savings. A school network may not hold addresses, but its connectivity programme may be shaped by provider inventory. A utility may not value addresses on its balance sheet, but its disaster-recovery plan may fail if it assumes address availability that the market no longer supplies cheaply.

This is why capital control at the registry layer matters for public services. If a scarce input can move only through slow, discretionary or policy-heavy channels, the cost is not paid only by traders. It is paid by the institutions that need flexibility. A public body may need to separate from a vendor, consolidate data centres, build redundancy, take over a contractor-run service, recover from bankruptcy in the supplier chain or support a new citizen-service platform. Address liquidity is not speculation in those cases. It is the ability to adapt.

There is an important distinction between price and discretion. Price is visible, comparable and budgetable. Discretion is harder to price and easier to exploit. A government can argue over whether an address block is too expensive. It can budget, finance, pool demand or choose a different design. It has a harder time planning around an opaque process that may or may not approve a transfer, recognise a lease, respect a legacy record or permit resources to move with a service. In poorer or smaller administrations, uncertainty can be more damaging than price because there is less staff capacity to manage exceptions.

The moral claim that restrictions protect weaker regions should therefore be handled carefully. Restrictions do not create new IPv4. They change who can navigate scarcity. Well-funded actors hire advisers, wait out process, structure around rules and keep optionality. Smaller public bodies inherit the delay. A regime that suppresses market movement in the name of fairness may end up protecting incumbents, not citizens. The better public-interest question is whether the rule lowers the cost of continuity for the institutions that actually deliver services.

IPv4 should be treated as institutional capital where it is embedded in public-service delivery. That does not mean every government should speculate on addresses or every agency should become a trader. It means that registry governance should stop pretending that addresses are a costless administrative token. A public-sector address range may carry years of integration work, security trust, vendor obligations and citizen habit. Destroying or trapping that value is not neutral. It is a form of capital impairment.

This capital fact also changes the meaning of legacy holdings. Legacy address records can look anomalous if judged only by present allocation formulas. In public-service terms they may be continuity assets. An old allocation used by a university network, a public research institute, a utility, a health network or a ministry may support services whose social value is not captured by current utilisation ratios. The right response is not romantic protection of every legacy arrangement. It is accurate evidence, holder clarity, transferability and a clean path for unused or misaligned resources to move without destroying the services that still depend on them. Legacy should be made legible, not used as a pretext for discretionary confiscation or institutional bargaining.

Leasing and transfers can support continuity when records are transparent

Leasing and transfers are often discussed as if they exist outside public interest. In a public-sector continuity frame, they can be instruments of resilience. A ministry that needs to stand up a new portal, a municipality replacing a failed vendor, a hospital building remote-service capacity, a school network expanding online access or a utility designing backup operations may not need permanent ownership of a large block. It may need reliable use, clean evidence of control, reachable contacts, security compatibility and a record that survives audit. A transparent lease or transfer can be better for public continuity than a rigid allocation regime that forces the institution to wait, redesign or remain dependent on a legacy supplier.

The key word is transparent. Public institutions need records that can be reviewed by auditors, courts, procurement officers, cyber-security teams and future contractors. They need to know who had authority to use which addresses, during what period, under what contract, with what security assertions and what dispute state. They need to know whether a resource can move if the service moves. They need to know whether a provider can withdraw use in a way that disrupts a statutory function. They need to know whether incident responders can interpret logs months or years later. These are ledger questions.

A narrow registry can support this by making transfer and leasing records accurate, portable and auditable. It can require clear holder authority, maintain contact data, support secure delegations, record time-bounded use and preserve history. It can make the public institution less dependent on informal email chains and vendor assurances. It can reduce fraud by making claims legible. It can help resolve disputes by preserving evidence instead of pretending that discretionary silence is stability.

A gatekeeping registry does the opposite. It treats movement as exceptional, leasing as suspect and market activity as a problem to be disciplined. That posture may sound protective, but it can harm public agencies that need flexible continuity. If a municipality cannot obtain address use without accepting a bundled vendor arrangement, the public loses bargaining power. If a hospital cannot cleanly record temporary address use during a migration, the audit trail suffers. If a utility cannot transfer resources away from a failing provider without a prolonged process, resilience is weakened. If a tax authority cannot design redundancy because address movement is uncertain, citizens inherit the risk.

Public procurement adds another reason to prefer transparent address markets over informal dependency. Procurement processes are designed to compare bids, specify deliverables and enforce contracts. They work badly when a critical input is hidden inside the vendor's network. If address rights and use can be recorded clearly, a public agency can write better tenders: the service provider must document address use, preserve portability, cooperate in transfer, maintain security records and return or move resources at contract end. If the registry environment refuses to recognise practical forms of address use, contracts become less honest. The public agency may buy continuity without being able to name the thing it is buying.

None of this requires registries to endorse every transaction or ignore abuse. It requires them to distinguish evidence from permission. A lease can be recorded without turning the registry into a commercial judge. A transfer can be recognised without the registry deciding whether the buyer is morally deserving. A dispute can be flagged without freezing unrelated public services. The registry's job is to make control, use and conflict visible enough for the relevant institutions to act. In the public sector, visibility is itself a form of resilience.

Public archives and citizen memory are part of the address problem

Public-sector address dependency is not limited to live portals. Archives matter. Governments are custodians of records that outlive administrations, contractors and technologies: laws, regulations, court judgments, procurement awards, tax guidance, land records, environmental permits, public-health notices, education materials, statistical releases and emergency orders. Many of these records are now accessed through web services that depend on old URLs, old hosting environments, old redirects and old address arrangements. If address continuity breaks, the damage can be quieter than a portal outage but more durable.

A citizen trying to verify a regulation, a journalist reviewing a procurement award, a lawyer citing an old judgment, a researcher checking a public-health notice or a company confirming customs guidance may rely on the continued reachability of an archived public page. The state may have a formal archive, but the practical archive is often the web. Search indexes, citations, bookmarks, legal filings, academic papers and public-service guides point to addresses and domains that must resolve to something trustworthy. When the infrastructure behind those records changes, the question is not only whether the current service works. It is whether the chain of public memory remains intact.

IPv4 appears in this archive problem indirectly. A public archive may sit behind old hosting, a shared provider, a static site, a content-delivery arrangement or a government data centre. The records may depend on reverse proxies, redirects, certificate renewals, firewall rules and address mappings that no current employee fully understands. If the addresses are lost, trapped in a vendor dispute or renumbered without careful redirection, the public record can fragment. A court judgment may still exist in a database but become difficult to find through the path citizens know. A procurement notice may still be stored but not reachable through the old reference. A public-health notice may be archived but stripped of the context that gave it authority at the time.

This is why address continuity has an evidentiary dimension. The registry record is not the public record, but it helps support the infrastructure through which the archive is reached and interpreted. Accurate holder data, transfer history and contactability help future operators understand who controlled an address range when a service was active. They help incident responders distinguish a defacement from a migration. They help auditors reconstruct whether a contractor fulfilled obligations. They help courts and public accountability bodies interpret technical evidence when a service failure affects rights or money.

The archive problem also shows why public-sector dependency cannot be solved by a simple forward-looking policy. New services may be built with better cloud design, IPv6 readiness, modern identity and more portable infrastructure. Old public records will still exist. The state cannot declare that only new architecture matters. It carries the past as part of its legitimacy. That past includes old address dependencies, old vendor arrangements and old integration choices.

For LACNIC-region governments with limited archival budgets, this is a serious continuity issue. Public records may be spread across agencies, municipalities and contractor estates. Some may be preserved by national archives; others may survive because a small technical team keeps an old server alive. A registry environment that facilitates clear recordkeeping, transfer and continuity helps the archive function. A registry environment that adds uncertainty to address control makes the public memory more brittle.

The continuity case against enforcement creep

Enforcement creep is dangerous because it converts administrative dependency into leverage. A registry may begin with narrow recordkeeping and then add compliance layers, eligibility judgments, usage conditions, approval requirements, sanctions and discretionary interpretations. Each addition may be defended as reasonable. Together they change the economics of the layer. The holder no longer depends on the registry only for accurate recording. The holder depends on it for permission to preserve value.

For public-sector networks, this is an unhealthy dependency. A ministry, court, hospital or utility should not have to wonder whether a registry's changing policy interpretation will impair a continuity plan. It should not have to keep public services on an inefficient vendor arrangement because transfer recognition is uncertain. It should not have to treat address rights as a favour. And it should not have to expose sensitive operational detail to a policy process that is neither a court, nor a regulator, nor a procurement authority, nor an emergency-management body.

This is not a call for registries to ignore law. If a court issues an order, a fraud is proven, a contract is breached or a public authority acts within its legal competence, the registry may have to reflect that reality in the record. The point is that the registry should not manufacture its own enforcement sovereignty out of scarcity. It should not use its position over a unique ledger to decide which commercial models, holders, regions or public institutions deserve continuity. Where enforcement is necessary, it should be anchored in law, contract, due process and reviewable evidence. Registry discretion should not be the enforcement source.

Mandate laundering is especially subtle in public-sector language. A registry can say it is protecting the region's development, the community's resources or the public interest. Those phrases are attractive because the public sector really does matter. But the existence of public reliance does not automatically authorise a private or semi-private administrator to become a public-policy judge. The more important the dependent services are, the more careful the architecture should be about discretionary chokepoints. Criticality is a reason for restraint, portability and failover, not for institutional self-expansion.

The running-code test is useful here. If a rule damages the live networks that deliver tax, customs, court, health, education, utility or emergency services, the burden should be on the rule, not on the running service. Policy should not be allowed to declare victory while operators quietly absorb the operational loss. In Internet coordination, implementation is not a detail that follows legitimacy. It is part of legitimacy. A rule that cannot survive contact with live public services is not stable merely because it was written in the language of stability.

The continuity case therefore favours holder rights and portability. Holder rights make the registry record predictable. Portability gives the holder an exit if administration fails, becomes politicised or no longer provides neutral service. Failover protects the ledger from the gatekeeper's weakness. These ideas are not radical when applied to domains, financial records, public archives or critical infrastructure. They become controversial in number resources only because the old model grew comfortable with non-portable dependency.

A narrow society for number resources

The positive alternative is not a government takeover of address administration and not a new institution with a thicker mandate. Governments can politicise infrastructure, fragment markets and turn technical dependencies into instruments of policy. Private gatekeepers can also overreach, extract rent and confuse participation with authority. The better direction is a narrower common layer: coordination that protects uniqueness, evidence, holder rights, portability and continuity while leaving commerce, public law and operational design to the institutions that actually bear the consequences.

This is where the Number Resource Society model is useful as a future frame. Its value is not that it offers a new flag to replace the old one. It is that it starts from the right question: what must be common for the Internet to keep working, and what should not be centralised at all? The common layer must prevent duplicate claims, preserve accurate records, support routing security, maintain contactability, record transfer history, expose dispute status, protect portability and allow failover. It should not become a judge of business model, regional virtue, public-sector need or political destiny.

For LACNIC-region public services, that distinction is practical. A tax authority needs continuity, not ceremonial stewardship. A customs service needs reliable endpoints and auditable changes. Courts need stable access and evidence trails. Hospitals need resilient connectivity and vendor independence. Schools need affordable expansion and supportable operations. Utilities need disaster-resistant coordination. Municipalities need the ability to change contractors without losing network identity. Archives need persistence across administrations. Citizens need services that continue to work even when the institutional story behind them is messy.

A narrow number-resource society would treat these needs as reasons to strengthen the ledger, not the gatekeeper. It would recognise that IPv4 scarcity is real capital scarcity and that suppressing movement does not abolish economics. It would support transparent leasing and transfers because public continuity often requires flexible use. It would protect holder rights because uncertainty is a hidden tax on every dependent service. It would build portability because no public service should be trapped by the failure or ambition of one administrative layer. It would treat registry administration as replaceable infrastructure rather than as a throne.

This model also fits the public-sector archive problem. Records should outlast contractors. Address evidence should outlast policy fashions. Dispute metadata should remain visible without allowing a dispute to erase operational history. Transfers should preserve the chain of control. Security assertions should be tied to verifiable holder authority. If a registry fails, the ledger should survive. If a vendor fails, the public service should move. If a policy room claims a mandate it does not have, holders should have rights strong enough to prevent dependency from becoming obedience.

The institutional design test is simple. Can a public service keep operating if a contractor changes, a provider fails, a ministry consolidates services, an archive is migrated, a disaster-recovery site is activated, a court order clarifies control or a registry administration becomes unreliable? If the answer depends on discretionary goodwill, the design is weak. If the answer depends on auditable records, portable rights and replaceable administration, the design is stronger. Public-sector resilience is not achieved by making every institution dependent on the same gatekeeper. It is achieved by making the common record durable enough that public institutions can change everything else.

The LACNIC region does not need an address-governance essay about national sovereignty to understand this. It needs a continuity economics account. Public services in the region depend on IPv4 because old obligations, uneven digitalisation, contractor-run networks, security allowlists, emergency-service requirements and public archives have made stable addressing part of the state's operating fabric. That dependency should not be romanticised. It should be made legible, priced honestly and protected through narrow coordination.

The registry's defensible role is therefore modest and important: record accurately, preserve uniqueness, maintain operational evidence, support secure assertions, respect holder rights, enable movement and keep the ledger usable when institutions change around it. The moment it claims a broader mandate over who deserves address value, it stops being the clerk public services need and starts becoming another source of public-sector risk. For citizens, the test is simple. The tax portal should work. The court file should be reachable. The hospital network should coordinate. The school should connect. The utility should respond. The archive should remain findable. IPv4 is part of that continuity not because it is glamorous, but because institutions have built years of public reliance on top of it.

Sources and further reading

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