Summary

  • LACNIC university-legacy-space analysis asks how campus networks, research labs, libraries, medical schools, observatories and student systems carry address memory outside ordinary ISP economics.
  • IPv4 scarcity turns dormant or oversized campus holdings into capital and public-mission questions around sale, lease, cloud migration, partner allowlists and renumbering cost.
  • A credible regional ledger should preserve university record truth and transferability without treating academic purpose as a license for discretionary registry gatekeeping.

In Latin America and the Caribbean, old campus IPv4 records are becoming a test of whether public-interest networks can treat scarce numbering as continuity, capital and responsibility without turning the registry into a moral gatekeeper.

The campus address book becomes a balance sheet

At many universities the most consequential infrastructure is not the newest. It is the small set of old records that everyone has stopped seeing. A server room in a faculty building carries DNS names that were first written for a different generation of operating environments. A medical school keeps teaching portals, telemedicine gateways, imaging archives and hospital-adjacent applications behind ranges that predate the cloud committee. An observatory exchanges data with partners abroad through firewall rules that were agreed when the campus network was run by a handful of engineers rather than a procurement office. A central library authenticates licensed journals, alumni services and remote access services through addresses that publishers, research partners and security vendors have quietly learned to trust. A student-services platform has moved from physical machines to virtual machines to cloud front ends, but the old public address still appears in allowlists, logs, mail reputation networks, VPN profiles and help-desk runbooks.

This is university legacy space. It is not simply an early allocation in a registry database. It is a record of how academic networks became operational institutions. In the LACNIC region that history has a particular texture. Universities were often among the first durable network users in their countries. They connected laboratories before broadband was normal. They hosted national academic services before ministries had strong digital units. They served cities beyond their campuses through extension programmes, libraries, hospitals, radio astronomy, meteorology, engineering labs and teacher-training platforms. Their networks grew around the academic calendar but came to support public functions that did not look academic at all.

Scarcity has changed the object without changing the room in which many universities discuss it. A record that once looked clerical now has financial value, operational dependency and political sensitivity. A campus that holds more IPv4 space than it uses may be sitting on a scarce digital asset. A campus that uses every address may still discover that the cost of renumbering is far greater than the market price of the addresses. A campus that wants to release or lease unused space confronts a different question: whether a public-interest institution may convert old academic privilege into cash without harming its mission or weakening future research capacity. A campus that refuses to discuss the matter also makes a decision, because dormant capacity has opportunity cost in a scarce market.

The LACNIC setting sharpens the issue. Latin America and the Caribbean contain world-class research institutions, large public universities, private campuses, technical institutes, national research networks, remote laboratories, island universities and institutions whose budgets fluctuate with currency, politics and enrollment. Some universities are strong enough to treat their legacy space as a strategic asset. Others lack the staff, legal confidence or administrative continuity to do more than keep old arrangements alive. Some have large obligations to students and hospitals. Some have campuses where a single public range is entangled with email, identity, building security, library access, lab instruments and cross-border research links. Scarcity does not turn those differences into a neat market. It turns them into a governance problem.

The mistake would be to treat universities as a sentimental exception to the address economy. The opposite mistake would be to treat them like ordinary commercial holders whose only rational move is asset monetisation. Universities are neither saints nor corporations in disguise. They are institutional networks with public missions, internal politics, long memory and weak incentives to price operational risk correctly. Their legacy space is therefore a good test of the whole registry question: does the number-resource order merely keep a narrow uniqueness ledger, or does it claim the authority to decide which institutional uses of scarce addresses are morally acceptable?

The answer matters because old campus records now sit at the intersection of capital and continuity. They are capital because scarcity gives them a price and makes dormant capacity economically meaningful. They are continuity because the identity of a campus network is often embedded in relationships that cannot be moved by spreadsheet. The hard part is not choosing one word. It is building a regime in which a university can preserve live services, release unused value when appropriate, document control honestly, and remain free from registry discretion over its mission.

Why universities received space for reasons firms did not

The university route into early Internet numbering was not the same as the enterprise route. A commercial firm usually wanted connectivity for production services, offices, customers, data centres or later cloud services. A university wanted those things too, but its network boundaries were looser. It needed space for dormitories, research groups, faculties, libraries, administrative buildings, experimental services, medical schools, public outreach, visiting scholars and sometimes national or regional academic infrastructure that temporarily lived on campus because no other institution had the competence to host it.

