ARIN and the economics of agenda-setting power

Summary

• Before an ARIN proposal has a title, the first label attached to a scarce-number problem can decide which evidence matters, which forum hears the issue and which remedies remain thinkable.
• The dispute begins before it has a title.

The first label before the proposal

The dispute begins before it has a title. A transfer request has taken longer than the parties expected, and the people around it are already describing different problems. One participant says the delay is anti-fraud diligence: old records, stale contacts and signer authority must be checked before a scarce IPv4 block moves. Another says it is liquidity friction: a buyer has capital committed, customers waiting and a closing timetable that becomes more expensive each week. A small operator says it is a new-entrant barrier, because the same extra document that a national network can produce in a day may take a thinly staffed ISP a month. A legacy holder says it is certainty protection, because historical records should not be casually disturbed. Staff see implementation risk. A lender sees settlement uncertainty. A customer sees continuity.

No policy text has been posted. No chair has ruled on scope. No Advisory Council motion has been made. No Board review is pending. Yet the argument has already entered its most important stage. The community is fighting over the first label.

That label decides which later answers sound natural. If the issue is fraud, the reasonable remedy is more proof. If the issue is liquidity, the reasonable remedy is faster recognition. If the issue is new-entrant access, the reasonable remedy is a lower fixed burden for smaller networks. If the issue is legacy certainty, the reasonable remedy is safe harbour for old records and clearer reliance rules. If the issue is administrative efficiency, the reasonable remedy is simpler forms and staff guidance. If the issue is institutional legitimacy, the reasonable remedy is public metrics, review rights and a record that explains the trade-off.

Agenda-setting power is the power to make that first classification before formal procedure begins. In ARIN, it is not a sinister force outside governance. It is an unavoidable part of governance. Every scarce-number dispute must first be described as some kind of problem. The description may be fair, partial or self-interested. It may come from a policy author, a staff note, a member concern, a consultation question, a Board question, a transfer participant, a security practitioner, a legacy holder or a customer-facing network. Once the description is accepted, it starts selecting the evidence, the forum, the affected class and the remedy menu.

This is why agenda-setting can matter more than the later vote. A vote, consensus call or adoption decision usually acts on an issue that has already been named. If the name is too narrow, some costs will never reach the decision. If the name is too broad, remedies may become more intrusive than the problem requires. If the wrong forum hears the issue, affected parties may be absent. If the wrong evidence is treated as decisive, good data may become irrelevant. The policy record can look orderly while the first move remains hidden.

ARIN's post-exhaustion environment makes this especially important. The registry sits near scarce IPv4 capacity, transfer recognition, legacy-resource treatment, public registration data, reverse-DNS continuity, RPKI and routing-registry reliance, fee exposure, member accountability and customer continuity. These are not separate moral worlds. A single dispute can touch several at once. The first label decides whether the cost is read as market friction, abuse prevention, operational continuity, member rights, administrative load or an off-point complaint. That is agenda-setting power.

Agenda-setting is upstream institutional power

Agenda-setting power has five parts. It is the power to name the problem, choose the forum, define the evidence, identify the affected class and set the remedy menu before formal procedure begins. Each part can be defended as ordinary institutional work. Together they form a control surface that deserves explicit attention.

Naming the problem is the obvious part. A transfer-delay complaint can be named as fraud prevention, liquidity failure, staff-capacity shortage, legacy uncertainty, unfair burden on small networks, unclear policy text, member-service quality, or insufficient public reporting. None of those labels is automatically false. Each captures one piece of reality. The danger is allowing one label to become the whole reality before the community has seen what it excludes.

Choosing the forum is the less visible part. The same concern can be sent to the Policy Development Process, staff practice, the Consultation and Suggestion Process, member consultation, Board oversight, legal review, fee discussion, technical service work or public education. Forum choice decides who is likely to appear, which vocabulary is rewarded and what proof is useful. A policy forum can change text. A staff-practice discussion can clarify implementation. A fee process can alter incidence. A Board question can demand metrics. A legal review can identify authority and risk. A technical service discussion can solve a dependency without reopening the policy bargain. If a concern is placed in the wrong forum, it may be rejected not because it lacks merit, but because the forum cannot hear it well.

Defining evidence is equally powerful. A fraud frame invites anecdotes about forged authority, compromised accounts, false documents and stale contacts. A liquidity frame invites transfer timing, failed closings, settlement uncertainty and discount evidence. A new-entrant frame invites testimony from smaller networks and first-time buyers. A legacy-certainty frame invites corporate-history records, reliance evidence and service-boundary examples. A public-reliance frame invites customer effects, RDAP and Whois dependency, reverse-DNS continuity and security reliance. The selected frame does not merely organize evidence. It ranks it.

Identifying the affected class decides whose welfare counts. A rule may affect transfer buyers, transfer sellers, legacy holders, small ISPs, cloud platforms, universities, public networks, lenders, brokers, downstream customers, staff, General Members, Service Members and non-member relying parties. If the frame says the problem is member discipline, indirect customers may disappear. If it says the problem is market liquidity, staff capacity and fraud exposure may disappear. If it says the problem is public trust, private settlement cost may sound secondary. The affected class is not a footnote. It is the political economy of the issue.

