ARIN's Mission Statement Is Not a Delegation Instrument

Summary

• ARIN's public mission explains the work it intends to perform and the constituency it says it serves. It is strong evidence of institutional direction, but it is not legislation, a treaty or a contract signed by every network in the region.
• Virginia law creates the nonstock corporation and supplies general corporate powers. ARIN's Articles of Incorporation define its purposes, while its Bylaws allocate authority among members, the Board, the Advisory Council, officers and staff.
• The Registration Services Agreement is the principal instrument that turns institutional purpose into holder-specific rights and duties. Version matters: ARIN says an existing holder is not required to sign a later RSA merely because a new form is published.
• A defensible adverse action should identify the applicable agreement, the exact obligation, the facts establishing breach, the notice and cure path, the operational consequence and the available review route. Invoking stewardship or mission cannot fill a missing step.

The sentence on the wall and the clause on the page

Mission statements are useful because institutions need a concise answer to a broad question: what are we here to do? They guide strategy, budgets, hiring, service design and public explanation. They allow a board to decide whether an initiative belongs within an organisation's work. They can discipline an executive team that drifts away from the corporation's declared purpose. None of that is trivial.

The trouble begins when a sentence written for direction is asked to perform the work of an instrument written for obligation. ARIN describes itself as supporting the operation and growth of the Internet by managing and distributing Internet number resources, coordinating policy development and conducting outreach. Its official welcome page also says that the Board maintains authority over scope, mission, strategic direction and fiscal oversight, while the President and staff execute that direction. Those statements tell readers a great deal about institutional design. They do not tell a particular holder what contractual term it breached or why a registry service may be stopped.

The distinction is easiest to see in an ordinary dispute. Suppose ARIN believes a holder has supplied inaccurate information, failed to pay, violated a service term or ceased to exist as a legal entity. The mission may explain why ARIN cares about accurate records or conservation. It cannot establish that the alleged fact occurred. It cannot identify which version of an agreement applies. It cannot choose between notice, cure, suspension, termination, revocation or restoration. It cannot determine which forum hears a disagreement. Each of those steps requires a more specific source.

This is not a claim that ARIN lacks power. ARIN is a functioning Virginia corporation with express purposes, internal organs, agreements and technical services. Holders who enter an RSA accept substantial duties and consequences. The point is one of legal and institutional hygiene: broad purpose must not be used as an all-purpose reserve whenever the operative documents are narrower, inconvenient or silent.

That hygiene protects ARIN too. An institution that can trace a decision from corporate capacity to a valid agreement, a defined obligation, evidence, notice and review is easier to defend than one that falls back on stewardship language. Mission is strongest when it remains in its proper place: at the beginning of the authority chain, not as a substitute for every link that follows.

Three categories that public debate keeps merging

The first category is organisational direction. ARIN's mission belongs here. It tells the Board and staff what the institution is trying to accomplish. It is relevant to strategy and budget, and it helps outsiders understand why the organisation operates a registry, supports policy discussions and provides related services. Direction can be broad because it must cover work over time.

The second category is corporate purpose and capacity. ARIN's Articles of Incorporation and the Virginia Nonstock Corporation Act belong here. The Articles identify a Virginia nonstock corporation, list purposes and invoke statutory powers. The Act supplies the background rules for a corporation of that form. Together, these materials answer whether ARIN exists as a legal person and whether an activity is within the field it may pursue.

The third category is an obligation binding a particular holder. The current Registration Services Agreement, version 14.0, is central here for those who signed it. It defines Included Number Resources, services, fees, holder responsibilities, policy treatment, termination, arbitration and the treatment of later forms. An older RSA or a different agreement may govern another holder. A legacy record may present yet another history. That is why the applicable instrument cannot be assumed from the latest PDF alone.

