ARIN Board Elections and the Economics of Registry Power

ARIN's board elections are easy to underestimate because the visible mechanics look modest. A candidate page appears. Eligible organisations assign voting contacts. A Nomination Committee prepares slates. The membership votes. The result refreshes the Board of Trustees and the Advisory Council, and the registry continues to operate. Read that way, an ARIN election looks like the internal housekeeping of a mature technical association.

That reading is procedurally accurate and institutionally too small. ARIN is not only a venue for annual community participation. It is the North American registry for Internet number resources in a world where IPv4 scarcity has made the registry record economically decisive. ARIN's own IPv4 addressing guidance records the depletion of its free IPv4 pool on 24 September 2015. Since then, scarcity has shifted the economic question from ordinary allocation to transfer recognition, waiting-list rationing, contract status, legacy-resource treatment, resource review, routing-security access, registry accuracy and the policy boundaries around a market in already issued address space. In that setting, board elections are not a ceremony above the economy. They are one of the few channels through which members influence the institution that can alter the cost of holding, moving and using scarce number resources.

The point is not that ARIN is uniquely fragile among the Regional Internet Registries. It is almost the opposite. ARIN is a useful case because its stress is quiet. AFRINIC has supplied the more dramatic warning: litigation, receivership, contested governance and the fear that control of the registry record can become a fight over institutional survival. RIPE NCC operates under European legal and sanctions pressure. APNIC's elections sit inside a large and politically varied Asia-Pacific region. ARIN's pressure comes from a different place. Its region contains the United States, Canada and parts of the Caribbean and North Atlantic, along with cloud platforms, access networks, hosting firms, universities, enterprise networks, address-rich legacy holders, brokers, lessors, financial buyers and lawyers who can place value on IPv4 continuity. If election legitimacy matters as a control question rather than a ritual, it matters in ARIN.

ARIN's public pages are useful factual exhibits. The Board of Trustees page says nine trustees are elected by General Members in Good Standing and that the President and CEO serves as a tenth trustee. The elections page says General Members elect the Board and Advisory Council in staggered terms. The Policy Development Process gives the Board a decisive role at the adoption point for recommended draft policies, including the ability to adopt, remand or reject. The Number Resource Policy Manual contains the transfer, waiting-list, resource-review and needs-based provisions that shape the market's exposure to ARIN discretion. The strategic planning and budgeting page shows that ARIN is a staffed, budgeted institution whose board direction becomes operational priority. These pages do not settle the legitimacy question. They show where the power sits.

The analytical frame should be stricter than official registry language. Lu Heng's public notes, the Number Resource Society and LARUS's continuity position supply a useful counter-frame because they treat registry power as infrastructure design rather than as a moral story about stewardship. In a note on why NRS exists, Lu argues that scarcity, value and geopolitics have turned central discretion at the registry layer into a structural risk, and that decentralisation should be understood as systems engineering rather than ideology. His note on registry-layer structural risk frames direct holding as exposure to contract, policy, audit, renewal and revocation surfaces. NRS states on its public site that IPv4 scarcity turns registry discretion into economic power. LARUS presents continuity-focused IPv4 leasing as a way to reduce customer exposure to registry-facing uncertainty. These are interested positions, and they should be read as such. Their value is that they force the question official language often softens: when a registry record becomes economically decisive, who controls the choke point?

The core argument follows from that question. ARIN board election legitimacy should be judged by whether the election gives members a credible way to discipline the registry's gatekeeping power over enforcement, budgets, transfer-market governance, policy agenda and member rights. A valid ballot is not enough. Legitimacy depends on whether the franchise, nomination architecture, candidate debate and board incentives map onto the consequences now attached to registry decisions. In a post-exhaustion market, board elections are not about the tone of community life. They are about institutional control over scarce capital infrastructure.

From allocation to control

ARIN was built to perform a technical coordination function: maintain uniqueness, administer registry records and support the orderly use of IP addresses and Autonomous System Numbers in its region. That function remains indispensable. Internet number resources need a public record. Operators need contact data, reverse DNS, routing-security hooks, transfer histories and a way to distinguish recognised control from fraudulent or duplicate claims. A functioning Internet still needs a trusted registry ledger.

What changed is the economic meaning of that ledger. In the pre-exhaustion world, much of ARIN's policy vocabulary made intuitive sense. "Need", "conservation", "aggregation", "registration" and "stewardship" described a registry distributing resources from a finite but still administratively available pool. An applicant asked for new space. The registry evaluated whether the applicant could justify the request. The cost of bad judgement was real, but the institutional role was relatively clear: ration a scarce public input while maintaining accurate records.

