Summary

  • IETF, ICANN and WSIS processes produce different kinds of authority. The IETF produces technical documents through open individual participation and engineering judgment; ICANN coordinates unique identifiers through corporate instruments and multistakeholder bodies; WSIS produces intergovernmental commitments and inclusive policy vocabulary.
  • Regional Internet Registries can participate legitimately in all three settings. Their technical expertise, ICANN role and diplomatic engagement are cumulative only for claims that preserve the scope and conditions of each setting.
  • Forum shopping becomes legitimacy laundering when an institution invokes IETF competence to defend a policy power, ICANN recognition to imply worldwide representation, or WSIS inclusion to suggest operational command over registries and networks.
  • The central audit question is not which forum discussed an issue. It is which actor decided which act, for which constituency, under which instrument, with what evidence, review, implementation and remedy.
  • Cross-forum coordination should use explicit handoffs. A diplomatic concern can enter an ICANN or RIR procedure; a technical finding can constrain a policy choice; a corporate decision can implement an agreed service. None should be retrospectively described as the mandate of all three.

Forum shopping is about the source of authority, not the meeting calendar

Institutions should appear in more than one venue. Engineers need to understand public policy. Governments need operational evidence. Registry organizations need standards, agreements and diplomatic relationships. A rule against cross-forum participation would make Internet governance less competent.

Forum shopping describes a narrower behavior. An actor selects the authority story most favorable to the immediate claim, then changes stories when the liabilities of the first become inconvenient. In one setting it is an expert implementing technical necessity. In another it is a recognized component of a global private-coordination arrangement. In a third it is a voice of a region or the technical community. Each description may contain some truth. The difficulty is that each is validated by a different constituency and authorizes a different act.

Technical competence can justify deference on protocol behavior. It does not create a legislature. Corporate recognition can establish a role under bylaws and agreements. It does not create universal political representation. Diplomatic inclusion can improve the legitimacy of public-policy debate. It does not supply credentials to change a registry or configure a route.

The shopper gains power by combining these propositions. Technical prestige answers doubts about competence. Institutional recognition answers doubts about continuity. Global inclusion answers doubts about representation. The resulting composite looks stronger than any one source. Yet no procedure may have considered the complete claim, and no remedy may reach it.

The audit must therefore follow authority, not attendance. Which forum supplied which proposition, and did the institution carry the corresponding limits when it moved?

Three forums issue three different currencies

The IETF's currency is engineering credibility. Its documents gain influence when entities can inspect the work, challenge assumptions, implement the result and observe interoperability. RFC 3935 describes open process, technical competence, rough consensus and individual participation as cardinal principles. The resulting specification can be highly authoritative about how a protocol should behave while remaining voluntary in adoption.

ICANN's currency is constituted coordination. Its authority comes from articles, bylaws, contracts, supporting organizations, advisory committees, board action and acceptance by parties that depend on the unique-identifier system. Its Bylaws define a bounded mission and formal accountability routes. The institution can approve or implement acts within that structure; it cannot turn every public concern into mission simply by calling it global.

WSIS currency is diplomatic and participatory legitimacy. Governments negotiate as states. Non-state actors contribute through consultations and parallel processes. Outcome texts identify development goals, public-policy responsibilities and respective roles. The Tunis Agenda can commit states politically and shape later institutions without becoming an operating agreement for every network function it discusses.

Currencies can be exchanged through explicit mechanisms. An IETF specification may be incorporated into an ICANN service. A WSIS concern may lead governments or private bodies to begin a policy process. An ICANN decision may be examined in a diplomatic review. Exchange does not mean equivalence.

The decisive anti-laundering rule is simple: an institution may not spend one currency as though it were another. Engineering credibility cannot purchase sovereign consent. Diplomatic endorsement cannot purchase protocol correctness. Corporate process cannot purchase a global electorate.

ICANN began as a public decision to pursue private coordination

The 1998 starting point already contained several authority sources. The United States Department of Commerce Statement of Policy on Internet names and addresses, commonly called the White Paper, proposed transition toward a new private, nonprofit corporation with global participation. It rejected a monolithic system of Internet government and sought a stable process for narrow coordination tasks.

