Summary

  • IPv4 scarcity can create acquisition cost and commercial value, but it does not turn an address block into freehold property: the operative rights depend on the relevant registry, policy, agreement and registration record.
  • An ISP should manage each prefix through one evidence chain—registry authority, contract, RDAP/WHOIS data, routing authorization, reverse DNS, abuse contacts, reputation, utilization and an IPv6 exit plan—rather than book an unverified price gain.

Scarcity creates a market, not a deed

IPv4 is scarce in a precise sense. IANA says its supply is exhausted, and the five Regional Internet Registries now distribute or record IPv4 under their own post-exhaustion policies. That scarcity can make a usable prefix costly to obtain and valuable to an operator that still needs IPv4 compatibility. It does not answer the legal or policy question of what the holder owns.

The Internet Numbers Registry System exists to keep number resources unique and registration data accurate. RFC 7020 describes an allocation hierarchy rooted at IANA, followed by RIRs, Local Internet Registries and network users. APNIC goes further in its current policy: delegation and registration do not confer ownership, account holders are custodians, and globally unique unicast space is licensed for use rather than owned. Economic value and property title are therefore different claims.

A defensible valuation case identifies the prefix, counterparty, date, registry status, rights transferred and comparable evidence. A finance team may track an acquisition cost, contractual right or disclosed transaction, but it should not infer a balance-sheet windfall from a broker quote or from the size of a legacy allocation alone.

A transfer changes the recognized holder under rules

Transfer policy is regional, not a universal conveyancing code. For specified transfers, ARIN requires the recipient to sign a Registration Services Agreement and says transferred number resources are issued solely for use on an operational network; NRPM section 8.5 also sets minimum block sizes and recipient utilization requirements. APNIC recognizes transfers only within its policy, requires an authentic registered source and, for many recipients, a documented use plan. The RIPE NCC permits permanent and non-permanent transfers, but both must be reflected in the RIPE Database and remain subject to the applicable policy.

Those differences matter in a cross-region deal. A contract between buyer and seller does not, by itself, update the authoritative registry or make the prefix routable. The parties must identify the responsible RIR, confirm that the source is the recognized holder, satisfy any holding period or needs test, complete the registry process and check the receiving network's eligibility. Inter-RIR transfers also depend on the policies of both sides.

The registry record is not the whole operating handover. Contacts, reverse-DNS delegation, Internet Routing Registry entities, Route Origin Authorizations, upstream filters and customer assignments may need coordinated changes. A prefix that has changed commercial hands but still points to stale operational authority can produce outages, invalid routes, abuse complaints or a failed transfer of control.

Leasing separates use from registry responsibility

Commercial arrangements can grant another network temporary use, but calling the payment rent from an appreciating owned asset assumes both ownership and appreciation. The effect depends on the registry region, the account relationship and the technical implementation. RIPE policy expressly accommodates non-permanent transfers; APNIC and ARIN have different transfer and reassignment structures. A private lease should never be presented as if every RIR recognizes the same legal interest.

For the resource holder, retained exposure can include inaccurate registration, abuse escalation, blocklisting, route-origin mistakes, customer reassignment records, reverse DNS and the difficulty of recovering a prefix already embedded in somebody else's services. For the user, exposure can include early termination, reputation inherited from previous traffic, route-filter delays and inability to control registry or RPKI objects directly. Price per address omits those liabilities.

A defensible lease file therefore records the exact prefix, term, permitted use, responsible contacts, routing and ROA authority, abuse response, reputation baseline, return procedure, registry treatment and the party that bears renumbering costs. If those controls are absent, recurring revenue can be an accounting description of unresolved operational risk.

The control surface is an inventory with live evidence

A useful IPv4 register starts with prefixes, not a portfolio valuation. For each block, the operator should record the authoritative RIR and account, source agreement, registered organization, contact status, announced origin ASN, ROAs, IRR objects, reverse-DNS delegation, downstream assignments, utilization method, services dependent on the block and any transfer or lease restriction. Ownership language should match the governing agreement rather than a generic asset label.

RPKI is especially easy to misunderstand. ARIN describes it as cryptographically verifiable statements linking number resources to holders and allowing them to attest which ASNs may originate their prefixes. A valid ROA documents an origin authorization; it does not prove market price, beneficial ownership or clean reputation. RDAP/WHOIS, RPKI, BGP observation and commercial records answer different questions and should not be substituted for one another.

Utilization also needs a named method. Address-management systems can show assignments, DHCP pools and customer records; route collectors show announcements; flow or subscriber systems show activity. None alone establishes that every address is productively used. A utilization percentage without a population, observation date, data source and method is not decision-grade evidence.

IPv6 changes the investment decision

IPv4 remains operationally important because users, services and counterparties still require it. Carrier-grade NAT and address sharing can extend a pool, but they add capacity planning, attribution, logging, support and failure modes. Acquiring or temporarily using more IPv4 can be rational when it protects a defined service or avoids a more expensive near-term constraint.

That is not a case for assuming perpetual appreciation. APNIC calls IPv6 the long-term solution and says there is not enough unused IPv4 for networks to grow indefinitely. Every IPv4 proposal should therefore be compared with IPv6 deployment, dual-stack design, address sharing, renumbering, product changes and the cost of supporting both protocols. The right measure is the total cost of delivering reachable service, not a forecast price for an address detached from its operating context.

For boards and finance teams, the conclusion is deliberately less dramatic than 'the asset era has begun.' IPv4 is scarce infrastructure with commercial consequences. Its value is conditional on policy-compliant registration, usable routing authority, clean operational history and a service that still needs it. Manage those conditions; do not confuse them with a land title.

A decision file for every acquisition or lease

  • Name the RIR, current recognized holder, agreement and exact registry process.
  • Verify eligibility, holding periods, needs tests and inter-RIR compatibility before signing.
  • Record RDAP/WHOIS, RPKI/ROAs, IRR, reverse DNS, origin ASN and abuse contacts separately.
  • Measure utilization with a stated dataset and date; do not equate an unannounced address with an unused one.
  • Check routing and abuse reputation before valuation and again before cutover.
  • Model renumbering, support, CGN, dual-stack and IPv6 costs alongside the transaction price.
  • Treat broker prices and private lease terms as market signals unless the underlying transaction is disclosed and comparable.
  • Set a dated IPv6 dependency-reduction target so new IPv4 capacity does not become a permanent strategy by default.

Sources