This breadth reflected the culture of research networking. Academic networks were built for openness before they were built for monetisation. A laboratory might need globally reachable hosts because collaborators abroad expected direct access. A physics group might run an instrument-control stack that did not fit ordinary enterprise segmentation. An engineering department might host experimental routers. A computer-science faculty might give students public services because learning the network meant touching the network. A library might authenticate readers to overseas publishers. Roaming academic access, with eduroam-like expectations of visiting scholar mobility, made the campus edge part of a wider trust fabric. A medical faculty might support a hospital network that was administratively separate but technically adjacent. A public university might provide connectivity to schools, cultural projects or scientific stations because it was the only credible technical anchor.

In Latin America and the Caribbean, this pattern intersected with uneven infrastructure development. Many countries developed academic networking before they developed mature competitive broadband markets. A national university or technical institute could function as a first mover, a convening node and a training ground for the engineers later hired by carriers, ministries, banks and software firms. Research networks linked cities and campuses that commercial providers did not prioritise. In smaller economies, especially in the Caribbean, a single university or regional campus could carry disproportionate importance because the national market was too small to sustain many independent technical institutions. In larger countries, old public universities combined scale with autonomy, giving their network teams room to build before procurement rules caught up.

That history explains why campus address plans often look untidy by modern standards. They were not designed by asset managers. They were designed by people trying to make research work. A range that appears underused today may have been reserved for an engineering faculty, a hospital network, a supercomputing cluster, a satellite campus, a public education programme or a collaboration that later changed shape. Another range may contain real use that is hard to see because the devices are seasonal, instrument-specific, behind old access-control gear or used only by partners who still rely on stable source addresses. Dormitory networks, student labs, research testbeds and administrative services may have been folded together in ways a modern security architect would never approve but a migration team cannot quickly unwind.

The public-interest mission also complicates ownership language. Universities did not obtain addresses merely to build shareholder value. They obtained them to teach, research, publish, collaborate and provide services. That mission gives them a stronger claim to continuity than a speculative holder has, but it does not mean the addresses belong to an undefined regional public. The institution that built around the space, maintained records, trained staff and carried risk has reliance interests that cannot be erased by a moral vocabulary about community. A registry may maintain uniqueness and accuracy; it cannot turn the academic origin of a block into a standing licence for administrative paternalism.

The best way to understand old university space is as institutional memory. It records choices made when the boundary between research and operations was porous. It reflects a time when a campus could be both a user and an infrastructure provider. It contains dead zones, mistakes, forgotten reserves and live dependencies. It may include addresses that should be transferred, leased, reclaimed internally or retired. But the decision cannot be made by looking only at utilisation ratios. A university network is not a factory floor. Its value lies partly in optionality, in the ability to start a research collaboration quickly, to support a crisis response, to host a temporary scientific service, or to maintain a stable identity across changing vendors.

This is why universities should not be judged by an enterprise efficiency script. A firm with a private customer base can sometimes renumber aggressively if the commercial benefit is large enough. A university has constituencies that are harder to price: students, faculty, patients, libraries, publishers, alumni, visiting researchers, national education networks and international partners. It has governance bodies that move slowly by design. It has procurement rules that favour continuity over experimental risk. And it has a mission that often requires keeping capabilities available before demand is fully visible. The economics are real, but they are institutional economics rather than simple inventory management.

Scarcity turns dormancy into capital

IPv4 scarcity has made dormant campus capacity visible in a way technical reports did not. A finance office can ignore an unused subnet when it has no obvious price. It is harder to ignore when similar space is leased, sold, valued by brokers or treated by operators as an input to customer revenue. Scarcity creates an accounting temptation: perhaps the campus has a hidden asset. The same scarcity creates an operational anxiety: perhaps what looks unused is part of a continuity dependency no one has fully mapped.

The price signal is useful because it forces attention. Universities are good at underpricing infrastructure that does not resemble a building, grant or faculty post. A public IPv4 block may enable student registration, journal access, research collaboration, email reputation, laboratory remote access and cloud transition, yet appear nowhere in strategic accounts. Once scarcity gives the block a market value, the institution has to ask better questions. Who is the holder of record? Which units depend on it? Which routes are announced? Which DNS names resolve into it? Which research partners allowlist it? Which hospital or clinic services have security assumptions around it? Which old devices cannot be renumbered without vendor intervention? Which addresses are genuinely idle?

But a price signal is not a complete moral argument. Universities in the LACNIC region face real funding pressures. Public universities may be underfunded, politically exposed or forced to delay equipment refreshes. Private universities may face enrollment shocks, currency constraints and competition from international providers. Research groups may depend on grants that arrive late or in foreign currency. A large unused address block can therefore look like a source of funds for scholarships, fibre upgrades, cyber-security, instrumentation or cloud credits. In poor or small markets, monetising a scarce digital asset may be less an act of speculation than an attempt to finance continuity.