These categories interact, but they do not collapse. Corporate capacity allows ARIN to enter agreements; it does not prove that every operator agreed. A signed agreement creates bilateral duties; it does not turn every recital into public legislation. A mission can guide the Board's interpretation of institutional priorities; it does not expand unambiguous contractual language by declaration.

The practical test is simple. When an action is proposed, ask which category supplies each proposition. If the proposition is that ARIN should improve data quality, mission and strategy may be sufficient. If the proposition is that the corporation may operate registry services, the Articles, Bylaws and Virginia law matter. If the proposition is that a named holder must do something by a date or lose a defined service, the applicable agreement and service terms must do the work.

What the 1997 formation documents actually establish

ARIN's formation history is unusually accessible. Its corporate page identifies an original filing dated 18 April 1997 and amendments dated 19 June and 7 August 1997. The consolidated HTML states that the corporation was formed under the Virginia Nonstock Corporation Act, would have members as provided in the Bylaws and would have no authority to issue capital stock. These are legal characteristics, not public-relations claims.

The seventh article contains a substantial purposes list. It includes increasing public knowledge, educating industry, representing the Internet community, managing and conserving scarce Internet protocol resources, encouraging solutions to number scarcity, supporting portability and competition, managing allocation and registration, and promoting Internet infrastructure. It also invokes the general and emergency powers available under Virginia law. This is a serious corporate-purpose text. ARIN's registry role is not an invention of a recent marketing page.

Yet the same text reveals the boundary. It is a filing by which a corporation defines the activities for which it is formed and the powers it may exercise as a corporation. It does not bear the signatures of every current resource holder. It does not identify every number resource covered by a service relationship. It does not state the full notice sequence for nonpayment, the current rules for transfer review or the dispute mechanism applicable to an RSA termination.

The Articles therefore answer a capacity question: may this corporation manage and register Internet number resources as part of its purposes? The answer is plainly yes. They do not answer a holder-liability question: has this holder accepted this obligation, and may this consequence follow now? Answering that requires the governing agreement and facts.

This distinction also prevents an error in the opposite direction. Critics sometimes say that because ARIN is not a government agency, its role is merely fictional. The Articles refute that overstatement. Private corporations can hold property, enter contracts, operate systems, provide services and enforce valid agreements. The absence of sovereign delegation does not erase corporate or contractual capacity. It limits the kind of claim that can be made for it.

The accurate conclusion is narrower and stronger. ARIN has an express corporate purpose to perform registry work. It has the ordinary legal capacities of its form. Those facts establish institutional competence, not a free-standing jurisdiction over every network or every record in a geographical description.

Nonstock form is not territorial jurisdiction

Virginia's statute gives nonstock corporations a legal framework. It addresses formation, powers, members, directors, records, amendments, combinations, dissolution and judicial proceedings. That framework matters whenever the question concerns ARIN's corporate life: whether a body acted with corporate authority, whether a member vote met the governing requirements, whether records must be available, or whether an amendment was validly adopted.

The Act is general. It applies to many corporations organised for very different purposes. It does not name ARIN as a public regulator. It does not assign Canada, the United States or Caribbean territories to a Virginia corporation. It does not convert a service region into governmental territory. The service region describes where ARIN performs its recognised registry role; it is not a jurisdictional clause enacted by all the states and countries within that region.

That difference matters for language such as responsibility, stewardship and regional authority. These words may accurately describe an operational role within the coordinated number-registry system. But operational recognition and statutory jurisdiction are different things. The first may arise through history, coordination, technical reliance and contract. The second normally requires a legal source capable of granting public power.

Section 501(c)(6) language should also be kept in proportion. ARIN's Articles invoke the United States tax category used for business leagues. The restriction helps describe permissible organisational form and the treatment of earnings. It does not certify democratic representation, establish public-law accountability or prove assent by nonmembers. Tax status answers a tax question.

This is why labels cannot complete an authority analysis. “Nonprofit” does not mean powerless, and it does not mean sovereign. “Member-based” does not mean every affected operator is a voting member. “Regional” does not mean territorial government. “Community-driven” does not identify the legal effect of a particular vote. Each label may be true in its proper sense while becoming misleading if used to answer a different question.