Setting the remedy menu is the final and most consequential part. By the time text is drafted, some remedies already feel reasonable and others feel strange. Tighter documentation, faster transfer paths, clearer status codes, safe harbours, review rights, public metrics, staff guidance, Board review, fee changes, member consultation and new policy text are all possible remedies for different versions of the same problem. The agenda setter does not need to ban remedies. It only needs to make them sound irrelevant.

Agenda-setting therefore happens before chair discretion. Chair discretion manages ambiguous signals after a topic has entered a procedural channel. Agenda-setting decides what the topic is, where it goes and which signals will count in the first place. That distinction matters for ARIN because a mature, orderly procedure can still inherit a bad frame.

Scarcity makes the frame expensive

Scarcity is the reason the first label carries economic weight. In a world with abundant IPv4 supply, a slow or burdensome process might be irritating but not structurally decisive. A network could often seek more addresses through ordinary allocation, renumber with less penalty or wait without turning delay into a balance-sheet question. That world is gone. IPv4 is still operationally necessary for many customers, applications, security systems, mobile networks, hosting platforms and transition architectures. ARIN's free pool exhaustion did not end demand. It changed the channels through which demand is satisfied.

After exhaustion, ARIN policy and practice sit closer to transfers, waiting-list scarcity, legacy holdings, routing-security dependence, public records and contractual reliance. A delay in registry recognition can affect a closing. An unclear legacy-service boundary can affect whether a holder signs an agreement or remains outside it. A documentation rule can change whether a smaller network can participate in a transaction at all. A fee or good-standing rule can become a settlement condition. A service-eligibility rule can influence RPKI readiness, routing-registry entries or reverse-DNS continuity. A public record can become part of due diligence, credit analysis, customer confidence and abuse-response routing.

Scarcity also turns uncertainty into a price. A buyer will pay less for a block whose transfer path is uncertain. A seller will accept a higher escrow burden if registry recognition is unpredictable. A lender will discount address capacity if the record is difficult to verify. A customer will demand continuity assurances if a provider's address supply depends on a pending registry step. A small network may delay expansion because it cannot afford the risk of starting a transfer that may stall. These effects can appear without any formal denial, revocation or disciplinary action. Delay, ambiguity and forum choice are enough.

That does not mean every friction is illegitimate. Fraud prevention is valuable precisely because scarce records are worth attacking. A forged transfer or compromised account can harm honest holders and honest buyers. Legacy certainty matters because old allocations may have thin paper trails but real operational reliance. Public records matter because networks, counterparties and security teams need a reliable reference layer. Staff capacity matters because rules must be implementable. Fees matter because the registry must fund reliable services. Member accountability matters because a private nonprofit with critical registry functions needs discipline from those who depend on it.

The scarcity problem is that all these goods can be invoked against each other. Fraud control can justify documentation that slows liquidity. Liquidity can justify speed that weakens record assurance. Legacy certainty can protect reliance or entrench incumbency. Public reliance can support transparency or expose holders to new burdens. Administrative efficiency can reduce delay or narrow review. Fee fairness can discipline costs or underfund service quality. Member accountability can improve legitimacy or overweight the active governance class. Institutional legitimacy can require restraint, but it can also be used to defend institutional self-protection.

The first frame therefore has distributional value. It decides which cost is treated as the main harm and which cost is treated as the acceptable side effect. A fraud frame sees delay as prudence. A liquidity frame sees delay as deadweight loss. A new-entrant frame sees documentation burden as exclusion. A legacy frame sees the same burden as respect for history. A staff-efficiency frame sees complexity as operational drag. A public-reliance frame sees incomplete records as a social cost. Because the same fact can support several frames, ARIN needs a way to expose the choice before the frame becomes common sense.

One dispute can wear many labels

A mature agenda-setting analysis should not pretend that only one frame is legitimate. ARIN's strength will come from making several plausible frames visible at once and forcing the community to say which one governs the decision.

The stewardship frame begins from uniqueness, accurate records and responsible administration of scarce number resources. It is powerful because ARIN's registry function is real. Without reliable uniqueness, contactability, transfer recognition and service continuity, the market around addresses becomes less trustworthy. Stewardship favours caution, evidence and orderly change. Its risk is elasticity. If stewardship is allowed to mean every desirable outcome, it can justify broad discretion over matters that should remain outside the registry's narrow function.

The fraud-control frame begins from the danger of forged authority, compromised accounts, false corporate succession, stale contacts and attempts to move resources without valid control. It favours tighter documentation, stronger authentication, targeted pauses and more careful staff review. Its risk is suspicion creep. A complicated history, a commercial transfer, a brokered sale or a legacy record can look messy without being fraudulent. Fraud language has moral force; it should be tied to testable signals.

The liquidity frame begins from the cost of moving scarce capacity to networks that value it. It favours faster transfer paths, clearer requirements, predictable timing, status visibility and fewer avoidable rounds of review. Its risk is underweighting the public cost of bad recognition. A market cannot be liquid if counterparties doubt the record. Speed without assurance is not efficiency; it is a different form of risk.

