Root-Zone Politics Are Not Number-Registry Authority

Summary

• ICANN's Bylaws assign distinct missions: coordination of names in the DNS root and certain generic-domain policies; coordination of the top level of IP-address and ASN allocation; and provision of protocol registries requested by standards bodies. The numbering clause expressly points to the IETF, RIRs, the affected community and tasks agreed with the RIRs rather than treating names institutions as the authors of number policy.
• Naming authority runs through top-level-domain customers, the ccNSO and GNSO, an ICANN-PTI naming contract, the Customer Standing Committee, naming-function reviews and a naming-specific separation procedure. Numbering authority runs through five regional communities, the RIRs, NRO and ASO, global number-policy procedures, and a service agreement under which the RIRs can collectively replace the numbering operator.
• Prestige spills over because one IANA label covers several functions, PTI performs them with shared resources, ICANN is PTI's parent, and the DNS root attracts exceptional governmental, commercial and public attention. These facts explain the confusion but do not transfer legal standing, policy competence, customer rights or successor-selection power.
• Any claim of authority should pass five tests: who develops the policy, who receives the service, which agreement governs, who can enforce it, and who can select a replacement. Root-zone status fails every test as a basis for directing regional allocations, recognizing RIR authority, rewriting number policy or controlling address-registration decisions.

One acronym encourages the wrong inference

The phrase "the IANA functions" sounds singular. It evokes a central switchboard from which one institution assigns all globally unique Internet identifiers. Public descriptions often reinforce the impression by listing domain names, number resources and protocol parameters under one heading. PTI employs the people who carry out the work, ICANN controls PTI, and the IANA website presents the results through a common public identity.

Operational coherence is useful. Unique identifiers require disciplined record keeping. Shared security, finance, human resources and technical expertise can reduce duplication. A user should not need to understand corporate structure to find an authoritative registry. The mistake begins when convenience of operation is converted into unity of mandate.

The IETF's description of the Internet Numbers Registry System gives a better starting point: IANA is a role, not an organization. For numbers, that role manages the top of the IP-address and ASN allocation hierarchies. The role is performed according to global number policies developed by the affected community and reflected in agreements with the RIRs. The operator's identity does not make the operator the sovereign author of every rule it implements.

The same principle applies to names. PTI receives and evaluates requests concerning the DNS root under documented procedures. Verisign separately performs the root-zone maintainer function under its agreement with ICANN, compiling, signing and distributing the root-zone file at IANA's direction. Neither operational position gives Verisign authority over IPv6 policy, and PTI's root-zone work does not let it decide how an RIR should allocate address space to regional members.

The category error persists because the most visible function lends prestige to the quieter ones. A change to the DNS root can become a geopolitical event. A new top-level-domain round attracts brands, governments, civil-society groups and investors. Domain registration disputes affect names that humans read. By contrast, a top-level ASN block allocation is infrequent, technical and usually noticed only by the numbering community. Visibility is mistaken for seniority; seniority is then mistaken for jurisdiction.

That inference should be resisted at every step. The functions are coordinated together because they all require globally unique values. They are governed separately because their users, technical consequences and legitimate policy forums are different.

The root zone has symbolic weight beyond its daily mechanics

The DNS root is a small but foundational list. It identifies the authoritative servers for top-level domains and carries the records needed for resolvers to begin navigating the global DNS. A change can add or remove a delegation, alter nameservers, update contacts or change DNSSEC material. Because every ordinary DNS lookup begins its chain of authority at the root, the root has become a symbol for control of naming on the Internet.

The symbolism exceeds the routine work. Most root-zone requests are bounded administrative changes. The IANA naming operator validates requests and applicable criteria; the maintainer produces and distributes the file. Root server operators serve it. These roles are deliberately separated. No single act of typing a top-level-domain label into the root creates general legislative authority over the Internet.

History nevertheless gave the root unusual political visibility. The United States government's pre-2016 authorization step sat in the root-zone change path. Debates over country-code delegations implicated national identity and local Internet communities. Generic-domain expansion involved competition, trademarks, consumer protection and substantial commercial stakes. The 1998 United States policy statement that preceded ICANN devoted extensive attention to DNS competition, representation and private coordination, even while discussing the broader names-and-addresses system.

