What AI Companies Should Know About IP Address Governance
AI companies depend on IP addresses, ASNs and routing security. Protect network identity, continuity and the option to replace a failing administrator.
The team’s articles
26 articles
AI companies depend on IP addresses, ASNs and routing security. Protect network identity, continuity and the option to replace a failing administrator.
How IP transfers can preserve accurate responsibility records without turning a technical registry into a commercial permission system.
An address change can disrupt years of working relationships. Why network continuity matters, and why essential coordination must remain accountable and replaceable.
Network identity can bind customers, routing, security and revenue to records controlled outside the company. Boards should ask who can change that identity, who bears the risk and whether the administrator can be replaced.
Networks need unique identifiers and reliable records. Lu Heng's Notes ask how to preserve those functions without giving a permanent administrator power over participants.
Follow a registry proposal through to its practical effect on your network, and understand Lu Heng's case for coordination that does not depend on one administrator.
Why a cross-border IPv4 transaction depends on more than a price: separate the agreement, registry record and working network, then examine the points of dependence.
See how address agreements, registry records and working routes differ, and why Lu Heng argues that keeping a record should not mean owning the network.
Lu Heng's running-code betrayal argument, explained through a working network: why procedure must serve continuity, and what a replacement needs to preserve.
An Internet registry coordinates numbers. Does that let it govern networks? Lu Heng's critique and the case for an orderly transition, explained.
Follow a changed record through route filters and RPKI to see why access can fail, and why Lu Heng argues for continuity and a real path to independence.
A registry does not carry every packet, but its records can still shape whether networks are recognised and can keep operating. This guide separates records, routing, authority and the exit a resilient system needs.