The Bylaws govern ARIN, not the whole region

ARIN's Bylaws translate the formation document into a working governance system. Their purpose and mission provisions connect the corporation to registry operations and an open policy-development process. Other articles define membership classes, member rights, the Board, the Advisory Council, officers, elections, committees and amendment procedures. That is the constitution of an organisation, not a statute for a continent.

The membership provisions are particularly clarifying. General Members are entities with a valid RSA or LRSA that meet eligibility requirements and pay applicable fees, while Service Members also have an agreement and pay fees but do not vote in ARIN elections. General Members in good standing have specified voting and discussion rights. The structure is real, but it is bounded. Contracting for service, qualifying for general membership, remaining in good standing and voting are distinct statuses.

Open policy participation is distinct again. A person may contribute to a policy discussion without being a General Member. An affected network may not participate at all. A General Member may be eligible to vote but abstain. A Service Member may have resources under agreement but no election vote. The word “community” can cover all of these people in ordinary speech, but it cannot serve as a precise denominator for institutional consent.

The Bylaws also allow the Board to adopt, amend or repeal subsidiary policies and procedures consistent with the Articles and Bylaws. That is an ordinary and necessary governance power. A registry cannot operate if every procedure is frozen forever. But internal authority to adopt a policy does not answer every question about its effect on an existing agreement. Consistency with the Bylaws is one inquiry; incorporation into a holder's contract, notice of the change and lawful application are others.

A Board vote therefore proves what it actually proves: the authorised corporate body took an institutional decision under the governing rules. It can set strategy, adopt procedures and oversee management. It does not retroactively make every affected party a voter, and it does not eliminate the need to identify a contractual bridge when a decision imposes a holder-specific burden.

This is not a criticism of boards as such. Corporate organs are indispensable. The discipline is to describe the scope of their acts accurately. A board resolution can authorise ARIN as a corporation. It cannot manufacture the external assent that an agreement requires.

Mission is an internal instruction with external significance

It would be equally mistaken to dismiss mission language as empty branding. ARIN's mission can have genuine effects. It can guide fiduciary decision-making, define strategic priorities, shape which projects receive funds and influence the interpretation of ambiguous internal policies. It can be evidence that an action was taken for a proper corporate purpose rather than for an unrelated private interest.

Mission also gives members a basis for accountability. If the Board spends heavily on activity unrelated to the organisation's purposes, members can ask why. If management abandons core registry services in favour of peripheral projects, mission becomes relevant to oversight. If a policy is challenged as inconsistent with the Articles or Bylaws, purpose language may help frame the dispute.

That significance still differs from direct obligation. A mission statement generally addresses the institution in the first instance: ARIN supports, manages, coordinates and advances. A holder's duty requires a different grammatical and legal structure: the holder shall pay, maintain, notify, secure, comply or refrain. The actor changes, the condition changes and the consequence changes.

This grammatical point is more than style. Institutions often move from “we are responsible for stewardship” to “therefore you must accept this consequence” without exposing the missing middle. The middle may exist in the RSA. If it does, citing it strengthens the decision. If it does not, mission language cannot create it simply because the desired outcome seems aligned with institutional purpose.

The safest public explanation would state the chain directly. ARIN's purpose authorises the corporation to operate the relevant service. The Board or staff has authority under a named governance provision. The holder accepted a named agreement. A specified service term creates the duty. Evidence shows the condition occurred. The agreement permits a stated response after stated notice. A defined review route is available. That explanation makes power legible.

The RSA is where the relationship becomes specific

The current RSA demonstrates why specificity matters. Version 14.0, dated 15 August 2025, defines Included Number Resources and the services ARIN provides. Subject to the agreement and service terms, it grants the holder specified contractual rights, including the exclusive right to be registrant of those resources within ARIN's database and the right to use them within that database. It also allocates responsibilities for account security, information, fees and compliance.

