IPv4 Continuity Is More Than Owning an Address Block

Ownership answers only one question

An address block can be bought, leased or assigned. That commercial or administrative relationship matters, but it does not tell the whole continuity story. A business also needs other networks to recognise the record, routers to accept the announcement, customers to trust the source and operators to know how to change the configuration safely.

The useful question is not simply, “Do we own these addresses?” It is, “What must remain true for this network identity to keep working, and who can change each part?”

Five dependencies sit behind a stable network identity

Continuity has at least five layers: a verifiable resource record; routing acceptance; security assertions and reputation; provider and operational relationships; and a path to correct or replace the administrator when conditions change.

A failure in any one layer can make a block commercially difficult to use even if the ownership document has not changed. The address can still belong to the same party while mail reputation falls, filters reject the route, contacts become unreachable or a provider cannot complete a necessary update.

• The record: what do other networks see, and can they verify it?
• The route: who announces the prefix, and which policies accept it?
• The reputation: what history follows the addresses across providers and customers?
• The operation: who can keep the service reachable during a change?
• The exit: can another coordinator take over without destroying the identity?

Scarcity makes continuity valuable; it does not make every claim true

IPv4 scarcity increases the value of an address that other systems already know and trust. Note 29 argues that scarcity is also a narrative: treating IPv6 as an automatic escape or IPv4 as a simple commodity hides the institutional and economic choices underneath.

The conclusion is not that IPv4 should be frozen or that IPv6 is irrelevant. It is that a business should price the actual continuity it needs. Buying a block without understanding the record, routing and governance dependencies can purchase an asset while leaving the operating risk untouched.

Leasing can expose the real continuity question

Leasing and buying are often presented as opposites. The more useful comparison is which party performs which operational work, what evidence is available, how long the arrangement lasts and how the network exits if the provider fails. A lease can be short-term and still require careful continuity controls; ownership can be long-term and still depend on an administrator outside the company.

Note 66 frames the broker question as a registry-risk question. The commercial transaction is only one part of the arrangement. The operator must understand who maintains the record, who can make changes and what happens when the relationship ends.

A better definition of control

Control is not the ability to make one change inside one account. It is the ability to keep the network identity usable while the surrounding institutions, providers and records change. That requires evidence other networks can verify and a process that does not turn a coordinator into a permanent gatekeeper.

Note 72 describes the principle directly: preserve uniqueness and accurate records, but make the administrator replaceable. Portability is what turns an abstract right into continuity that an operator can use.

Audit the identity before you need it

List the address blocks that support customer access, mail, security allow-lists and critical services. For each one, identify its record source, route origin, security assertions, provider, reputation dependencies and replacement path. Mark the layer where your organisation has no independent evidence or no practical alternative.

That list gives a more honest answer than ownership alone. It tells you which part of your network identity is an asset, which part is a dependency and which part needs a change plan before an outage or dispute forces the issue.