The ethical issue is not whether universities may ever sell or lease. A blanket moral prohibition would freeze value and punish institutions that happened to receive space early but now need cash for real services. The issue is governance: whether the institution can distinguish surplus from reserve, short-term cash from long-term capability, and private benefit from public mission. A university that sells addresses to cover a budget hole without mapping dependencies may damage its own research infrastructure. A university that leases dormant space under opaque arrangements may invite reputational risk, abuse exposure and political criticism. A university that refuses all transactions on principle may strand capital that could support students and labs.

The worst answer is registry moralism. A regional registry is not equipped to decide whether a campus should monetise a block to fund a medical school network, keep it for future research or lease it under safeguards. That decision belongs to the holder, its governing bodies, its public obligations, its legal environment and the market counterparties that bear contractual risk. The registry's legitimate concern is narrower: the record must be accurate; control must be proved; transfer or lease metadata must not create conflicting claims; abuse contacts must be reachable; security assertions must remain intelligible; disputes must be recorded rather than hidden. Beyond that, scarcity does not make the registry a university ethics board.

The sensible response is a campus address audit that treats IPv4 neither as sacred heritage nor as loose inventory. The audit should map routing, DNS, mail, VPN, library access, research partner allowlists, hospital-adjacent services, lab instruments, cloud dependencies, security controls and contractual obligations. It should classify space into operationally embedded, strategic reserve, transition reserve, candidate lease, candidate sale and unknown. It should attach decision rights and risk owners. It should explain why a transaction supports the institution's mission, not merely that it produces revenue. Such work is mundane. In a scarce IPv4 world, it is also financial governance.

The cost of changing a campus number

Renumbering a university is usually described as a technical project. That description understates the problem. It is a social, contractual and reputational project with technical components. The more open and collaborative the institution, the more external memory accumulates around its addresses. A commercial platform may know its customers; a university may not know all the foreign laboratories, publishers, student devices, alumni services, visiting fellows, hospital partners and public agencies that still treat its addresses as identifiers.

Identity is the first hidden cost. Public addresses become campus identity because other services use them to infer trust. Library publishers may recognise a university range for access to journals. Research partners may allowlist addresses for data exchange. Scientific instruments may send observations to known endpoints. Mail networks may have sender reputation tied to old ranges. VPN gateways may be embedded in faculty laptops, field devices and partner documentation. A medical school may connect clinical teaching services, simulation environments or hospital research data through rules that were negotiated years earlier. An observatory or environmental sensor network may be reachable through addresses written into scripts by a doctoral student who has since left the country.

A further cost is procurement inertia. Latin American and Caribbean universities often operate under procurement rules that are good at preventing arbitrary spending but poor at quick infrastructure adaptation. Public universities may need tenders, budget-year approvals, legal opinions and political sign-off. Private universities may be faster but still constrained by vendor contracts, dollar-denominated services, data-protection concerns and board oversight. A cloud migration may be approved for application hosting but not for all the network identity work needed to make the migration clean. The result is partial modernisation: services move to cloud, but old campus addresses remain as anchors because external parties trust them.

Student services add another layer. Enrollment, learning platforms, identity platforms, payment gateways, housing, health services and alumni portals must survive semester cycles. Universities can tolerate scheduled maintenance, but they are highly sensitive to outages during registration, examination, scholarship deadlines or graduation. If a renumbering project fails during those windows, the cost is not merely technical downtime. It is student anger, administrative backlog and reputational damage. In countries where many students commute, work part-time or depend on public scholarships, digital access failures can have social consequences. The address plan becomes part of the university's duty of care.

Labs and field stations are even harder. Research infrastructure often has long useful lives. Instruments in astronomy, oceanography, seismology, agriculture, medicine and engineering may be expensive, remote and maintained by small teams. Their software may be old because the scientific instrument is old. Their network rules may have been written for reliability rather than elegance. A telescope-related data path, a marine sensor platform, a tropical disease lab, an earthquake monitoring collaboration or a genomics data path may depend on stable network assumptions. Replacing those assumptions can require vendor support, foreign partner coordination and grant compliance. The market value of the address block may be visible; the replacement cost of the institutional trust around it may not.

This is why a pure utilisation measure is dangerous. If a campus uses only part of a legacy block, the unused portion may still serve as a transition reserve. During migration, dual operation is often necessary: old and new services must coexist while contracts, DNS, firewalls, certificates, monitoring and user devices are updated. A university with no spare address capacity may be forced into brittle, compressed migrations. Dormant capacity can therefore be economically rational even when it appears inefficient. The question is not whether every address is lit today. It is whether the capacity supports credible continuity, transition or future mission.