Post-exhaustion scarcity changes the role. The registry is no longer mainly distributing abundance. It is administering scarcity among resources already embedded in networks, contracts, product lines, acquisitions, hosting platforms, public-sector systems and enterprise migrations. A transfer may be part of a corporate acquisition. A returned block may enter a waiting list. A legacy holder may want RPKI access. A smaller network may need a /24 to avoid dependence on upstream addressing. A cloud platform may treat IPv4 inventory as a constraint on customer growth. A bankruptcy estate may discover that address continuity affects recovery value. A buyer or lender may ask whether the registry record is stable enough to support the transaction.

These are capital-allocation questions as much as technical-administration questions. ARIN does not set the price of IPv4 addresses. It does not run every negotiation. It does not guarantee that every network will route a block. Yet it controls the recognition layer. A private transaction that cannot be reflected in the registry record may have little practical value. A buyer who cannot satisfy current recipient policy may face delay, restructuring or abandonment. A source organisation that cannot prove authority, clear dispute status or eligibility may lose a market window. A legacy holder that wants modern routing-security services may face a contractual decision that changes its risk profile. The registry is not the whole market, but it is a bottleneck through which market value must pass.

This is why board elections matter economically. The board is not merely above the machinery; it helps define the institution's risk appetite, budget priorities, election architecture and policy posture. A board that sees ARIN primarily as a cautious steward of a common resource will read transfer restrictions differently from a board that sees ARIN primarily as a public ledger with narrow anti-fraud and accuracy duties. A board focused on institutional liability may preserve review gates that impose friction outside the registry. A board focused on member accountability may demand better publication of transfer timelines, resource-review triggers, denial categories and appeal routes. A board focused on budgetary defence may strengthen legal and compliance capacity; a board focused on ledger quality may prioritise accuracy, security, transfer service and public reporting.

The distinction between ledger and gatekeeper is therefore the analytical hinge. A ledger records recognised control, contacts, reverse DNS, routing-security status, transfer history, dispute state and accuracy signals. A gatekeeper decides whether a business plan, timing, use case, region, contractual posture or market transaction deserves recognition. Every registry must have some gates to prevent fraud and duplicate claims. But every gate beyond record protection must carry a higher burden once the resource is valuable. Election legitimacy is the institutional answer to that burden. If members cannot meaningfully discipline the gates, the gates begin to look like private administrative power wrapped in community language.

The franchise problem

ARIN's member structure is real governance, but it is not full consent by everyone exposed to ARIN decisions. The membership page distinguishes Service Members, General Members and Trustee Members. It also says membership is not required to obtain direct Internet number resources, take part in policy discussion, submit suggestions or participate in public consultations. Voting power is narrower. General Members in Good Standing, through designated Voting Contacts, elect trustees and Advisory Council members. The elections page adds timing requirements around eligibility and Voting Contact designation.

That structure creates a legitimacy paradox. General Members have meaningful power because they elect trustees and Advisory Council members. Yet the affected economic community is wider than the voting class. A direct resource holder may not be a General Member. A hosting customer may depend on ARIN-numbered infrastructure without knowing ARIN exists. An enterprise buyer may rely on vendor IPv4 continuity but have no vote. A lender, broker, insurer, acquisition target or customer may price registry risk without participating in ARIN membership. Even inside the voting class, the vote is not weighted by customers served, routes originated, capital exposed, addresses held, transfer activity or downstream dependency.

That is not automatically a defect. One-organisation voting avoids a formal plutocracy in which the largest address holders dominate by scale. It gives smaller General Members a voice and keeps election mechanics comprehensible. A capital-weighted franchise would carry obvious legitimacy problems of its own. But the current structure means ARIN elections cannot be treated as regional sovereignty. They are member governance in a specialised corporation, not consent by the whole economic field.

This distinction matters because technical institutions often use "community" in an expansive way. ARIN's policy process is open to an Internet community broader than the electorate. That openness is valuable, and the archived discussion record is an institutional asset. But the community of discussion is not the same as the community of voters. The voters are not the same as all resource holders. Resource holders are not the same as the customers and capital that depend on registry continuity. A transfer rule can be procedurally developed in the community and still impose costs on absent parties.