This was neither pure privatization nor spontaneous technical self-ordering. A national government used its existing position and agreements to recognize a private institutional form. The new corporation would then seek wider acceptance. Public authority selected a transition direction; corporate documents and operational reliance supplied the continuing arrangement.

The distinction is essential because later narratives often begin after the difficult handoff. ICANN can be described as a global multistakeholder community, a private corporation, a technical coordinator or a product of United States policy. Each description captures a period or function. None alone explains the institution's authority.

The White Paper also illustrates how forum choice shapes language. It spoke to a domestic administrative process while anticipating international support. It used competition, private-sector leadership, stability and representation rather than treaty delegation. Its own text said the policy statement did not contain mandatory provisions with the force of law, even as the government's contractual position gave the transition practical consequence.

The origin should produce modesty. ICANN's legitimacy did not descend from one constitutional event. It accumulated through law, agreements, technical operation, participation and reliance. An institution with accumulated legitimacy must state which part supports the particular power it claims.

The IETF's authority is deliberately strong and deliberately incomplete

The IETF can speak with unusual force about protocols because it invites technically competent challenge and publishes work that others can implement. There is no general membership class. Entities contribute as individuals even when employers fund their work. Mailing lists, drafts, decisions and documents are generally visible.

This design reduces several representational problems. A entity need not prove authority to speak for a country or company before identifying a protocol defect. A sound technical argument can prevail without a bloc vote. Independent implementation can expose mistakes that rhetorical agreement concealed.

The same design creates boundaries. Individual participation does not aggregate into democratic representation of Internet users. Rough consensus is not consent by every affected person. Running code can demonstrate feasibility and interoperability; it cannot decide distributive justice, legal title or the lawful scope of a regulator.

RFC 7282 explains that rough consensus is not simple voting and that dominant technical objections must be examined rather than counted away. This is valuable for standards work. It would be a fragile basis for taxing operators, confiscating an asset or deciding a civil dispute, because those acts require legal authority and procedural protections of another kind.

Forum shopping exploits the positive half and suppresses the boundary. A policy is described as technically necessary because engineers discussed adjacent architecture. The prestige of the standards process then shields a discretionary institutional choice. The proper response is to ask for the exact technical invariant and specification. If the disputed rule cannot be traced to interoperability, security or another defined technical requirement, IETF prestige does not decide it.

The 2000 IETF-ICANN agreement is a boundary document

RFC 2860 records the memorandum concerning the technical work of IANA signed by the IETF and ICANN in 2000. It is often cited as evidence of a stable relationship between the standards and identifier-coordination institutions. That is correct. Its deeper value is that it specifies limits.

The agreement concerns technical work needed for protocol parameters and related tasks. It recognizes the IETF's role in technical specifications and an IANA function carried out through ICANN. It expressly distinguishes some policy concerning domain names and IP address blocks from the technical work covered by the memorandum.

This is what an honest cross-forum handoff looks like. The parties, subject, duties and exclusions are identifiable. The IETF does not become ICANN's legislature. ICANN does not acquire authorship of IETF standards. IANA work remains a function that can be described separately from the corporation performing it.

The document also demonstrates why broad appeals to “the Internet community” are unnecessary when an operational relationship can be stated precisely. One body requests and documents assignments under its procedures; another performs agreed registry services. Problems can be located at the boundary.

Forum shopping reverses this discipline. A specific technical relationship is cited to suggest general endorsement of an institution's governance. Or ICANN recognition is used to make an informational IETF document sound like binding policy. The original agreement does not support either conversion.

The lesson from 2000 is not that the institutional settlement is permanent. It is that legitimacy improves when cooperation is written as a limited interface rather than a shared aura.

ICANN authority comes with corporate verbs and review paths

ICANN's current Bylaws define its mission as ensuring the stable and secure operation of the Internet's unique-identifier systems. For numbers, the mission includes top-level coordination, registry services requested by the IETF and RIRs, and facilitation of global number policy with the affected community and RIRs. The Bylaws also say that ICANN shall not act outside its mission and does not hold governmentally authorized regulatory authority.