Those clauses are far more useful in a dispute than a mission sentence. They identify the parties, the covered resources and the exchange. They tell a holder what ARIN promises and what ARIN expects. They can be read with the facts of a particular account. They also provide language against which an arbitrator or court can test performance.

The RSA makes a careful statement about rights: the holder acquires express contractual rights to the Included Number Resources by virtue of the agreement. Whatever larger debate may exist about the legal character of number resources, that clause gives the parties a defined contractual starting point. It is neither a grant of sovereign title nor a claim that the holder has no enforceable interest.

The agreement also distinguishes different consequences. For fee delinquency, it describes notices, stopping services, possible termination and revocation after specified conditions. It provides routes by which services may be restored or resources may, if not reissued, be restored after payment and signature of the then-current agreement. Elsewhere it defines termination for cause and a dispute mechanism. Those details show why “ARIN may act under its mission” is an inadequate account.

Version 14.0 also restricts a particular policy consequence. It says ARIN generally will not reduce services or revoke Included Number Resources for lack of utilisation, while allowing review when the holder requests a transfer or additional resources and permitting refusal of those requests where utilisation does not comply with policy. That is a precise allocation of power. A broad conservation purpose should not be read to erase it.

Versioning is a governance fact, not clerical detail

The latest RSA is not automatically the agreement for every holder. ARIN's own RSA FAQ says organisations are not required to update when ARIN publishes a new version, except in the stated circumstance of a change in legal status. Version 14.0 likewise says there is no requirement for a holder that signed it to engage in a subsequent version.

That fact changes how an adverse decision must be audited. It is not enough to open the current PDF and find a useful clause. The analyst must identify the agreement actually governing the holder at the relevant time. Older versions may allocate rights, amendment mechanisms, liability, notice and dispute resolution differently. A later clarification may be attractive without being binding on an earlier signatory.

Version diversity also creates an institutional transparency need. ARIN does not publish a complete public denominator showing active resources by RSA version, legacy status, government modification and no-agreement status. Without that information, outsiders cannot know how uniform the contractual population really is. A policy described as universal may reach holders through different legal paths.

The history of legacy agreements illustrates the point. The FAQ says the Board ended the legacy maintenance-fee cap introduced with the LRSA, that the cap ended on 31 December 2023 and that from 1 January 2024 legacy resources brought under agreement are covered by an RSA and current plan fees. This explains current administration, but it does not mean every legacy record has always been under the same agreement.

A sound decision record should therefore preserve at least six items: agreement type, version, execution date, covered resources, incorporated terms as of the relevant date and any authorised modification. That is not legal ceremony for its own sake. It is how both sides know which promise is being enforced.

Policies can change without making consent disappear

Registry policy must evolve. Fraud methods change, routing-security services develop, transfer practices mature and contact expectations shift. A workable RSA cannot reproduce every operational rule in its signed pages. Incorporation of policies and service terms is therefore unsurprising.

But dynamic policy creates a recurring accountability question. By what mechanism does a later rule become part of an existing holder's obligations? The answer may lie in the RSA's incorporation and amendment language. It may differ by version. It may depend on notice, consultation, a Board act or the character of the change. The answer is not simply that policy was discussed openly.

Open participation can improve the quality and legitimacy of a rule. It lets operators identify technical errors, exposes distributional effects and creates a public record. It does not make every entity a principal for every absent holder. Nor does it make attendance equivalent to contractual assent. Policy process and contract formation are different mechanisms even when they are deliberately connected.

The distinction matters most for sanctions. A policy can define expected conduct. The RSA can incorporate policy. Staff can find noncompliance. A separate provision may authorise suspension, refusal, termination or revocation. Notice and review may then apply. Each step should be shown. Otherwise a broad reference to “policy” conceals whether the consequence was actually authorised.

