Summary

  • Number Resource Society is a global non-profit membership and advocacy organisation. Its legitimate rulemaking role is to represent bounded member mandates, campaign, research, publish model proposals and convene scrutiny—not to allocate Internet number resources, maintain an authoritative registry, issue RPKI credentials, accredit service providers, decide appeals or direct an institutional handoff.
  • The binding and operational layers remain distinct. RIR communities make regional allocation and registration policy; the NRO coordinates the RIR system and global proposals; IANA performs recognised global numbering functions; RIR technical teams operate RDAP, RPKI and registration systems; courts and authorised review bodies decide matters within their jurisdiction.
  • “A contract with exit” is therefore an advocacy test. NRS can ask whether a rule is necessary, whether affected operators can contest it, whether records and service can survive institutional failure, and whether an incumbent has converted technical dependence into political captivity. The responsible institutions must answer, adopt and implement any remedy.
  • NRS will be most credible when it applies the same discipline to itself: disclose whom it represents, separate member instruction from research judgment, publish sources and conflicts, explain how mandates can be withdrawn, and never market a proposed portability architecture as a service or authority it already operates.

Begin with the institutional boundary

The phrase “NRS rulemaking” can mislead if it is read as a claim that Number Resource Society writes binding rules for Internet number resources. It does not. NRS describes itself as a global non-profit membership organisation that campaigns, empowers and supports businesses and operators. That role can be influential because organised evidence and representation affect public debate, elections, consultations and the quality of institutional reform. Influence is not the same as delegated authority.

The organisations that hold operational responsibility are identifiable. Regional Internet Registries allocate and register number resources under their regional policies and service arrangements. Their communities develop those policies through established processes. RIR staff operate registration databases, RDAP, reverse-DNS support, RPKI services and other technical systems. The Number Resource Organization coordinates among the RIRs and supports global policy processes. IANA manages globally recognised number-resource functions within its remit.

None of those responsibilities transfers to NRS because NRS publishes a campaign or represents members in a governance proceeding.

This distinction is not a reason to minimise NRS. It is the condition for taking it seriously. Advocacy is strongest when the advocate can state what it knows, whom it represents, which institution must act and how the public can judge the response. An organisation that exaggerates its formal authority weakens its evidence. An organisation that maps authority precisely can expose where responsibility is being avoided.

The contract with exit begins at this boundary. NRS can press institutions to justify dependence, publish model safeguards and organise operators around a reform demand. It cannot create a recognised transfer, change the authoritative ledger or appoint a successor operator by declaring that the result should exist. The campaign and the implementation must remain connected, but they must never be confused.

Advocacy can be part of rulemaking without becoming the rulemaker

Public rules rarely emerge from one constitutional moment. They are shaped by proposals, evidence, technical review, member pressure, board decisions, implementation reports, litigation and repeated interpretation. An advocacy organisation can participate throughout that chain. It can identify a recurring harm, commission research, draft model language, submit comments, support affected operators, compare institutional responses and preserve a public record of promises against results.

That is a meaningful form of rulemaking participation. It changes which problems reach an agenda and which evidence decision-makers must confront. It can improve the bargaining position of smaller operators that cannot sustain permanent policy staff. It can connect a technical incident to a broader governance pattern. It can also make procedural language legible to members who would otherwise encounter a rule only when service is at risk.

But participation does not erase constitutional allocation. APNIC policy is made through the APNIC policy-development process and implemented by APNIC within its authority. Equivalent regional rules follow the processes of AFRINIC, ARIN, LACNIC and RIPE NCC. Coordinated global policy follows the recognised RIR and NRO path before reaching IANA implementation. Technical specifications require engineering adoption and testing. Legal rights depend on applicable law, contracts and competent adjudication.

NRS should therefore describe its outputs accurately: an operator demand, a member mandate, an advocacy submission, a research report, a model clause or a proposed accountability test. Those labels are not modest disclaimers. They reveal the pathway through which a proposal could become legitimate and expose any institution that tries to treat consultation as consent without actually deciding.

Why exit belongs at the centre of the campaign

Number-resource governance combines public coordination with deep operational dependence. An operator may disagree with a registry decision yet remain dependent on the institution for accurate records, credentials, reverse-DNS delegation, transfer processing and recognised standing. Formal participation can coexist with practical captivity. A member may vote, comment and appeal while knowing that institutional rupture could threaten the continuity of its network identity.

