Why IP Addresses Became Valuable — and Why Ownership Is Not Control

Imagine running a network that customers, partners and security systems have learned to recognise by its IPv4 addresses. The addresses are no longer just numbers in an engineer’s diagram: they appear in contracts, allowlists, routing policy, monitoring systems and business plans. If you try to move them, a question follows immediately: what exactly is valuable, and who has the power to decide what remains valid?

IPv4 scarcity created a market around address space. That market is real. But a price does not create ownership, a registry record does not create political authority, and a transfer does not automatically preserve a network’s identity. Those are separate questions, and treating them as one is how infrastructure risk gets hidden behind financial language.

Scarcity made a technical resource economically visible

IPv4 uses a finite 32-bit address space. Early allocation assumed that addresses would remain easy to obtain; the growth of networks made that assumption untenable. Once the central and regional pools became constrained, organisations with unused or transferable address space could offer something that new networks still needed.

That is why transfer markets, leasing arrangements and specialist intermediaries appeared. A network may pay for access to a range because it needs IPv4 reachability, because changing addresses would break customer relationships, or because an existing block is easier to integrate than a new one. The economic value comes from operational use under scarcity. It is not proof that the number has become an ordinary financial asset.

The market question is therefore useful but incomplete: what can an address block help a network keep doing? The more important governance question is: who can change the record that lets other networks recognise it?

Three different things are being called ownership

When people say that a company “owns” an IP block, they may be referring to three different relationships:

• Use: the organisation operates the addresses in its network and depends on them for services.
• Record: a registry or another coordination service records which organisation is entitled to use or request changes for the resource.
• Recognition: routers, filters, security systems and counterparties accept the organisation’s announcements and continue to associate the addresses with its network.

A sale, lease or transfer can change one relationship without securing the others. A contract can allocate commercial responsibilities while the registry record remains unchanged. A record can be accurate while routes are still unauthorised or filtered. A route can work today while the operator has no practical way to replace the service that maintains the record.

This is why the old phrase “IP asset” needs precision. It can describe an economically important infrastructure resource. It cannot, by itself, answer who may alter the record, who carries the operational risk, or whether the holder can leave one administrator for another.

Why a price cannot solve a governance problem

Markets are good at revealing that people value a scarce resource. They do not automatically provide a durable identity, a correct registry, a valid route or a fair process for resolving conflicting claims.

In practice, a network may rely on registration data, route-origin authorisations, reverse DNS, provider relationships and customer allowlists at the same time. Changing one layer can create work or failure in the others. The organisation paying for the resource bears the consequences, even when it did not design the rules that determine whether the resource remains recognised.

That distinction also matters when a broker or provider is involved. The transaction may be commercial, but the continuity question is structural: who keeps the record, who can approve a change, what evidence proves the holder’s position, and what happens when the relationship ends?

The existing commercial discussion of IPv4 as strategic infrastructure is one useful view of demand. It should sit beside, rather than replace, the technical question of how a network remains independently verifiable.

IPv6 changes supply, not the question of power

IPv6 provides a much larger address space and is essential to the Internet’s long-term growth. It does not instantly replace every IPv4 dependency. Networks, applications, customers and security systems adopt the two protocols at different speeds.

More importantly, adding addresses does not decide who is entitled to maintain the records underneath them. IPv6 can reduce scarcity while leaving the institutional design of registration untouched. Abundance and decentralisation are related infrastructure choices, but they are not the same choice.

For a basic explanation of the addressing layer, see the IPv4 introduction. The economic story begins there, but it should not end there.

The alternative: preserve the record and make the administrator replaceable

Lu Heng’s argument starts from a sharper requirement than “make IP addresses more valuable”. A network needs accurate records, proof that changes are authorised and a way for other networks to verify those facts. It should not have to surrender its identity because one organisation controls the only accepted record.

A more resilient coordination system would separate the essential function from the permanent administrator:

• the holder can present independently verifiable evidence of its resource and authorised changes;
• participants can check the same history without trusting one office to rewrite it;
• routing and registration can change together through a tested transition;
• an operator can replace a service provider or coordinator without rebuilding the network’s identity.

This is not a call to discard records or to move control to a different central institution. It is a demand that coordination remain useful while authority stays limited, accountable and replaceable. Note 51 examines why a registry model becomes unstable once IPv4 is treated as a real asset, and Note 72 sets out boundaries for protecting uniqueness without turning coordination into ownership.

Why the transition cannot wait for a dispute

Every new dependency makes a later change more expensive. Customer allowlists, route policies, monitoring, contracts and reputation systems all accumulate around an address range. If a registry, provider or political process fails, the operator may discover that its commercial “asset” cannot be carried to a replacement service without a simultaneous agreement from everyone who relies on it.

The time to identify those dependencies is while the network is working. Operators need to know which records matter, how route authorisations are checked, which parties must update their systems and what evidence would survive a change of coordinator. Waiting until an institution is contested turns a design problem into an outage problem.

IPv4’s market value is therefore only the visible surface of a deeper issue. The real question is whether the Internet can preserve useful, verifiable identity without making every network permanently answerable to one administrator. That is why the discussion belongs in the history of Internet governance, not only in an asset spreadsheet.

To see the wider public stakes, continue with the question of who gets a say in Internet governance, then follow Lu Heng’s original arguments through Note 45 on the narrative of IPv4 scarcity.