This method avoids two extremes. It does not freeze policy at the date of original allocation, which would make registry administration unworkable. It also does not let institutional process become a blank cheque. Change remains possible, but the legal route by which change reaches a holder remains reviewable.

Adverse action should be decomposed into verbs

The phrase “resource action” can conceal several acts. ARIN might reject a request, stop a service, lock account access, decline to create a routing-security entity, terminate an agreement, revoke a registration, return a record to legacy status, restore a service or reissue resources. These acts have different practical effects and may rely on different clauses.

Fee delinquency in version 14.0 provides a concrete example. The agreement does not describe one instantaneous leap from unpaid invoice to disappearance. It describes payment duties, a delinquency notice, stopping services, a six-month condition for termination and revocation, and possible restoration before or after revocation under stated conditions. The sequence makes proportionality and cure visible.

Termination for cause requires another analysis. What is the asserted cause? Which clause makes it material? What notice was delivered, by which permitted method, and when? Did a cure period apply? Did the holder dispute the action through the route identified in the agreement? What happens to legacy resources and nonlegacy Included Number Resources if termination stands? A mission statement cannot answer any of these questions.

Separating verbs also exposes third-party effects. Ending access to an account is not necessarily identical to changing a registry record. Changing a registry record is not necessarily identical to invalidating every route originated by an operator. RPKI, IRR, reverse DNS and Whois-related services may respond differently. A decision letter should identify the system consequence rather than using one broad word.

This is important because registry data is relied on beyond the two contracting parties. Network operators, counterparties, security teams, transfer entities and customers may respond to a record change. Contractual authority can still justify the change, but wider reliance raises the standard for notice, reasons, sequencing and reversibility.

The strongest case for ARIN's discretion

ARIN cannot run a registry as if every holder possessed an unconditional veto. Accurate contact and organisational data matter. Fees fund services. Fraud can corrupt the record. A holder's dissolution, merger or loss of authority can require action. Routing-security systems cannot remain trustworthy if credentials and control claims are never checked. Operational staff need discretion to evaluate evidence and act.

The Articles expressly include management and conservation of Internet protocol resources. The Bylaws allocate authority and create governance bodies. The RSA imposes real duties and provides serious consequences. Members elect institutional bodies, and policy development is open to participation. This is a stronger foundation than an organisation operating through unpublished custom alone.

Moreover, the absence of governmental delegation does not make voluntary obligations optional. A holder that signs an RSA cannot answer every enforcement action by saying ARIN is not a state. Private agreements bind precisely because parties can create enforceable duties without legislation. Courts and arbitration routinely give effect to such arrangements, subject to applicable law.

The best defence of ARIN is therefore documentary, not mythic. It should say: the corporation is authorised to provide the service; this holder entered this agreement; this obligation applies; these facts establish failure; this notice was given; this consequence is proportionate and permitted; this remedy remains. That is more persuasive than saying ARIN acts for the Internet community.

The same documentary defence places limits on discretion. Staff judgement must remain attached to a condition in the governing terms. The Board's strategic authority does not erase a contractual restriction. An open policy process does not cure defective notice in an individual case. Institutional necessity cannot be presumed whenever the agreement provides a narrower route.

Government holders reveal the contractual nature of the system

ARIN's FAQ notes limited accommodations where a government entity is legally unable to accept standard provisions concerning matters such as indemnity, governing law or arbitration. This is a revealing practice. It shows that the relationship is built through legal instruments encountering the law of the contracting party, not through a uniform command descending on every holder in the region.

Government modifications should not be romanticised as fully negotiated equality. ARIN still administers a standardised service and has significant practical leverage. Nor do special forms for public bodies tell us what modifications ordinary private holders can obtain. The public record does not provide a complete list of government variations and their legal bases.

Still, the existence of accommodation proves an important point. The instrument matters. Governing law matters. Capacity to consent matters. A clause may need adjustment because another legal rule prevents acceptance. If mission alone supplied obligation, these negotiations would be unnecessary.