These clauses matter because they name both capacity and restraint. ICANN can enter agreements, operate services, receive advice, approve decisions and participate in its Empowered Community arrangements. Board action has corporate consequence. Reconsideration, independent review, document disclosure and other mechanisms provide routes for challenge within defined scopes.

Corporate legitimacy is not inferior to diplomatic legitimacy. It is different. A well-designed private body can be more open, specialized and responsive than an intergovernmental organization. Its policies can gain wide acceptance because they solve coordination problems and because affected parties participate.

But “global public interest” does not transform a corporation into a world government. The public cannot vote it out through a universal election. Its procedures allocate voice through designed stakeholder categories and supporting bodies. Contracts reach some parties directly and others only through dependency or market structure.

When ICANN enters another forum, it should carry these facts with it. A claim that the multistakeholder model is legitimate must identify the relevant ICANN body, decision and review path. A claim that governments support an action must distinguish Governmental Advisory Committee advice from an intergovernmental commitment. A claim of technical necessity must identify the standard or operational evidence.

Corporate verbs make power visible. “The Board approved,” “the parties agreed” and “the review panel found” are more accountable than “the community decided” when the legal act was corporate.

WSIS distributes political standing without creating an Internet cabinet

The Geneva Declaration and Tunis Agenda were negotiated in a different institutional register. States held sovereign standing. The texts recognized roles for the private sector, civil society, intergovernmental organizations and international organizations. They called for governance that was multilateral, transparent, democratic and inclusive.

This vocabulary corrected a real exclusion. Institutions built around a small technical and commercial circle could affect countries and populations that had little ability to enter their procedures. WSIS made development, sovereign equality and wider participation part of the legitimacy test.

Its compromise depended on differentiated roles. The 2005 working definition described Internet governance as development and application by governments, the private sector and civil society, in their respective roles, of principles, rules, procedures and programmes. It did not say every entity had the same power in every institution.

The resulting Internet Governance Forum was designed for dialogue rather than binding decision. Other functions remained with existing bodies or domestic public authorities. This separation allowed political disagreement to continue without an immediate operational seizure.

Diplomatic language is nonetheless easy to overread. A statement that all governments should have an equal role and responsibility for international Internet public policy does not mean each government administers one equal share of the IANA registries. Recognition of the technical community does not appoint every organization using that label. Full involvement does not mean unanimous consent to every downstream policy.

WSIS supplies standing to raise public questions and a vocabulary for evaluating institutions. A specific actor still needs a lawful or agreed mechanism to decide and implement a specific act.

RIRs speak as implementers in the IETF register

Regional Internet Registries have genuine technical competence. They operate registration services, allocate address space and autonomous system numbers, support reverse DNS and resource certification, publish data and work with network operators. Staff and community entities contribute to technical documents and operational discussion.

In the IETF register, this experience is valuable evidence. A registry can explain how an address-policy choice interacts with aggregation, special-purpose space, registration data or route-origin validation. Implementation reveals constraints that a purely abstract proposal might miss.

RFC 7020 documents the current Internet Numbers Registry System and delineates functions among the IETF, IANA, RIRs and local registries. It says routing decisions remain outside the registry system and preserves the IETF's role concerning non-policy aspects of addressing. The document is informational, not a permanent grant of political authority.

The risk appears when implementation competence is converted into jurisdiction over operators. A registry may say a rule protects “the architecture” without identifying the technical failure that noncompliance would cause. Commercial use, customer location, corporate structure or disagreement with registry leadership may be policy concerns; they are not automatically uniqueness or interoperability failures.

Technical claims should therefore be falsifiable. Which packets, records, certificates or allocations become inconsistent? Which standard is violated? What evidence would show that the risk is absent? If those questions have no answer, the claim belongs in an institutional policy debate with the corresponding burden of justification.

RIR expertise should receive serious weight. It should not be treated as a transferable licence to define rights outside technical competence.

RIRs speak as constituted bodies in the ICANN register

Within ICANN, the RIRs have a formal relationship through the Number Resource Organization and Address Supporting Organization. The ASO Memorandum of Understanding defines roles in global number-policy development, advice and appointment. The ASO Address Council is composed through the regional arrangements described by the agreement.

