IPv4 leasing ISP operational model explained

IPv4 leasing ISP is an operational model where an Internet Service Provider uses contractually leased IPv4 address blocks instead of permanently owned address space. The ISP announces and assigns these addresses to customers while the original holder remains registered in the RIR database. This approach allows ISPs to deliver public IPv4 connectivity, avoid CGNAT in selected services, and scale address capacity under current IPv4 scarcity conditions.

What is IPv4 leasing ISP?

IPv4 leasing ISP refers to the temporary use of IPv4 address space by an ISP under a formal lease agreement with an address holder. The leased prefixes remain registered to the owner in the RIR, while routing and usage rights are delegated to the ISP for a defined period.

Key properties:

• No transfer of IPv4 ownership

• Time-bound contractual usage

• Routing authorization via LOA

• Registry objects aligned with ISP operations

• Compatible with standard ISP provisioning workflows

How IPv4 leasing works for ISPs

From an operational perspective, IPv4 leasing ISP follows established routing and registry processes:

• The address holder authorizes the ISP ASN using a Letter of Authorization

• Route and route6 objects are created or updated accordingly

• RPKI ROAs are configured to match the announcing ASN

• The ISP announces the prefix via BGP from its network

• IPv4 addresses are assigned to subscribers, services, or infrastructure

Leased space is routed and filtered in the same way as owned space, provided registry and RPKI data are consistent.

Comparing the traditional IPv4 ownership model with the modern leasing approach: Lowering entry barriers for global internet services.

Common use cases

IPv4 leasing ISP models are commonly applied in the following scenarios:

• ISPs offering public IPv4 to business or premium subscribers

• ISPs migrating customers away from CGNAT where required

• Regional ISPs expanding faster than legacy IPv4 allocations allow

• Access networks supporting services that require inbound IPv4 reachability

• ISPs and network operators separating address supply from access infrastructure

These use cases often depend on clean address history and predictable geolocation.

Explained for network engineers

At the infrastructure level, IPv4 leasing ISP introduces policy and lifecycle considerations rather than data plane changes:

• Prefix sizing must respect minimum routable blocks, typically /24

• ROA max-length should be explicitly defined to avoid invalid announcements

• BGP announcements must strictly match authorized ASNs

• Abuse handling and customer attribution remain the ISP’s responsibility

• Lease expiration requires operational planning to renumber or renew

From a routing perspective, leased IPv4 behaves identically to owned IPv4. Differences exist in registry authority, contractual control, and long-term planning.

For infrastructure teams:

Clean IPv4 blocks with full RPKI, rDNS, and LOA support are commonly used in ISP and hosting environments.

Summary

• IPv4 leasing ISP enables public IPv4 delivery without ownership transfer

• The model relies on standard BGP, LOA, and RPKI mechanisms

• ISPs use it to avoid CGNAT for specific services or customers

• Operational behavior matches owned IPv4 at the network level

• Registry alignment and lease lifecycle management are critical