The franchise problem becomes sharper after IPv4 exhaustion because the consequences of registry decisions spread farther from the formal membership. A resource-review action can affect a sale, financing, merger or customer migration. A transfer-recipient requirement can change the size and timing of a buyer's address plan. A waiting-list rule can alter the path available to small entrants. A contract boundary around RPKI or IRR can affect legacy-holder risk as routing-security expectations rise. The people who pay those costs may not have the same practical ability to vote, attend meetings or write policy text.

Low participation would weaken the mechanism further. Specialist governance often attracts the people with the time, vocabulary, institutional memory and direct incentive to participate. That can produce technically literate decisions, but it may not represent the full distribution of economic exposure. Silence may mean trust; it may also mean the cost of participation is high relative to the chance of changing outcomes. In a scarcity system, silence is a poor proxy for consent.

This is why the election should be read as an accountability device, not as a proof of broad consent. The question is not whether ARIN has a member franchise. It does. The question is whether that franchise is used to test the institution's enforcement posture, budget logic, transfer-market assumptions and policy boundaries. A member electorate that treats the election as a civic routine will tend to reward continuity. A member electorate that understands the scarcity economy can demand candidates who explain where ARIN's authority should stop.

Nomination architecture and acceptable dissent

Election legitimacy begins before the ballot. ARIN's Election Processes describe a structured system of board-approved nomination and election rules, board guidance, a Nomination Committee, candidate questionnaires, assessment activity and petition rights. The Board also appoints election-related officers and approves materials used in the cycle. Those mechanisms have sensible purposes. A registry board is not a debating club. Trustees oversee a critical technical institution with fiscal, legal and operational duties. Screening can reduce the risk of unqualified, conflicted or unserious candidacies.

The same architecture creates the economics of acceptable dissent. If the current board supplies guidance about the skills needed, helps shape the nomination path and approves the election system, incumbency has indirect influence over what counts as qualified. A skills matrix can emphasise finance, cybersecurity, audit, legal expertise, governance experience, technical depth, community service or executive judgement. Each emphasis favours a different kind of candidate and a different theory of ARIN. None is neutral.

This is not a claim that the process is closed. Petition rights and published materials matter. Member representation in nomination work matters. Candidate statements matter. Structured review may protect ARIN from a board that lacks fiduciary competence. But a registry election is not legitimate merely because it avoids chaos. It must also allow serious dissent to reach voters. In ARIN's case, serious dissent would not mean anti-registry vandalism. It would mean candidates willing to ask whether needs-based review still belongs in ordinary private transfers, whether resource review is too broad, whether legacy-service boundaries create leverage, whether the transfer market needs better aggregate reporting, whether the budget strengthens the ledger or the gatekeeper, and whether "community-developed policy" is being asked to carry too much authority.

The danger is not crude exclusion. It is soft narrowing. A candidate who speaks the familiar language of stewardship, continuity and consensus may look safe. A candidate who speaks about capital controls, mandate laundering and registry-layer risk may look disruptive even when the candidate is asking legitimate institutional questions. The election architecture should be able to tell the difference between reckless disruption and disciplined reform. If it cannot, the ballot becomes a ratification instrument rather than a choice.

The standards for qualification should therefore be explicit about institutional theory as well as professional skill. A board needs trustees who understand audit, security, finance and governance. It also needs trustees who understand that IPv4 exhaustion changed the nature of the institution. A candidate can be technically competent and still fail to grasp the economic consequences of transfer friction. Another can be a serious reform candidate while challenging inherited registry language. The nomination system should not confuse comfort with competence.

For Voting Contacts, this means candidate information must allow meaningful comparison. If all candidate statements sound like variations on continuity, member voters cannot assess the deeper question: should ARIN remain a broad steward of number-resource use, or should it narrow toward ledger-first administration wherever possible? Should the board demand more economic impact analysis for transfer rules? Should it press for clearer resource-review data? Should it treat budget growth as service capacity or institutional expansion? Should it view election participation as member relations or as control over a scarcity layer? Those are election questions, not side issues.

An institution that fears serious dissent will eventually make dissent more radical by denying moderate reform a route to representation. ARIN is stable enough not to need such defensiveness. It should be able to put the ledger-versus-gatekeeper question on the ballot without treating it as a threat to the registry's existence.

Board incentives after exhaustion

