团队文章权力与治理

Mandate laundering: when a registry claims political power

An Internet registry coordinates numbers. Does that let it govern networks? Lu Heng's critique and the case for an orderly transition, explained.

目录

Imagine a company that keeps the address book for a city. Keeping entries accurate is a useful service. Now imagine that company saying its role gives it the right to decide who may operate a business anywhere in the city. The work it performs has not changed, but the authority it claims has grown enormously.

That gap is the starting point for mandate laundering. In Note 62, Lu Heng uses the term to describe a limited coordinating role being presented as a much broader political mandate. For Internet networks, the question is direct: does maintaining the record give an administrator the right to rule the people who depend on it?

A small registry desk casts the shadow of a gate around a much larger city.
Mandate laundering is the jump from maintaining a shared record to claiming authority over everyone who depends on it.

Start with the job: keeping Internet numbers distinct

An IP address helps other networks find where to send traffic. An autonomous system number, or ASN, identifies a network that exchanges routing information with other networks. These identifiers need coordination so that incompatible claims to the same number do not undermine communication.

IANA describes its role as global coordination of these numbering systems. Regional Internet Registries, usually called RIRs, sit within the allocation and registration structure. Operators build and run the networks that use those numbers.

The distinction matters. A registry has an important job. Lu Heng's argument asks where that job ends, who authorized any wider power, and how a working network can remain safe when its administrator fails or overreaches.

What is being “laundered”?

A mandate is an authorization to do a particular job on someone's behalf. The word laundering describes a change in how power is presented: an administrative role goes through the language of policy, consensus, community and region, and comes out looking like authority to govern a much larger public.

Consider three different statements:

  1. We maintain the registry. This describes a function.
  2. Participants in our process agreed on a policy. This describes a decision and its participants.
  3. Therefore, we speak for everyone in the region. This claims representation of people far beyond those participants.

The third statement does not follow automatically from the first two. That unsupported jump is the mechanism the concept is meant to expose. A bigger meeting or a longer procedure does not, by itself, answer who granted the additional authority.

Why “community” needs a precise meaning

Community can mean the people on a mailing list, members who pay fees, the operators using a service, or everyone living within a region. Those groups overlap, but they are not the same group.

In Note 62, Lu Heng challenges the way institutional language moves between these meanings. Agreement among participants can be made to sound like consent from an entire population. A geographic service area can be made to sound like a political constituency.

His criticism reaches beyond poor communication. He argues that procedural participation is being used to support powers for which the claimed public mandate has not been established. Making the procedure easier to read would not settle that question.

Why an address holder should care

Picture an operator running a service for customers. The operator pays for equipment, maintains connections and answers when the service fails. Its public addresses may also appear in customers' firewall rules, partner systems and monitoring tools.

Now consider a disputed change to the records on which other parties rely. Changing a database entry does not physically turn every router off. But it can affect the evidence that providers and other systems use to recognize the operator's use of those addresses. The consequences depend on the change and on those systems' decisions.

The operator therefore needs more than a promise that an internal process was followed. It needs accurate records, a way to contest mistakes, and a workable continuity plan. Lu Heng's concern is the imbalance between an administrator's power over recognition and the costs borne by the networks and customers downstream.

The guide to proof of control explains why a registry entry, routing authorization and commercial relationship answer different questions. Treating them as one all-purpose permission makes that imbalance harder to see.

Why another consultation is not the whole answer

Consultation can help people identify mistakes and disagree in public. It cannot supply every kind of authority simply because it took place. A process can document a decision without establishing a right to make that decision for everyone affected.

Note 62 consequently calls for a transition beyond the present institutional structure. Its proposed direction is to narrow discretion, separate registration from territorial and political claims, protect continuity, and make review and replacement possible outside the incumbent's own process.

This is a structural argument. It asks whether people can replace the coordinator while preserving the useful coordination. If the only way to leave is to damage a running network, the formal ability to object offers little practical independence.

What should stay, and what should change?

Networks still need unique numbers and records they can trust. Lu Heng's proposal keeps those shared functions while making the institution that performs them replaceable. A network should be able to leave a failing coordinator and keep working.

Note 72, the Bill of Rights of Uniqueness Coordination, sets out the requirements: keep records accurate, keep running networks operating, make exit possible, and limit the shared layer to the functions networks actually need. Building that exit path is part of the proposed transition.

The practical test is whether a change of institution can preserve the information and relationships a network needs to keep operating. Registry-state export addresses one part of that problem: carrying verifiable records forward. Exporting a file alone does not establish a trusted successor or guarantee that other networks will accept it.

How to begin while the network is still running

Note 62 connects this transition to three kinds of work in Lu Heng's wider enterprise:

  • Make the problem visible. BTW.Media's role in the argument is to make institutional decisions, incentives and consequences understandable. People cannot challenge a power relationship they cannot see.
  • Keep operators able to function. LARUS represents the commercial continuity work: operators need practical support while the wider structure changes.
  • Organize people who would otherwise stand alone. NRS brings the member-side protection and representation described in the Note. An isolated operator has less room to challenge an institution on which it depends.

These are means of preparing a transition. The intended destination is a shared coordination system with less discretion, more choice and no permanent institutional gatekeeper. Each step should make it easier for networks to operate independently.

Why the work has to begin before a crisis

A working replacement path takes preparation. Operators need to know which records matter, who relies on them, how their accuracy can be checked, and how disagreements will be resolved. Waiting until the current institution is unavailable leaves the hardest coordination work for the worst possible moment.

Note 62 places operators, governments and the technical community within that transition. Their responsibilities differ: operators carry the service and customer burden; governments face public consequences; technical participants help determine whether an alternative can actually work. They need a shared transition effort that turns those different responsibilities into practical capacity.

Urgency follows from this lead time. The goal is to build the capacity to change the system while the network can still depend on continuity.

A useful question to carry into the next discussion

When an institution says “the community decided,” ask: which people, deciding what, under whose authorization, with what consequences for those outside the room? Then ask what happens if the decision is wrong or the institution cannot continue.

Those questions turn an abstract debate about governance into a visible relationship between service, authority and responsibility. They also reveal why an administrator's usefulness is not sufficient proof of every power it claims.

Read Note 62: Mandate Laundering for Lu Heng's full argument and transition architecture. This article provides a starting point; the Note develops the institutional critique and explains how his wider work connects to the proposed transition.