Heng Lu publishes framework for IPv4 governance

Heng Lu on July 29 published a policy framework for IPv4 and Internet number resource governance that argues for thinner registry control, stronger continuity protections and resource-level portability. The proposal is aimed at keeping networks running even when registry operations, disputes or institutional failures threaten service.

Why it matters: - IPv4 remains operationally critical for customer connectivity, application delivery, security controls and business continuity, even as IPv6 deployment continues. - Heng Lu argues that Internet number coordination should protect running networks with the minimum technical controls needed for independent systems to interoperate. - The framework is designed to reduce disruption when records are disputed, operators change, or registry governance becomes unstable.

What happened: - Heng Lu published a policy framework for IPv4 and Internet number resource governance on July 29, 2026. - The framework consolidates principles developed across heng.lu notes, including Running-Code Primacy, thin coordination, registry continuity, resource-level portability and institutional accountability. - The complete framework is available at heng.lu.

The details: - The framework says core registry functions should stay limited to objective and verifiable technical requirements. - Those functions include preserving number-resource uniqueness, verifying control, maintaining accurate and auditable records, supporting reverse DNS and routing-security services, recording transfers and disputes, and protecting continuity during operational or governance difficulties. - Lawful commercial decisions involving leasing, financing, customer location, transaction pricing and deployment strategy should stay outside mandatory registry control unless they directly affect uniqueness, security integrity or registry accuracy. - The framework says a registry may record, coordinate and protect uniqueness, but should not decide whether a lawful business model or deployment strategy should exist. - Running-Code Primacy puts continuity of operational networks ahead of institutional procedure. - Under that principle, number-resource rules should be judged by whether they protect uniqueness, accurate records, proof of control, security integrity or network continuity. - Registry records should reflect operational, legal and market reality rather than serve as the sole source that creates that reality. - When disputes arise, the affected record or resource should be isolated where possible, and the last verified operational state should remain in place while the dispute is reviewed. - The framework calls for resource-level portability, meaning the verified registry state and administration of a specific number resource should be able to move to a qualified successor mechanism if the existing operator cannot maintain essential services. - That portability is separate from changing a company’s legal identity, membership status, place of incorporation or regional affiliation. - The proposal covers continuity for an individual number resource, including its registration record, proof of control and relevant security information. - Essential registry records and services should be versioned, independently auditable, securely backed up and supported by tested continuity arrangements. - The framework also supports separating registry administration from enforcement and dispute resolution. - The registry operator may preserve evidence, identify competing claims, maintain audit trails and temporarily pause incompatible record changes. - Final decisions affecting operational continuity should follow a clearly defined and independent review process. - Essential registry and security services should stay available unless a narrowly defined technical condition or binding decision requires otherwise. - Institutional responsibility should remain proportionate to institutional power, especially when decisions can delay transfers, change registry recognition or interrupt essential services. - The framework says such decisions should use objective criteria, documented reasons, defined service periods, transparent review procedures and accountability.

Between the lines: - The framework is an argument for smaller, more auditable registry authority and more protection for existing networks during disputes. - It also signals skepticism toward registry-level control over lawful commercial activity that does not affect technical integrity. - The proposed model favors continuity and reversibility over centralized enforcement power.

What's next: - Heng Lu says the publication is intended to support continued discussion about a thinner, more resilient, portable and accountable system for Internet number coordination. - The framework may shape further debate over how IPv4 resources are governed as networks continue to rely on them.

The bottom line: - Heng Lu wants Internet number governance to do less, but do it more reliably: protect uniqueness, preserve continuity and keep running networks online.