Boards have incentives even when trustees act in good faith. ARIN's Board oversees scope, mission, strategy, fiscal direction and corporate governance. The strategic planning and budget materials show that ARIN is a professionally staffed institution with operating plans, expenses, reserves, legal obligations, engineering work and member services. That makes board elections economically concrete. Trustees influence how ARIN allocates resources among registry operations, software, security, transfer service, legal review, public policy, outreach, meetings, elections, routing-security support, data publication and risk management.

The first board incentive is caution. A registry can cause serious damage if it recognises a fraudulent transfer, mishandles a dispute, loses control of records, ignores a court order, weakens security or permits duplicate claims. Caution is rational. But caution can become a default that protects ARIN's institutional position while pushing delay and uncertainty onto resource holders. If the registry's liability is more contained than the holder's commercial downside, the registry will naturally prefer more documentation, more review and more conservative approval. That posture may reduce ARIN's risk while increasing market friction.

The second incentive is continuity. Stable technical institutions value staff expertise and institutional memory. That too is rational. ARIN staff know the registry systems, historical records, legacy issues, transfer documentation, contacts and operational duties far better than most outsiders. Yet continuity can harden into path dependence. Rules designed for free-pool allocation may persist because they are familiar, defensible and embedded in systems and forms. Post-exhaustion conditions require the board to ask whether allocation-era logic still fits a transfer-market world. A continuity board may see each rule as a small inherited safeguard. A reform board may see the accumulation of those safeguards as a control layer.

The third incentive is reputation. ARIN benefits from being seen as stable, neutral, professional and community-based. It has good reason to defend that reputation. But reputational defence can discourage economic candour. It is easier to say ARIN administers number resources under community-developed policy than to say ARIN's decisions can affect asset liquidity, contract leverage and capital allocation. The first statement is true. The second is also true. A legitimate board should be able to say both.

The fourth incentive is control over the election system itself. A board that approves nomination and election rules, supplies guidance and shapes the definition of needed skills inevitably affects the candidate pool. That is not sinister by itself; a board must protect institutional competence. But the power requires humility. Incumbents should not define qualification so narrowly that only continuity candidates appear credible. Nor should they treat election orderliness as the same thing as election legitimacy.

The fifth incentive is budgetary self-preservation. Every mature institution develops programmes, staff roles, committees, systems and external relationships that argue for continuation. Some are necessary. Some may become comfortable. A board that sees the registry as a public ledger should ask whether spending reduces uncertainty for operators and holders. A board that sees the registry as a broad governance platform may spend more on institutional presence, consultation structures and defensive posture. Both can be justified in particular cases. The election should allow members to judge the direction.

These incentives are not accusations. They are the normal political economy of an institution sitting over scarce resources. The right response is not distrust for its own sake. It is election discipline. Trustees should be asked how they will distinguish ledger protection from institutional expansion, when caution becomes friction, when continuity becomes inertia and when community language becomes a substitute for measuring costs.

Enforcement posture: review, transfer and legacy boundaries

Board elections matter because enforcement posture is not simply staff technique. It reflects institutional theory. ARIN's NRPM contains a resource-review framework, transfer rules, waiting-list limits, recipient requirements and legacy distinctions. Staff apply those rules, but the board sits above the strategic and policy environment in which enforcement is interpreted, funded and legitimised.

Resource review is the clearest example. Section 12 of the NRPM permits ARIN to review current usage in several circumstances, including when an organisation requests resources, when fraud or policy violation is suspected, when reassignment or reallocation compliance is at issue, and at intervals permitted by the text. The same section contains an important limitation around legacy address space. A review power may be necessary to protect the registry from fraud, false authority and severe non-compliance. But in a post-exhaustion market it can also become a source of economic uncertainty. A review can delay a transfer, complicate a merger, chill a buyer, disturb financing or force a holder to spend legal and management time defending resources that are already operationally embedded.

The remedy gap is important. If a review is later resolved in the holder's favour, the lost commercial window may not return. A buyer may have walked away. A lender may have changed terms. A customer migration may have failed. An acquisition timetable may have moved. Process is not merely procedure in an asset market; it is part of the asset's value. A board that understands this will demand aggregate reporting, clear triggers, review timelines and narrow use of discretionary authority. A board that thinks only in internal compliance terms may underestimate the external cost.

