When the Water Company Says Your House Belongs to It

Imagine your water company tells you this:

Because I am the only water provider in your area, I represent you.
Because I represent you, you owe me loyalty.
Because you owe me loyalty, you are not allowed to change provider.
Because you are not allowed to change provider, your house effectively belongs to me.
And because your house depends on my pipes, I may threaten you, overcharge you, extract from you, and raise prices without limit.

Any normal person would say the company is insane.

More precisely, the company is not insane.
It is doing something worse.

It is converting a utility function into a sovereignty claim.

A water company is a service provider.
It is not the owner of the house.
It is not the representative of the resident.
It is not the government of the district.
It is not the moral owner of water.
It does not acquire political authority merely because the resident has no alternative pipe.

Exclusivity is not ownership.
A service region is not a territory.
A billing relationship is not allegiance.
A pipe connection is not title.
The ability to cut off service is not a lawful right to rule.

If a water company is the only provider, the conclusion should run in the opposite direction.
Its discretion should be narrower.
Its duties should be higher.
Its pricing should be constrained.
Its records should be auditable.
Its conduct should be subject to stronger limits.
And the system should create a path for substitution, emergency service, or portability.

Monopoly does not create sovereignty.
Monopoly creates duty.

That is the basic absurdity of the AFRINIC lock-in policy.

AFRINIC’s problem is not that it performs a registry function.
A registry function is necessary.
Internet number resources require uniqueness.
IP addresses and ASNs require accurate records.
Networks must know that the same number resource has not been registered twice.
The coordination layer must preserve operational continuity.

Those are technical functions.

But AFRINIC converts that narrow technical function into something else.
It treats regional registry administration as if it were regional ownership.
It treats database authority as if it were asset control.
It treats membership as if it were allegiance.
It treats policy interpretation as if it were a right to decide the fate of running networks.

It says, in effect:

Because you are in my region, you must use me.
Because you must use me, you cannot leave.
Because you cannot leave, I may define the conditions under which your resources survive.
Because I define those conditions, I may judge your business model, your customers, your geography, your leasing, your transfers, and your commercial use.
And if you disagree, I may threaten deregistration.

This is the water company saying the house belongs to it.

A registry is not the owner of number resources.
An RIR is not a state.
A service region is not a people.
A policy room is not a legislature.
A membership contract is not political allegiance.
A database record is not a confiscation instrument.

The central danger is not merely that AFRINIC failed.

Institutions fail.
Registries fail.
Boards fail.
Elections fail.
Procedures fail.
Private companies fail.

The central danger is that when AFRINIC fails, abuses power, enters conflict, becomes unreliable, or loses trust, resource holders have no real exit.

That is lock-in.

And this point must be stated precisely.

This is not member transfer.

I am not talking about a member moving from AFRINIC to ARIN, RIPE NCC, APNIC, or another RIR.
I am not talking about a company moving its legal seat from one region to another.
I am not talking about membership migration.
I am not talking about who attends which meeting, pays which fee, or belongs to which regional corporate structure.

That is not the issue.

The issue is whether a specific number resource can move its registry administration, registration record, proof of control, and operational continuity away from a failed, abusive, conflicted, or untrusted registry.

This is resource-level portability.
Not member-level transfer.

A member is a contractual relationship.
A number resource is an operational asset.

A member is an accounting unit.
A number resource is infrastructure.

A member may remain in one region.
A particular number resource still needs a failover path.

A member may continue to exist under a registry’s corporate membership rules.
A particular IP block should not be permanently trapped inside that registry’s political, legal, or operational failure.

The house does not belong to the water company merely because the water meter is registered in its system.

The network does not belong to AFRINIC merely because the number resource record sits in AFRINIC’s database.

The registry record describes reality.
It does not own reality.

Once IPv4 became a real asset, lock-in stopped being an administrative inconvenience.
It became asset control.

It suppresses liquidity.
It destroys financing certainty.
It chills leasing markets.
It weakens transferability.
It turns registry discretion into commercial leverage.
It allows a registry to control value without bearing the loss if that value is destroyed.

That is the most dangerous form of power: control without liability.

AFRINIC can say:

I do not bear your business loss.
I do not bear your customer loss.
I do not bear your financing loss.
I do not bear your routing disruption.
I do not bear the destruction of your asset value.
But I retain the power to threaten the registry status of your resources.

That is not coordination.
That is hostage power.

If a water company could raise prices without limit, threaten disconnection, prevent substitution, deny portability, and still disclaim all liability for the damage it causes, no one would call that public service.
They would call it infrastructure capture.

AFRINIC’s lock-in policy is the same structure applied to Internet number resources.

It turns region into cage.
It turns registry record into leash.
It turns membership into obedience.
It turns policy into confiscation risk.
It turns technical coordination into monopoly extraction.

The registry’s proper role is narrow.

It may maintain uniqueness.
It may record who holds which number resource.
It may require proof of control.
It may prevent duplicate registration.
It may correct fraud in registration.
It may preserve technical integrity.
It may maintain minimal security assertions.

But it may not own the commercial destiny of the resource holder.

It may not decide that leasing is morally suspect.
It may not turn customer geography into enforcement authority.
It may not convert regional history into asset control.
It may not use its database to suppress liquidity.
It may not treat operationally embedded resources as revocable privileges merely because it dislikes the holder’s business model.

A registry is a clerk of uniqueness.
It is not Olympus.

This is why portability is not optional.
It is the minimum hard right.

Without portability, every RIR is a lock-in point.
Without portability, every registry failure becomes an operator crisis.
Without portability, every resource holder is exposed to institutional fantasy.
Without portability, every valuable IP block remains hostage to a private-law entity that claims public-infrastructure importance while avoiding public-law accountability.
Without portability, the Internet’s addressing system is not a coordination system.
It is a cage.

Running-Code Primacy gives the correct order.

Running networks come first.
Uniqueness comes first.
Proof of control comes first.
Operational continuity comes first.
Asset continuity comes first.
Failover comes first.
Replacement paths come first.

Registry ritual does not come first.
Regional mythology does not come first.
Community slogans do not come first.
Membership loyalty does not come first.
Institutional survival does not come first.

If AFRINIC can provide a narrow, accurate, reliable, low-cost registry service, it may continue to provide that service.

If it cannot, specific number resources must be able to leave its control.

Not the member.
The resource.

Not the company’s identity.
The registration administration.

Not the legal seat.
The operational record.

Not the region.
The proof of control.

That is the difference between coordination and captivity.

This is not an attack on the registry function.
It is a defense of the registry function from registry capture.

A system that cannot tolerate exit is not a coordination system.
It is a monopoly.

A registry that cannot be replaced is not a service provider.
It is a sovereignty claim.

And an RIR that uses its monopoly over number-resource records to demand loyalty is exactly like the water company telling residents that their houses belong to it.

Normal society would reject that water company.

The Internet should reject the same logic when it appears in registry form.

The solution is not to make the water company more polite.
The solution is not to ask it to write better slogans.
The solution is not to let it call the neighborhood a community and the pipe map a constitution.

The solution is to deny the sovereignty claim.

AFRINIC does not own the house.
AFRINIC does not own the network.
AFRINIC does not own the resource.
AFRINIC maintains a record.

And when the recordkeeper becomes the risk, the record must be portable.