NRS is well placed to campaign around that dependency because its public position emphasises operator control, ownership claims, decentralisation and resistance to concentrated authority. The strongest version of the argument does not promise that every registration can move immediately to a competing provider. It asks a more disciplined question: which elements of dependence are technically necessary for uniqueness, and which survive only because the incumbent has never been required to make continuity portable?

Exit is useful as a constitutional test even where immediate provider substitution is not available. A rule should disclose whether it increases switching cost, concentrates credentials, makes data non-exportable, ties unrelated conduct to essential service or allows an institutional dispute to destroy a valid record. The answer can reveal mission expansion long before an operator attempts to leave.

NRS can turn that test into a campaign method. For each proposed rule, it can publish an exit-impact question, gather operator evidence and ask the responsible RIR or coordinating body to explain mitigation. The institution still decides the rule. The advocate makes the cost of dependence visible and ensures that “technical necessity” cannot remain an unsupported conclusion.

Source of truth means an evidence discipline

BTW and NRS can share a reform position without treating advocacy claims as self-proving. A source of truth is credible because it separates observed fact, member testimony, institutional record, analysis and proposal. It links readers to the governing document, identifies uncertainty and corrects the record when better evidence appears. Alignment should increase that discipline, not relax it.

For NRS, the first source is its own public identity. Its website, charter, membership terms, campaign materials and disclosed appointments show what the organisation says it does. Those materials support describing NRS as a non-profit membership and advocacy organisation. They do not support describing it as the NRO, a recognised RIR, a registry operator, an RPKI certification authority, an accreditation body or an appeals court.

The second source is the official institutional record. RIR bylaws, policy manuals, service agreements, election records and technical documentation establish who decides and operates regional services. NRO materials establish the coordination and global-policy framework. IANA documentation identifies global numbering functions. Court orders and corporate records establish legal control where relevant. These sources may support an NRS criticism, but they do not become evidence that NRS possesses the powers they describe.

The third source is member experience. Operators can show delay, cost, uncertainty, inaccessible review or continuity risk that formal documents do not reveal. NRS can aggregate that evidence responsibly, protect confidential details and disclose sampling limitations. The combination of official record and grounded experience allows advocacy to become more than rhetoric while keeping institutional identity exact.

Representation needs a visible mandate

An advocacy organisation gains influence by speaking collectively. That creates a duty to explain the collective. “Operators believe” is not a sufficient evidentiary phrase when operators have different business models, jurisdictions, resource histories and risk exposure. NRS should state whether a position comes from a formal member vote, a board decision, a consultation sample, appointed representation, casework, commissioned research or staff analysis.

The distinction matters because each source supports a different claim. A member resolution can authorise an advocacy demand. A case file can demonstrate a failure mode. A survey can estimate experience within a defined population. A legal opinion can interpret an instrument. A technical workshop can identify implementation constraints. None of them alone proves universal operator consent.

Mandates also need boundaries. If a company appoints NRS to represent it in RIR governance, the appointment should identify the forum, issues, duration and ability to revoke. Representation in a meeting does not transfer the company's registration relationship. A power to submit comments or vote where lawfully authorised does not make NRS the holder, registry or service provider. The public language should preserve those differences.

Exit applies internally too. A member should be able to leave NRS or withdraw a mandate without losing unrelated network-resource rights, because NRS does not own or operate those rights. Clear termination, data-return, complaint and conflict procedures demonstrate the principle NRS asks incumbent institutions to respect. Advocacy for freedom is more persuasive when representation itself is voluntary, legible and reversible.

The APNIC process shows where a proposal must go

The execution-plan anchor for this article is APNIC because APNIC's policy process offers a concrete example of how advocacy and authority should interact. A proposal can be drafted by a participant, discussed in a Special Interest Group, revised against objections, assessed for implementation and advanced through the recognised regional process. NRS can support members at each stage without claiming to replace that process.

It can help an operator document the problem statement, translate operational harm into policy language and identify affected groups. It can commission technical analysis before a meeting, publish a plain-language brief and convene an open workshop. During discussion, it can present evidence and answer questions about the member mandate. After a decision, it can compare implementation with the adopted text and record unresolved impacts.

APNIC, not NRS, would decide whether a regional policy reached consensus and would implement an adopted rule within its authority. APNIC technical teams would assess systems, data and operational effects. Where a proposal implicated global coordination, the regional and NRO processes would determine the next step. Where it affected IANA functions, the recognised global-policy route would apply.