The practice also suggests a transparency opportunity. ARIN could publish a redacted matrix of categories of approved modification, the type of legal barrier, the agreement version and the effect on remedies. It need not reveal confidential government advice. A matrix would help other holders understand whether the nominally standard agreement has materially different accountability paths.

More broadly, cross-border holders may operate under local corporate, insolvency, sanctions, data, telecommunications and administrative laws. The RSA's chosen law and dispute provisions matter, but they do not make every foreign mandatory rule vanish. Mission language contributes nothing to resolving those conflicts. Careful contracting does.

Remedies are part of authority, not an afterthought

An institution's power is easier to trust when the person affected can obtain reasons and challenge application. Version 14.0 includes dispute provisions and an arbitration route for identified matters. That route is a real constraint, though its practical accessibility depends on cost, location, timing, available relief and the holder's ability to preserve operations while the dispute proceeds.

The agreement should not be described as if arbitration were a general constitutional court. An arbitrator acts under the agreement and the assigned dispute. Corporate-law questions, claims involving third parties or mandatory legal rules may require a court. Internal reconsideration, member governance and policy reform are different remedies again.

The remedy must match the act. A holder challenging a staff finding needs access to the factual record and the clause applied. A member challenging a Bylaw amendment needs the corporate adoption record. A network objecting to future policy may use the policy process. A party alleging breach of contract may invoke the agreement's route. Treating “community discussion” as the answer to an immediate termination would confuse prospective policy with individual relief.

Operational timing also matters. A remedy that arrives after records, credentials and customer relationships have been irreversibly disrupted may be formally available but practically weak. High-impact actions should therefore consider stays, staged effects, preservation of records, emergency review and restoration mechanics. The RSA contains some cure and restoration features, but public data do not show how they work across cases.

The central accountability proposition is straightforward: the more serious the consequence, the more explicit the authorising clause, factual reasons, notice and review should be. Mission supplies none of those details. It can explain the public value of enforcement, but not excuse an absent remedy.

The denominator ARIN does not yet publish

Public documents reveal possible authority. They do not show how authority behaves in aggregate. ARIN could make its governance more measurable by publishing annual counts of warnings, service stops, terminations, revocations, restorations, disputes, arbitrations, reversals and court proceedings, separated by ground and agreement category.

The counts should distinguish nonpayment, inaccurate records, unauthorised control, fraud, dissolution, transfer-related review, policy noncompliance and other grounds. They should distinguish current RSA versions, older versions, legacy histories and government-modified forms where disclosure is safe. They should show median notice periods, cure rates, time to review and restoration outcomes.

No confidential holder dossier is required. Aggregated data and carefully anonymised case summaries would be enough. Such disclosure would allow members to determine whether severe powers are exceptional, routine, concentrated or frequently corrected. It would also allow ARIN to demonstrate consistency rather than merely assert it.

The missing denominator affects claims of community accountability too. The Bylaws identify who may vote, but the public should be able to compare eligible General Members, ballots cast, Service Members, contracted holders and affected resource organisations over time. Open policy participation can then be reported separately. This would prevent one denominator from being substituted for another.

Measurement is not hostility. It is the bridge between written governance and experienced governance. If adverse actions are rare and carefully reversed when wrong, the data will strengthen ARIN's legitimacy. If a category produces repeated disputes or restoration, the data will show where terms or procedures need repair.

A practical authority test for any ARIN decision

The first question is identity: which legal entity is acting, and which legal entity or person is affected? Similar names, affiliates, predecessors and operational contacts should not be treated as interchangeable. The record must connect the actor and holder to the relevant account and resources.

The second question is instrument: which Articles, Bylaws provision, Board resolution, agreement version, service term or policy applies? A citation to the current website is limited public evidence if the dispute arose under an older version. The governing text should be preserved as it stood on the relevant date.