This constituted role is more than technical reputation. It gives named bodies functions within ICANN. A global number policy must travel through procedures requiring regional agreement and ICANN action where IANA implementation is needed. The ICANN Board and ASO do things that an informal engineering discussion cannot do.

The formal role is also narrower than the language of global representation can suggest. The ASO does not become a parliament of all Internet users. RIR policy entities are not elected by the populations of their service regions. Membership, meeting participation, address holding and national citizenship are different relationships.

Institutional recognition proves that ICANN and the RIR organizations agreed on a coordination arrangement. It can produce binding corporate acts for the parties and accepted changes in the number system. It does not prove that every affected operator authorized every policy or that every government delegated sovereign power.

This distinction matters when an RIR defends a controversial decision. “ICANN recognizes the RIR system” answers a question about the current coordination structure. It does not answer whether the particular decision followed policy, respected an agreement, used reliable evidence or supplied an effective appeal.

Recognition is a platform for accountable action, not a substitute for reasons.

RIRs speak as a technical community in the diplomatic register

At WSIS, the IGF, NETmundial and United Nations reviews, RIR organizations often appear within a broader technical-community category. They emphasize an open, interoperable Internet, bottom-up coordination, regional participation and the risks of intergovernmental control over operations. These contributions can improve diplomatic understanding.

The category is strategically useful. It distinguishes organizations with operating knowledge from governments, companies speaking primarily as market actors and advocacy groups. It reminds negotiators that a text can disrupt working systems even when its political objective is attractive.

Yet “the technical community” has no single appointment chain. It can include standards contributors, registry organizations, security responders, researchers, operators, software developers and institutions with conflicting interests. A joint statement by several prominent bodies is evidence of their position, not automatic consent by everyone whose work is technical.

The category also changes the RIR narrative. In regional policy, the registry may describe itself as accountable to its members and community. In ICANN, it is part of a recognized supporting arrangement. In a diplomatic room, it may speak as part of a globally distributed technical community protecting the Internet's operation.

These identities can coexist, but the mandate must be restated each time. Was the speaker authorized by an RIR board, a policy community, the NRO, an event coalition or only by an employer? Is the statement technical evidence, organizational advocacy or a claim about public policy? What dissent exists among operators?

Diplomatic inclusion gives the speaker access and standing. It does not retrospectively convert organizational advocacy into technical consensus or regional representation.

“The community” is where the three narratives blur

Each forum uses the word community. The IETF community consists of individuals participating in standards work. The ICANN community consists of designed bodies, constituencies, advisers and entities around a corporation. An RIR community may include members, resource holders, meeting entities, mailing-list contributors and interested observers. WSIS speaks more broadly of stakeholders and global participation.

The word is useful because these institutions are not reducible to employees or governments. It is dangerous because it hides the authorization chain. A person can be a respected contributor without representing anyone. A membership vote can bind an association without expressing the will of a region. An open consultation can gather comments without ratifying the final decision.

Community language allows forum shopping with minimal friction. A position supported on an IETF list becomes “technical community consensus.” A decision produced through RIR procedure becomes “the region's policy.” A coalition statement at WSIS becomes “global multistakeholder support.” Each translation expands the represented population.

The correction is to replace the collective noun with a procedural account. Identify who could participate, who did participate, who decided, how objections were handled and whom the result binds. Report the denominator where possible. Distinguish organizational endorsement from individual contribution.

This does not weaken community institutions. It protects their most legitimate achievements from inflated claims. A technically sound specification does not need fictional worldwide consent. A valid corporate decision does not need to pretend to be a plebiscite. A persuasive diplomatic statement does not need to become an operating order.

The more exact the authorization claim, the less opportunity there is to launder one forum's standing through another's vocabulary.

Governments also change identity across the three forums

Forum shopping is not a private-institution monopoly. Governments change posture as they move. At WSIS they negotiate through sovereign delegations. In ICANN they provide public-policy advice through the Governmental Advisory Committee and may participate elsewhere. At the IETF, civil servants and public-sector engineers generally contribute as individuals rather than casting national votes.

These roles are legitimate when declared. A security researcher employed by a ministry should be able to make a technical argument without waiting for diplomatic clearance. A government representative should be able to state national public policy without pretending it is an IETF result.