At the same time, universities should not hide behind complexity forever. Some dependency maps are vague because no one has been paid to do the work. Some reserves are merely forgotten. Some old public addressing can be replaced by private addressing, modern identity platforms, VPN redesign, cloud-native access or better segmentation. Some leases could be structured without harming campus operations. Scarcity requires disciplined inquiry. It does not require forced renumbering by registry theory, and it does not excuse institutional neglect.

LACNIC's region is not one university market

It is tempting to speak of the LACNIC region as a single academic environment. That obscures the economic problem. Latin America and the Caribbean contain countries with large national higher-education sectors and countries where one or two institutions dominate higher education. They contain research-intensive public universities, teaching-focused private universities, Catholic and secular institutions, technical institutes, medical schools serving foreign students, open universities, regional campuses and cross-border programmes. Their address holdings, staffing models and bargaining power differ sharply.

The first divide is scale. A large public university in Brazil, Mexico, Argentina, Chile or Colombia may have technical staff, legal counsel, cyber-security units, data centres and political weight. It may still be bureaucratic, but it can at least convene the right people. A small university in a Caribbean state or Central American country may depend on a few engineers, outside vendors and personal memory. The smaller institution may hold modest legacy space that is nevertheless central to its operations. It may lack the capacity to evaluate a lease proposal, negotiate abuse handling, document a transfer or migrate services safely. Scarcity rewards knowledge. That creates inequality.

The second divide is funding. Some public universities have constitutional or statutory protections; others live through austerity cycles, strikes and delayed budgets. Private universities may be well capitalised or financially fragile. Research networks may receive stable support in one country and precarious project funding in another. Exchange rates affect cloud bills, equipment purchases and consultant fees. A dollar-denominated IPv4 transaction can therefore look different depending on the institution. For one university, selling space may be a strategic portfolio decision. For another, it may be a desperate way to replace core switches or keep a campus link alive.

The third divide is procurement. Public institutions often face rules designed for fairness, transparency and anti-corruption. Those rules can be valuable, but they were not built for liquid digital assets whose value fluctuates and whose operational dependencies are technical. How does a university tender a lease of address space? How does it evaluate counterparties? Does the transaction count as sale of public property, service contract, intangible asset management, telecom arrangement or IT outsourcing? Who signs? What happens if abuse complaints arrive from a lessee's customer? How does the university ensure that the arrangement does not damage its reputation or future transferability? Without clear doctrine, delay becomes the default.

The fourth divide is the role of research networks. National and regional research-and-education networks are part of the region's academic infrastructure, but they are not all-powerful. They can provide connectivity, coordination, expertise and a community of practice. They can help universities map dependencies and share migration lessons. Yet they may not control the legacy holdings of member institutions, and they should not become substitute gatekeepers. The purpose of a research network is to strengthen academic connectivity, not to convert old campus resources into pooled political property. The university holder's rights and responsibilities remain central.

The fifth divide is small-country dependency. In smaller states, universities often carry functions that look national. They train teachers, doctors, civil servants and engineers. They host public lectures, archives, health programmes and disaster-response expertise. Their network identity may be entangled with state agencies, international donors, foreign campuses and regional organisations. If such an institution monetises address space badly, the harm may spill beyond campus. If it cannot monetise any surplus, it may miss a rare chance to fund connectivity in a market where commercial options are expensive. The correct policy must be sensitive to this dual role without assuming that a registry can micromanage it.

The region's diversity makes a single moral story useless. Some universities should probably release more space. Some should keep reserves. Some should lease under strong controls. Some should consolidate. Some should seek shared technical support. Some should treat old blocks as strategic capital for scholarships or research equipment. What they all need is a thin, reliable registry ledger that records truth and does not substitute regional ideology for institutional decision-making.

The registry should record the campus, not govern it

The central institutional distinction is simple: a registry record should describe reality, not create it. A university that controls a block should be recorded accurately. Its contacts should be reachable. Its route-related and security metadata should be intelligible. Transfers, leases or changes of control should not produce conflicting claims. Disputes should be marked so that third parties understand uncertainty. These are real registry functions. They protect uniqueness and operational trust.

What the registry should not do is decide whether a university's use is sufficiently academic, sufficiently local, sufficiently efficient or sufficiently morally attractive. That would turn the ledger into a gate. A registry may have views about conservation, regional development or anti-abuse norms. Those views do not become a mandate over campus capital. The more valuable IPv4 becomes, the narrower the registry's role should be, because administrative discretion over scarce assets becomes economic power. Scarcity does not turn a bookkeeper into a landlord.

Universities make this point visible because their missions are easy to romanticise. If a registry can say that university addresses are part of a regional educational commons, it can use sympathetic cases to expand authority. But the same logic can later be used against any holder. A public mission does not cancel holder rights. It makes institutional responsibility more important. The university must answer to its students, faculty, patients, donors, taxpayers, board or ministry. It should not also be subject to a registry's informal theory of whether a lease, sale, reserve or cloud migration aligns with the registry's idea of regional virtue.