Transfer recognition raises the same issue. ARIN's transfer guide divides transfers into merger, acquisition and reorganisation transfers; specified-recipient transfers within the ARIN region; and inter-RIR transfers. It also describes officer acknowledgements, dispute checks, recipient requirements, RSA expectations, waiting-list consequences and cross-RIR compatibility. Many of these controls protect the ledger. Verifying source authority protects the ledger. Checking dispute status protects the ledger. Requiring evidence of corporate reorganisation protects the ledger. But recipient need tests for private specified transfers sit closer to market control. They ask the registry to judge the buyer's future operational requirement even though the space is not being drawn from the free pool.

There are defensible reasons for some transfer controls. ARIN can reasonably worry about sham transactions, forged authority, immediate arbitrage of residual-pool space, hidden disputes and record pollution. The problem is proportionality. A gate that prevents documented fraud is easier to justify than a gate that preserves allocation-era scarcity logic inside a market transaction. The board should ask what harm each transfer rule prevents, how often the harm occurs, what cost the rule imposes, whether narrower alternatives exist and how affected parties can challenge decisions. If the answer is not known, the institution is governing by inherited vocabulary rather than evidence.

Legacy resources add another legitimacy test. ARIN's legacy-resource guidance treats pre-ARIN resources as a distinct category and explains the relationship between basic registry services and agreement-based services. That distinction is institutionally valuable because legacy holders are not ordinary applicants for new resources. Their claims come from a different historical moment. At the same time, modern routing-security expectations can create pressure to enter agreements if services such as ARIN-hosted RPKI or IRR access are tied to contract status. The board's job is to ensure that service policy does not become quiet coercion. If a service boundary is necessary for legal, operational or financial reasons, ARIN should state the reason and the consequence plainly. If a formerly optional service becomes practically necessary for ordinary operations, the boundary should be reconsidered.

Enforcement legitimacy therefore depends on restraint. Fraud should be pursued. Duplicate claims should be stopped. False authority should be rejected. Records should be kept accurate. But review, transfer approval and service access should not become instruments for extending registry power beyond the ledger. Elections matter because trustees can insist on that distinction.

Budgets as control documents

Budgets are underrated legitimacy documents. They reveal what an institution thinks its risks are and what it is willing to make possible. ARIN's planning and budgeting materials show that the board approves the budget and that strategic priorities translate into work. That means member elections indirectly influence the staff capacity, systems and external work that define ARIN's posture toward the market.

If transfer-market friction is a serious problem, the budget should support clearer transfer service, better publication, faster ticket handling, more transparent guidance and aggregate reporting that does not expose confidential transaction details. If record accuracy is central, the budget should strengthen data quality, contact validation, fraud detection, security and public registry reliability. If routing security is a priority, the budget should fund engineering, education and support that lower adoption barriers without turning security tools into excessive contract leverage. If election participation is weak, the budget should support member education that explains why board seats matter in a scarcity economy. If resource review creates concern, the budget should fund oversight, timelines and reporting, not only legal capacity.

A board cannot credibly claim accountability while treating the budget as internal housekeeping. A transfer rule without adequate service capacity creates delay. A resource-review power without transparency creates fear. A public policy system without economic data creates debate that may be open but under-informed. An election system without voter education creates formal choice without substantive control. Money is where legitimacy becomes capacity.

Reserves also matter. Prudent reserves protect continuity. A registry must be able to withstand technical incidents, legal disputes, security events, revenue fluctuations and infrastructure needs. Yet reserves shape institutional incentives. A well-reserved registry may have more ability to invest in modern systems and service reliability. It may also feel less immediate pressure to justify fees, spending and programme expansion to members. Elections are where members can ask whether reserves, fees and services align with the actual public value ARIN supplies.

The central budget question is whether spending strengthens the ledger or strengthens the gatekeeper. Spending on secure systems, accurate records, transfer reliability, fraud prevention, contact data, reverse DNS and routing-security coherence strengthens the ledger. Spending on broad institutional positioning, defensive legal architecture or ever more elaborate participation structures may be justified, but it also can expand the institution's control surface. Members should not treat those categories as morally settled. They should ask which risks are being reduced for the market and which risks are being reduced mainly for ARIN.

The economics-style test is simple. Does a dollar spent by ARIN reduce uncertainty for operators, holders, buyers, sellers and dependent customers? Or does it increase the institution's ability to manage, delay, interpret and condition their choices? Many expenditures will do both. That is why board judgement matters. An election that does not discuss budget theory is not fully testing the institution.

Policy agenda and the cost of voice

ARIN's policy process is a real institutional asset. The PDP provides public discussion, Advisory Council shepherding, staff and legal review, last call, board adoption, petitions and emergency or suspension mechanisms. The Public Policy Mailing List is archived. Proceedings are published. These structures make quiet capture harder and allow outsiders to see how policy ideas move through the institution.