The third question is condition: what event triggers the power? Nonpayment, misrepresentation, failure to maintain information, bankruptcy, dissolution and policy noncompliance are not synonyms. Evidence should be matched to the condition rather than to a general suspicion that action is desirable.

The fourth question is consequence: what exactly may ARIN do? It may refuse a new request, stop a service, terminate an agreement or revoke covered resources only as the applicable terms provide. The decision should not use a narrower power as a rhetorical bridge to a wider effect.

The fifth question is procedure: what notice method, time period, cure opportunity, escalation and approval are required? Compliance with substance does not cure a missing procedural step where the step forms part of the bargain.

The sixth question is remedy: who can review the decision, what standard applies, can effects be stayed, and what restoration is possible? A remedy should be communicated with the decision, not discovered after the deadline.

The seventh question is external effect: which registry, RPKI, IRR, reverse-DNS or public-data changes will follow, and which third parties may rely on them? This final question ensures that an internal contract action is not described as though its operational consequences were invisible.

What can be said with confidence, and what remains unknown

The public record supports several firm findings. ARIN is a Virginia nonstock corporation. Its formation file includes the April, June and August 1997 documents. Its Articles expressly include number-resource management and conservation among its purposes. Its Bylaws separate mission, membership classes, Board powers, advisory functions and policy procedures. The current RSA is version 14.0 dated 15 August 2025. ARIN says existing holders generally need not adopt a later RSA merely because it is published.

The record also supports a firm negative finding: none of those facts turns the welcome-page mission into a statutory delegation. The mission page is an official institutional description. It can accurately explain ARIN's role while remaining neither legislation nor a signed agreement.

Important questions remain unanswered. ARIN does not publish the population of resources and holders by agreement version and status. There is no complete public series of adverse actions and outcomes. The materials reviewed here do not include a judicial or arbitral holding that decides whether mission language may expand a particular RSA obligation. They do not show how often staff cited mission rather than an operative term in contested decisions.

Those unknowns limit the claim. It would be wrong to say ARIN has in fact used mission language unlawfully in every disputed case. It would also be wrong to say the document stack eliminates all ambiguity. The evidence supports a method and a boundary, not a verdict on unseen files.

That restraint is essential. Institutional criticism becomes credible when it distinguishes what documents prove, what they suggest and what must still be obtained. The mission-delegation distinction should itself be applied with the evidentiary discipline it demands from ARIN.

The finding: purpose begins the chain but cannot finish it

ARIN's mission is legitimate organisational language. It describes a real registry role and gives the Board and staff a direction. Its Articles provide strong corporate purposes. Virginia law supplies a legal person and corporate powers. The Bylaws establish member and governance machinery. The RSA creates specific rights and duties for the holder that accepted it. None of these layers is imaginary, and none should be forced to do the work of all the others.

The line that matters is between authority over the corporation and obligation imposed on a holder. ARIN's Board can direct ARIN within its governing instruments. Members can exercise the rights the Bylaws give them. Policy entities can contribute evidence and shape proposals. A holder can accept enforceable duties by contract. These are meaningful forms of authority and participation, but they have different principals, procedures and limits.

When the institution seeks a serious operational consequence, the analysis should move away from nouns such as stewardship, community and responsibility. It should identify verbs: who may require, suspend, terminate, revoke, restore or review; under which version; on what evidence; after what notice; with what effect; and subject to which remedy.

That approach does not weaken registry administration. It makes administration durable. Operators can plan when obligations are knowable. Members can supervise when corporate acts are distinguishable from service enforcement. Staff can defend decisions when the applicable clause and evidence are visible. Courts and arbitrators can review a record rather than a slogan.

The mission statement belongs at the beginning of the story. It tells ARIN what kind of institution it seeks to be. The delegation question begins where that statement ends. For every holder-specific burden, the decisive evidence is not the aspiration on the wall but the authority, agreement, condition, procedure and remedy on the page.