The doctrine of running-code primacy is useful here. Running networks are not symbolic participants in a policy story. They are the thing the registry exists to serve. For a university, the running code includes authentication platforms, library access, research data transfers, email, VPNs, lab instruments, student portals and partner connections. A rule that threatens those services in the name of administrative preference has the order backwards. Procedure is legitimate when it protects the running network's minimum common needs: uniqueness, accuracy, proof of control, security assertions, transfer records and continuity. It loses legitimacy when it polices business model, customer geography, institutional morality or capital use.

This boundary does not mean universities can do anything without consequence. If a university leases space to a party that generates abuse, it may face contractual, reputational and operational consequences. If it sells space without authority, internal law may invalidate the decision. If it hides a dispute, counterparties may be misled. If it leaves contact records stale, incident response suffers. These are serious matters. But the enforcement mechanisms should be contracts, courts, procurement law, cyber-security procedures, insurance, governance and market discipline. The registry should not become police, prosecutor and judge over essential numbering records.

There is a practical reason for restraint. Registry discretion creates uncertainty, and uncertainty raises the cost of good behaviour. If universities fear that documenting a lease will invite moral scrutiny, they may keep arrangements informal. If they fear that asking about transfers will trigger questions about historic use, they may avoid audits. If they fear that unused capacity creates vulnerability, they may conceal it. A thin ledger encourages truthful records because the act of recording is not treated as surrendering control to a gatekeeper. A thick governance regime encourages defensive opacity.

The LACNIC region should be especially wary of mandate laundering through academic language. The region's universities are real. Its educational needs are real. Its funding inequalities are real. But affected stakeholders are not automatically principals who can authorize restrictions on a holder's assets. A meeting room, a mailing list or a policy consensus may provide expertise and warning. It does not become the governing body of every campus that holds addresses. A service region is a service region. It is not a sovereign owner of university space.

This distinction also protects smaller institutions. Large universities can often navigate thick process. They can hire counsel, attend meetings and wait. Small institutions cannot. A registry regime that promises fairness through discretion often favours those with administrative capacity. A thin, predictable ledger helps the under-resourced campus because it lowers transaction costs and makes rules easier to understand. The less a university must plead its virtue to a procedural room, the more it can focus on mapping dependencies and protecting services.

The proper registry question is therefore not "Should this university be allowed to monetise?" It is "Can the record remain accurate, unique, auditable and continuous if the university acts?" If the answer is yes, the registry should record. If legal disputes exist, record the dispute. If security assertions change, record the change. If contactability fails, require correction of the record. But do not smuggle capital control into the language of stewardship.

The public-interest problem inside the university

Rejecting registry paternalism does not solve the university's own ethical problem. A campus cannot simply announce holder rights and ignore mission. Its address space may have been acquired through public subsidy, academic privilege, early technical trust or national research policy. Even where the legal holder is a private university, its social licence often rests on education, science and professional formation. Monetising legacy space therefore requires more than proving registry control. It requires institutional justification.

The first ethical question is intergenerational. Address space obtained in the early Internet was often sized for a future that did not unfold as expected. Today's administrators may be tempted to convert that surplus into current cash. Future students and researchers may need stable network identity, transition reserves or scarce addresses for projects not yet visible. Selling all apparent surplus can be a way of consuming institutional optionality. Keeping all surplus can be a way of denying current students the benefits of an asset that could fund better connectivity, security or research equipment. The ethical answer is not hoarding or liquidation; it is a decision process that values future capability honestly.

The second question is distribution. If a public university sells or leases address space, who benefits? Does the money return to the network, library, research computing, student services or scholarships? Or does it disappear into a general budget where the connection to digital infrastructure is lost? A transaction that funds cyber-security, campus Wi-Fi, lab connectivity or medical teaching platforms has a stronger mission claim than one used to cover unrelated deficits without transparency. The addresses were part of the university's infrastructure endowment. Their monetisation should not be detached from the infrastructure and educational purposes that gave them legitimacy.

A public-interest address policy for a university should therefore contain several elements. It should define who can approve transactions. It should require a dependency audit. It should preserve reserves for student services, research computing, medical or field equipment and cloud transition. It should require abuse controls for leasing. It should disclose enough to satisfy public accountability without exposing security-sensitive details. It should route proceeds toward digital infrastructure or other mission-linked uses. It should review the decision periodically because both scarcity and campus needs change.