The new-entrant access frame begins from the uneven burden placed on smaller or first-time networks. It favours plain guidance, proportionate documentation, clear pre-checks, predictable fees and safe paths for organizations without dedicated registry staff. Its risk is romantic simplification. Some new entrants are genuine infrastructure builders; some may be thin vehicles for speculative positioning. The frame needs evidence rather than sentiment.

The legacy-certainty frame begins from historical reliance. Many resources in the ARIN region carry old records, old corporate histories and agreement boundaries that do not match today's account systems. This frame favours continuity, safe harbours, careful proof maps and respect for last verified operational state. Its risk is incumbent optionality. Legacy certainty can protect real networks, but it can also preserve advantages for holders that face fewer modern burdens than later entrants.

The administrative-efficiency frame begins from the cost of running the process. Staff must interpret policy, review documents, maintain systems, answer tickets, avoid inconsistency and keep services functioning. This frame favours simpler rules, clearer forms, standard categories and guidance that reduces case-by-case judgment. Its risk is internalization. The easiest process for the registry may not be the least costly process for the affected market.

The public-reliance frame begins from the fact that ARIN's records and services are used by people beyond the account holder. RDAP and Whois lookups, reverse-DNS delegation, routing-security relationships, transfer logs, public notices and service states can influence buyers, lenders, security teams and customers. This frame favours publication reliability, clear status codes, continuity safeguards and aggregate reporting. Its risk is over-publication or over-signalling in ways that create market penalties before a matter is resolved.

The security-continuity frame begins from RPKI, routing-registry support, reverse DNS, account security and the operational dependencies built around them. It favours strong authentication, resilient systems, continuity during disputes and service-specific eligibility rules. Its risk is using security vocabulary to settle non-security choices. A security dependency may require narrow safeguards; it does not automatically justify broad control over resource use.

The fee-fairness frame begins from who pays for registry capacity and who benefits from it. It favours cost transparency, member-visible budgets, fee incidence analysis and service categories that do not shift disproportionate burden onto smaller networks. Its risk is starving the function or treating every registry cost as suspect. Reliable records, security and publication require money.

The member-discipline frame begins from the membership system as a check on ARIN power. It favours member consultation, election accountability, clearer service-to-governance rights and performance data. Its risk is mistaking the active member or policy class for the whole affected economy. Service Members, indirect users and downstream customers may depend on ARIN without voting or appearing in governance forums.

The institutional-legitimacy frame begins from trust in ARIN itself. It favours reasoned records, visible trade-offs, auditability, independent review, and restraint where registry power touches market value. Its risk is becoming too abstract unless tied to concrete mechanisms. Legitimacy is not a slogan; it is a design question about reasons, metrics, rights and remedies.

These frames overlap. A good policy may need several. But overlap is exactly why the first label matters. If the community sees only one label, the policy will price only one harm.

Evidence follows the label

Evidence does not enter a debate neutrally. It is filtered by the frame that tells participants what kind of proof matters.

Under a fraud-control frame, the strongest evidence is concrete and episodic: forged letters, inconsistent signatures, old contacts used by the wrong person, suspicious login patterns, contested succession documents, transfer attempts by non-holders, account compromise, conflicting claimants and staff examples of failed proof. Such evidence is valuable. It explains why a registry cannot simply approve every request that arrives with a contract attached. But it can also crowd out evidence about ordinary transactions. A small number of dramatic fraud cases can make every messy file look suspect unless the evidence distinguishes fraud from complexity.

Under a liquidity frame, the strongest evidence is aggregate and transactional: processing times, staff-response time separated from applicant-response time, repeated documentation rounds, abandoned transfers, escrow extensions, discount patterns, buyer financing delays, failed closings and timing uncertainty. That evidence can show deadweight loss. But liquidity evidence can understate why the review exists. A fast path that increases bad recognition may reduce visible delay while raising hidden risk.

Under a new-entrant frame, the strongest evidence is testimony from networks with limited staff, small balance sheets, thin legal support or first-time contact with ARIN. It includes time spent understanding requirements, inability to produce old corporate proof quickly, cost of counsel, difficulty interpreting status, and the need to coordinate registry steps with customer launches. Such evidence is often anecdotal because small networks may not have large datasets. Treating only large datasets as valid evidence can exclude the very group the frame is meant to reveal.

Under a legacy-certainty frame, the strongest evidence is historical: old allocation records, corporate succession, predecessor names, mergers, operating continuity, service use, prior ARIN communications and reliance by customers and counterparties. It often requires tolerance for imperfect archives. The risk is that historical evidence can become a shield against reasonable modernization if the process never asks which reliance deserves protection and which burden is still proportionate.

Under an administrative-efficiency frame, the strongest evidence is operational: ticket volume, staff hours, repeated support categories, unclear form fields, system limitations, implementation cost, inconsistent interpretation and delays caused by ambiguous policy language. That evidence should matter because staff cannot run rules that are impossible to administer. But staff burden should not be the only cost ledger. A rule that makes staff review easier by shifting uncertainty to buyers and sellers may look efficient internally while raising external cost.