Public audiences therefore learned ICANN through names. The corporation's own name foregrounds Assigned Names before Numbers. Its meetings devote large, visible constituencies to generic and country-code domains. Governmental advice often becomes news when it concerns controversial strings. These are reasonable explanations for prestige spillover, not proof that it is legitimate.

Institutional prestige is a form of soft power. An organization seen as custodian of the root may be invited to speak for Internet coordination generally. Governments may assume its board can settle an address dispute. Journalists may use "IANA control" without distinguishing the relevant function. Entities from names institutions may carry confidence and procedural habits into discussions about numbers. None of this needs a conspiracy. Repeated exposure to one branded institution can make its boundaries disappear.

The corrective is not to diminish the root. It is to describe the authority precisely. Root-zone administration is important because resolvers need one coherent starting point. Number-registry authority is important because addresses and ASNs must remain unique and be distributed through a legitimate hierarchy. The two systems interact, especially through reverse DNS, but importance in one is not a title deed to the other.

ICANN's mission contains four clauses, not one blank cheque

The current ICANN Bylaws define a mission around the stable and secure operation of unique-identifier systems, then divide it into distinct functions. The first coordinates names in the DNS root and certain policies for second-level registration in generic top-level domains. The second facilitates coordination of the root server system. The third coordinates allocation and assignment at the top-most level of IP numbers and ASNs. The fourth provides registries requested by protocol-standards organizations.

The wording of the numbers clause is especially revealing. ICANN provides registration services and open access for global number registries as requested by the IETF and RIRs. It facilitates development of global number-registry policies by the affected community and carries out related tasks as agreed with the RIRs. The clause does not say that the GNSO, ccNSO, Customer Standing Committee or root-zone maintainer may write number policy.

The Bylaws also say that ICANN shall not act outside its mission. That restriction is broader than the distinction between names and numbers, but it strengthens it. An institution cannot turn general responsibility for unique identifiers into authority over every service that uses them. Nor can it convert coordination into governmental regulation. The mission is a set of bounded tasks, not a claim to cyberspace.

Article 9 then gives the Address Supporting Organization a specific role: advising the Board on policy issues relating to operation, assignment and management of Internet addresses. The ASO is the entity established through the 2004 memorandum between ICANN and the NRO. Its Address Council consists of the NRO Number Council. This construction incorporates the existing regional-numbering system into ICANN rather than replacing that system with a names-led council.

The country-code and generic names structures are separately defined. The ccNSO develops and recommends global policies relating to country-code top-level domains. The GNSO develops policies concerning generic top-level domains within its scope. Their expertise and standing are real, but subject-specific. A vote in a names council is not a vote in an RIR policy forum.

The distinction can be expressed as a rule of construction: broad mission language identifies the systems ICANN may coordinate; the function-specific institutions and agreements identify how that coordination becomes legitimate. The first cannot be read while ignoring the second.

Number policy rises from the regions

The Internet Numbers Registry System is hierarchical. IANA manages the top of the unicast IP-address and ASN pools. Five RIRs administer continent-scale regions. Local Internet registries, network operators and other customers receive resources under regional rules. The hierarchy supports uniqueness and aggregation while distributing decisions close to affected operators.

Policy follows this structure. Regional allocation rules are developed in the relevant RIR communities through their open forums. A global policy is narrower: it concerns actions or outcomes needed across all RIRs and IANA, such as how IANA allocates blocks to the regional registries. The ASO memorandum sets out how a common proposal moves from the regions through the NRO and Address Council to the ICANN Board.

This arrangement does not remove ICANN. The Board has a defined ratification role, and the ASO advises it. The ASO also selects two ICANN directors. But the arrangement does not begin with the Board inventing a preferred allocation rule and ordering five regions to accept it. Consensus must be established through the regional policy communities and certified through the agreed global mechanism.

The distinction between facilitation and origination is essential. ICANN can ask whether the agreed steps were followed, whether a proposal is truly global and whether implementation fits its mission. It can provide the IANA operation that executes an adopted policy. Those functions are not equivalent to possessing the political mandate of RIR members and entities.

RFC 7020 captures the division in technical terms. The IETF specifies underlying facilities and constraints. IANA manages the top of the allocation hierarchy according to global number policies. RIRs conduct regional policy development and administer the resources for which they are responsible. Local registries then serve networks and end users. Routing decisions made by networks sit outside the registry system itself, even though address allocation and aggregation influence them.