Such a policy does not need to mimic corporate asset management. It should reflect the university's mission. But it must also resist nostalgia. Old addresses are not morally pure because they came from academic history. They can be wasted, mismanaged or used as private fiefdoms by departments that never face the opportunity cost. Public mission cuts both ways: it justifies continuity, and it demands accountability for dormant value.

Cloud migration does not erase legacy identity

Many university leaders assume the cloud will make old address questions disappear. It rarely does. Cloud changes where compute runs and who operates parts of the stack. It does not automatically change the public identity that partners, publishers, devices and security vendors have learned. In some cases it makes that identity more important, because applications move faster than external trust relationships.

This is the economic meaning of portability. A university should be able to change transit providers, data centres, clouds and managed-service vendors without losing the network identity around which research and student services have formed. Portability is not merely a market convenience. It is a continuity principle. When identity is locked to a provider, the provider gains leverage. When identity is locked to a registry with no exit, the registry gains leverage. A serious campus strategy should reduce both forms of hostage risk.

Legacy IPv4 can support this strategy if governed well. A university that understands its holdings can use them as portable identity anchors across cloud and network transitions. It can announce space through different providers, segment critical services, support controlled bring-your-own-address deployments and preserve partner trust while changing infrastructure below. That requires accurate records and strong engineering. It also requires holder rights. If every movement of address identity is subject to discretionary approval, portability becomes permission theatre.

The cloud also changes the sale-or-lease question. A campus that migrates many services to cloud may free local address capacity. But if cloud deployment depends on stable source ranges, some of that capacity should be retained or restructured rather than sold. If a cloud provider supports customer-owned space, the university may preserve identity while reducing on-campus hosting. If it does not, the university may need proxies, gateways or staged renumbering. The optimal decision is architectural, not ideological.

Universities in the LACNIC region face additional constraints. Cloud regions may be outside the country. Latency, data residency, currency exposure and procurement rules may affect adoption. A university may not be able to rely on a single provider or a permanently favourable contract. Portable address identity can give it bargaining power. It can move workloads without forcing every partner to relearn its network face. In that sense, old campus space is not legacy baggage. It is a strategic buffer against vendor and jurisdictional dependency.

Dormant capacity and the politics of appearing wasteful

University address holders are vulnerable to a charge that is both powerful and crude: waste. If a campus holds more IPv4 than it currently uses, critics can argue that scarce resources are being denied to networks that need them. The claim has emotional force in a region with unequal connectivity. It also risks becoming a tool for capital control.

The first response is empirical. Some dormant capacity is real. Old allocations may contain unused ranges, forgotten projects, abandoned departmental networks and reserves far beyond any plausible academic need. Universities should not pretend otherwise. In a scarce environment, leaving such space undocumented and idle has a social cost. It reduces supply, hides value and weakens the institution's credibility. A public-interest university should be willing to identify genuine surplus and consider responsible release, lease or internal redeployment.

The second response is functional. Not all unused space is waste. Universities need buffers for migration, experiments, research campaigns, cyber-security redesign, disaster recovery, partner projects and sudden public missions. A public-health emergency, earthquake response, regional education initiative or large scientific collaboration may require rapid deployment. Procurement may be slow; address availability can be the only flexible resource the network team controls. A campus that has no reserve may save apparent inventory and lose institutional agility.

The third response is comparative. Commercial networks are not the only legitimate higher-valued users of IPv4. A university service that supports low-income students, hospital training, agricultural research or disaster monitoring may create public value that exceeds the price a buyer would pay. Markets reveal willingness to pay, not all mission value. The university's job is to account for that value, not to deny price signals. A disciplined internal policy can say: this range is reserved for a named continuity purpose; this range is held for a funded migration; this range is genuinely surplus; this range is unknown and must be investigated.

The fourth response is anti-paternalistic. Even if a university is wasteful, that does not automatically make a registry the proper enforcer. Waste in a public institution is normally handled through governance, audit, funding oversight, public debate, procurement law and leadership accountability. A registry that uses waste rhetoric to restrict transfer or reclaim operationally embedded space crosses from recordkeeping into political administration. The cure may be worse than the disease because it creates uncertainty for every holder.

There is also a regional fairness issue. If university space is leased or sold internationally, critics may say scarce regional resources are leaving Latin America and the Caribbean. The geography is politically salient, but it should not be treated as ownership. An address is a globally unique identifier. Its value comes from global interoperability. A university's mission may be local, national and regional, but its research collaborations are often international. A blanket rule that capital must remain inside a service region risks trapping value where it cannot be best used. It may also reduce the price universities receive, effectively taxing them in the name of regional sentiment.

That does not mean geography is irrelevant. A public university may reasonably prefer transactions that support local connectivity, regional research networks or educational partners. It may design leases that avoid reputationally risky uses. It may prioritise domestic or regional projects when terms are otherwise comparable. Those are holder choices grounded in mission. They should not be converted into registry commands. Voluntary mission preference is different from administrative capital control.