Under a public-reliance or security-continuity frame, the strongest evidence includes service incidents, RDAP and Whois lookup dependence, reverse-DNS delegation failures, RPKI support patterns, routing-registry update issues, customer-impact cases and security-team reliance on public status. This evidence brings indirect parties into view. It also requires careful handling because not every service dependency should become a reason to expand policy power.

Under a fee-fairness or member-discipline frame, the strongest evidence includes budgets, reserves, service metrics, member categories, participation rates, Voting Contact maintenance, Service-to-General conversion and consultation response. This evidence tests whether ARIN's accountability system can discipline the costs it imposes. It should not replace the technical and operational evidence, but it should prevent registry expense and member authority from being treated as background.

The purpose of a better agenda-setting process is not to choose one evidence class forever. It is to require an evidence matrix before the issue hardens. If the proposed frame is fraud control, what liquidity evidence is still relevant? If the proposed frame is liquidity, what fraud evidence is still relevant? If the frame is new-entrant access, what staff burden and legacy certainty evidence must be checked? If the frame is public reliance, what private settlement cost should still be acknowledged? The matrix should not make the debate longer for its own sake. It should stop one kind of evidence from pretending to be the whole record.

The remedy menu narrows before text appears

The most practical reason to care about agenda-setting is remedy narrowing. A bad frame does not need to produce bad intentions. It produces a short menu.

Call the problem fraud, and the menu will naturally include tighter documentation, officer acknowledgements, multi-factor checks, longer staff review, targeted transfer pauses, stronger audit trails and stricter account control. Those may be exactly right for forged authority. They may be excessive if the real problem is unclear status communication or missing guidance for ordinary transfers. A fraud menu tends to treat delay as an acceptable price of safety.

A liquidity label points in the opposite direction: faster paths, pre-clearance, clearer requirement lists, service-level reporting, status codes, shorter review loops, standard closing evidence and predictable transfer timing. These may be exactly right for routine transactions. They may be insufficient where stale records or contested authority create real risk. A liquidity menu tends to treat proof burden as suspect.

Frame the question as new-entrant access, and plain-language guides, lower fixed proof costs, tiered documentation, advisory office hours, template evidence, fee-sensitive paths and post-implementation review of small-network use move to the front. These may be right where process complexity excludes smaller providers. They may not solve a dispute dominated by legacy chain-of-title uncertainty or deliberate abuse.

A legacy-certainty opening favours safe harbours, reliance-preserving status, last-verified-state protection, review before service disruption, clear agreement boundaries and a proof map for old corporate histories. These may protect continuity. They may also reduce pressure on old holders to maintain current records unless paired with accuracy duties.

An administrative-efficiency frame brings standardization, staff guidance, simplified forms, clearer internal categories, automated checks and limits on discretionary interpretation. These can reduce errors and cost. They can also become internal convenience if the measure of success is staff smoothness rather than external predictability.

Public reliance makes a different set of instruments plausible: public metrics, clearer status flags, aggregate reporting, continuity safeguards and published rationales for high-consequence states. These can reduce information asymmetry. They can also create reputational harm if status language is too broad or too early.

Fee fairness pushes fee changes, cost allocation, service category review and budget disclosure into view. These may address real incidence. They will not necessarily solve the policy or service problem that created the cost.

Member accountability usually reaches for member consultation, election attention, General Member reporting, participation metrics and Board questions. These may discipline the institution. They may leave non-member relying parties without a voice.

Institutional legitimacy, finally, draws reasoned records, independent review, affected-party registers, explicit exclusions and post-implementation metrics toward the centre. These can strengthen trust. They can also be too general unless tied to specific decisions.

The remedy that disappears is often the one that matters. A fraud frame can make safe harbours sound reckless. A liquidity frame can make documentation sound protectionist. A staff-efficiency frame can make public metrics sound burdensome. A member frame can make customer continuity sound indirect. A legacy frame can make new-entrant access sound impatient. Remedy narrowing is not a later accident. It is the first label doing its work.

ARIN does not need a process in which every possible remedy is debated to exhaustion. It needs a visible reason why one remedy family was selected and another was rejected. If the remedy is tighter documentation, the record should explain why faster status visibility, safe harbours or review rights were not enough. If the remedy is faster transfer processing, the record should explain why fraud controls remain adequate. If the remedy is public metrics, the record should explain what privacy or confidentiality costs are controlled. That explanation belongs upstream, before text hardens.

Forum choice changes the participants

Forum choice is agenda-setting in institutional form. A problem can be described correctly and still lose substance if sent to the wrong place.

The Policy Development Process is the right forum when the issue is the rule itself: eligibility, transfer criteria, allocation policy, resource status, or language that governs number-resource treatment. Its strength is public deliberation over text. Its weakness is that it can be slow, high-cost and dominated by those who can track policy over time. It is not always the best forum for implementation clarity, fees, legal interpretation or service performance.