Problems arise when the roles are blended opportunistically. A government may cite the openness of an IETF discussion as evidence that its preferred regulation is technically endorsed, even though no standards action adopted the policy. It may call GAC advice an international governmental consensus without disclosing the participation and consensus rule. It may cite a WSIS paragraph as if it directly binds private operators at home without implementing legislation.

The accountability direction can reverse as well. In diplomatic settings, the government is answerable through public institutions. In a standards setting, its employee may disclaim representation and speak personally. If the same proposal moves between the two, observers need to know when it became an official position and under what authority.

No actor should be forced into one permanent identity. The rule is provenance. Each claim must carry the role in which it was made, the forum's decision status and the route by which it can acquire another kind of authority.

The IANA transition combined all three narratives under stress

The 2014-2016 IANA stewardship transition is a useful test because technical continuity, corporate accountability and geopolitical legitimacy were all in view. The United States announced an intention to transition its stewardship role, subject to criteria including security, stability and support for the multistakeholder model. Communities developed proposals for names, numbers and protocol parameters. ICANN accountability reforms proceeded alongside operational planning.

The transition needed all three currencies. Technical communities had to show that functions would continue. Corporate and contractual arrangements had to identify responsible bodies and review mechanisms. Governments and global stakeholders needed confidence that the change would not replace one state's special role with capture by another actor.

Success did not mean that the currencies merged. The numbers proposal rested on arrangements involving the RIRs, service levels and intellectual-property or accountability provisions relevant to that function. Protocol-parameter work had its own relationship. Names required another accountability structure. Diplomatic support did not write the operational details, and operational competence did not settle every political concern.

The later narrative often compresses the transition into a victory for “the multistakeholder community.” That phrase conceals the division of labor that made the change possible. It can also be used to defend current institutions as though completing the transition granted an indefinite mandate.

A transition proves capacity for the acts it successfully transferred. It does not immunize future decisions. The continuing legitimacy of each body depends on performance, bounded authority and available correction after the celebratory moment has passed.

Translation is legitimate when the handoff is visible

Cross-forum influence is necessary. A diplomatic process may identify that developing-country operators face participation barriers. An RIR can receive the concern through its policy or governance procedure. Technical work can test whether a proposed remedy threatens uniqueness or routing scalability. ICANN can act if a global policy requires IANA implementation.

This sequence is not laundering because each step has a named recipient and transformation. The diplomatic statement supplies a public problem and political expectation. The regional process supplies evidence and a policy decision. The IETF supplies technical constraints where relevant. ICANN and IANA supply defined implementation acts. No institution claims to have supplied the authority of all the others.

Translation also permits refusal. The technical evidence may show that the first proposal is unsafe. A registry process may conclude that the evidence does not support a rule. A government may decide that voluntary reform is inadequate and legislate within its jurisdiction. Each refusal should be reasoned and visible.

Laundering, by contrast, erases the handoff. A broad WSIS commitment is said to “require” a particular registry policy without an adopting procedure. An RFC is said to “mandate” an institutional sanction beyond its technical scope. ICANN recognition is said to prove that an RIR represents a continent.

The difference is procedural traceability. Legitimate translation changes the form of a claim through an authorized decision. Laundering changes the label while preserving the desired conclusion.

Remedies reveal which authority is actually being used

The fastest way to identify the real forum is to ask where a losing party can challenge the act. An IETF entity may raise a technical objection, appeal process failures through defined channels or propose a new document. These routes can correct standards work; they do not award damages for a registry suspension.

An ICANN decision may be subject to reconsideration, independent review, ombuds work, board accountability or contractual dispute, depending on the act and claimant. An RIR has its own corporate, membership, policy and service-review routes. A government order may be reviewed in an administrative tribunal or court. A WSIS outcome is ordinarily challenged through diplomacy, public debate and later negotiation rather than individual judicial appeal under the outcome text.

Forum shopping often seeks the authority of one system with the immunity of another. A registry invokes technical consensus but tells the affected operator to use a narrow corporate appeal. A government invokes diplomatic agreement but avoids domestic legislative scrutiny. A private body invokes global public interest but argues that no public-law remedy applies.