From mandate laundering to campus autonomy

The rhetoric around number resources often turns administrative facts into political claims. A registry serves a region; therefore it is said to speak for a region. A policy process includes participants; therefore it is said to express community will. A database record is necessary for uniqueness; therefore it is treated as a source of authorization. This is mandate laundering: a narrow coordination role is passed through regional and procedural language until it appears to justify broader control.

University legacy space is an attractive object for such laundering because it carries public symbolism. If a registry says it is protecting educational resources, the claim sounds benevolent. If it says it is preventing speculation by universities, it sounds prudent. If it says it is keeping scarce addresses in the region for development, it sounds redistributive. Yet each version risks the same structural error. It treats a service region as if it were a political owner and treats a registry as if it were the guardian of capital allocation.

The better doctrine is holder autonomy under a thin common layer. The holder is not omnipotent. It must respect law, contract, record accuracy, security, dispute status and institutional governance. But the holder is the party whose networks, students, researchers and partners bear the consequence of address decisions. It is closer to the facts than a registry policy room. It pays the migration cost. It answers the help-desk calls. It faces faculty when journal access breaks. It faces medical partners when research gateways fail. It faces auditors if proceeds are misused. That proximity should matter.

Autonomy also disciplines universities. If the registry is not the moral parent, the institution cannot blame registry policy for avoiding hard choices. It must build its own address governance. It must decide whether dormant capacity is reserve or surplus. It must decide how to handle leases. It must decide whether cloud migration requires portable identity. It must document why a sale supports mission. It must face public criticism if the decision is poor. Holder rights and holder responsibility belong together.

Running-code primacy provides the technical limit. The registry may intervene where the common network requires it: duplicate claims, inaccurate control records, fraud, broken contactability, conflicting security assertions, unresolved disputes that must be visible to relying parties. It may not intervene because a campus transaction feels insufficiently academic, because the buyer is outside a preferred geography, because leasing is morally disliked, or because an old policy culture still imagines need-based allocation as the normal state of the world. Once IPv4 is scarce capital, need is revealed partly by price and risk. The registry does not know a university's future better than the university does.

This does not abolish community discussion. Universities, research networks, operators, governments and civil-society groups can all contribute expertise. They can publish model policies, warn about abusive leasing, share migration practices, develop procurement templates, train campus engineers and expose bad transactions. Participation is useful when it produces knowledge. It becomes dangerous when it is inflated into authority over absent holders. A stakeholder is affected; a principal authorizes. The two categories should not be confused.

For LACNIC-region universities, campus autonomy should be practical rather than rhetorical. A recommended model would include a public address inventory, internal classification, legal review of holder authority, risk scoring for dependencies, transaction rules, abuse-response procedures, cloud-portability planning and periodic board-level reporting. National research networks could provide shared tooling and training. Governments could clarify public-asset rules where universities are state institutions. Markets could provide price discovery. The registry could keep records accurate. Each actor would remain in its lane.

The most important lane discipline concerns enforcement. If a university violates procurement law, a court or competent public authority should handle it. If a lessee abuses the network, contracts, providers, law enforcement and security responders should handle it. If a route is hijacked, technical security mechanisms and operational coordination should handle it. The registry should not use the address book as punishment. Essential registry services are too close to network continuity to become disciplinary weapons.

This is not a call for deregulation in the lazy sense. It is a call for correct regulation by the correct institution. Universities operate within legal, academic and public frameworks. Those frameworks can govern asset sales, conflicts of interest, data protection, hospital networks and procurement. A private registry's comparative advantage is neither moral philosophy nor public administration. Its comparative advantage is maintaining a narrow, accurate, auditable uniqueness ledger.

What an NRS-style future would change

The positive alternative is not simply "let universities do whatever they want." It is a more resilient number-resource society built around exit, portability, redundancy and verifiable records. The Number Resource Society model is useful because it starts from the operational problem rather than the institutional self-image of registries. Voluntary arrangements fail when exit is blocked and discretion is centralised. Critical networks survive when records are portable, validation is distributed and no single gatekeeper can convert administrative control into capital control.

For university legacy space, the first benefit would be portability. A campus should be able to move its number-resource records away from a failing, conflicted or unsuitable registry service without losing the resources around which its network identity is built. Portability would not make the campus immune from law or contract. It would make the registry a service provider rather than a hostage point. If service quality declines or discretion expands, the holder has an exit. Exit is the cleanest accountability mechanism in a voluntary order.