Staff practice is the right forum when the issue is how an existing rule is implemented: forms, guidance, status communication, ticket handling, evidence categories, support scripts and service timelines. Its strength is speed and operational competence. Its weakness is visibility. A staff-practice solution can reduce friction without changing policy, but it can also create de facto policy if it changes how burdens fall.

Member consultation is the right forum when the issue affects governance rights, service categories, institutional direction or the bargain between payers and the registry. Its strength is accountability to organizations that fund and depend on ARIN. Its weakness is representativeness. General Members, Service Members, legacy holders, indirect customers and relying parties do not have identical positions.

Board oversight is the right forum when the issue concerns risk appetite, executive metrics, aggregate transparency, resource allocation to staff, adoption discipline, legal posture or service-boundary strategy. Its strength is institutional authority. Its weakness is distance from ordinary affected parties. A Board can demand metrics and reasons, but it should not be a substitute for open policy debate where text is at stake.

Legal review is the right forum when the issue concerns authority, contractual boundaries, court orders, liability or enforceability. Its strength is discipline around risk. Its weakness is that legal caution may protect the institution while shifting cost outward. A legal answer is not automatically an economic answer.

Fee processes are the right forum when the question is who pays, how costs scale, whether service categories are fair and whether budget choices match registry duties. Their strength is incidence. Their weakness is that they cannot fix a bad transfer rule, a vague status code or a missing appeal path by themselves.

Technical service work is the right forum when the issue concerns RDAP, Whois, reverse DNS, RPKI, routing-registry support, account security or publication systems. Its strength is precision. Its weakness is tunnel vision. A technical fix may reduce operational risk while leaving the governance question unresolved.

Public education is the right forum when the issue is misunderstanding: what a status means, what evidence is required, how to prepare for a transfer, what member category provides voting rights, or how to maintain account authority. Its strength is low friction. Its weakness is that education can be used to avoid reform. If the process is genuinely too burdensome, explaining it better is not enough.

The forum should be chosen with reasons. A transfer-delay complaint might require policy text for eligibility, staff guidance for evidence lists, Board metrics for processing categories, and public education for preparation. Sending the whole problem to only one forum will hide part of it. A forum-choice rationale should therefore state what the chosen forum can decide, what it cannot decide and where the excluded parts will be handled. Without that map, "wrong forum" becomes a soft dismissal.

Moral vocabulary allocates virtue

Agenda-setting works partly through moral vocabulary. Words such as stewardship, abuse, liquidity, fairness, certainty, burden, public trust and efficiency do not merely describe. They allocate virtue.

Stewardship is the most powerful word in registry governance. It can mean care for uniqueness, accuracy and continuity. Used that way, it is indispensable. It can also mean institutional preference, caution without evidence, or discomfort with market movement. Once a proposal is named as stewardship, the opponent may sound reckless even when raising a valid cost.

Abuse has similar force. It can point to real harms: hijacking, forged authority, spam infrastructure, unreachable contacts, compromised accounts and bad-faith transfers. But abuse can also expand until it includes any behaviour the institution dislikes. If the word is used too broadly, a holder must first prove it is not part of the moral problem before its economic evidence is heard.

Liquidity sounds efficient and modern. It points to settlement confidence, reduced discount, movement of unused capacity and better use of scarce resources. But it can also understate why a registry must verify authority. If liquidity becomes the only virtue, fraud control and public reliance look like mere friction.

Fairness is attractive because scarce resources are distributed unevenly. Yet fairness can mean equal treatment of existing holders, support for new entrants, protection of small networks, comparable fee burden, historical reliance or regional development. Different fairnesses conflict. The first agenda setter often chooses which fairness counts.

Certainty sounds conservative in the best sense. It protects reliance, financing, customers and planning. But certainty for whom? Certainty for legacy holders may be uncertainty for entrants. Certainty for staff may be uncertainty for buyers. Certainty for public records may be reduced privacy or flexibility for account holders. The word must be unpacked.

Operational burden is another flexible phrase. Staff can use it to explain why a rule is hard to run. Operators can use it to explain why a requirement is hard to satisfy. A good agenda distinguishes internal burden from external burden instead of letting one claim cancel the other.

Public trust and institutional legitimacy can help ARIN discipline discretion. They can also become broad shields. A registry can claim that trust requires caution, when in fact trust may require speed, reasons, metrics or restraint. Trust is not one policy. It is the condition produced when affected parties can see the trade-offs.

A market-efficiency frame can expose deadweight loss. It can also obscure distribution, security and public-reliance costs. A purely efficient transfer path that raises fraud risk or weakens record certainty is not socially efficient. It is cheaper for some parties because others absorb the risk.

The remedy is not vocabulary policing. ARIN needs these words. The remedy is translation. Every moral term should be converted into a measurable claim. If stewardship is invoked, what record harm is being prevented? If abuse is invoked, what conduct is being addressed and by what evidence? If liquidity is invoked, what delay or uncertainty is being reduced? If fairness is invoked, which class is treated unfairly? If legitimacy is invoked, what review or reporting will improve trust? Translation turns virtue back into policy.

The beneficiaries are hidden in the frame