This distribution of authority is why an address controversy must be routed to the correct forum. A dispute over a regional transfer rule belongs first within that RIR's policy and appeal structures. A dispute over IANA's timely execution of a valid top-level request belongs under the numbering SLA. A question about the technical definition of a special-purpose block may belong with the IETF. Sending all three to a names body because ICANN operates the root would erase the very accountability chain needed to decide them.

Naming authority has different customers and institutions

The post-2016 naming arrangement is elaborate because its customer base and risks are different. ICANN contracts with PTI to perform the IANA naming function. Top-level-domain registry operators are direct customers. The naming contract and statement of work specify how requests are handled, impose service expectations and require continuity, transparency and fair treatment.

The Customer Standing Committee monitors PTI's naming performance. Its core membership comes from generic and country-code top-level-domain operators, with liaisons from other parts of the ICANN community. It can engage PTI over deficiencies and escalate persistent problems to the ccNSO and GNSO. It cannot itself replace PTI, but it sits within a naming-specific chain that can lead to a special review.

Periodic and special IANA Naming Function Reviews evaluate performance against the naming contract. The ICANN Bylaws define the evidence, composition, recommendations and approval steps. In a severe case, a review can recommend a Naming Function Separation Process. That procedure can lead to a request for proposals, selection of another naming operator, non-renewal or termination of the naming contract, or a reorganization of PTI.

Every noun in that paragraph matters. It is a Naming Function Review. It assesses the Naming Function Contract. The Customer Standing Committee serves naming customers. A separation working group considers another operator for the naming function. These mechanisms do not silently become numbering procedures because PTI also performs number work.

The root-zone maintainer arrangement adds another distinct line. Verisign performs maintenance under an agreement with ICANN. IANA authenticates, verifies and submits changes; Verisign compiles, signs and distributes the root-zone file. The naming contract says PTI is not authorized to perform the maintainer's services unless authorized, and PTI may not change policies and procedures developed by the relevant bodies. Even within names, prestige does not erase role separation.

Names governance is therefore not a monolith, much less a source of number-registry authority. The ccNSO, GNSO, registry operators, CSC, PTI, ICANN and Verisign occupy different positions. If root-zone prestige cannot collapse distinctions among naming actors, it certainly cannot collapse the boundary between names and numbers.

The numbering contract places standing with the RIRs

The 2016 numbering agreement was written precisely to prevent standing from becoming ambiguous after United States stewardship ended. ICANN signed with AFRINIC, APNIC, ARIN, LACNIC and the RIPE NCC. The agreement recognizes the RIRs as representing the affected number community and makes ICANN the provider of administrative and technical services under global policies.

The RIRs can review performance, demand cooperation, pursue mediation and arbitration, decline renewal, terminate after an uncured finding of material failure and select a successor. They must exercise their powers collectively and unanimously. The IANA Numbering Services Review Committee advises the NRO Executive Council but cannot bind it without an express delegation.

This arrangement is not subordinate to the naming contract. The five RIRs are not third-party observers waiting for the Customer Standing Committee to recognize their grievance. Their standing comes from their own agreement. If a top-level number allocation is mishandled, the relevant contractual path runs from the RIRs to ICANN, with external dispute resolution if necessary.

PTI performs the number work through a subcontract from ICANN, but that corporate arrangement does not displace the principal bargain. ICANN remains accountable to the RIRs for the promised service. The shared operator supplies efficiency; the separate agreement supplies legitimacy.

The replacement clause makes the boundary unmistakable. On non-renewal or termination, the RIRs may select a successor numbering operator. By contrast, the naming separation procedure follows the ccNSO, GNSO, review team, ICANN Board and Empowered Community steps defined for names. One community's replacement decision does not choose the other's provider.

This is functional non-transferability in legal form. The current organization can perform several services, but the authority to continue each service comes from a different relationship. If PTI ceased performing names, it would not automatically lose the numbering agreement. If the RIRs replaced ICANN for numbering, Verisign would not thereby stop maintaining the DNS root. Operational changes might create shared-services work, but the mandates do not fall like dominoes.

The 2016 transition preserved diversity on purpose