The remedy mismatch is evidence of laundering. If the institution says the act is authorized by technical consensus, a challenger should be able to identify and contest that consensus at the relevant technical decision point. If it is a corporate decision, the board, instrument and review should be named. If it is law, jurisdiction and judicial review should be available.

Authority without its native remedy is prestige detached from accountability.

Public-interest organizations can either expose or amplify the switch

Research institutes, civil-society groups, professional associations and other public-interest organizations operate across the same venues. They can compare claims, preserve institutional memory and give affected groups expertise they could not otherwise afford. Their independence can make cross-forum scrutiny possible.

They can also amplify forum shopping. Funding, access and professional networks may reward language acceptable to conveners. A coalition may repeat “multistakeholder,” “technical community” or “sovereign equality” without identifying the institutional act under review. Many endorsements can create an appearance of broad authority even when the signatories approved only general principles.

The useful public-interest intervention is forensic. It compares the same actor's submissions across forums. It notes changes in constituency, authority verb and claimed beneficiary. It asks whether dissent visible in one venue disappeared from the narrative presented in another. It identifies funding and organizational relationships relevant to the position.

This work should not assume that inconsistency proves bad faith. Institutions adapt explanations to audiences, and a short diplomatic statement cannot reproduce a technical document. The issue is whether the adaptation changes the claimed mandate.

A public-interest organization earns trust by separating evidence from advocacy. Official statements show what institutions claim and do. Independent research tests legitimacy and consequences. Normative analysis states what the author thinks should follow. Combining these categories in one unmarked narrative would repeat the very laundering being examined.

The incentive is to borrow the strongest feature and avoid the cost

Each forum has a legitimacy strength and an accountability cost. The IETF offers expertise and openness but demands technically answerable objections and implementation evidence. ICANN offers constituted decision and continuity but exposes corporate power, designed constituencies and review limits. WSIS offers sovereign equality and inclusion but requires diplomatic compromise and often leaves implementation elsewhere.

An institution has an incentive to borrow the strength while avoiding the cost. It invokes IETF engineering authority but does not make the policy falsifiable. It invokes ICANN recognition but does not accept mission limits or effective review. It invokes WSIS inclusion but does not show state authorization or downstream law.

The incentives intensify during crisis. A security event favors technical urgency. A challenge to legal authority favors global recognition. A criticism of representation favors diplomatic inclusion. The narrative can change faster than the underlying power.

Funding and careers reinforce the pattern. Organizations gain access by presenting themselves as bridges among communities. Staff become fluent in each vocabulary. This expertise is valuable, but it can make the authority switch too smooth for outsiders to see. A sentence assembled from “rough consensus,” “bottom-up multistakeholder” and “respective roles” may sound settled while joining three different procedures.

The control is not a purity test. It is a disclosure rule. Every consequential claim should identify which source supplies competence, which supplies decision power, which supplies political support and which supplies remedy. If those sources differ, the gaps should remain visible.

A cross-forum authority ledger would make switching reviewable

Institutions should publish a compact authority record for major cross-forum claims. It need not be a new governing body. It is a trace of provenance.

The record should identify the proposition, the forum in which it originated, the speaking actor and role, the decision status, the constituency able to participate, material objections and the instrument through which the proposition later changed form. If implementation followed, it should name the responsible institution, date and review route.

For example, a WSIS recommendation on wider government participation might be recorded as a diplomatic commitment. An ICANN or RIR consultation would be a separate entry. A board or policy decision would identify what changed. Technical implementation would cite the relevant specification and deployment evidence. Later reports could claim the measured result, not a generalized triumph of multistakeholderism.

The record should also preserve negative results. If the IETF did not adopt a proposal, an expired draft should not be cited as standards consensus. If GAC advice lacked consensus or was not accepted, that status should travel. If an RIR consultation drew few entities, “community support” should be qualified. If a UN outcome invited action rather than required it, later summaries should retain the verb.

This discipline would improve institutional memory. New staff and outside observers could see which authority source remains active and which was merely persuasive context. It would also reduce repeated litigation over labels by making the operative act easier to locate.

The ledger would not settle legitimacy. It would make legitimacy claims auditable.

Seven questions expose a laundered mandate