The second benefit would be a clearer distinction between record truth and policy preference. A decentralised or interoperable ledger model can focus on deterministic facts: which holder controls which resource, what transfer occurred, what dispute exists, what security assertion has been made, what contact is responsible. Such a ledger does not need to decide whether a university's lease is morally pure. It needs to make the state of control visible and non-conflicting. Policy preferences can exist at the edge, in contracts, institutional rules and market choices, rather than inside the mandatory recognition layer.

The third benefit would be resilience for small and under-resourced institutions. A small Caribbean university or regional technical institute should not depend entirely on the institutional health, politics or procedural culture of one registry. It should have access to tools that make its records portable, auditable and understandable. It should be able to prove control without sending staff into a policy maze. It should be able to transact responsibly without needing insider knowledge. A thinner, more mechanistic record layer reduces the advantage of large institutions that can afford process navigation.

A fourth benefit would be better continuity planning. A portable record layer aligns with cloud migration, provider changes and research collaboration. The university can treat its address identity as independent from any single transit provider, data centre, cloud platform or registry institution. That supports the real operating pattern of modern academic networks: hybrid, collaborative, cross-border and slow to renumber. It also reduces the incentive to cling to old infrastructure merely because changing delivery threatens identity.

An NRS-style model would still need safeguards. It would need mechanisms to prevent duplicate claims, prove control, record disputes, handle fraud and support security metadata. It would need adoption paths that do not break running networks. It would need transitional compatibility with existing records. It would need education for holders that have never treated address space as capital. But those requirements support the model rather than refute it. They describe the work of building a better ledger, not the case for preserving discretionary gatekeeping.

The registry layer cannot do that work for them. It can either help by staying narrow, accurate and portable, or hinder by converting scarcity into permission. The NRS direction is attractive because it lowers the political temperature of the registry question. If the ledger is replaceable and records are portable, fewer disputes become existential. A university can focus on mission and continuity rather than pleading for administrative tolerance.

The old campus record as institutional truth

The economics of LACNIC-region university legacy space are not a side issue in Internet governance. They reveal the transition from an abundant academic Internet to a scarce, capitalised and institutionally dependent one. Universities received and kept address space for reasons unlike commercial ISPs: openness, laboratories, student services, libraries, medical schools, observatories, public extension, research networks and collaboration across borders. Those reasons still matter. They make campus space more than inventory. They do not make it exempt from scarcity.

The decisive fact is that IPv4 scarcity has turned old records into capital while operational history has turned them into identity. A campus block may be worth money in a market. It may also be the address by which publishers, partners, hospitals, instruments, alumni services, student services and foreign collaborators recognise the institution. Treating it only as capital risks breaking continuity. Treating it only as sacred academic heritage risks wasting value. Treating it as regional property risks empowering a gatekeeper that did not create the value and does not bear the migration cost.

The right lens is institutional stewardship by the holder, not registry stewardship over the holder. A university should audit, classify, preserve, lease, sell or migrate according to mission, law and operational reality. It should be transparent enough to maintain public trust. It should not hide behind complexity. It should not sell future capability casually. It should not let departments hoard addresses without purpose. It should not lease identity without abuse controls. It should not mistake cloud migration for the disappearance of network identity.

The registry's job is narrower. It should keep the uniqueness ledger truthful. It should record control, contactability, transfers, disputes and security-relevant facts. It should not decide whether a campus has enough academic virtue to keep a block, whether a lease is politically pleasing, whether a buyer's geography satisfies a regional story, or whether dormant capacity is morally offensive. When a registry expands into those questions, it ceases to be a neutral ledger and becomes a capital gatekeeper. That is precisely what scarce IPv4 cannot afford.

The LACNIC region needs this distinction because its universities are too important and too unequal for blunt rules. Large public universities, small island campuses, medical schools, technical institutes, research networks and field laboratories do not share one balance sheet or one migration path. Some need liquidity. Some need reserves. Some need technical help. Some need legal clarity. All need records that will not be weaponised against them.

The broader future points toward the Number Resource Society approach: exit rights instead of enforced permanence, portability instead of lock-in, redundancy instead of monopoly, and mechanisms instead of moral narratives. That future would not erase universities' public obligations. It would make those obligations easier to meet by removing unnecessary gatekeeper risk from the ledger layer. A university could preserve continuity, release value, move providers and document control without asking a regional institution to bless its mission.

Old campus address records look technical because they are written as numbers. In practice they contain memory: of early research networks, student access, laboratories, public service, institutional autonomy and years of trust accumulated by live services. Scarcity has made that memory valuable. The question now is whether the region will treat value as a reason for clear rights and better ledgers, or as an excuse for thicker permission. Universities should choose clarity. Registries should choose restraint. The ledger should tell the truth, and the campus should remain responsible for what it does with that truth.

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.