The stewardship transition could have created one supervisory council for all IANA functions. It did not. The IANA Stewardship Transition Coordination Group asked three operational communities—names, numbers and protocol parameters—to develop plans according to their own needs. It then assessed whether the plans were compatible and workable together.

The final proposal defended this diversity as a form of subsidiarity. The three components were detailed and different because the communities had different subject matter, priorities and established institutions. The coordination group's task was not to flatten them into a single constitutional model. It was to ensure that independent arrangements could coexist without operational disruption.

The numbers community proposed a direct agreement with the five RIRs and a regional Review Committee. The protocol-parameters community relied on its memorandum and established relationship with ICANN, with policy authority remaining in the IETF. The names community created PTI, a naming contract, the CSC, reviews and a separation path closely connected to ICANN's accountability reforms.

PTI became the common operating affiliate for coherence and operational logistics. ICANN provides shared services. This common layer can make the result look centralized from outside. In constitutional terms, however, it is a hosting arrangement beneath three mandates, not a new source of undifferentiated policy power.

The transition's architecture offers a decisive answer to prestige spillover. The communities considered the same historical operator at the same political moment and chose different oversight structures. That choice would make little sense if root-zone authority automatically included number policy. Separate proposals were not temporary drafting quirks; they were the mechanism through which legitimacy was located with affected users.

The arrangement also rebuts the idea that organizational unity is required for technical stability. Compatibility can be achieved through agreements, shared services, coordination and transition planning. Policy unity is neither necessary nor desirable where the affected communities differ.

The root-zone administrator is not the root-zone maintainer

Confusion across functions often begins with confusion within the DNS root itself. The IANA naming operator receives a change request, validates authority and technical criteria, and submits an approved change. The root-zone maintainer compiles the zone, applies the change, signs the relevant material and distributes the resulting file to root server operators. Root server operators then serve the zone.

Before the transition, NTIA supplied an authorization step and Verisign maintained the zone under its United States cooperative agreement. After the transition, the NTIA step was removed, and ICANN entered a maintainer agreement with Verisign. ICANN and Verisign tested the revised arrangement in parallel before it took effect.

This division shows why the phrase "control of the root" is analytically weak. Control of what: validation, policy, compilation, signing, distribution or service? Different actors answer each question. A top-level-domain operator also controls its delegated zone, while recursive resolvers and network operators decide which root information they use. The existence of one canonical public root does not eliminate distributed responsibility.

Number registration has a parallel but different hierarchy. IANA records top-level allocations to RIRs. RIRs allocate or assign resources regionally. Local registries and networks receive and use them. No root-zone maintainer sits above that hierarchy with authority to approve an ASN transfer. A DNS root role cannot be mapped onto number allocation merely by calling both systems hierarchical.

The lesson is methodological. Institutional analysis should identify the exact transaction and the actor entitled to perform it. Titles such as administrator, operator, maintainer, registry and policy body describe different powers. Prestige grows when those titles are treated as synonyms.

Reverse DNS is an intersection, not a merger

Reverse DNS is the hardest boundary case because it connects address space to the DNS. IPv4 reverse delegations use in-addr.arpa; IPv6 uses ip6.arpa. IANA, the RIRs and address holders participate at different levels of those zones. A reader might conclude that whoever controls the DNS root therefore controls the meaning or ownership of IP addresses.

The conclusion is wrong. Reverse-DNS delegation follows number-resource authority; it does not create it. A PTR record can associate an address with a domain name, but it does not allocate the address. A parent-zone update can make a reverse zone reachable, but it does not decide whether the holder satisfied an RIR's transfer policy. DNSSEC validation protects the integrity of a naming chain; it does not adjudicate title to the underlying number block.

The numbering SLA's 2024 amendment reinforces this distinction. The parties added reverse-resolution services to the agreement between ICANN and the RIRs, including performance expectations for request acknowledgement, propagation and availability. That placement recognizes reverse DNS as a service needed by the numbering community, even though the service uses DNS technology.

The IETF also has a role because it specifies the relevant protocols and technical boundaries. The RIRs have authority over regional number records and submit upper reverse changes. IANA administers the relevant upper zones according to those responsibilities. This is coordinated authority across a seam, not the annexation of numbers by names.