Every frame creates beneficiaries, even when the speaker intends only good governance.

A narrow fraud-control frame benefits parties that can produce documents quickly and tolerate delay. Large incumbents, sophisticated buyers, repeat transfer participants and well-advised legacy holders may handle the burden. Smaller networks, distressed sellers, public institutions with slow procurement, and first-time buyers may struggle. Staff benefit because stronger proof reduces the chance of bad recognition, but they may also inherit more review work.

A narrow liquidity frame benefits buyers, sellers, brokers, cloud platforms, acquisitive networks and anyone whose strategy depends on fast movement of scarce capacity. It may also benefit new entrants that need a predictable path. It can disadvantage holders exposed to forged claims if controls weaken, and it can burden staff if speed expectations rise without better systems.

A new-entrant frame benefits smaller ISPs, emerging providers, public networks and organizations with limited registry fluency. It can disadvantage incumbents if remedies reduce grandfathered certainty or expose unused holdings to pressure. It can disadvantage staff if every burden is treated as exclusion rather than proof protection.

A legacy-certainty frame benefits holders with old records, universities, enterprise networks, public agencies and organizations whose operational history began before modern agreements. It can disadvantage new entrants and buyers if legacy protection reduces available supply or preserves asymmetric burdens.

An administrative-efficiency frame benefits staff, frequent users of the system and participants who want predictable processing. It can also benefit the whole market if efficiency reduces uncertainty. But if efficiency means standardized burdens that ignore different capacities, small networks and unusual legacy cases may pay the price.

A public-reliance frame benefits customers, lenders, security teams, abuse desks, counterparties and downstream users who depend on trustworthy records and services. It can burden account holders if publication becomes too detailed or if status signals damage transactions before a matter is settled.

A security-continuity frame benefits networks that depend on RPKI, routing-registry support, reverse DNS and account security. It can burden holders outside modern service relationships or with complex authority histories if security prerequisites are not narrowly tailored.

A fee-fairness frame benefits parties currently overpaying relative to use or bearing costs created by others. It can disadvantage larger holders if fees shift toward resource scale, or smaller holders if flat service costs are defended as simplicity. It can disadvantage service quality if fee pressure is separated from reliability needs.

A member-discipline frame benefits General Members and active participants who can use elections, consultations and governance channels. It may leave Service Members, indirect users and customers with weaker representation. It can also discipline staff and Board decisions if the membership base is informed and engaged.

An institutional-legitimacy frame benefits the system as a whole when it creates reasons, metrics and contestability. It can disadvantage participants who profit from ambiguity: insiders who know how a practice really works, intermediaries who sell navigation, incumbents whose advantages are hidden in old categories, or staff habits that survive because they are not measured.

The point is not to accuse any beneficiary of bad faith. In specialized infrastructure, expertise and exposure often travel together. The broker may know transfer friction because the broker sees many cases. The large network may know implementation burden because it operates at scale. The small ISP may know entry cost because it feels every fixed requirement. The legacy holder may know historical reliance because it lives inside it. Agenda-setting becomes legitimate when the beneficiary map is visible enough that evidence can be weighed without pretending interests do not exist.

Why this is different from chair discretion

Agenda-setting and chair discretion are neighbours, but they are not the same thing.

Chair discretion begins after a matter has entered a meeting, list, consultation or policy channel. It concerns how ambiguous participation becomes procedural direction: whether a concern is in scope, whether the discussion has advanced, whether remaining dissent has been answered, whether a suggested change is small or large, whether a record should move to the next stage. It is necessary because open governance cannot operate without judgment.

Agenda-setting is earlier. It asks how the matter arrived as that kind of issue in the first place. Before anyone evaluates a concern, someone has usually decided whether the concern is about fraud, liquidity, access, legacy certainty, administrative efficiency, public reliance, security, fees, member discipline or legitimacy. Before a presiding person manages a discussion, someone has usually selected the forum. Before the community argues over text, someone has usually decided which evidence the text is meant to answer.

This difference is not academic. If a transfer-delay complaint is introduced as fraud risk, then later procedural management will naturally ask whether the fraud concern has been answered. If it is introduced as liquidity friction, later management will ask whether delay has been reduced. If it is introduced as small-network access, later management will ask whether fixed burdens are proportionate. The same procedural standard can produce different paths because the upstream frame changed the question.

That is why agenda-setting analysis sits before later procedural judgments about how a discussion should proceed. The problem is not how ARIN's procedural leaders translate a discussion once a frame exists. The problem is whether the frame itself was visible and contestable before the discussion became a process with momentum.

The distinction also protects procedure from being blamed for every hidden cost. A chair can manage a discussion well and still inherit a frame that made the wrong costs peripheral. Staff can implement a rule carefully and still implement a remedy chosen from a narrowed menu. The Board can review a record and still miss that the first label excluded the most important economic question. Agenda-setting analysis asks institutions to inspect the first move rather than overloading later procedural checks with work they are not designed to do.

