ARIN's Public Policy Mailing List looks modest if it is judged by its surface form. It is an email list. It is public. It is archived. Anyone willing to follow the rules of conduct can subscribe and speak. ARIN's own mailing-list page describes the Public Policy Mailing List, or PPML, as open to the general public and as a forum for ideas and issues around existing and proposed ARIN policies. The same page says PPML discussion is an intrinsic part of ARIN's Policy Development Process. As a factual description, that is useful. As an account of power, it is incomplete.
A policy mailing list is not merely a comment channel. It is a device for turning attention into authority. A problem is named. A proposed text is submitted. A small number of people speak early. Others add support, object, suggest language, question scope, ask staff questions, revive old arguments, or fall silent. The Advisory Council decides whether the text is clear, in scope, and suitable to move through the process. Staff and legal review changes the perceived range of feasible outcomes. Public meetings and consultations add formal visibility. Last call narrows the opportunity for new objections. The Board reviews the process and decides whether to adopt. Staff then converts the adopted words into operational practice. What begins as argument in an archive can become the rule that determines whether scarce IPv4 capacity moves, under what conditions, and at whose cost.
That is the political economy of PPML. The list allocates scarce procedural capacity. It rewards those who can draft, monitor, reply, cite precedent, understand policy text, attend meetings, and translate business risk into the language of number-resource stewardship. It raises the cost of dissent for parties that are affected but absent. It makes agenda control valuable because the first problem statement frames the range of legitimate answers. It makes coalition formation visible because the record shows who supported, opposed, qualified, or ignored a proposal. It gives the institution a way to say that a result was developed in public rather than imposed privately. Those features can improve legitimacy. They can also turn a narrow participation record into a broader claim of mandate.
ARIN is a useful test case precisely because it is orderly. It is not the most dramatic registry. It has not supplied the institutional theatre of a court-supervised registry crisis. It operates in a region with sophisticated network operators, hyperscale platforms, universities, cable systems, access networks, address-rich legacy holders, brokers, lawyers, enterprise buyers, public institutions, and capital-market actors that can price IPv4 risk with unusual discipline. Its public materials are detailed. Its policy process is documented. Its policy manual is public. Its elections and membership categories are described on its website. Its legacy-resource materials draw visible lines between basic record services and agreement-linked routing services. If the mailing-list model can remain legitimate after IPv4 exhaustion, ARIN is one of the places where that legitimacy should be visible. If the model contains structural weaknesses, ARIN reveals them in a quiet and therefore analytically useful way.
The argument is not that ARIN's mailing list is false theatre. The argument is that openness is not the same as representativeness, and a documented process is not the same as an economic mandate. After exhaustion, IPv4 policy is no longer only a technical rationing exercise. It is a body of rules governing an asset market whose settlement layer still runs through a nonprofit registry. PPML therefore deserves to be read as an institution of agenda control, coalition formation, dissent-cost allocation, and capital-market governance. Its legitimacy depends not only on whether the door is open, but on whether the process can distinguish ledger protection from gatekeeping, active-community support from affected-economy consent, and registry continuity from institutional self-protection.
Exhaustion changed what procedure means
The same procedure has a different meaning before and after IPv4 exhaustion. In the allocation era, policy debates were mainly about rationing from an administratively managed pool. The registry had to decide who qualified for addresses, how much documentation was enough, what utilization threshold was fair, how to conserve scarce space, how to preserve aggregation, and how to support growth. These were difficult questions, but the institutional setting was comparatively simple. The registry was distributing a scarce technical resource from a remaining stock.
After exhaustion, the same process began to operate over a different economy. ARIN's IPv4 Addressing Options page states that its free pool of IPv4 address space was depleted on 24 September 2015. The page points applicants toward the waiting list, specified-recipient transfers, and IPv6 adoption. That date marks more than an administrative milestone. It changed the role of the policy process. ARIN no longer sits mainly in front of an issuance system with an address pool behind it. It sits above a market environment in which already-issued IPv4 blocks support live networks, corporate acquisitions, leasing structures, customer contracts, security services, diligence processes, financing questions, and balance-sheet assumptions.
In that world, policy is not only allocation policy. It is market infrastructure. ARIN's transfer guide describes transfers due to mergers, acquisitions, and reorganizations; transfers to specified recipients within the ARIN region; and inter-RIR transfers to specified recipients. The Number Resource Policy Manual says number resources are nontransferable unless ARIN has expressly approved a transfer request in writing, and that ARIN is tasked with making prudent decisions on whether to approve transfers. The same section says number resources are not sold under ARIN administration, but assigned for exclusive use under policy and agreement terms.
Those statements are administrative and legal positions. They are also economic facts. If a buyer and seller agree on a price but cannot close a recognized transfer without registry approval, the registry is part of the market's settlement system. If a recipient must document operational need, sign an agreement, and satisfy policy before recognition, policy constrains liquidity. If inter-RIR transfer depends on reciprocal, compatible, needs-based rules, policy shapes cross-border address flows. If waiting-list rules prevent recent transfer sources from reapplying for a defined period, policy affects arbitrage, small-network access, transaction timing, and the value of residual returned space. These are not incidental consequences. They are the economics of the rule.
ARIN may have good reasons for many of these frictions. A registry cannot safely recognize forged transfers. It cannot ignore live disputes over holder authority. It cannot treat dissolved entities, stale contacts, or undocumented acquisitions as if records were self-validating. It may have legitimate policy concerns about speculation, warehousing, routing integrity, and the continuing idea that number resources are assigned for use rather than owned as ordinary property. The point is not that market friction is inherently illegitimate. The point is that post-exhaustion friction has to be named for what it is. Some friction protects the ledger. Some friction controls market conduct. A mature process should not hide the second inside the first.
This is why a mailing list that once looked like a technical coordination mechanism must now be analysed as a political economy. The relevant question is not only whether discussion was open. It is who could afford to participate usefully, who could frame the problem, who could keep a coalition together, who could object in time, which affected interests stayed silent for rational reasons, and who ultimately paid the cost of the resulting rule. A list can be public while still underrepresenting the parties most exposed to its outputs. A small access network may not have staff time to monitor every proposal. A large platform may participate only when a draft touches a specific address strategy. A legacy holder may wake up only when transfer terms or service access are at issue. A lessee using addresses under a private arrangement may be economically exposed but procedurally invisible. A lender may understand address risk through diligence memos rather than PPML threads. Silence in the archive should therefore never be mistaken for consent in the market.
The post-exhaustion registry is not just a steward of scarcity. It is the recordkeeper of a scarce input whose market value was created by network dependence and by the slow incompleteness of IPv6 transition. That does not make ARIN a securities exchange or a state regulator. It does make PPML a place where private attention, institutional discretion, and capital value meet. The language of technical stewardship is no longer enough.
The policy machine and its conversion points
ARIN's Policy Development Process is valuable because it makes the policy machine unusually visible. It says the process is used to create and update policies ARIN uses to administer Internet number resources. It says changes must be developed through open and transparent processes with a meaningful opportunity for public participation. It says PPML is archived and publicly available, Public Policy Consultation proceedings are published, Advisory Council and Board minutes are published, and adopted policies are documented in the NRPM.
The same PDP defines PPML as the list used for discussion of Internet number-resource policy by members of the Internet community. It defines that community broadly as individuals interested in the management, promotion, and operation of the Internet, including people inside and outside the ARIN service region. It gives the proposal author the first important role: reducing an idea into a formal problem statement and proposed changes to policy text. It gives the Advisory Council an institutional role as the elected body that facilitates communication, deliberates on possible changes, and makes recommendations to the Board. Policy shepherds guide proposals through the process. Staff supplies implementation expertise, staff and legal review, and policy experience reports.
The PDP's principles are also important. Internet number-resource policy must enable fair and impartial administration, be technically sound, and be supported by the Internet community. The triad is sensible. It is also open-textured. "Supported by the Internet community" cannot mean unanimity among every party affected by a rule. No serious policy process could work that way. But if the affected economy is wider than the active mailing-list record, the phrase must be used with discipline. A visible subset of participants can provide procedural support. It cannot magically represent every operator, buyer, seller, customer, lessee, lender, public institution, or legacy holder whose economic position may be altered by the result.
The policy life cycle contains several conversion points. A policy proposal must contain a clear problem statement, proposed changes to the NRPM, and fall within policy scope. The Advisory Council can advance it, remand it to the author, reject it as out of scope, or deem it editorial. Draft policies can be revised, abandoned, sent for staff and legal review, presented to the community, or advanced. Recommended draft policies can move to last call. Last call creates a closing record, after which the Advisory Council must consider feedback and decide whether the text still meets the policy principles and whether substantial issues remain undiscussed. Board adoption integrates the policy into the manual. Staff then implements.
Each conversion point has an economics. The author anchors the problem. Early respondents make a frame sound normal or contest it before it hardens. Staff and legal review changes what participants believe is feasible, risky, or administratively burdensome. A shepherd can keep a draft alive, revise it into acceptability, or let it lose momentum. Public meeting discussion can add visibility, but also privileges those with time, travel capacity, or remote-attendance discipline. Last call raises the burden on late dissent because the process is near closure. Board review can validate the process without reopening every market consequence. Implementation converts policy into ticket handling, documentation requests, account rules, service eligibility, and transfer timing.
This structure is not defective because it has conversion points. Any serious process needs filters; otherwise policy would be a permanent argument with no usable output. The risk is that the filters may be mistaken for broad legitimacy. A proposal can be procedurally clean and economically thin. It can meet the documented steps while failing to map who did not participate, what transaction costs were added, how small networks would be affected, how legacy holders would price uncertainty, what lawyers would diligence, what brokers would discount, or how staff discretion would be measured after adoption. The machine is visible. The external cost map is less visible.
ARIN's orderly process therefore deserves a double reading. One reading is procedural: was the idea in scope, discussed, reviewed, advanced, adopted, and implemented according to the rules? The other is economic: did the process identify the parties that would pay, the discretion it created, the market conduct it restricted, the alternatives it rejected, and the limits of the support it actually received? The first reading can show that ARIN followed its rules. The second determines whether those rules are adequate in a post-exhaustion address economy.
Agenda control and the first mover's advantage
Agenda control is the quietest form of power in mailing-list policy. It does not require censorship. It does not require a closed room. It works by deciding what the discussion is about.
In ARIN's process, the proposal author must submit a problem statement and proposed policy text. That requirement is a discipline. It prevents vague complaints from consuming the process. It makes the author do work before asking the community to respond. It also gives the author the first chance to define the problem in terms that favour one kind of answer over another. If a transfer issue is framed as hoarding, the list will look for anti-hoarding controls. If it is framed as liquidity, the list will look for smoother movement. If legacy-resource status is framed as a service-access problem, debate will focus on contracts, fees, and service tiers. If it is framed as historical reliance, debate will focus on evidence, expectations, and limits on discretion. If address leasing is framed as evasion, the list will seek enforcement. If it is framed as continuity outsourcing, the list will ask why registry recognition should be tied to direct holding.
The author does not decide the outcome. But the author can set the first mental model. That is valuable because most participants are busy. Many will read the proposal, a few replies, perhaps an assessment, and then join under the established frame. In a high-attention environment, a frame can be contested early. In a low-attention environment, the first frame often persists because reframing is expensive. A late participant must not only argue a position; it must persuade others that the entire problem has been described incorrectly.
ARIN's process tries to discipline this power through scope and completeness requirements. The Advisory Council can remand unclear proposals. Staff and legal review can identify risks. PPML participants can object. Petition mechanisms exist for certain Advisory Council actions. These safeguards are real. They do not eliminate the first-mover advantage. A technically precise proposal can still define the wrong economic problem.
Post-exhaustion makes this more important because many policy disputes are distributional. Needs assessment in private transfers is not only a routing or database question. It affects the price of address capacity, the ability of new entrants to build ahead of demand, the attractiveness of leasing, the liquidity available to holders with surplus space, and the bargaining power of sellers. Waiting-list restrictions affect whether returned space acts as a small-network subsidy, a queueing device, or an arbitrage opportunity. Legacy-service distinctions affect whether historical holders face soft pressure to enter contemporary agreements. Resource-review procedures affect transaction certainty and therefore price. Inter-RIR compatibility rules affect whether address movement follows operational need, regional policy boundaries, or political decisions about which registries are acceptable counterparties.
If these issues are framed only as stewardship, conservation, or anti-abuse, market consequences may be treated as secondary. If they are framed only as market freedom, legitimate registry concerns may be understated. A good mailing-list economy forces both frames into the same record. It asks what ledger problem the rule solves, what market conduct it restricts, what evidence shows that the restriction is necessary, what lower-cost alternative was considered, which parties are likely absent, and how implementation will be measured.
The danger is not that ARIN lacks procedure. It is that procedure can make agenda control look like neutral orderliness. A well-formed proposal enters the system. The list discusses it. The Advisory Council shepherds it. The Board adopts it if the process and principles are satisfied. Yet the initial question may have been too narrow. In institutional economics, the power to define other people's transaction costs is often hidden inside the power to define the problem.
Coalition formation in an expert public
Coalitions on a mailing list do not look like parliamentary parties. They form around habits, interests, expertise, reputational capital, and endurance. Some participants regularly defend conservation principles. Others emphasize transfer liquidity, operational continuity, routing hygiene, small-network access, legal certainty, legacy reliance, anti-fraud controls, or administrative simplicity. Staff comments do not have to take sides in a partisan sense to influence perceived feasibility. Advisory Council members may speak as individual participants while also being people who later deliberate formally. Large operators may be selective. Brokers and lawyers may speak when transfer mechanics matter. Smaller operators may appear only when a rule touches them directly.
The currency of this coalition economy is not only votes. It is credible text, procedural memory, patience, and the ability to make one's argument sound like the process's own values. A participant who can say that a proposal fails fair and impartial administration, technical soundness, or community support speaks in a stronger register than a participant who merely says that it harms its business. A participant who can cite NRPM sections, prior drafts, staff comments, and earlier list debates has an advantage over one who describes market harm without translating it into policy language. A participant who can attend meetings, return during last call, and track revisions has more influence than one who sends a single late objection.
ARIN's membership and election structure adds another layer. ARIN's membership page says membership is not required for obtaining direct number resources, participating in PDP discussions, submitting suggestions, or joining public consultations. Its elections page says representatives from General Members in Good Standing elect candidates to the Board and Advisory Council for staggered three-year terms. The Board page describes the Board as having authority over scope, mission, strategic direction, and fiscal oversight. The Advisory Council page says the Council forwards consensus-based policy proposals to the Board for ratification.
This is meaningful member power. It is not sovereign power. A General Member electorate is not identical to the whole affected economy. It is not every direct resource holder, because direct resources do not require membership. It is not every downstream user whose services depend on address continuity. It is not every address lessee, acquisition target, lender, customer, hosting client, health system, school, municipal network, Caribbean operator, tribal network, or small enterprise whose operations may depend on a block. ARIN deserves credit for making policy discussion open beyond voting membership. But openness and representation are different concepts.
Coalition formation therefore creates a legitimacy problem even when nobody behaves badly. The active list may produce a real coalition of people who participated in good faith. The member electorate may elect real representatives. The Advisory Council may deliberate seriously. The Board may review carefully. Yet a policy can still emerge from a coalition narrower than the impact zone. The problem is not fraud. It is scale mismatch.
The mismatch becomes sharper when coalition language turns into community language. Community can accurately describe the people who participated. It can describe the wider set of people interested in number-resource policy. It should not be used as if every affected party authorized the result. That conversion is the beginning of mandate laundering: turning the existence of an open process into the fiction of a general mandate.
The issue is not unique to ARIN. Expert publics often govern technical systems because broad publics do not have the time, knowledge, or incentives to participate. That is not inherently illegitimate. The question is whether the expert public remains honest about its limits. The more valuable IPv4 becomes, the harder it is to pretend that the active policy list represents only a technical community. It also represents a subset of market actors with different capacities to pay the participation cost.
The real price of dissent
The cost of dissent in ARIN's policy system is not a fee at the door. It is the cost of being effective.
A dissenting participant must understand the proposal, the relevant NRPM sections, the stage of the PDP, the timing, the likely staff concerns, the Advisory Council's decision points, prior related debates, and the difference between a complaint that sounds personal and an objection that can change the record. The participant must write clearly, withstand repetition, reply when language changes, and return at the right time. If the matter reaches last call, a dissenter must identify substantial issues that remain undiscussed, not merely restate dislike.
This favours repeat participants. That does not make repeat participants villains. Many are valuable precisely because they remember history and can test new text against old problems. But institutional legitimacy cannot ignore the asymmetry. A registry regular, consultant, counsel, broker, or long-time engineer can amortize the cost of participation across many debates. A small network cannot. A holder affected by one rule may have to climb the learning curve at the exact moment when the process has already advanced.
There is also a disclosure cost. Mailing lists create public archives. That is good for transparency. It can deter participation. A business may not want to reveal acquisition plans, address needs, internal utilization, customer concentration, legal strategy, leasing exposure, or commercial dependence in a public thread. A small operator may fear looking uninformed. A legacy holder may avoid attracting attention. A broker may not want to disclose how a rule affects deal flow. A lessee may not know whether it has standing to speak because it is not the registered holder. Counsel may prefer private diligence to public argument. Silence can therefore be rational even when the party has serious concerns.
Timing creates a further cost. Early comments shape the frame. Later comments must dislodge an accumulated process. Last-call objections face a higher burden because the text has already survived earlier filters. Petition rights are valuable, but a petition requires procedural knowledge, timing discipline, and visible support. The more a proposal advances, the more expensive dissent becomes.
From an institutional-economics perspective, the archive records selected preferences. It records preferences whose holders paid the participation cost. It records harms that could be articulated in the accepted format at the accepted time. It records visible actors, not all affected actors. A policy community that treats the archive as a complete map of interests will overstate its own mandate.
The response should not be to abandon mailing lists. It should be to treat dissent costs as part of policy design. When a proposal affects transfers, legacy-resource certainty, service eligibility, waiting-list access, resource review, routing-security access, or agreement-linked rights, the process should assume that some highly exposed parties may be absent. It should require a plain-language impact section, not only a problem statement and proposed text. It should distinguish between "no objection appeared" and "the likely affected classes were identified and their interests considered." It should record non-participation risks. It should not let procedural silence become economic consent.
That discipline would also protect ARIN. A registry that can show it considered absent costs is less vulnerable to the charge that the process was captured by visible insiders. A registry that says merely that nobody objected invites scepticism in a market where the most exposed parties may have strong reasons not to speak.
Transfers as administered capitalism
ARIN's transfer system is where mailing-list economics meets administered capitalism. The registry does not operate a simple free market in IPv4 addresses. It also does not operate a pure allocation bureau. It recognizes market movement while conditioning recognition on policy. That hybrid is the post-exhaustion reality.
ARIN's transfer guide describes merger, acquisition, and reorganization transfers; transfers to specified recipients within the ARIN region; and inter-RIR transfers. It says the new organization in a merger or acquisition must provide evidence that it acquired assets using the resources. For specified-recipient transfers within the region, the guide says source and recipient organizations both submit requests, and the source must be the current registered holder, not be involved in a dispute over the resources, provide a signed and notarized officer acknowledgement, and satisfy other eligibility conditions. For inter-RIR transfers, the guide points to requirements for both source and recipient sides and to the policy compatibility of the other registry.
Some of this friction protects the ledger. Current-holder verification protects against false sellers. Dispute checks prevent recognition from worsening contested title-like claims. Officer acknowledgement reduces authority risk. Merger documentation protects against fabricated acquisitions. Minimum transfer size rules avoid excessive fragmentation. Reserved-pool exclusions preserve special-purpose policy pools. These are ledger safeguards. They protect the truth and usability of the record.
Other friction controls market access. NRPM section 8.5 requires specified recipients to meet transfer-recipient requirements. It contains operational-use language, an initial /24 path for organizations without an IPv4 allocation, documentation showing use of at least half the requested block within 24 months for larger initial or additional blocks, and efficient-use requirements for prior blocks. Section 8.4 ties inter-RIR transfer to reciprocal, compatible, needs-based policies. The source side of 8.3 and 8.4 includes waiting-list consequences after a transfer. These rules do not merely prevent forged records. They judge who may acquire capacity and under what future-use theory.
There are arguments for retaining such rules. A registry may worry that without need-based controls, address space will be accumulated by intermediaries, parked for speculation, withheld from real networks, or concentrated in ways that disadvantage smaller operators. It may also want to preserve the long-standing doctrine that addresses are assigned for use rather than sold as ordinary property. These concerns deserve to be heard. But after exhaustion the burden of justification changes. If two parties negotiate for already-issued space, the registry must be clear about whether its intervention protects record integrity or allocates economic opportunity.
That distinction is not semantic. Fraud prevention, authority verification, and dispute isolation are ledger functions. A broad judgment about a recipient's future need is a market-control function. Market controls may be defensible, but they should be defended as market controls. Otherwise a policy process can smuggle allocation-era rationing into a transfer market while speaking only in the language of stewardship.
PPML shapes the boundary. A proposal can tighten documentation, relax need rules, alter waiting-list penalties, change the treatment of M&A transfers, or reshape inter-RIR compatibility. Participants can frame the change as small-network protection, anti-speculation, operational efficiency, liquidity, or fairness. The frame determines which coalition forms. A small operator seeking residual access may support restrictions. A broker may oppose them. A legacy holder may care most about certainty. A large network may prefer predictable large transfers. An anti-abuse specialist may worry about shell entities and reputation risk. The list becomes the bargaining table, but many with capital at risk are not at the table.
The result is administered capitalism: private prices exist, private negotiation exists, but a nonprofit registry's policy process defines the channels through which capital can move. That is why mailing-list legitimacy is not a procedural side issue. It is part of market architecture.
Legacy resources and the soft power of services
Legacy resources are ARIN's clearest test of historical certainty. They predate ARIN's ordinary contractual structure and were inherited into ARIN's database from earlier Internet administration. ARIN's legacy-resource page says legacy holders have access to several services even if they are not under an ARIN agreement: unique registration in Whois and RDAP, updates to public data, reverse DNS management, maintenance of registry records through ARIN Online, and DNSSEC access. The same page says organizations with legacy resources not covered by an agreement do not have access to ARIN's RPKI or IRR services, and that they must be under an ARIN agreement to use those services.
That line is institutionally revealing. Basic ledger continuity is preserved even without an agreement. Advanced routing-security and routing-registry services require one. ARIN's position is understandable. RPKI and IRR access have operational and legal implications, and ARIN may reasonably want a defined relationship before offering them. Yet the economic effect depends on how essential those services become. If RPKI and IRR are optional conveniences, agreement-linked access is a service boundary. If routing practice increasingly expects them, the boundary becomes leverage.
Legacy certainty matters because it affects asset quality. A legacy holder wants the record to remain stable. A buyer wants clean chain-of-control evidence and predictable transfer recognition. A seller wants to avoid unexpected reinterpretation of historical status. A network using the addresses wants continuity of reverse DNS, public records, routing-security options, and transaction value. The registry wants accurate records and legal clarity. These interests can align if the registry treats history as a boundary and services as explicit choices. They become adversarial if service necessity quietly pulls older holdings into a broader regime without admitting the economic coercion.
ARIN's own material shows the tension in a relatively disciplined form. The legacy-resource page states that the legacy fee cap expired on 31 December 2023 for new coverage, while organizations with active Legacy Registration Services Agreements entered before 1 January 2024 continue to have fee limits for already covered legacy resources. It also explains that early Internet number resources were allocated under a different administrative model, and that when ARIN was formed, its Board decided to supply registration services for those legacy resources without requiring original holders to sign an agreement or pay service fees. That is an important recognition of historical difference.
Policy-list economics enters because changes to legacy service status, fee treatment, RPKI access, transfer requirements, or agreement incentives would be debated by the active community, not by every legacy holder or every downstream network that depends on a block. Legacy holders may be universities, companies, small early networks, public bodies, or entities that barely monitor registry policy. Their silence on PPML may not mean consent to a shift in asset treatment. It may simply mean they are not present in the process economy.
Here the ledger-versus-gatekeeper distinction becomes concrete. A ledger preserves accurate historical records, authorized updates, clean transfers, reverse DNS, and public lookup services. A gatekeeper uses service access, contract status, fee policy, and procedural language to shape the holder's choices. ARIN's documentation keeps part of that distinction visible. The legitimacy question is whether future policy changes will preserve it when the commercial importance of advanced services increases.
Resource review and the audit problem
Accountability in ARIN's system has several channels: public archives, Advisory Council deliberation, Board review, elections, published manuals, staff and legal review, meeting minutes, and documented implementation. These are real safeguards. They also share a limitation: much of the accountability is internal to the same institutional universe that produces the policy.
Resource review illustrates the point. NRPM section 12 permits ARIN to review current usage of resources maintained in its database. Reviews may occur when new resources are requested, when ARIN has reason to believe resources were obtained fraudulently or contrary to policy, when ARIN suspects noncompliance with reassignment or reallocation rules, or at other times without having to establish cause unless a full review has been completed in the previous 24 months. If ARIN finds material noncompliance, the section allows ARIN to request or require return of resources and, in some circumstances, revoke resources issued by ARIN as needed to bring an organization into compliance. The section states that it does not create additional authority to revoke legacy address space, though legacy utilization can be considered in assessing overall compliance.
A review power is necessary. Fraud exists. Records become stale. Organizations disappear. Reassignments may be mishandled. Address space obtained under one representation may be used under another. But a review power also creates asset uncertainty. A block embedded in a live network or transaction may be exposed to documentation risk, utilization interpretation, customer-data sensitivity, and staff judgment. The policy includes limits, but the power itself shapes behaviour. Buyers diligence review risk. Sellers discount complicated histories. Smaller operators may avoid visibility. Market actors price uncertainty into deals.
The issue is not whether ARIN should have no review power. That would be reckless. The issue is whether the policy community treats review power as a narrow registry safety instrument or as a broad lever of control. A ledger-first review system would focus on fraud, duplicate claims, dead organizations, materially false records, and clear policy violations tied to issuance or transfer. It would publish aggregate statistics on triggers, duration, outcomes, voluntary returns, revocations, and reviews initiated without cause. It would make recourse visible. It would distinguish correcting records from threatening network continuity. A gatekeeper review system would normalize broad discretion while relying on the public aura of stewardship.
Mailing-list procedure matters because audit powers are often legitimized through policy text. The list may debate words, but the affected market later experiences those words as a risk category. If dissenters cannot afford to participate effectively, the policy may pass with insufficient attention to transaction uncertainty. If the proposal is framed as anti-fraud, objections about cost may sound self-interested. If it is framed as accountability, objections about discretion may sound like resistance to oversight. The economics of the frame matter.
True accountability requires looking beyond whether a policy was adopted correctly. It asks whether downstream use of discretion is measurable. ARIN already publishes many materials. It could go further by making high-consequence discretion auditable at an aggregate level without exposing confidential customer information. That would strengthen the registry. The more valuable IPv4 becomes, the more trust depends on evidence that discretion is narrow, predictable, and reviewable.
Ledger or gatekeeper
The ledger-versus-gatekeeper distinction is the most useful way to assess ARIN's mailing-list economics. Lu Heng's public writing on registry continuity and mandate laundering, indexed through his public notes at heng.lu/all-notes, argues that the core registry function should be separated from institutional power. In that view, continuity means preserving uniqueness, registration accuracy, publication services, security continuity, running-network reliance, and independent dispute handling. It does not mean protecting every authority claim made by the incumbent institution. The Number Resource Society and LARUS have advanced related public arguments in sharper member-rights and continuity language, warning that IPv4 scarcity can turn registry discretion into economic power. These positions are interested positions. Their analytical value is that they put economic reliance at the centre rather than treating it as an inconvenience to official procedure.
The question they raise is simple: what must continue for the Internet to work? The answer is narrower than many institutional claims imply. Number resources must remain unique. The public record must be accurate. Authorized changes must be recorded. Disputes must be isolated rather than allowed to damage unrelated networks. Reverse DNS, RDAP, Whois, RPKI, IRR where used, and related registry services should not be casually broken. Transfers must not be forged. Running networks should not be destabilized by institutional conflict. The registry must be reliable enough that the ledger can be trusted.
What does not automatically follow? It does not follow that the registry should approve business models. It does not follow that the active mailing-list community should decide how much address capacity a buyer may accumulate through private transactions unless a concrete ledger or market-harm case is proven. It does not follow that service-region language gives a registry a claim over the capital value operators create. It does not follow that membership elections transform a private nonprofit into a public sovereign. It does not follow that a process with public archives represented all affected parties. It does not follow that dissenters who failed to appear consented.
The ledger is an information and coordination function. The gatekeeper is a discretionary power function. A registry must sometimes gatekeep to protect the ledger. The danger begins when every gatekeeping decision is described as ledger protection. Needs assessment in transfer markets, agreement-linked service access, waiting-list restrictions, resource review, and inter-RIR compatibility may all have legitimate reasons. Each should be labelled honestly: which part protects record integrity, which part controls market behaviour, which part increases institutional leverage, and what evidence justifies the cost.
This distinction is not anti-ARIN. It is a way to protect ARIN from the institutional drift visible across the registry system. A registry that can say, "this is a ledger safeguard and here is the evidence," will retain legitimacy. A registry that says, "the community discussed it, therefore our discretion is legitimate," will gradually weaken its claim even if every procedural step was documented.
Official registry materials are useful exhibits in this analysis. They tell readers how ARIN says PPML works, how the PDP is structured, how transfers are approved, how membership and elections operate, and where legacy-service lines are drawn. They should not be treated as the final framing source for the politics of that system. A procedure can describe itself accurately while understating the power it concentrates. The infrastructure-economics critique supplies the question the procedure must answer: does this rule protect the ledger, or does it turn the recordkeeper into a gatekeeper over economic reliance?
Mandate laundering in a mature registry
Mandate laundering is more subtle in ARIN than in a crisis registry because ARIN's procedures are orderly. That makes the risk more important, not less. The danger is not that ARIN declares itself sovereign over North America. The danger is that a chain of modest institutional claims produces a broad result.
The chain runs like this. A policy proposal is submitted through an open process. PPML discussion occurs. Active participants support, oppose, or amend. The Advisory Council shepherds the text. Staff and legal review identify feasibility and risk. Public consultation adds visibility. Last call closes the record. The Advisory Council advances. The Board reviews the history and adopts. Staff implements. Later, when the rule affects transfers, review, legacy services, routing-security access, or waiting-list eligibility, the institution can say that the policy was developed by the community.
Every step may be true. The leap is in the final sentence. "Developed by the community" can mean that a documented subset of interested participants produced a policy through an open process. It should not mean that the policy carries the moral authority of the whole affected economy. It should not mean that absent parties authorized every consequence. It should not mean that registry discretion has become public law. It should not mean that operational reliance is subordinate to whatever the active list can sustain procedurally.
This distinction matters because ARIN's region contains many types of dependence. A public agency may depend on stable addresses for civic services. A hospital network may depend on address continuity through contractors. A small access network may depend on a modest block to avoid costly renumbering. A large platform may depend on long-horizon address planning. A university may hold legacy space with complex history. A Caribbean operator may have less policy capacity than a large mainland network. A lessee may not be the registered holder but may carry operational risk. These parties do not occupy the same position in the mailing-list economy.
Mandate laundering occurs when the existence of participation hides those differences. It lets an institution say "the community" when it means "active participants." It lets it say "policy" when it means "a rule with market consequences." It lets it say "stewardship" when it means "control over transfer, review, or service access." It lets it say "open" when the real issue is the price of attention.
The cure is not populism. A registry cannot run a referendum among every affected party for every rule. The cure is humility about what the process proves. PPML proves that discussion was possible and that some participants created a record. It does not prove that all affected interests were represented. Advisory Council approval proves that the text met internal criteria. It does not prove that economic cost was fully measured. Board adoption proves process review and institutional acceptance. It does not transform private coordination into public mandate. A mature registry should say these limits out loud.
Humility would not weaken ARIN. It would make its claims more credible. The institution could distinguish between procedural legitimacy and economic legitimacy. It could say that a rule passed properly, that the record contains the arguments received, that absent interests were considered through a specific impact analysis, and that implementation will be measured. That is a stronger claim than the ritual invocation of community.
Member power and the limits of consent
ARIN's member structure deserves separate attention because it is both real and limited. General Members in Good Standing elect most Board members and the Advisory Council. The Board has authority over scope, mission, strategic direction, and fiscal oversight. The Advisory Council is central to the PDP. Elections therefore matter. They are not decorative. They are part of the accountability architecture.
But member power does not answer every legitimacy question. Membership is not required to obtain direct number resources or to participate in policy discussion. Voting contact designations and member status shape election power. Downstream networks, customers, address lessees, lenders, brokers, and many operationally dependent parties do not necessarily have a vote. Even among eligible organizations, the person who votes may not be the person whose team understands transfer-market exposure. A member electorate can govern a nonprofit without representing the full economic field affected by registry policy.
This is not a defect unique to ARIN. Many private coordination bodies combine open participation, member elections, and expert processes. The problem arises when the institution treats these mechanisms as substitutes for affected-party analysis. A member vote can select a Board. It cannot by itself show that a transfer rule is economically proportionate. An Advisory Council election can produce legitimate policy stewards. It cannot by itself show that a resource-review power is narrow enough. An open list can supply arguments. It cannot by itself show that silent legacy holders, smaller operators, or indirect users have accepted a new service dependency.
Member power also interacts with coalition formation. Organizations with large address interests may have stronger incentives to monitor elections. Policy regulars may know candidates and issues better than occasional participants. Smaller networks may value registry services but lack time to evaluate governance choices. The result is not necessarily capture, but it is a predictable participation gradient. That gradient should be part of the legitimacy analysis.
A more precise account would say: ARIN has member-elected governance, open policy discussion, and documented policy adoption. Those features provide institutional accountability. They do not erase the need to examine agenda control, dissent costs, coalition narrowness, and downstream market impact. Consent in a mature IPv4 economy cannot be inferred from the mere availability of participation.
Registry-layer risk and the cost of uncertainty
Registry-layer risk is the risk that the recordkeeper's rules, contracts, reviews, service boundaries, or institutional decisions will affect the value or continuity of a network resource. It is different from routing risk, although the two can interact. It is different from market price risk, although it affects price. It is different from abuse risk, although abuse handling can trigger registry consequences. It is the risk that the layer meant to preserve the ledger becomes a source of uncertainty for the asset recorded in the ledger.
In ARIN's region, this risk is sophisticated because the market is sophisticated. Brokers understand transfer categories. Lawyers know the difference between 8.2, 8.3, and 8.4 transfers. Buyers ask about RSA status, legacy status, dispute history, utilization, reassignment records, RPKI readiness, reverse DNS, officer authority, and inter-RIR compatibility. Sellers ask how long recognition will take, whether source status is clean, whether prior transfers create restrictions, and whether a block's history will reduce price. Operators compare direct holding, transfer purchase, and leasing exposure. Financing parties ask whether address recognition survives if a transaction fails. Every one of these questions exists because the registry layer is not frictionless.
Some uncertainty is unavoidable. A registry cannot approve a forged transfer for speed. It cannot ignore a live dispute. It cannot pretend that a dissolved entity can sign documents. It cannot abandon policy simply because a buyer wants rapid closing. The problem is not friction itself. The problem is the absence of a clear line between necessary friction and discretionary leverage.
Mailing-list policy is part of that line. A policy can reduce registry-layer risk by clarifying criteria, narrowing discretion, and improving predictability. It can increase risk by adding vague standards, documentation burdens, broad review triggers, lock-ups, service dependencies, or contract-linked conditions. The same process can do either. What matters is whether participants assess rules as market infrastructure rather than internal administrative text.
The cost of uncertainty is not evenly distributed. Large operators can hire counsel, hold spare capacity, wait out process, and influence debate. Small networks may not. Sophisticated legacy holders can manage agreement choices. Others discover risk only when a transaction begins. Brokers can adapt by pricing friction. End users cannot. A mailing-list archive may show a fair debate among experts while the cost is borne by parties that were never present.
This is the economic case for a higher standard of analysis. Policies that affect registry-layer risk should include not only problem statements and proposed NRPM text, but a transaction-impact discussion: who waits longer, who pays more, who becomes more dependent on contract status, who loses optionality, which absent parties are likely affected, what evidence justifies the cost, and how the implementation will be audited. Without that, the list can produce rules with hidden externalities.
What PPML does well
It would be wrong to treat the mailing list as merely a problem. PPML can do things no closed process can do. It creates public memory. It lets outsiders see how a policy evolved. It allows technical objections to interrupt administrative convenience. It gives smaller participants a way to address the institution without private lobbying. It lets staff and Advisory Council members hear operational detail they might otherwise miss. It archives dissent that may become important later. It makes policy language harder to move through unnoticed.
ARIN's publication of list archives, PDP rules, meeting materials, Advisory Council and Board minutes, transfer guidance, and the NRPM is therefore valuable. The question is how to make that transparency robust in an asset-market environment. A list is good at exposing arguments among those present. It is weaker at measuring absent costs. It is good at refining text. It is weaker at producing independent economic analysis. It is good at preserving visible dissent. It is weaker at hearing parties that cannot safely disclose exposure. It is good at expert consensus. It is weaker at proving representativeness.
The best use of PPML is as a deliberative record, not as a mandate machine. It should be where proposals are tested, not where all legitimacy is presumed to originate. The list can surface ledger problems, but a transfer-market rule should also be judged by transaction evidence. The list can identify abuse concerns, but an anti-abuse policy should specify the conduct and the lowest-cost intervention. The list can discuss legacy services, but silent legacy holders should be affirmatively considered. The list can debate waiting-list restrictions, but residual rationing should not be allowed to justify broad control of privately held space.
This approach would strengthen ARIN because it would align procedure with the post-exhaustion economy. The registry would not have to pretend every rule is merely technical. It could say: this rule protects the ledger; this rule restricts market behaviour; this rule imposes cost; this evidence justifies the cost; this is how dissent was considered; this is how implementation will be measured. That is a more honest legitimacy structure than treating open discussion as a universal solvent.
Toward a better economics of mailing-list policy
A better economics of PPML would start with four distinctions.
First, distinguish openness from affordability. A list is open if anyone can subscribe and post. Participation is affordable only if affected parties can understand the issue, identify their exposure, speak without unreasonable commercial risk, and intervene before closure. For high-consequence policy, ARIN should not be satisfied that the door was open. It should ask who realistically could walk through it.
Second, distinguish ledger safeguards from market controls. Ledger safeguards verify authority, prevent duplicate claims, preserve records, isolate disputes, and maintain service continuity. Market controls decide who may acquire capacity, under what need standard, after what waiting period, with what lock-up, and under which agreement. Both may be legitimate. They should not be confused.
Third, distinguish active-community support from affected-economy consent. The active community can produce reasoned support. It cannot speak for every party affected by address-market rules. When policy affects capital movement, the record should identify likely affected classes and explain how their interests were considered even if they did not appear.
Fourth, distinguish institutional continuity from network continuity. ARIN as an organization is important because it operates registry functions. But the continuity interest that justifies the registry is the continuity of uniqueness, records, security publications, authorized changes, and running networks. The institution serves that continuity. It should not use that continuity to protect every discretionary extension of its own role.
These distinctions could be operationalized without dismantling the PDP. Policy proposals affecting transfers, legacy-resource status, service eligibility, waiting-list rules, resource review, inter-RIR compatibility, or agreement-linked rights could require a market-impact section. Staff and legal review could include a registry-layer risk assessment, not only implementation feasibility. Last-call notices could identify affected classes and summarize unresolved economic objections. Advisory Council advancement could state whether the proposal is a ledger safeguard, a market-control rule, or both. Board adoption could include a short accountability note for high-consequence policies. Implementation could be followed by aggregate metrics after a defined period.
None of this requires ARIN to adopt a free-market ideology. It requires ARIN to admit that post-exhaustion number policy affects markets. That admission would make the policy process more legitimate, not less. It would also protect the list from being asked to do too much. A mailing list is a useful deliberative instrument. It is not a substitute for economic analysis, affected-party mapping, service-continuity planning, or independent dispute handling.
The North American test
ARIN's institutional advantage is that it still has room to make these distinctions before a dramatic crisis forces them. Its public materials already contain many ingredients of accountability: open PPML archives, public PDP rules, elected Board and Advisory Council seats, transfer categories, legacy-resource explanations, waiting-list rules, resource-review text, and published policy manuals. The risk is not absence of structure. The risk is that structure becomes self-validating.
The North American registry sits at the centre of a mature address economy. IPv4 scarcity has made number resources economically significant. Transfers, leasing, legacy certainty, routing-security access, contractual status, and registry review all matter. Mailing-list procedure therefore cannot be judged by Internet-governance nostalgia. It must be judged by whether it disciplines agenda control, exposes coalition limits, lowers the cost of dissent, and keeps the registry's role closer to ledger than gatekeeper.
If ARIN treats PPML as an evidentiary forum, it can remain a strong institution. If it treats PPML as a broad mandate machine, it will drift toward gatekeeping even without scandal. The difference will not be visible in a single policy. It will appear as a gradual thickening of rules, reviews, service dependencies, and procedural claims around a market that needs a reliable ledger.
The correct standard is not anti-registry. It is pro-ledger. Protect uniqueness. Protect registration accuracy. Protect authorized transfer recording. Protect reverse DNS, RDAP, Whois, RPKI, IRR where used, and clean dispute isolation. Protect smaller networks from residual-scarcity games where evidence supports intervention. Protect the market from fraud. But do not pretend that every procedure-backed restriction is merely stewardship. Do not mistake active-list endurance for universal consent. Do not let member power become a substitute for affected-economy analysis. Do not let the institution that keeps the book become a gatekeeper over the capital value created by operators.
ARIN is the test because it is orderly. If an orderly registry can show that mailing-list procedure remains humble, evidence-based, and ledger-first after exhaustion, the RIR model has a credible path toward legitimacy in the asset era. If even ARIN's process turns openness into mandate, policy into capital control, and community language into insulation from economic scrutiny, the problem is not local dysfunction. It is built into the mailing-list economics of the post-exhaustion registry system.
The list is not just a list. It is where cost, attention, procedure, and power meet. In the IPv4 abundance era, that may have been good enough. In the IPv4 asset era, it must be held to a higher standard.