Boundary technologies often invite institutional overreach because each entity can point to a necessary step. Necessity is not supremacy. A maintainer must publish the delegation, but cannot choose the lawful address holder. An RIR can recognize the holder, but cannot force a malformed zone into the DNS. The IETF can define the protocol, but does not decide each regional allocation. Governance works when each necessary actor can refuse within a reviewable scope and cannot use that refusal to claim the others' mandates.

Board power is real and constrained

Because ICANN's Board sits above the corporation and PTI, observers sometimes treat it as the final legislature for every identifier question. The Board does have substantial authority. It approves corporate actions, ratifies qualifying global number policies, oversees ICANN's performance and acts within the accountability framework. The ASO selects two directors, while names bodies select others.

Board membership does not merge mandates. Directors serve as individuals with duties to ICANN, not as representatives ordered by the nominating body. An ASO-selected director does not become an RIR delegate with power to rewrite regional policy. A director associated with names does not acquire number-community consent merely by voting on an ICANN resolution.

For number policy, the Board's role is embedded in the ASO memorandum and the Bylaws. The proposal must arise through the agreed regional and global sequence. Board review is a safeguard and a point of institutional responsibility, not an independent substitute for community agreement. If the Board has concerns, the established procedure governs how they are addressed.

For naming performance, the Board operates under Articles 16 through 19, the naming contract and the special approval thresholds around reviews and separation. The ccNSO, GNSO and Empowered Community have defined positions. Those provisions are detailed precisely because ordinary corporate discretion was not considered enough.

The Board also cannot act outside ICANN's mission. An expansive claim based on the corporation's public prestige can therefore be challenged as a mandate problem, not merely criticized as poor etiquette. Institutional legitimacy depends on showing the chain from mission to affected community to agreed procedure.

This does not make the Board ceremonial. It means authority is conditional. The Board can ratify, oversee, fund, contract and enforce within defined channels. It cannot transform a root-zone controversy into a regional number-allocation rule without the number community's process.

Shared resources create dependency, not jurisdiction

PTI's operation of names, numbers and protocol parameters uses common people, facilities and support from ICANN. The post-transition services agreement covers functions such as finance, legal support, human resources and technology. Shared arrangements can create operational dependencies. A disruption to a common authentication service or office may affect more than one function.

Dependency matters for continuity. A community considering another operator must know which systems can be separated, which records are portable and which expertise is shared. Transition plans must preserve the other functions. The risk is practical, not constitutional.

Organizations often convert dependency into influence. If one party controls a shared service, it may shape timing, budgets or information. That is why separate agreements need funding duties, performance measures, portability and review. But influence arising from dependency is not legitimate policy authority. It is a risk to be governed.

The distinction can be tested with a simple counterfactual. Suppose ICANN stopped funding a common service and number performance deteriorated. The RIRs would have a claim under their agreement; ICANN could not defend the failure by invoking its names-community approval. Conversely, if the naming contract were amended after a proper names procedure, the change would not rewrite the RIRs' SLA unless those parties separately agreed.

Shared branding creates a similar dependency of public understanding. The IANA name reassures users that registries are authoritative. Splitting every function into a different brand could create confusion and weaken trust. Keeping the brand is sensible so long as public materials state which mandate supports each act.

The right conclusion is therefore neither total separation nor assumed unity. Operational integration can continue. Authority must remain function-specific, evidenced and portable.

Five tests for functional non-transferability

The first test is policy origin. Who develops the rule being applied? A generic-domain consensus policy originates through the GNSO's defined mechanisms. A global country-code policy follows the ccNSO's scope. A regional number rule arises in the relevant RIR community. A global number rule must pass through all regions and the ASO sequence. A protocol-parameter instruction arises from the relevant standards body. If a claim points only to ICANN's general status, it has not answered the policy question.

The second test is customer identity. Naming customers include top-level-domain registry operators and other direct users specified by the naming arrangement. Numbering customers at IANA's top level are the RIRs. Protocol-registry users organize through the IETF relationship. The customer determines what satisfactory service means and who can supply direct evidence of failure.

The third test is the governing agreement. Names performance is defined by the ICANN-PTI naming contract and statement of work. Numbers performance is defined principally by the RIR-ICANN SLA, with PTI performing under a subcontract. Root maintenance is governed by the ICANN-Verisign agreement. Protocol parameters follow the IETF-ICANN memorandum and related arrangements. One agreement cannot be cited as if it amended another.