ARIN's legitimacy depends on both disciplines. Chair discretion should be narrow, reasoned and reviewable. Agenda-setting should be plural, explicit and challengeable. The first prevents procedural judgment from becoming hidden allocation. The second prevents problem definition from doing the allocation before procedure begins.

AFRINIC is the warning, not the template

AFRINIC should be used carefully in an ARIN analysis. The institutions differ. ARIN does not occupy the same crisis posture, legal environment or recent governance history. It should not be described as if it were living another registry's breakdown. The caution is narrower: when trust falls, problem definition becomes factional weaponry.

In a low-trust registry, the first label is rarely received as neutral. A fraud frame is read as a pretext for control. A liquidity frame is read as a private asset strategy. A development frame is read as a political shield. A stewardship frame is read as institutional self-protection. A member-fairness frame is read as factional counting. A continuity frame is read as a bid for immunity. The same policy text that might be workable in ordinary times becomes harder to defend because each side assumes the other has already rigged the vocabulary.

That is the economic cost of low trust. Buyers, sellers, lenders and relying networks discount not only decisions, but also definitions. They price the risk that a registry will later redescribe a transaction as abuse, a reliance claim as speculation, a service request as leverage, or a policy concern as off-topic. Courts become more attractive because the internal vocabulary is no longer trusted. Public claims harden. Staff lose the benefit of the doubt. Every forum choice looks like a tactical move.

ARIN's advantage is that it can act before that condition. A stable institution can make agenda-setting contestable as ordinary discipline rather than emergency repair. It can require problem statements to show alternative labels. It can map affected parties before the loudest participants define the public. It can publish forum-choice reasons before losing parties claim they were sent to a dead end. It can collect frame-neutral metrics before every metric is treated as advocacy.

The AFRINIC warning is not that ARIN should fear every disagreement. Disagreement is healthy. The warning is that hidden problem definition becomes much more expensive after trust erodes. If the first label is not contestable in ordinary time, it will be litigated, politicized or discounted in bad time. The cheapest moment to discipline framing is before anyone needs it to win.

Making the first frame contestable

Agenda-setting power cannot be abolished. ARIN must begin with some description of every problem. The reform is to make the first frame visible enough that the community can challenge it before text, forum and evidence harden.

The first tool is an alternative-frame problem statement. A high-consequence issue should not arrive with only one official description. If the lead frame is fraud prevention, the intake record should also ask whether the matter could be liquidity friction, documentation burden, legacy certainty, staff-capacity shortage or public-reliance risk. If the lead frame is liquidity, the record should ask whether fraud control, record accuracy, customer continuity or fee incidence is also implicated. The author or sponsor may prefer one frame, but the record should show that alternatives were named.

The second tool is an impact map. Before remedies are debated, the process should identify likely affected groups: existing holders, transfer buyers, transfer sellers, small ISPs, new entrants, universities, public networks, cloud providers, brokers, lenders, downstream customers, staff, General Members, Service Members, legacy holders and public relying parties. The map should say who benefits, who pays, who can participate easily and who is likely absent. It should be concise, but it should exist.

The third tool is a forum-choice rationale. If an issue goes to policy, staff practice, consultation, Board oversight, legal review, fee process, technical service work or public education, the record should say why that forum is competent and what remains outside it. A concern sent away from one forum should not disappear. It should receive a destination.

The fourth tool is an evidence matrix. The matrix should state what evidence would matter under each plausible frame. Fraud signals, transfer timing, queue delay, small-network testimony, legal continuity, operational metrics, customer effects, budget effects, participation metrics and public-confidence indicators do not need equal weight in every case. They should be listed so that rejecting one evidence class becomes a reasoned choice rather than an accident of vocabulary.

The fifth tool is a remedy map. It should list remedy families before one is selected: tighter documentation, faster paths, clearer status codes, safe harbours, review rights, public metrics, staff guidance, Board review, fee changes, member consultation, technical service changes, public education or new policy text. The final remedy can be narrow. But the record should show which remedies disappeared and why.

The sixth tool is an explicit exclusion note. Every frame excludes something. A fraud-control frame may exclude some liquidity cost. A liquidity frame may exclude some fraud concern. A member frame may exclude indirect customers. A staff-efficiency frame may exclude private settlement burden. Writing down "what this framing does not decide" is a simple way to prevent hidden foreclosure.

The seventh tool is frame-neutral metrics. ARIN should measure outcomes in ways that do not belong to only one side: transfer timing by category, documentation rounds, reason codes, review outcomes, service incidents, appeal or escalation use, participation by affected class, fee incidence and customer-continuity effects where they can be reported safely. Metrics reduce the reward for rhetorical framing because later claims can be checked.

None of this requires a new ideology. It is institutional hygiene for a post-exhaustion registry. The community can still make choices. The point is that it should know which first move it is making.

A constructive agenda-setting test for ARIN

A practical test can be applied whenever an ARIN issue touches scarce IPv4 movement, legacy treatment, public records, routing-security services, reverse DNS, fees, member accountability or customer continuity.

The first question is: what is the first label? The label should be written plainly. Is the problem fraud prevention, liquidity friction, new-entrant access, legacy certainty, public reliance, security continuity, administrative efficiency, fee fairness, member discipline, institutional legitimacy or something else? A label that cannot be stated is already doing hidden work.

