Summary
- The Compact adopted in September 2024 is an intergovernmentally negotiated framework with participation and voluntary endorsement by non-state actors. Its Internet-governance section reaffirms existing WSIS outcomes and stakeholder roles rather than defining a new technical chain of command.
- The final text makes concrete institutional assignments where Member States intended them: a data-governance working group, processes for an international AI scientific panel and global dialogue, United Nations coordination and a 2027 high-level review. It makes no comparable assignment concerning IANA, Regional Internet Registries, address blocks or autonomous system numbers.
- Internet number authority is function-specific. IETF specifications define technical facilities and reserved uses; the IANA role manages the top of the allocation hierarchy; RIRs allocate and register resources under community-developed policies; networks decide whether and how to announce routes. These acts are not interchangeable.
- The Compact can influence national law, development finance, connectivity policy, human-rights expectations and inter-institutional coordination. Any claim that it changes a registry's operating power must still identify the actor, function, instrument, effective act, transferred capability, review mechanism and continuity plan.
The vocabulary sounds constitutional because the subject is global
The Global Digital Compact, adopted as an annex to the Pact for the Future in September 2024, speaks in the register of common purpose. It describes the Internet as a critical global facility. It says that the network must be open, global, interoperable, stable and secure. It recognizes global and multistakeholder governance and names governments, the private sector, civil society, international organizations, technical and academic communities and other relevant stakeholders.
Language this broad easily acquires a constitutional aura. The Internet is global, the agreement is global, and the named actors already perform consequential functions. It is tempting to read the text as a new settlement of who has authority over the infrastructure.
That reading skips the institutional verbs. The Compact recognizes, reaffirms, acknowledges, promotes, supports, invites, calls upon, requests and commits. Each verb has an entity. In the Internet-governance section, Member States commit to promote an open and reliable Internet, support the Internet Governance Forum, cooperate against fragmentation and refrain from shutdowns. They do not establish a number registry, appoint its operator, approve an allocation policy or direct a transfer of records.
The distinction matters most where public-policy language meets scarce or unique technical resources. IPv4 addresses, IPv6 blocks and autonomous system numbers are administered through global and regional registries. Decisions in that system affect network entry, routing coordination, security records, transfers and operational continuity. A broad claim that the Compact "empowers the technical community" could be used to shield an incumbent. A contrary claim that a United Nations agreement now supervises number allocation could be used to bypass the existing policy and service chain. Neither follows from the text.
The Compact changed the political environment in which technical institutions operate. It did not silently rewrite their mandates.
The 2023 proposal was an input, not the adopted settlement
The chronology prevents later language from being projected backward. In May 2023, the Secretary-General's Policy Brief 5 proposed a Global Digital Compact and offered ideas for Member State consideration. It described stronger international cooperation as necessary and treated long-established multistakeholder institutions as part of the Internet's governance.
The brief was explicit about institutional continuity. It said existing digital-cooperation organizations should be brought together according to their respective mandates and competencies. In its proposed follow-up model, Internet-governance objectives would continue to be supported by the IGF and bodies such as ICANN and the IETF within their areas of expertise. It also proposed an annual Digital Cooperation Forum to review implementation and coordinate a hub-and-spoke arrangement.
These were recommendations from the Secretary-General, not powers already adopted by the General Assembly or accepted by the named institutions. The brief says its ideas were neither exclusive nor exhaustive and were intended as a basis for consultation. That status is central to an authority analysis. A policy brief can propose a forum; it cannot create the forum merely by describing it.
Member States then negotiated. The April 2024 zero draft framed the Compact as objectives, commitments and actions, reaffirmed WSIS, named collaboration with technical and academic communities, and treated the IGF as a key platform. Revisions altered language before adoption.
The final Compact did not establish the proposed Digital Cooperation Forum. It recognized the IGF as the primary multistakeholder platform for discussion of Internet-governance issues and created a different review architecture. That change demonstrates why proposal, draft and adopted text must remain separate. Institutional authority cannot be borrowed from an idea that did not survive negotiation.
The final text is led by governments and open to voluntary non-state endorsement
The Compact carefully identifies its speaking actor. It says, "As governments, we will work" with other stakeholders in their respective roles and responsibilities. Its principles recognize the contributions of all sectors, but the commitments were negotiated and adopted by Member States through the General Assembly process.
The follow-up section confirms the distinction. International and regional organizations, the private sector, academia, the technical community and civil society are invited to endorse the Compact voluntarily and take part in implementation. Voluntary endorsement may create a public commitment for the endorsing institution. It does not turn that institution into a party with powers equal to a state, nor does it assign a technical function.
This structure does not reduce non-state participation to decoration. Companies operate networks and platforms; technical communities develop standards and maintain registries; researchers and civil society supply expertise, scrutiny and affected-user evidence. Implementation cannot succeed without them. But contribution, endorsement and operational authority are different relationships.
The Compact also respects national policies, priorities, capacities and applicable legal frameworks. A Member State may implement a commitment through legislation, regulation, funding or diplomacy within its competence. Those later acts can create enforceable duties. The Compact's text alone does not supply the domestic procedure, jurisdiction, due process or remedy that such duties require.
For a private registry, the same discipline applies. Endorsing the Compact may support a commitment to openness, inclusion or anti-fragmentation. It does not enlarge the registry's service region, make an address registration a property title, authorize seizure of a resource, change a membership agreement or bind networks to accept a route.
The Compact creates political commitments and a framework for cooperation. Operational effect still travels through an authorized institution and a specific instrument.
"Respective roles and responsibilities" is a boundary clause
The phrase "respective roles and responsibilities" appears throughout the history of Internet-governance diplomacy because it permits agreement among actors that do not accept one hierarchy. Governments can retain public-policy and legal authority. Companies can operate infrastructure and services. Civil society can represent interests, investigate harm and challenge power. Technical communities can develop standards and administer coordinated resources. International organizations can convene, assist and act within treaties or mandates.
The phrase is not self-executing. It does not list every actor, define the scope of every role, resolve overlap or create a remedy when an institution exceeds its competence. That ambiguity allows cooperation; it also allows strategic expansion.
An incumbent may say that its historic role was internationally reaffirmed and therefore cannot be questioned. But reaffirming the existence of roles does not validate every present procedure or grant permanent exclusivity. The role remains bounded by the instruments that created it and by applicable accountability.
A government may say that sovereign public-policy responsibility allows it to direct any technical operation. But public-policy competence does not automatically provide credentials, contractual rights, community approval or network acceptance. A legitimate law may affect operators; it still has jurisdictional and procedural limits.
A new coalition may call itself the technical community and claim the Compact's recognition. The text names a stakeholder category, not a corporation or electoral college. A category does not appoint its representative or confer custody of a registry.
The only safe use of the phrase is as an instruction to identify the relevant role for the issue. For an address allocation, one asks which registry policy and agreement apply. For a protocol reservation, one asks what the standards process authorizes. For a route announcement, one asks which network originates and which networks accept it. For a rights restriction, one asks which public authority and law apply.
The Compact preserved this functional pluralism. It did not resolve it into a sovereign.
Reaffirming Geneva and Tunis preserves history rather than replacing it
The final Internet-governance section says governance should continue to follow the outcomes of the Geneva and Tunis summits, including enhanced cooperation. This is a continuity clause. It is not a declaration that earlier ambiguities have disappeared.
The 2003 Geneva Declaration of Principles recognized the sovereign public-policy authority of states, the important technical and economic role of the private sector, the important role of civil society, the facilitating role of intergovernmental organizations and the standards-related role of international organizations. It called for multilateral, transparent and democratic management with full involvement of stakeholders. It then asked for further inquiry into definitions, issues and responsibilities.
The 2005 Tunis Agenda adopted a broad working definition of Internet governance and distinguished the roles of stakeholders. It created the IGF as a non-binding forum without an oversight role or involvement in day-to-day technical operations. It also discussed enhanced cooperation and recognized the need for stable, secure functioning.
Those texts widened political standing and established forums. They did not create a single operator of names, numbers, standards, routes and content policy. Their deliberate distribution of functions is the inheritance the Compact reaffirmed.
If the 2024 negotiators had intended to replace the existing number-registry structure, a general reference to Geneva and Tunis would be an implausible transfer mechanism. A transition would need to identify the function, current and successor operators, policies, records, service levels, credentials, effective date, dispute process and continuity safeguards. No such provisions appear.
Reaffirmation therefore has two symmetrical effects. It denies the claim that the Compact displaced technical institutions merely by entering the field. It also denies those institutions a new and unlimited title. Their authority remains what the existing chain supports - no less, and no more.
The Compact makes specific assignments when it means to change institutions
The final text contains a useful internal control. Where Member States intended new institutional work, they used more concrete language.
On data governance, the Compact requests that the Commission on Science and Technology for Development establish a dedicated working group, specifies an inclusive dialogue and points toward a report to the General Assembly. On artificial intelligence, it commits to an international scientific panel and a global dialogue, and requests co-facilitators to develop terms of reference and modalities through an intergovernmental process for General Assembly adoption.
For United Nations coordination, it requests a proposal for an office that builds on the existing technology envoy function and asks for operational functions, structure, location, mandate renewal, resources and staffing. For review, it decides to hold a high-level meeting during the eighty-second General Assembly session, based on a Secretary-General's progress report and stakeholder input, with co-facilitators to develop modalities.
These clauses do not complete every later detail, but they identify bodies, outputs and next acts. They show the drafting tools available when institutional change is intended.
The Internet-governance subsection uses a different structure. It recognizes the Internet's qualities, reaffirms global multistakeholder governance and WSIS outcomes, acknowledges the IGF as a discussion platform, and lists four government commitments. It does not request a number-policy working group, designate an allocation authority, create a registry review body or direct ICANN, IANA or an RIR to act.
Absence alone is not always decisive. Here it is reinforced by continuity language and the specificity used elsewhere. The text knew how to create a process. It chose not to create one for Internet number operations.
This comparison is a better guide than the grandeur of the preamble. Institutional power resides in the operative assignment, not in the proximity of a technical body to a global aspiration.
The Internet Numbers Registry System has several distinct functions
The Internet Numbers Registry System described in RFC 7020 distributes globally unique IP address space and autonomous system numbers. It is hierarchical for administrative and scaling reasons, but hierarchy does not make every entity a subordinate office of one global government.
At the top, the IANA role manages the IP address and AS number allocation hierarchies. Regional Internet Registries receive resources and serve Local Internet Registries and other customers. Local registries and providers serve their own users and customers. Community-developed policies address allocation, registration and related administration.
RFC 7020 identifies goals that can conflict: managing finite pools, supporting hierarchical allocation and maintaining accurate unique registration. It explicitly separates the registry from route operation. Whether an address is announced and how the announcement propagates are operational questions outside the registry system's scope.
The companion RFC 7249 identifies the IANA registries associated with the system: AS numbers, IPv4 address space and IPv6 global unicast assignments. It also distinguishes special-purpose reservations governed through IETF processes from ordinary allocations handled through the registry system.
These distinctions produce at least five acts: defining the technical number space; reserving values for protocol purposes; allocating blocks down the hierarchy; registering the allocation and related information; and announcing or accepting routes. A sixth act may involve contractual or legal treatment of a holder's rights. No one adjective such as "multistakeholder" decides all six.
The Compact does not name any of these acts. Its commitment to an interoperable and reliable Internet expresses a public objective against which the system can be evaluated. It does not identify which actor may alter a registry entry or on what evidence.
An authority claim concerning numbers must therefore descend from global vocabulary to the exact transaction.
ICANN's role is narrow even where its language is global
The ICANN Bylaws define a mission to ensure the stable and secure operation of unique identifier systems. For numbers, ICANN coordinates allocation and assignment at the top-most level of Internet Protocol numbers and autonomous system numbers. The words "top-most level" are a material boundary.
ICANN does not ordinarily decide whether a regional customer qualifies for an address block under an RIR policy. It does not choose which routes every network accepts. It does not turn address registration into universal ownership. Its number function sits at the top of a system whose other levels have distinct policies and relationships.
The Bylaws are a corporate governance instrument. The Compact did not amend them. Nor could rhetorical recognition of the technical community substitute for the corporate acts, agreements and policy procedures required to change ICANN's mission.
This point cuts both ways. ICANN cannot cite the Compact's praise for stable global coordination as authority to expand into functions outside its mission. A critic cannot cite the Compact's governmental adoption as proof that Member States collectively acquired ICANN's operational credentials.
Where public policy and identifiers interact, coordination may be necessary. Sanctions, competition law, court orders, cybersecurity obligations and human-rights duties can affect institutions. The resulting action still needs a valid legal and institutional route. Stability is an objective to weigh in that route, not an immunity and not a universal warrant.
The correct question is not whether ICANN is private while the Compact is public. It is which function ICANN is performing, which instrument authorizes it, which accountability applies and whether a later valid act changed that chain.
The Compact supplied no such later act for number allocation.
Global number policy travels through the ASO process, not diplomatic implication
The Address Supporting Organization connects regional number-policy communities with ICANN. The ASO Memorandum of Understanding and its global policy process define how a proposal requiring common action across all RIRs moves through regional forums, the Address Council and the ICANN Board.
The process is cumbersome because global number policy can affect every region and the top of the allocation hierarchy. It requires more than a general declaration that a policy would advance inclusion or stability. The proposal must fall within the defined category, obtain the required regional support, be reviewed and transmitted through named bodies, and receive the action the governing instruments specify.
The Compact did not replace this path. It did not say that a General Assembly majority, a Compact endorsement list, the IGF or a group of technical organizations can skip regional policy processes. It also did not ratify every existing ASO procedure as permanently legitimate.
The Compact can influence the debate around a proposal. Entities may use its development, rights, inclusion or anti-fragmentation commitments as policy arguments. Governments may participate in regional communities or implement related domestic measures. The IGF can expose conflicts and connect institutions. None of those acts is equivalent to adoption of a global number-resource policy.
This distinction protects less-resourced entities as well as incumbents. If broad diplomatic language could be converted directly into number policy, the actor best able to control interpretation would gain an informal shortcut. A visible policy process at least identifies the proposal, decision stages, objections and accountable institutions.
The right response to weaknesses in that process is to reform it through its governing and legal mechanisms, not to pretend the Compact silently supplied a substitute.
The IANA numbering service is governed by an actual service agreement
As part of the 2016 stewardship transition, ICANN and the five RIRs signed the Service Level Agreement for the IANA Numbering Services before the transition and brought it into effect when the transition occurred. It identifies the parties, services, policies, performance requirements, reporting, review, dispute handling, term and termination arrangements.
This is what an operational mandate looks like. It does not rely on a declaration that the Internet is global. It says who must perform which service for whom, under what standards and with what consequences. The IANA performance pages and the Number Resource Organization's review process provide evidence against the service obligations.
The agreement is not the source of every right in the number system. It governs a defined relationship at the top of the hierarchy. Regional allocation and registration remain subject to RIR policies and customer or membership arrangements. Protocol reservations follow their own standards path. Routing remains distributed among networks.
The contrast with the Compact is decisive. The GDC contains public commitments and review mechanisms at the level of digital cooperation. It does not modify the numbering agreement's parties, service levels, instructions or termination rights. A private institution cannot point to GDC endorsement as a substitute for compliance with the agreement. A Member State cannot invoke the Compact alone to issue an operational instruction under a contract to which it is not a party.
If a future intergovernmental agreement were intended to alter this service, it would still need implementation capable of transferring or constraining the operational function without breaking uniqueness and continuity. Political authority and technical capability would have to meet in a specific act.
The 2024 Compact stopped well before that boundary.
Registration, routing and legal control must not be collapsed
Public discussion often treats an address block as one entity controlled by one registry. In practice, several records and relationships matter. A registry records an allocation or assignment. A holder may have contractual or membership rights and duties. A Route Origin Authorization can identify an autonomous system authorized to originate a prefix for RPKI validation. Network operators decide which routing information to announce and accept. Courts and public authorities may affect persons or agreements within jurisdiction.
These layers can point in different directions. An accurate registry entry does not force a network to carry a route. A route visible in BGP does not prove lawful entitlement to the address space. An RPKI object supports route-origin validation but does not adjudicate every contractual dispute. A court order may bind parties without producing universal network acceptance.
The Compact's anti-fragmentation and reliability language is relevant to the consequences of decisions across these layers. It does not merge them. "Maintain an open Internet" is not an instruction to approve a disputed transfer. "Prevent fragmentation" is not a presumption that every existing route or holder must remain unchanged. "Technical community" is not a single custodian of all records.
This separation is especially important under IPv4 scarcity. Addresses can carry significant economic value in transfers and leases, but the registry system's technical purpose remains uniqueness and coordination. Describing number resources as assets does not settle property status across jurisdictions or expand a registry's remedies.
Any operational claim should name the layer. Is the requested act a registry update, a certificate change, a route announcement, contract enforcement or legal seizure? The answer determines the evidence and authority. The Compact supplies principles that may inform the decision. It does not choose the decision maker.
Connectivity commitments affect demand without reallocating supply
The Compact makes significant commitments on connectivity. It calls for meaningful and affordable access, resilient infrastructure, financing, connectivity for schools and hospitals, and attention to underserved communities. These commitments can shape development budgets, universal-service policy, procurement, spectrum planning, satellite access and local network support.
They can also affect demand for Internet number resources. A new network may need IPv6 space and an autonomous system number. Growth can increase the need for training, registry services, routing security and accurate records. Governments and development institutions may fund the capacity required to participate in regional policy and deploy IPv6.
Demand does not create allocation authority. A ministry implementing a school-connectivity programme normally requests resources through the relevant registry path or a provider. The Compact does not reserve a pool for GDC projects, order an RIR to waive policy, or authorize the United Nations to issue numbers.
Nor does the commitment justify discriminatory denial by a private body. An RIR should apply its governing policy, contractual duties and applicable law. If those rules undermine legitimate access or development, the remedy may be policy change, legal challenge, institutional review or alternative technical design. The Compact can strengthen the public argument for that remedy without becoming the transaction itself.
This is a useful model of diplomatic influence. Global consensus sets priorities and mobilizes cooperation. Specialized institutions translate those priorities within their competence. Evidence flows back to public review. Authority remains traceable at each step.
Confusing demand policy with resource title would weaken both. Development commitments would become hostage to disputes about institutional control, while registry decisions would be defended or attacked with language too broad to resolve their facts.
Anti-fragmentation is an outcome to protect, not a competence to seize
The Compact asks stakeholders to cooperate against fragmentation. This is one of its most operationally resonant commitments because names, numbers, routes, protocols, shutdowns and incompatible regulation can all affect the experience of a global Internet.
Fragmentation has multiple meanings. A state may block connectivity. Networks may cease exchanging routes. resolvers may use incompatible naming roots. Regulations may make services unavailable across borders. Technical standards may diverge. Markets may split even while packets remain interoperable.
No single institution has authority over every form. Giving a registry power over content policy would not solve regulatory fragmentation. Giving an intergovernmental forum credentials to alter routes would not make networks accept them. Giving a company control of standards would create another concentration risk.
The anti-fragmentation commitment should therefore trigger a dependency analysis. Which layer is splitting? Which actors can cause or remedy it? What legal and technical instruments apply? What continuity risks follow from intervention? Which affected communities can challenge the decision?
The Compact can coordinate that analysis, promote transparency and create diplomatic cost for shutdowns or incompatible action. It can encourage institutions to consider cross-border effects. It cannot answer every case by assigning power to whichever actor claims to preserve unity.
Stability language has often been used to protect incumbents from scrutiny. Reform language can be used to discount continuity risk. A disciplined reading avoids both. The GDC makes openness, reliability and non-fragmentation public objectives. The competent institution must still justify the specific means and remain accountable for failure.
The objective limits authority by requiring reasons; it does not create authority by incantation.
Public law can change operations, but the legal bridge must be visible
Saying the Compact did not transfer number authority does not place technical institutions outside law. Companies and nonprofit registries are incorporated in jurisdictions. Their staff, contracts, bank accounts, facilities and members are subject to applicable legal systems. Governments can legislate, regulate, sanction, investigate and obtain court orders within lawful competence.
The relevant public act may materially affect operations. Sanctions can restrict service to a listed party. Insolvency proceedings can affect a registry. A court can interpret a contract. Data-protection law can constrain public registration information. Competition law can address market conduct. Constitutional or human-rights law can limit state action.
The bridge must be stated: legal basis, jurisdiction, actor, procedure, evidence, review and remedy. The Compact may inform interpretation or policy purpose, especially where a state has committed to openness, rights and non-fragmentation. It is not a replacement for those elements.
This protects public legitimacy. If a government wants an address-related action, it should not hide behind "the international community" when only domestic authority is being exercised. Affected parties should know where to challenge the measure. Other networks and jurisdictions can then assess whether and how to recognize its effects.
It also protects technical legitimacy. A registry should not respond to political pressure by claiming a global mandate it does not possess. It should identify the policy, law or agreement that permits action and disclose continuity safeguards where possible.
The Compact makes cooperation easier by supplying common objectives. It does not erase the legal boundaries that make coercive action accountable.
Diplomatic agreement, institutional mandate and operational act need separate ledgers
Claims about the GDC can be tested by keeping three records.
The diplomatic ledger contains the adopted commitment: who agreed, the text, date, scope, reservations or explanations, review process and later state action. For non-state actors, it records voluntary endorsement and the commitments the endorser publicly accepts.
The institutional ledger identifies the organization expected to act, its mandate, governance, applicable policies, funding, jurisdiction, conflicts and review. A Compact commitment may lead an institution to amend this ledger through a valid decision. Until then, recognition of the institution is not expansion of its authority.
The operational ledger records the actual transaction: allocation request, registry update, policy decision, service instruction, certificate action or route event; the actor; evidence; timestamp; authority invoked; affected parties; and correction path.
An authority claim is credible only when the ledgers connect. "Member States support an open Internet" belongs in the first. "The RIR board adopted a policy after its community process" belongs in the second. "The registry approved this transfer under that policy" belongs in the third.
Skipping a ledger creates familiar errors. A diplomatic aspiration is treated as a registry instruction. An institutional mission is treated as proof that a specific decision was correct. An operational fact, such as a visible route, is treated as legal title. The GDC's broad vocabulary makes disciplined separation more important because many actors can truthfully cite it while seeking different outcomes.
Public review should follow the same chain. The 2027 high-level review can assess progress on Compact objectives. It is not an appeal from an individual number-resource decision unless a later instrument creates that function. Evidence from number institutions can inform the review without transferring their case files or jurisdiction to the General Assembly.
A seven-question authority test prevents vocabulary capture
Any institution claiming that the Compact changed operational rights should answer seven questions.
First, what exact act is proposed: standard, allocation, registration, transfer, revocation, certificate change, route action or legal enforcement? Second, which sentence of the adopted Compact concerns that act rather than a general objective? Third, who is the actor authorized to perform it?
Fourth, what instrument gives that actor access and power: law, treaty, corporate bylaw, policy, contract, membership rule, technical standard or network agreement? Fifth, what valid act changed the prior arrangement after September 2024? Sixth, what records, credentials, duties and liabilities moved? Seventh, who can review error and preserve service during dispute?
For Internet numbers, the Compact alone cannot complete this test. It provides relevant objectives and stakeholder expectations. The missing operational elements must come from the existing number system or a later, explicit reform.
The test is symmetrical. A technical institution claiming immunity because the Compact reaffirmed its role must identify the boundary of that role and the accountability attached to it. A government claiming new supervision must identify the implementing authority. A coalition claiming to represent the technical community must show selection and mandate. A holder claiming permanent ownership must distinguish registry status, contract, route use and applicable property law.
This method does not diminish diplomatic consensus. It prevents consensus from being captured as evidence for a power the negotiators did not grant.
Voluntary endorsement creates a claim to test, not a licence to operate
The Compact's endorsement mechanism gives non-state actors a meaningful way to associate themselves with the agreement. A registry, standards organization, network operator or industry body that endorses it can be asked how its conduct advances inclusion, openness, security, human rights and cooperation. The endorsement becomes relevant evidence of the institution's own public commitments.
The scope should not be exaggerated. Endorsement is voluntary and general. It does not certify technical competence, confer recognition as a Regional Internet Registry, make the endorser representative of every engineer or user, or authorize access to another institution's systems. It cannot replace the acceptance, policy or agreement required for a number-resource function.
This matters because endorsements are easy to convert into a coalition narrative. If several prominent technical institutions endorse, a later statement may say "the technical community supports" a contested policy. That conclusion requires more evidence. The institutions may have endorsed the Compact's objectives without endorsing that policy. Their governing communities may not have considered it. People affected by the number decision may not be represented by the endorsers.
A responsible endorser should publish a scope note. It should identify the governing act that approved endorsement, the commitments considered applicable, the operating functions excluded from any implied change, and the process for reporting implementation. Where endorsement affects a proposed policy, the institution should use its normal decision procedure rather than treating the earlier act as blanket approval.
The United Nations endorsement register should likewise be read as a list of voluntary commitments, not as a chamber that can ratify technical policy. The number or prestige of endorsers may demonstrate political support. It does not complete the authority chain for an allocation, transfer or revocation.
This distinction gives endorsement more credibility. A public promise can be reviewed against conduct without being inflated into a power the signer never possessed.
Four plausible disputes show where the Compact stops
Consider a government connectivity programme that needs address space for new public networks. The Compact supports the development objective and may justify funding, training and cooperation. The applicant still follows the relevant RIR policy or obtains service through a provider. If the request is refused, review follows the registry's procedures and applicable law, not an appeal to the GDC high-level meeting.
Consider an RIR facing a disputed transfer during litigation. The Compact's stability, inclusion and rights principles may inform how the institution evaluates continuity and communicates with affected parties. They do not decide title, jurisdiction or the registry update. The RIR must identify the policy, contract, order and review route that authorize its action.
Consider a technical coalition proposing that a block be reserved for a new protocol. The phrase "technical community" does not let the coalition assign the values. Special-purpose reservations follow the relevant IETF and IANA procedures. The coalition may contribute evidence, but participation is not reservation authority.
Finally, consider a network rejecting a route originated from registered address space. The registry record and any RPKI data are evidence operators may use. The Compact's commitment to a reliable, non-fragmented Internet may support dialogue. It does not compel universal route acceptance. Routing relationships, security policy, sanctions, technical evidence and contracts remain relevant.
These examples are not edge cases. They show why the operational layer resists one global verb. "Support," "coordinate" and "reaffirm" can create a common policy direction while leaving different institutions responsible for different acts.
They also reveal the remedy problem. A person challenging the government, registry, standards decision or network needs a different forum in each case. Calling all four Internet governance does not create one appellate body. The Compact's legitimacy depends partly on preserving those distinctions while making their public consequences reviewable.
The 2027 review should examine effects without pretending to hear appeals
The Compact establishes a high-level review during the eighty-second session of the General Assembly. That review is based on a Secretary-General's progress report and input from stakeholders and existing forums. It is a real accountability event at the level of the Compact.
For Internet numbers, useful evidence could include whether connectivity programmes obtained appropriate IPv6 resources, whether developing-country entities could engage in regional policy, whether number registries published accurate and timely service information, whether routing-security capacity improved, and whether legal or institutional crises threatened continuity. The evidence can show whether the digital-cooperation commitments are working.
The review should not convert those questions into jurisdiction over individual registry cases. It is not equipped to authenticate every allocation record, interpret every membership contract or order a route change. Its outputs can recommend public policy, capacity, transparency and further institutional work. A competent body must handle the underlying transaction.
This boundary should be stated in the progress report. When an operational dispute is presented as GDC evidence, the report should identify the authority that owns the case, summarize the broader systemic issue and avoid declaring rights it cannot adjudicate. Where no remedy exists, that gap is itself a legitimate policy finding.
The review can also detect institutional overclaiming. If a private body says the Compact authorized its conduct, the report can ask for the operative chain. If a state says a technical action implements the Compact, the report can ask for legal basis and proportionality. Such scrutiny promotes accountability without seizing the function.
The most useful outcome would be a map of interfaces: where public commitments depend on technical institutions, where those institutions depend on law and finance, and where affected parties lack review. That is coordination with evidence, not centralized operation.
Public-interest language does not settle ownership of number resources
Both Internet-governance declarations and technical institutions often describe coordinated identifiers as resources administered in the public interest. The phrase expresses an important orientation. Unique numbers must remain usable across networks, registration must avoid duplication, and administration should not become a private windfall detached from Internet operation.
Public interest is not a complete legal category. It does not answer whether a particular holder has contractual rights, whether a transfer is recognized, whether a court can issue an order, what a registry may revoke, or what compensation follows. Those questions vary by instrument and jurisdiction.
The GDC does not use the language needed to settle them. It neither nationalizes address space nor declares it private property. It does not grant private registries beneficial ownership of unallocated pools. It does not state that governments may redistribute registrations outside the established system.
This restraint is essential under IPv4 scarcity. Market value creates incentives to describe registration as title when seeking certainty and as revocable permission when asserting institutional control. A diplomatic reference to the Internet as a global facility cannot resolve that conflict. Decision makers must examine the specific policy, agreement, history, reliance, law and operational impact.
IPv6 does not eliminate the governance question. Its larger space changes scarcity economics but still requires uniqueness, registration and routing coordination. Autonomous system numbers likewise support routing identification but do not confer a general licence to operate a network.
Public-interest commitments should require better reasons from every side. A holder should explain the basis of its claim. A registry should explain the basis and limits of its discretion. A government should explain jurisdiction and due process. The Compact supports that demand for accountability. It does not predetermine the answer.
The Compact's real Internet-governance effect is coordination with boundaries
The GDC changed the public-policy landscape in several durable ways. It placed an open, global, interoperable, stable and secure Internet inside a wider digital-cooperation settlement. It reaffirmed multistakeholder governance in a General Assembly outcome. It identified the IGF as the primary platform for discussion, connected implementation to WSIS processes, invited voluntary endorsement and created a high-level review.
Those acts can influence budgets, diplomatic positions, national strategies, institutional priorities and the evidence demanded from private actors. They can make shutdowns, exclusion and fragmentation harder to defend. They can help developing countries demand capacity and meaningful participation. They can create a common forum in which technical consequences of policy are made visible.
The effect is coordination, not custody. The Compact does not grant ICANN, an RIR or an undefined technical community new rights over address blocks. It does not vest Member States collectively with registry credentials. It does not decide ownership, route acceptance or the outcome of a disputed allocation.
That restraint is not a drafting failure. A global digital compact could not safely reassign operational functions through general language without the detailed transition and accountability that unique identifiers require. Its more defensible role is to set public objectives, establish review and require institutions to explain how their specific mandates serve the shared network.
The next argument about number authority should therefore begin with the actual function and instrument, not with the prestige of the phrase "Global Digital Compact." Diplomatic consensus can coordinate public policy. Operational rights must still be proved where they are exercised.