The fourth test is enforceability. The CSC monitors names and can escalate within the naming chain. The RIRs hold numbering rights and act collectively. ICANN can enforce its root-maintainer agreement. The IETF has the rights established for protocol registries. Prestige does not give a body standing it lacks in the relevant instrument.

The fifth test is replacement. The names separation procedure can choose another naming operator. The RIRs may choose a successor numbering operator. The root maintainer can be transitioned under its own provisions. The ability to replace one provider without automatically replacing the others is decisive evidence that the functions are institutionally separable.

Together these tests expose most false claims. They do not ask who has the largest conference, the best-known brand or the most politically charged history. They ask who is authorized to make and enforce the decision at issue.

Common category errors in public debate

The first error is to say that ICANN allocates addresses to Internet users because it coordinates the top-level pool. In ordinary operation, RIRs serve regional members and other recipients. IANA's top-level role is essential but narrow. It does not make ICANN the direct registry for every network.

The second is to infer that a controversial top-level-domain decision proves how ICANN would decide an ASN dispute. The entities, policies, evidence and review channels differ. A history of deference or intervention in names may offer a cultural warning, but it is not a legal precedent for number policy.

The third is to treat the Customer Standing Committee as a universal IANA regulator. Its mission concerns naming performance. Numbering has a separate Review Committee with advisory status and separate contractual parties. A names escalation cannot cure a number-service failure.

The fourth is to assume that ICANN's ability to contract with the root-zone maintainer allows it to alter reverse-DNS authority contrary to number allocations. Maintenance must follow authenticated, authorized instructions and the relevant responsibilities. Technical publication is not beneficial ownership.

The fifth is to assume that an ICANN Board seat selected through the ASO turns the Board into the source of regional consensus. Selection gives the numbering community participation in corporate governance. It does not transfer the RIR communities' policy mandate to two individuals.

The sixth is to treat one operator as proof that separation is impossible. The 2016 arrangements expressly contemplate function-specific successors. Transition may be costly and shared systems may need division, but difficulty is not non-existence.

The seventh is the opposite mistake: claiming that ICANN has no role in numbers. The Bylaws give it a top-level coordination mission, the Board participates in global-policy ratification, and ICANN is the numbering service counterparty. Correcting overreach should not erase defined authority.

Why spillover can damage number governance

Venue error is the first harm. If governments, companies or advocates bring a regional allocation dispute to names institutions, the people with operational knowledge and policy standing may be bypassed. A highly visible forum can then pronounce on a question it is poorly equipped to resolve.

The second harm is accountability dilution. ICANN may be blamed for an RIR decision it did not make, while the RIR escapes scrutiny. Or ICANN's prestige may be used to validate a weak regional action without testing the regional procedure. Responsibility becomes broad enough that no one is answerable for the exact act.

The third is consensus capture. A well-resourced names constituency can dominate attention at global meetings and present its priorities as the Internet community's view. Number entities are not necessarily absent; their mandate is exercised through different forums. Counting attendance in the wrong room can manufacture consensus.

The fourth is crisis centralization. During an RIR governance dispute, outsiders may call for ICANN to take over because it appears to be the nearest global authority. The impulse can ignore recognition criteria, regional legitimacy, operational continuity and the agreed roles of the NRO and ASO. A rushed central intervention may weaken the distributed system it claims to protect.

The fifth is evidential substitution. Root-zone stability metrics, naming-service reviews or generic-domain compliance records may be offered as proof that number registration is sound. They measure different transactions. Shared staff can justify a cross-function operational-risk assessment, but not the substitution of one function's evidence for another's.

The final harm is precedent by rhetoric. Repeated descriptions of ICANN as the owner or supreme regulator of Internet numbers can harden expectations. Future boards, governments or courts may encounter a public record that overstates the mandate. Precision today protects institutional boundaries tomorrow.

Boundaries do not require institutional hostility

It is possible to defend number-community autonomy without treating ICANN as an adversary. The current system depends on cooperation. ICANN funds and supports PTI, contracts for root maintenance, hosts governance structures and performs the numbering service. The RIRs participate in the ASO, select directors and reimburse the service. The IETF supplies technical constraints. These relationships can work well because duties are allocated, not because everyone is fused.