This division makes advocacy more effective. It gives NRS a specific target, timetable and evidentiary burden. It also prevents an incumbent from dismissing the campaign as an attempt to build an unrecognised parallel registry. NRS can be forceful about the outcome while exact about the lawful path.

A map of actors prevents NRS–NRO confusion

The similarity of the initials creates a recurring editorial risk, but the organisations are not interchangeable. NRS is Number Resource Society, a membership and advocacy organisation. NRO is the Number Resource Organization, the coordinating body formed by the RIRs. The NRO's governance documents concern the recognised RIR system; they do not constitute an NRS charter or delegate NRO functions to NRS.

RIRs remain the regional institutions responsible for allocation, registration and associated services. Their communities hold regional policy authority through their own processes. The NRO coordinates among those registries, supports the Address Supporting Organization relationship and provides a path for coordinated global number policy. IANA implements globally recognised functions within the established framework.

Technical operators carry another layer of responsibility. RPKI certification, RDAP publication, database integrity, reverse-DNS delegation, key management, incident response and migration engineering require qualified teams, controlled systems and auditable procedures. An advocacy body may propose standards and scrutinise results, but it should never be described as performing these functions unless a separately recognised operational role is actually established and evidenced.

Courts, arbitrators and independent institutional review bodies form a fourth layer. They decide according to jurisdiction and delegated competence. NRS can support a member, fund research, publish an amicus-style argument or campaign for a better appeal. It cannot turn its preferred outcome into a binding decision. A precise actor map is the simplest protection against turning political alignment into invented authority.

The contract with exit is a public checklist

The word “contract” here should not imply that NRS has signed a multilateral registry covenant. It describes a model accountability checklist that NRS can advocate. The checklist asks institutions to state the bargain created by a rule: what coordination benefit it supplies, what dependence it creates, which parties carry the risk, how the rule can be challenged and what happens when a participant or institution leaves.

The first item is purpose. A proposal should identify the concrete failure it prevents. Duplicate registration, unverifiable provenance, insecure transfer, broken continuity or inconsistent recognition may justify coordinated action. Administrative convenience, reputational preference or a desire for political conformity is not enough. The institution proposing the rule must connect the measure to the failure.

The second item is scope. The responsible body should say which resource, record, service and decision the rule governs. A technical interface requirement should not become authority over unrelated speech or commercial conduct. An emergency continuity power should not become permanent administrative control. An evidence requirement should not become an unreviewable licence to reject disfavoured operators.

The third item is exit. The institution should explain whether records are exportable, credentials can transition, pending disputes remain visible, fees are bounded and service can continue during a lawful handoff. NRS can publish the answers and compare them across regions. It cannot itself certify that an operational handoff is safe.

Registration, allocation and advocacy must stay separate

Internet number resources depend on globally coherent recognition. Regional policy determines how resources are allocated, assigned, transferred and registered within the relevant framework. Registration systems record authoritative relationships and publish information needed by relying parties. These functions cannot be replaced by an advocacy database or a member declaration.

NRS may argue that an operator holds a stronger economic or governance interest than an incumbent contract acknowledges. It may campaign for ownership language, portability, clearer custody or limits on revocation. Those are political and legal propositions. They do not create a valid allocation, alter the recognised holder or authorise a route announcement.

The distinction protects NRS members. If advocacy language is mistaken for operational authority, a member may rely on a document that the wider system does not recognise. That can create conflicting claims, failed transactions or routing-security problems. Responsible advocacy should state where a proposed right remains aspirational and which recognised institution must act before an operator can rely on it.

It also protects the reform itself. Incumbents can dismiss a portability campaign if its language appears to promise an alternate registry that does not exist. Precision forces a harder response. An RIR must explain why a proposed export, review right or continuity safeguard is unsafe or impractical; it cannot answer merely that NRS lacks registry authority, because NRS has not claimed it.

RPKI, RDAP and technical continuity belong to operators

The operational surface of a registry relationship extends beyond a row in a database. RPKI credentials affect route-origin validation. RDAP and related publication systems provide registration information. Reverse-DNS services, authentication controls, transfer workflows and incident-response procedures can affect continuity. Any portability proposal must account for these dependencies.

NRS can research the dependency map and publish operator requirements. It can ask whether a credential can be reissued without a dangerous gap, whether historical status remains discoverable, whether contacts can be corrected during a dispute and whether a failed institution has tested restoration. It can convene engineers from different regions to challenge assumptions and document unresolved risks.