But openness is not the same as equal influence. Policy discussion rewards people who can afford to read long threads, understand precedent, attend meetings, write in registry vocabulary and participate over time. Large organisations can amortise this cost through staff, counsel or consultants. Brokers and specialised market participants can follow the rules because their business depends on them. A small operator with customer churn, a one-off transfer buyer, a legacy holder seeking to avoid attention or a customer of a hosting network may not have the time or incentive to convert practical pain into policy text. The process can be open and still economically skewed.

The policy agenda therefore becomes an election issue. Board and Advisory Council candidates should be asked whether ARIN's public policy system has enough economic information to judge transfer, waiting-list, resource-review and service-access rules. The problem is not too much procedure. The problem is insufficient economics. A rule that affects liquidity should be accompanied by evidence about who pays, how large the friction is, what harm the rule prevents and whether the harm could be addressed by a narrower tool.

For transfers, relevant information includes processing times, documentation cycles, denial categories, abandonment patterns, inter-RIR bottlenecks and the practical reasons requests fail. For waiting-list policy, it includes time to fill, size distribution, later demand and the effect of lock-ups. For resource review, it includes triggers, outcomes, time to resolution and the difference between fraud cases and routine compliance cases. For legacy services, it includes how many holders use basic services, how many enter agreements for advanced services and what operational consequences attach to the difference. Confidentiality limits detail, but it does not prevent aggregate reporting.

The separation between policy text and implementation also deserves attention. Some of the most economically important issues may sit outside the main NRPM path: transfer-service levels, forms, fee schedules, staff timelines, RPKI or IRR access, contract language, data publication and customer support. If these matters are channelled through suggestions or consultations with less visibility than policy proposals, the public policy process can look more complete than it is. Elections should test whether candidates understand that policy agenda includes service and budget choices, not only manual text.

The cost of voice also explains why "community-developed policy" must be used carefully. The phrase is accurate in the narrow sense that policies pass through open procedures. It becomes misleading if it suggests consent by all affected parties. The active policy community is not the whole economic community. Board adoption is not public law. Member voting is not regional sovereignty. A policy can emerge from a recognised process and still require independent economic justification.

This is not an argument against public policy development. It is an argument for making it more accountable to consequences. A community process becomes more legitimate when it supplies more evidence to the present and asks less of the absent. ARIN already has the procedural machinery. The missing discipline is to make costs visible before they become policy habits.

Ledger versus gatekeeper

The ledger-versus-gatekeeper distinction is not anti-ARIN. It is pro-clarity. ARIN's indispensable work is ledger work: keeping unique records accurate, maintaining Whois and RDAP, supporting contactability, managing reverse DNS, recording recognised transfers, supporting routing-security data, validating points of contact and preventing fraud. The Internet needs that work, and the market needs it more after exhaustion because stale or false records now carry larger financial consequences.

The gatekeeper role begins when the registry uses its recognition layer to decide broader questions: whether a buyer's future need is adequate, whether a holder's business model fits allocation-era purpose language, whether a legacy holder should enter a broader agreement to obtain modern services, whether an out-of-region deployment has enough connection to the ARIN region, whether a waiting-list applicant's transfer history should delay access, whether a resource review should demand return, and whether a policy community's active participants can justify a rule that changes private liquidity. Some of these questions may be defensible. They are not neutral bookkeeping.

ARIN's NRPM contains both impulses. Registration principles point toward uniqueness, contactability and public record accuracy. Conservation and stewardship principles point toward allocation discipline and efficient use. During abundance, the mix was easier to defend. After exhaustion, the gatekeeper side requires stronger accountability because the relevant resource is often moving between private parties rather than being issued from a common pool.

A ledger-first ARIN would not abandon standards. It would still verify identity, authority and documentation. It would still require accurate contact data. It would still mark or handle disputes. It would still reject fraud and duplicate claims. It would still require clean evidence for transfers. It would still protect residual waiting-list space from obvious arbitrage. It would still obey applicable law. What it would reduce is open-ended business-need judgement in ordinary private transfers, service dependency that turns contract status into leverage, and discretionary review where record truth is not at risk.