Names expertise can also help number operations. Security practices, continuity testing and registry engineering may be shared. A DNS specialist is relevant to reverse DNS. A corporate audit can examine common controls. Cross-community consultation is sensible where a proposed change affects multiple functions.

Consultation is not consent. A names body may identify a dependency but cannot approve a number policy for the RIRs. The RIRs may explain number effects but cannot dictate generic-domain policy. The strongest cross-community work states which body owns the final decision and why.

Boundaries should also be permeable to evidence. If a common service fails, every affected community should receive a truthful account. If a planned naming separation would disrupt number operations, the RIRs should be consulted before implementation. Functional autonomy does not justify secrecy about shared risk.

The goal is disciplined federation: common operations where efficiency and security justify them, separate mandates where legitimacy requires them, and explicit coordination at the seams.

How to speak accurately about authority

Public institutions should stop using "IANA authority" without naming the function. A statement should say IANA naming operator, IANA numbering operator or protocol-parameters registry operator. Root-zone administrator and root-zone maintainer should not be interchangeable. ICANN's corporate role should be distinguished from PTI's operational role.

Claims about number policy should cite the regional or global policy path. Claims about service performance should cite the numbering SLA and monthly reports. Claims about naming oversight should cite the naming contract, CSC or naming review. Claims about root-file production should cite the maintainer agreement. This citation discipline is not pedantry; it reveals who can be challenged.

Meeting records should identify the capacity in which a entity speaks. An ICANN director, ASO Address Council member, RIR executive and Review Committee member may be the same person at different times, but the authority changes with the role. Personal expertise can cross boundaries; institutional power cannot be assumed to follow.

Media coverage should ask the five non-transferability questions before describing a body as in control. Who made the policy? Who is the customer? Which agreement applies? Who can enforce? Who chooses a successor? If the answers point to the RIRs and number community, root-zone prestige is context rather than authority.

Courts and governments should be equally precise. ICANN's California incorporation and agreements create legal rights, but they do not make every number dispute an ICANN corporate matter. An RIR's jurisdiction, membership commitments and regional procedures may control a regional decision. The numbering SLA governs top-level service between its named parties. Root-zone arrangements answer different questions.

Accuracy in language has an operational payoff. During a failure, responders know whom to contact, what evidence to preserve and which remedy is available. During policy development, entities know where consent must be built. During transition, counterparties know which service can move and which can remain.

The limits of the separation argument

Functional distinction should not be exaggerated into total independence. Names and numbers both contribute to the stable operation of unique identifiers. They share the IANA brand, PTI, ICANN support and some technical infrastructure. A corporate or security failure can cross the boundary. Budget decisions at ICANN can affect PTI's capacity to perform all three functions.

ICANN also has a genuine mission in number coordination. The Board's ratification role and the ASO's place in the Bylaws are not decorative. Global number policies need execution at the top of the hierarchy. The RIRs chose ICANN as counterparty in 2016 rather than forming a wholly separate operator from the first day.

Nor are the RIRs immune from legitimacy questions. Regional policy participation, membership accountability, board conduct, recognition and continuity can all be contested. Saying that the GNSO lacks authority over an RIR does not prove that every RIR decision is correct. It identifies the forum and standards through which the decision should be judged.

Operational communities can also agree to change their relationships. The parties may amend the numbering agreement. ICANN's Bylaws can be amended through their required procedures. The IETF and ICANN can update their memorandum. Functional non-transferability is not eternal immobility; it means change requires consent from the right holders rather than prestige-based assumption.

Finally, some events legitimately need joint action. A major compromise of shared systems, a change to the IANA intellectual property arrangements or a transition affecting common staff may touch all functions. Joint action remains a coordination of mandates, not evidence that one mandate swallowed the others.

Prestige should follow performance within mandate

ICANN deserves recognition for stable root-zone coordination when the evidence supports it. PTI deserves recognition for accurate numbering service when its reports and RIR review support that conclusion. The RIRs deserve recognition for legitimate regional policy when their communities can see how decisions were made. Prestige is healthiest when it follows demonstrated performance within a defined role.