The design, operation and assurance of these systems remain with the RIRs, IANA where applicable, recognised successor operators and relevant technical communities. Key ceremonies, certificate issuance, repositories, authentication, service-level commitments and incident response require controlled operational authority. NRS should not be described as issuing, revoking, validating or migrating them.

This boundary does not make technical questions off-limits to advocates. It sets the standard for their work. A credible NRS report should name the responsible operator, cite the published procedure, distinguish a test result from a policy demand and invite technical correction. That makes public pressure usable by engineers rather than forcing them to begin by repairing the organisation chart.

Accreditation must not be invented by an advocate

A portable service model raises the question of who may receive records or operate a successor service. The answer cannot be a private NRS designation presented as globally authoritative. Recognition affects uniqueness, security and the rights of existing holders. Criteria must arise through the institutions that lawfully govern the service and must be accepted by the relying ecosystem.

NRS can campaign for fair, published qualification criteria. It can argue that an incumbent should not design eligibility solely to exclude competitors. It can commission comparative research on financial resilience, security controls, data protection, community accountability and continuity readiness. It can publish questions that every candidate and incumbent should answer.

Actual accreditation, recognition or appointment belongs to the relevant RIR, NRO and IANA processes, procurement authority, court or other competent body, depending on the function and trigger. Technical conformance testing should be performed by qualified, accountable operators or independent assessors under an adopted standard. Appeals need a body with delegated power to change the decision.

The advocacy test is whether the route to qualification is transparent, proportionate and contestable. The operational test is whether the candidate can preserve authoritative state and service. NRS can keep both tests visible while remaining outside the decision chain.

Appeals need independence and lawful power

An appeal is meaningful only if the reviewer can examine evidence, apply a known standard and provide an effective remedy. NRS may assist an operator in preparing a case, identify systemic patterns, publish anonymised findings or campaign for an independent forum. It is not itself the appeal authority merely because it represents the complainant.

The correct forum depends on the dispute. A policy-development complaint may belong in a regional process. A membership or service decision may follow an RIR's internal review and applicable contract. A corporate-control or insolvency question may require a court. A technical conformance dispute may need an expert review body. A global recognition question follows the relevant NRO and IANA framework.

NRS can improve this landscape by publishing a remedy map. Operators often encounter multiple channels without knowing which can pause an action, restore a credential, correct a record or award compensation. A source-backed guide can expose gaps, circular appeals and deadlines that make review fictional.

The campaign should seek remedies before harm becomes irreversible: notice, temporary preservation, access to evidence, reasoned decisions and a route to independent review. The institutions with lawful authority must enact and administer those protections. NRS's role is to make the absence visible and help affected members use the channels that exist.

NRO evidence is a comparator, not an NRS constitution

The NRO's RIR Governance Document is relevant because it discusses recognised RIR services, ongoing governance expectations, remediation, emergency continuity and possible derecognition. It shows that continuity and handoff questions already exist within the official RIR system. It does not show that NRS can recognise or derecognise a registry.

NRS can cite the document to ask whether operator protections are sufficiently explicit. It can compare the treatment of data, services, successor operation and affected users with its members' concerns. It can identify provisions that depend heavily on institutional discretion or lack public metrics. It can submit proposals through the appropriate regional or global consultation.

The decision chain remains official. The RIR communities and NRO framework determine governance obligations and recognition processes; IANA performs its defined role; qualified operators execute continuity. If a court order affects an institution, the lawful authority must also be integrated. NRS cannot generalise a comparator into its own jurisdiction.

This is the central correction to the old framing. NRO material is evidence about how the recognised system works. NRS material is evidence about the advocate's mission, membership, campaigns and proposals. The two can be analysed together without merging their identities.

Emergency continuity should be demanded before crisis

Institutional failure is the hardest test of any exit principle. Data may be inaccessible, keys may be disputed, staff may be unavailable and courts may impose conflicting constraints. Operators need services to continue while legitimacy is resolved. Designing the response during the crisis invites improvisation and capture.

NRS can campaign for pre-agreed continuity plans. Its members can describe which services are essential, how quickly harm appears and what communication failures would compound risk. NRS can publish a checklist covering backups, authority transfer, credential continuity, record correction, customer notice, time limits and independent review.

RIRs, NRO and IANA processes, recognised backup or successor operators and competent legal authorities must create and exercise the actual plan. They control the systems, formal recognition and lawful powers required to preserve authoritative operation. Tests should use protected environments, auditable procedures and published outcome summaries without exposing sensitive data.