A gatekeeper-first ARIN would see scarcity as a reason to preserve broad stewardship. It would argue that without needs assessment, transfers may enable hoarding; without resource review, underused resources may stay locked; without agreement requirements, holders may consume services without sharing costs; without candidate screening, unqualified trustees may endanger the registry. These arguments are not frivolous. The problem is that they all expand institutional discretion. The more discretion expands, the more board elections must be robust enough to legitimate it.

The right standard is proportionality. If ARIN imposes a gate, the board should be able to state the harm prevented, the evidence that the harm is real, the economic cost imposed, the narrower alternatives considered, the way affected holders can challenge decisions and the date or condition for review. A gate without proportionality becomes a habit. A habit wrapped in community vocabulary becomes mandate laundering.

Mandate laundering

Mandate laundering is the conversion of a limited technical function into a broader claim of authority through vocabulary, procedure and repetition. The function begins modestly: maintain a unique registry. The vocabulary expands: stewardship, conservation, region, community, technical need, fairness, public interest. Procedure then validates the vocabulary: mailing-list discussion, Advisory Council recommendation, board adoption, member election, staff implementation. The result may be a rule that looks neutral because it emerged from a recognised path, even if its practical effect is control over scarce capital.

ARIN is not uniquely guilty of this pattern. Technical communities often build institutions before the resources they administer become valuable. Early legitimacy comes from competence and trust. Later power comes from control of a scarce layer. The institution continues to use the vocabulary of competence and trust even after the economic stakes have changed. That is how administrative authority becomes political economy without fully admitting it.

Elections can interrupt mandate laundering or reinforce it. They interrupt it when members ask whether ARIN's authority remains tied to necessary ledger functions. They reinforce it when elections merely refresh trustees who repeat familiar language. A candidate who says "I support stewardship" may be saying something reasonable. A candidate who can explain what stewardship should not cover in a transfer-market world is offering a more useful form of accountability.

The risk is especially high around "community-developed policy". The phrase is true in a procedural sense. It can become laundering if it implies consent by all exposed parties. The active community is not identical to the economic community. The electorate is not identical to the full set of affected operators and customers. A policy can be procedurally developed and still impose costs on people who were absent, unaware, underrepresented or rationally silent.

Mandate laundering is also visible in the shift from "need" to "deservingness". Technical need sounds objective. In practice, a needs test can become an institutional judgement about whether a buyer deserves recognition of a transfer. The buyer's willingness to pay, customer commitments, growth plans and risk-bearing capacity are treated as insufficient unless they fit a policy form. This may prevent some abuse. It may also substitute registry judgement for market judgement. The board's job is to distinguish the two.

Official narrative should therefore be treated as evidence of how ARIN understands itself, not as the authority that frames the conclusion. The fact that a registry says it is a steward tells us something about institutional culture. It does not answer whether a transfer delay is proportionate, whether a contract boundary fairly allocates risk, whether legacy certainty is protected or whether the member franchise can discipline board discretion. Legitimacy must be earned in those concrete decisions.

The most legitimate version of ARIN would be comfortable with a narrow mandate. It would say: we maintain the registry; we verify transfers; we protect uniqueness; we provide publication and security services; we run a transparent policy process; we avoid turning administrative necessity into economic command. That version of ARIN would be harder to mythologise and easier to trust.

What a legitimate ARIN election should test

A legitimate ARIN election in the post-exhaustion era should test more than resumes. It should test institutional theory. Does the candidate believe ARIN should remain a broad steward of number-resource use, or should it move toward a ledger-first role wherever possible? Does the candidate understand IPv4 transfer markets as an unavoidable scarcity response, or as a regrettable development to be constrained? Does the candidate see legacy resources as historical anomalies to be normalised, or as a distinct boundary that must be respected for trust? Does the candidate view needs assessment as an enduring fairness principle, or as an allocation-era tool that should shrink when resources move through private transactions? Does the candidate treat budget growth as member service, continuity investment, risk defence or institutional expansion?

The election should also test the institution. Can candidates raise these questions without being treated as destabilising? Can Voting Contacts distinguish reform from incompetence? Can the petition route permit dissent while filtering bad-faith candidacies? Can the Board's guidance identify needed skills without pre-selecting institutional continuity? Can assessment distinguish genuine conflicts from candidates who challenge the current model? Can campaign communication rules allow enough substance for members to make an informed choice?

The ideal board is not an anti-ARIN board. It is a board capable of defending ARIN by narrowing ARIN where necessary. Institutions often try to preserve legitimacy by expanding language: more stewardship, more community, more consultation, more mission. In scarcity systems, legitimacy may require the opposite: fewer claims, clearer boundaries, narrower discretion, better reporting and a sharper distinction between record integrity and market control.