The reverse order is dangerous. If prestige becomes the premise, an institution can claim adjacent authority because it is trusted elsewhere. The result is mandate inflation: root stewardship becomes names sovereignty; names sovereignty becomes identifier sovereignty; identifier sovereignty becomes a claim over networks and content. ICANN's own mission limitations reject that progression.

The Internet's identifier system is resilient partly because no single prestige hierarchy controls every layer. Standards, top-level registries, regional registries, local registries, DNS operators and network operators constrain one another. Coordination is achieved through documented interfaces and agreements rather than a universal administrator.

The IANA label should be understood in that distributed tradition. It marks trusted performance of several related roles. It does not erase the communities that authorize those roles. Shared execution is a service to plural governance, not an argument against it.

A boundary that protects both systems

Separating names authority from number authority protects the numbering community from capture by a more visible constituency. It also protects names governance from being held responsible for decisions it cannot legitimately control. Clear boundaries make accountability fairer in both directions.

For numbers, the operative chain is explicit. The IETF defines technical constraints. Regional communities develop regional policy. The five RIRs coordinate global policy through the NRO and ASO arrangements. ICANN and PTI perform the top-level service under an agreement that the RIRs can enforce and, ultimately, replace.

For names, generic and country-code communities develop policies within their scopes. PTI performs the IANA naming function under contract. The CSC monitors customers' service. Naming reviews and the separation procedure provide escalations. Verisign maintains the root-zone file under a distinct agreement. Root server operators distribute the result to users.

The chains meet in one corporation and in several technical seams, but they do not become interchangeable. An actor's authority at the meeting point is limited to the task that brought it there. This is the essence of functional non-transferability.

Root-zone politics will continue to attract attention. Governments will care about national domains, companies will care about generic strings, and security specialists will care about the DNS root. That attention can illuminate governance. It becomes harmful only when it is treated as a source of power over a different registry system.

The correct response is not a slogan that ICANN has all authority or none. It is a mandate map. Name the function, policy community, customer, agreement, remedy and successor right. Once those are visible, the prestige spillover loses its constitutional force. The DNS root remains vital, and the number registries remain governed by the communities whose networks depend on them.

Sources

1. ICANN Bylaws, Articles 1, 9 and 16–19 — distinct mission clauses, ASO role, naming contract, CSC, naming reviews and naming-specific separation.
2. RFC 7020, The Internet Numbers Registry System — IANA as a role, the allocation hierarchy, IETF responsibilities and regional policy authority.
3. 2004 ICANN Address Supporting Organization memorandum — global number-policy relationship among the NRO, ASO and ICANN, retained here as the historical text underlying the cited policy sequence.
4. ICANN announcement of the 2004 ASO memorandum — stated purpose of the ASO and bottom-up number-policy role.
5. Service Level Agreement for the IANA Numbering Services — RIR standing, operator duties, policy separation, remedies and successor selection.
6. Internet Number Community transition proposal — the numbering community's choice of a direct agreement and regional Review Committee.
7. IANA Stewardship Transition Proposal — independent proposals from names, numbers and protocol-parameters communities and the subsidiarity rationale.
8. RFC 7979, protocol-parameters community transition response — distinct operational communities and the IETF response.
9. IANA Naming Function Contract — PTI's naming duties, exclusions, transparency and continuity.
10. ICANN Board record approving the naming contract — naming-specific customers, service expectations and legal arrangement.
11. PTI agreements index — separate naming, numbering, protocol-parameter and root-maintainer instruments.
12. Post-transition IANA corporate arrangements — PTI, common services and separate number and protocol subcontracts.
13. Root Zone Maintainer Agreement overview — distinct IANA and Verisign roles in root-zone production and distribution.
14. Root Zone Maintainer Service Agreement — maintainer duties and transition terms.
15. ICANN account of the post-transition root-zone arrangement — removal of the NTIA authorization role and continuation of Verisign maintenance.
16. NTIA 1998 Statement of Policy on Internet Names and Addresses — historical emphasis on DNS coordination and the creation of a representative nonprofit corporation.
17. RFC 2860, IETF-ICANN memorandum concerning IANA technical work — division between IETF technical authority and IANA operational work.
18. NRO numbering SLA page and reverse-resolution amendment — placement of reverse DNS within the numbering service relationship.