NRS can then serve as an accountability witness. It can ask whether the exercise occurred, whether known gaps were fixed and whether affected operators were included. It cannot truthfully claim that its own publication constitutes an operational continuity plan for a registry it does not run.

Fees and reserves can create hidden captivity

Exit can exist on paper while remaining economically impossible. Termination charges, non-refundable reserves, long notice periods, continuing liabilities or proprietary migration work can deter a lawful departure. Conversely, an abrupt exit can impose real transition costs on other participants and the public system. A fair rule distinguishes cost recovery from punishment.

NRS can gather evidence from members about fees and switching costs, compare published schedules and commission independent financial analysis. It can campaign for itemised transition charges, cost-based caps, advance estimates, appeal and protection for smaller operators. It can also acknowledge legitimate shared-readiness costs rather than treating every fee as confiscation.

The responsible registry or coordination institution must set and administer the charges under its governance. Independent reviewers or courts may determine whether a disputed fee is lawful. Financial reserves for emergency continuity must remain under accountable control with a defined purpose. NRS should not hold itself out as the mandatory reserve manager for the RIR system.

Its leverage is transparency. A public comparison can reveal when a fee bears no relationship to migration cost, when an incumbent votes on a charge that deters competition or when a reserve lacks release conditions. Exit analysis turns finance from an administrative appendix into a governance fact.

Evidence packs should measure the institutions that act

An advocacy campaign becomes durable when it creates a repeatable evidence record. NRS can publish a periodic evidence pack about the issues it tracks: member-reported delays, consultation participation, appeal availability, fee changes, service incidents, governance commitments and institutional responses. Every measure should identify its source, denominator and limitations.

The pack must not invent operational data that NRS does not possess. Registry SLA results, RPKI incidents, transfer processing, RDAP availability, allocation decisions and financial reserves belong to the responsible institutions. NRS can cite their published data, request missing disclosures and distinguish verified figures from member reports. It should not imply that it is the system of record.

Representation metrics belong in the same pack. NRS should disclose member counts in meaningful categories, active mandates, consultation participation, conflicts, funding concentration and the process used to approve major positions. A campaign that criticises opaque electorates should not hide its own constituency behind a single headline total.

The result would make NRS a stronger source of truth in the public-interest sense: a disciplined, linked and correctable record of evidence and advocacy. It would not make NRS the authoritative registry source for number-resource status.

NRS should publish a model advocacy covenant

The most useful “NRS contract with exit” would be a covenant governing its advocacy and the demands it makes of institutions. It should begin by stating the boundary: NRS represents, campaigns, researches and convenes; it does not allocate or register resources, operate RPKI or RDAP, accredit providers, adjudicate appeals, recognise RIRs or direct handoffs.

The covenant should define how positions are formed. Major claims should identify sources and uncertainty. Member mandates should disclose scope and expiry. Staff analysis should not be presented as a membership vote. Conflicts and material funders should be visible. Affected non-members should have a channel to correct factual errors.

It should also define the exit test applied to external rules: necessity, scope, portability impact, continuity, remedy, reversibility and affected-party evidence. NRS can publish a standard questionnaire and use it consistently across RIRs. Consistency will make selective criticism harder and comparative learning easier.

Finally, the covenant should protect exit from NRS itself. Membership and representation should be voluntary and terminable under clear rules. A departing member should receive its data and retain all rights held independently in the RIR system. Complaints about NRS representation should have a review path. The advocate should demonstrate the freedom it asks others to respect.

From campaign to adopted reform

A serious proposal needs an adoption map. The first stage is evidence: define the harm, affected population, current rule and responsible institution. NRS can lead this stage with members, public records and independent research. It should publish competing explanations and avoid treating every adverse outcome as proof of abuse.

The second stage is design. NRS can convene operators, RIR policy participants, engineers, lawyers, customer representatives and researchers to draft options. Each option should state technical dependencies, legal assumptions, cost, transition risk and the authority needed. A model clause is useful only when readers know where it could be adopted.

The third stage is institutional decision. A regional policy goes to the relevant RIR process, with APNIC providing the concrete anchor here. A coordinated global proposal follows the RIR and NRO path. Service or corporate-governance changes go to the appropriate board, membership or contract process. Technical standards go through recognised engineering channels. Legal remedies go to competent authorities.