The first question is origin: where did the proposition first receive a decision status rather than merely appear in discussion? The second is speaker: did the person act individually, for an employer, for a constituted body or for a state?

The third is scope: did the source address protocol behavior, institutional policy, public policy or an operational transaction? The fourth is constituency: who could authorize, participate, entity and replace decision makers?

The fifth is conversion: which instrument moved the proposition into another forum's form? A citation is not a conversion. A memorandum, bylaw amendment, policy adoption, contract, law or implementation decision may be.

The sixth is remedy: where can an affected party obtain correction before harm becomes irreversible? The seventh is counterfactual: would the institution accept the same authority logic if the result opposed its interests?

These questions should be applied symmetrically. Technical institutions should not be presumed virtuous because they are decentralized. Governments should not be presumed representative merely because they are states. Private processes should not be presumed illegitimate merely because they use contracts. Diplomatic processes should not be dismissed merely because implementation is indirect.

The objective is functional honesty. Every form can be legitimate for acts it is equipped and authorized to perform. Every form can overreach when it borrows another's prestige.

An institution that can answer all seven questions may still make a bad decision. At least the public will know what kind of decision it made and where correction belongs.

Watchpoints for the next cross-forum claim

Watch for an RFC cited without the section that defines its scope or status. Publication can prove that a document exists and received a particular process; it does not make every adjacent institutional policy technically mandatory.

Watch for “ICANN-recognized” used as a complete defense. Recognition identifies a place in the current arrangement. It does not resolve whether the contested act was authorized, proportionate or reviewable.

Watch for “the technical community” without named organizations, authorization and dissent. The phrase may describe expertise, coalition identity or claimed representation; those are not equivalent.

Watch for WSIS or United Nations language whose verbs change in retelling. “Recognize,” “support,” “invite” and “commit” should not become “mandate” unless another instrument supplies that effect.

Watch for community nouns that expand between documents. RIR members, meeting entities, operators, a service region and the public are different constituencies.

Watch for remedies located in a forum other than the one invoked to justify the act. That mismatch often reveals that prestige has travelled farther than accountability.

Watch for crisis narratives that switch sources quickly: technical necessity when speed is needed, corporate recognition when authority is challenged, and diplomatic inclusion when representation is questioned.

Finally, watch for success reports that credit “the model” rather than the institutions and people who performed measurable acts. Diffuse credit makes future power easier to claim and failure harder to assign.

Conclusion: authority cannot be assembled from borrowed prestige

The IETF, ICANN and WSIS each solved a different institutional problem. The IETF developed a way for individuals to produce influential technical documents through open work, engineering judgment and implementation. ICANN created a constituted coordination system for unique identifiers with corporate acts, agreements and review. WSIS created a diplomatic settlement in which states retained public-policy authority while non-state actors gained recognized standing and a continuing forum.

None is complete. The IETF does not represent the world's population. ICANN does not possess governmentally authorized regulatory power. WSIS does not operate registries or networks. Their limitations are not defects to be concealed. They are the conditions under which each source of authority remains intelligible.

Regional Internet Registries sit at the junction. They implement technical systems, hold roles in ICANN's number arrangements and advocate in diplomatic spaces. That position gives them knowledge and access. It also gives them unusual capacity to change legitimacy narratives without changing the underlying power.

The answer is not to confine them to one room. It is to require the authority claim to travel with its provenance. Technical expertise must identify the technical question and evidence. ICANN recognition must identify the governing instrument and review. Diplomatic support must identify the negotiating actor, verb and downstream implementation route. Regional claims must identify the people and organizations that actually authorized them.

Cross-forum translation can then become a strength. A public concern can reach a competent procedure. A technical constraint can discipline a political proposal. A corporate decision can make a negotiated objective operational. Each handoff can be challenged where it occurs.

Legitimacy laundering begins when the handoff disappears. Prestige from engineering, continuity from private coordination and inclusion from diplomacy are blended into a mandate that no forum examined as a whole. The resulting power seems global precisely because its source cannot be located.

Internet governance does not need one supreme forum. It needs institutions that state which authority they are using, accept the remedy attached to it and stop when that authority ends. A technical result, a corporate act and a diplomatic commitment can reinforce one another. They cannot be mixed to manufacture consent.

Sources