For members, the practical implication is direct. Voting is not only about personalities. It is about who decides how ARIN interprets scarcity. A trustee who understands transfer-market economics may ask different questions about sections 8.3 and 8.4. A trustee who understands legacy history may ask different questions about RSA boundaries. A trustee who understands balance-sheet risk may ask different questions about liability and enforcement. A trustee who understands small-operator dependence may ask different questions about waiting-list rules and minimum block sizes. A trustee who understands institutional design may ask different questions about nomination architecture and campaign limits.

That is why member power matters despite its limits. General Members cannot represent every exposed party, but they can make ARIN more accountable to the economic reality around the registry. They can reward candidates who speak precisely about enforcement, budgets, transfer friction and legacy certainty. They can penalise candidates who rely only on comforting words. They can ask the Board to publish more usable data. They can require policy impact to be discussed in operational and economic terms, not only procedural support.

The election should also test the Advisory Council because policy agenda is part of registry power. Advisory Council members influence how proposals are shepherded, revised, advanced or abandoned. A council that thinks in allocation-era categories will handle transfer rules differently from one that sees transfer liquidity as a central post-exhaustion issue. Members should not treat Advisory Council votes as secondary housekeeping. They are part of the same legitimacy chain.

A practical legitimacy standard

ARIN's legitimacy should be judged by a demanding but fair standard. First, the registry must maintain a reliable ledger: unique records, accurate contacts, sound technical services, secure systems, orderly transfers and resilient operations. Second, any gatekeeping beyond ledger protection must be explicit, proportionate and reviewable. Third, elections must give General Members a meaningful opportunity to influence enforcement posture, budget priorities, policy agenda and election architecture. Fourth, ARIN must not confuse active process participation with consent by all exposed parties. Fifth, the Board must recognise that post-exhaustion IPv4 scarcity has converted many registry decisions into economic decisions.

This standard does not require ARIN to become a pure market registry overnight. IPv4 markets can create problems: fraud, concentration, opaque leasing chains, stale records, poor routing-security hygiene and transfers that do not map cleanly onto operational reality. A responsible registry must address those risks. But the answer cannot be unlimited preservation of allocation-era discretion. The answer is narrower: protect the ledger, publish the rationale for gates, measure the cost of friction and let members vote on candidates who understand the trade-off.

The legitimacy risk for ARIN is not sudden collapse. It is quiet overreach. A stable institution can slowly accumulate discretionary control because its language sounds responsible and its procedures are orderly. The registry says "stewardship" while the market hears "approval risk". It says "technical need" while buyers hear "conditional liquidity". It says "community-developed policy" while many exposed parties hear nothing. It says "membership election" while dependent customers have no role. None of these phrases is necessarily false. Each is incomplete.

Board elections are where the incompleteness can be corrected. Not perfectly, and not alone, but materially. A member electorate that understands ARIN's economic role can choose trustees who demand better boundaries. A board that understands its incentives can resist the temptation to turn every risk into more discretion. A nomination system that understands legitimacy can let serious dissent reach the ballot. An Advisory Council that understands transfer economics can ask whether a policy's market effects are proportionate. Staff operating under clear board direction can implement rules with discipline rather than institutional drift.

ARIN's North American stability makes this achievable. The institution has published rules, elections, budgets, professional staff, policy forums and a comparatively mature legal environment. It does not need a crisis to reform. It needs elections that treat governance as control over a scarcity layer.

The public record gives readers enough to continue the scrutiny. The most important exhibits are ARIN's Board of Trustees page, Elections page, Election Processes document, Membership page, Policy Development Process, Number Resource Policy Manual, Transferring IP Addresses & ASNs guide, IPv4 Addressing Options page, Legacy Resources at ARIN page and Strategic Planning & Budgeting page. The counter-frame can be read in Lu Heng's notes on NRS and decentralisation and registry-layer structural risk, in NRS's public explanation of its purpose and in LARUS's continuity-focused IPv4 leasing position.

Those exhibits point to the same institutional question. ARIN's board elections matter because the registry is no longer just administering a technical queue. It is supervising a record layer tied to scarce, valuable and operationally embedded resources. The election question is therefore not whether ARIN has a community. It does. The question is whether that community, through member power, board incentives and policy oversight, can keep the registry from mistaking control for legitimacy.