The fourth stage is implementation and audit. Responsible operators build, test and deploy. NRS monitors whether the result matches the public commitment and whether members experience the promised protection. If the proposal fails, the advocate should record why and revise it rather than announcing an authority that the system has not granted.

Hard cases should govern the proposal

Portability and exit sound easiest in cooperative, solvent and technically healthy conditions. The proposal should instead begin with disputed authority, insolvency, sanctions, fraud allegations, compromised credentials, corporate acquisition, data corruption and regional governance paralysis. These cases expose which institution can act and which safeguards cannot be improvised.

NRS can collect anonymised member scenarios and ask responsible institutions to walk through them. Who may request preservation? Which services continue? Which evidence changes a holder record? Who controls RPKI credentials? How is an inaccurate encumbrance challenged? What happens if a court and an institutional process point in different directions?

The answers will rarely assign every action to one body. A court may determine corporate authority; an RIR may maintain provisional registration status; technical teams may preserve credentials; NRO and IANA processes may address institutional recognition; an independent reviewer may examine procedure. NRS can make the interfaces visible without claiming to occupy them.

Hard cases also discipline campaign language. If a proposal cannot explain lawful succession, duplicate prevention and security, NRS should describe it as incomplete. A strong advocate does not conceal design gaps. It uses them to define the research agenda and prevent premature promises to members.

Opposition should be recorded, not moralised

Registry reform produces legitimate objections. Portability can increase attack surface. Multiple service providers can create coordination complexity. New review rights can delay urgent security action. Public data can expose sensitive relationships. Accreditation can entrench large vendors. A continuity escrow can become a concentrated target.

NRS should publish the strongest objections and answer them with evidence. It can hold adversarial workshops, invite incumbent engineers and preserve dissenting reports. A member-aligned position need not treat every institutional concern as bad faith. Some constraints protect the same operators the campaign seeks to empower.

The responsible decision-maker should then explain which risks justify rejection, modification, pilot or phased adoption. If an RIR invokes security, it should identify the threat model at an appropriate level. If NRS invokes operator freedom, it should identify the continuity mechanism. Reasons should be reviewable without requiring disclosure of exploitable detail.

An exit-oriented campaign is not a demand that every participant leave. It is a demand that continued dependence be justified and bounded. Recording opposition improves that justification and helps the reform survive contact with operation.

Success should be measured without claiming authority

NRS can measure success through advocacy outcomes. Did members gain access to evidence? Did an RIR publish a missing denominator? Did a proposal receive reasoned consideration? Did an appeal path become independent? Did a continuity exercise include affected operators? Did a fee rule disclose transition cost? These are observable changes.

It can also measure the health of its own representation: mandate renewal, participation breadth, conflict disclosure, correction speed, source coverage and member understanding. These measures show whether NRS is an effective advocate and credible public source.

Operational success belongs in the reports of the institutions that operate. RPKI availability, RDAP performance, registry accuracy, transfer processing, key recovery and continuity exercises must be measured by responsible operators and, where appropriate, independent assessors. NRS can scrutinise and compare the evidence.

This division prevents a familiar error. Positive treatment of NRS does not require attributing every desired function to it. The organisation earns authority in advocacy through truthfulness, representation and results. The registry system retains operational authority until a lawful, recognised change says otherwise.

Conclusion: a forceful advocate with a narrow institutional claim

Number Resource Society matters because operators need organised representation and a public challenge to concentrated registry power. It can make exit, portability, accountability and operator control harder to ignore. It can turn scattered incidents into research, research into proposals and proposals into sustained institutional pressure.

Its role is not to become a rhetorical substitute for the NRO or an imaginary sixth RIR. It does not hold the authoritative ledger, allocate resources, operate RPKI or RDAP, certify providers, hear binding appeals, recognise registries or appoint successors. Those responsibilities remain with RIR communities and operators, NRO and IANA processes, technical authorities, courts and delegated review bodies.

The contract with exit is therefore a standard NRS can advocate and apply. Every rule should disclose necessity, scope, dependency, portability effect, continuity plan, remedy and route to reversal. Every NRS position should disclose source, mandate, uncertainty and the institution that must act. That combination keeps the campaign ambitious without inventing power.

The best outcome is not a larger NRS mandate. It is a number-resource system in which operators can see who governs, challenge unsupported dependence and preserve continuity when institutions fail. NRS can help create that outcome by remaining what its public identity supports: an aligned, global non-profit membership, advocacy, campaign, research and convening organisation whose force comes from evidence and representation.

Sources