The second question is: what alternative labels exist? The process should name at least the plausible competitors. A transfer delay can be fraud control and liquidity friction at the same time. A documentation rule can be record accuracy and small-network burden at the same time. A fee-linked service condition can be cost recovery and access barrier at the same time.

The third question is: who benefits from each label? This is not a search for bad faith. It is a map of incentives. If fraud is the label, who gains from slower review? If liquidity is the label, who gains from speed? If legacy certainty is the label, who gains from safe harbours? If member discipline is the label, who gains from using membership channels rather than public-reliance channels?

The fourth question is: what evidence becomes central? The answer should include both the evidence the preferred label elevates and the evidence it risks marginalizing. A process that cannot say what evidence would change its mind is not testing a frame; it is defending one.

The fifth question is: what forum is chosen? The answer should identify the forum, the reason and the limits. If the forum is policy, what implementation questions remain? If the forum is staff practice, what policy questions remain? If the forum is Board oversight, what public participation question remains? If the forum is legal review, what economic incidence question remains?

The sixth question is: what remedies disappear? If faster paths are rejected, why? If tighter documentation is rejected, why? If public metrics are rejected, why? If safe harbours are rejected, why? The missing remedy often reveals the real frame.

The seventh question is: what costs are excluded? This is the hardest and most useful question. The record should say whether the frame excludes private settlement cost, staff burden, customer continuity, fraud risk, fee incidence, small-network participation, legacy reliance, public-record reliance or member accountability. Exclusion is not always wrong. Hidden exclusion is the problem.

The eighth question is: how can the framing be challenged before text hardens? There should be a defined moment for participants to contest the problem statement, the forum, the evidence matrix and the remedy map. Challenging the frame should not require opposing the whole goal. A participant should be able to say, "fraud is real, but this is also a liquidity problem," or "liquidity is real, but this remedy creates public-reliance risk."

The ninth question is: what review will test the frame later? If the issue was framed as fraud control, did fraud indicators improve? If it was framed as liquidity, did transfer timing and settlement uncertainty improve? If it was framed as new-entrant access, did small networks use the path? If it was framed as staff efficiency, did external cost fall or merely move? If it was framed as legitimacy, did confidence become measurable through participation, lower dispute rate or clearer records?

This test would not make ARIN slower by default. It would make speed and caution more honest. It would also reduce the burden on later procedural actors. A chair does not have to repair an invisible frame if the frame was contested at intake. Staff do not have to guess whether a remedy was meant to solve fraud, liquidity or access if the record says so. The Board does not have to infer cost incidence from a procedural summary if the impact map is already there.

The legitimacy question is the first move

ARIN's post-exhaustion legitimacy will not be decided only by the quality of its final policy text. It will be decided by whether affected parties can see the first move that made the final text seem reasonable.

The first move is often quiet. It is the sentence that says a delay is diligence rather than friction. It is the meeting notice that sends a concern to policy rather than staff practice. It is the consultation question that asks members about service quality but not indirect customers about continuity. It is the staff note that asks for evidence of fraud but not evidence of settlement cost. It is the Board packet that treats a metric as operations rather than market confidence. It is the education page that explains a burden without asking whether the burden should exist.

Each of those moves may be defensible. The problem is not that ARIN must never choose a frame. It must. The problem is when the choice is invisible. Invisible framing lets policy choices appear more inevitable than they are. It lets private costs look like market friction in one debate, abuse prevention in another, operational continuity in another, member rights in another, administrative efficiency in another and off-topic complaint in another. The same cost moves between moral categories without a public account of why.

A visible framing process would make ARIN stronger. It would protect staff from the suspicion that implementation preferences are being smuggled into policy. It would protect policy authors from the charge that their problem statements hide distributional effects. It would help the Advisory Council and Board see whether a record reflects real trade-offs or only the vocabulary of the first participant to name the issue. It would help small operators, legacy holders, buyers, sellers, public networks and customers know when their evidence belongs in the discussion.

The final legitimacy question is therefore simple: can ARIN let the community contest the frame early enough that policy choices reflect visible trade-offs rather than a hidden first move?

If the answer is yes, agenda-setting power becomes part of accountable governance. The first label is still powerful, but it is not sovereign. Alternative labels are visible. Evidence is plural. Forum choice is reasoned. Remedies are compared. Exclusions are named. Later procedure inherits a stronger record.

If the answer is no, the first label will keep doing the real work. Formal process will remain open, but open around a narrowed question. Participants will argue over text while the remedy menu has already shrunk. Staff will implement rules whose underlying frame is contested. The Board will review records that do not show what was excluded. The market will price ARIN governance as a risk layer because it cannot tell whether a cost was weighed or merely defined away.

Agenda-setting power is unavoidable. The choice is whether ARIN treats it as a hidden privilege of whoever names the problem first, or as an explicit discipline of a registry whose records and services now sit inside scarce-resource economics. In the post-exhaustion era, the first label is not just language. It is the beginning of allocation.