Summary

  • The rights audit asks whether a number-resource holder gained a new invocable claim with an identified duty-bearer, trigger, required act, deadline, review route and remedy after the 17 December 2025 adoption of Resolution 80/173.
  • The resolution produced genuine institutional changes, most clearly permanent status for the Internet Governance Forum, annual reporting expectations and further United Nations coordination. These changes improve continuity of discussion but do not create holder standing before ICANN or an RIR.
  • No new right was found for allocation, registration correction, transfer recognition, provider choice, data export, RPKI service, reverse DNS, continuity during dispute, independent registry appeal or route acceptance.
  • The resolution's human-rights and universal-access commitments remain important. They operate through existing international law, domestic measures and later institutional action; the text does not turn an IP address or ASN service request into a directly enforceable claim.
  • The official UN follow-up table confirms the implementation emphasis: participation, financing, capacity, reporting, indicators, IGF development and WSIS-Global Digital Compact coherence, rather than number-holder service rights.
  • A later right could still emerge if a legislature, regulator, court, ICANN instrument, RIR policy or binding service agreement adopts a specific duty and remedy. That later instrument, not conference rhetoric, would carry the operational change.
  • Future reviews should publish a rights-delta ledger beside their declarations, recording the affected user, duty-bearer, executable act, deadline, evidence, review and remedy. Where the result is zero, the record should say so plainly.

The question begins after the ceremony

High-level meetings are evaluated by negotiated language, diplomatic balance, institutional survival and the number of commitments preserved. An operator evaluates change differently. The relevant moment is when a resource holder submits a request and an institution must decide what happens next.

Suppose a network wants a registration error corrected, an IPv4 transfer recognized, a Route Origin Authorization issued through a hosted service, a reverse-DNS delegation changed or a disputed hold reviewed. Did WSIS+20 give that holder a new form, a new respondent, a new deadline or a new remedy? Could the holder cite the resolution and compel a result without another law, policy or contract?

The distinction is not semantic. Institutions often describe a declaration as progress while affected users encounter the same gate, evidence standard and appeal route. The declaration may still shape future reform, but the right has not changed until the operational relationship changes.

This audit therefore starts on 18 December 2025, the day after adoption. It compares the holder's publicly identifiable position before and after the resolution, then checks the official follow-up actions visible in 2026. It does not count speeches, side events or stakeholder praise as rights. It counts only changes a holder can invoke.

The method is intentionally severe. A right can be politically modest and still pass if it has a duty-bearer and remedy. A celebrated commitment fails if no holder can use it. This is how institutional applause is converted into an accountable balance sheet.

An operational right has six necessary parts

The word "right" covers several different ideas. It can refer to a human right grounded in international or domestic law, a membership entitlement, a contractual service promise, a policy eligibility rule or a technical permission created by possession of credentials. This audit does not collapse them. It asks whether any instrument changed the holder's executable position.

Six parts are needed. First, the beneficiary must be identifiable: a number-resource holder, applicant, member or operator in a defined condition. Second, a duty-bearer must be named or determinable: ICANN, an RIR, a registration provider, a review body or another institution with the relevant power.

Third, the required act must be specific. "Cooperate" or "promote inclusion" is not enough. The institution must correct, disclose, decide, recognize, transfer, preserve, review or compensate. Fourth, a trigger must tell the beneficiary how the duty begins, such as a valid request, verified error, approved transfer or service failure.

Fifth, there must be a decision standard and time. An institution can defeat a right by delaying indefinitely or applying an unknowable test. Sixth, a refusal or failure needs review and remedy. The remedy may be correction, reconsideration, independent appeal, continuity protection, compensation or judicial enforcement, depending on the source of the right.

Not every right must contain all detail in one paragraph. A resolution can incorporate an existing mechanism or direct a named body to establish one by a date. Resolution 80/173 does neither for number holders. Its Internet-governance provisions affirm roles, cooperation, participation and forums; they do not assemble an executable claim.

The baseline was regional and contractual before WSIS+20

Before December 2025, number holders already possessed different service positions under regional policies, membership rules, contracts and applicable law. An RIR could register an allocation or assignment, process specified transfers, provide registration-data services, support reverse DNS and offer RPKI functions. The exact entitlement varied by region, resource status and account standing.

Those positions were not supplied by WSIS. They arose from the Internet Numbers Registry System, ICANN's top-level coordinating role, RIR policy, organisational documents, service agreements and national legal systems. RFC 7020 describes the IANA-RIR-LIR structure and the goals of uniqueness and accurate registration, but it does not create a universal private cause of action for every holder request.

Transfer recognition illustrates the baseline. APNIC, ARIN, LACNIC and the RIPE NCC publish different policy and service conditions; AFRINIC's framework and circumstances differ. A holder may qualify for an in-region or inter-RIR transfer where compatible rules exist. That is an entitlement under the relevant rules, not a global right derived from General Assembly language.

The baseline also contained gaps. There was no universal right to choose a registration provider independently of regional structure. There was no common maximum time for correcting every registry record, no shared compensation regime for delay and no uniform independent appeal for all service refusals. RPKI service access and account effects remained connected to regional arrangements.

An honest post-review audit must preserve this baseline. Otherwise, an existing service may be wrongly attributed to WSIS+20, or an aspirational paragraph may be presented as filling a gap that remains.

What the final text actually changed

The final outcome, Resolution 80/173, was adopted by consensus on 17 December 2025. It reaffirms a people-centred, inclusive and development-oriented information society, addresses digital divides and finance, restates human-rights commitments, covers data and artificial intelligence, and renews the WSIS implementation architecture.

Its clearest institutional change in Internet governance appears in paragraph 99: the Internet Governance Forum becomes a permanent United Nations forum, with a continuing secretariat intended to rest on a stable and sustainable basis under UN budget procedures. Paragraphs 98 and 100 add annual progress reporting and stronger transmission of IGF outcomes into relevant UN work.

The resolution also requests further action. UNGIS is to prepare a joint WSIS-Global Digital Compact implementation roadmap for consideration by CSTD in 2026. Action-line facilitators are to develop targeted roadmaps and report outcomes in 2027. The Secretary-General is to submit a biennial implementation report through CSTD. A further WSIS review is scheduled for 2035.

These are real changes in institutional duration, reporting and coordination. The mistake would be to infer a change in number-holder rights merely because the same document has an Internet-governance section. The final text does not mention an IP address holder, ASN holder, RIR customer, allocation request, resource transfer, registry correction, ROA, reverse DNS or provider migration.

The audit therefore credits the text for what it did while refusing to credit an absent act. Permanent discussion is not permanent registration standing.

The rights-delta table records a zero without hiding it

The central findings can be stated compactly.

Candidate operational right Position after Resolution 80/173 New duty-bearer or act Audit finding
Apply for number resources under a global WSIS rule Existing regional and provider rules continue No new institution or acceptance duty No change identified
Correct an inaccurate holder or resource record Existing registry procedures and applicable law continue No universal correction clock or remedy No change identified
Obtain recognition of an IPv4 transfer Compatible RIR policies continue to govern No new transfer criterion or inter-RIR duty No change identified
Choose or change registration provider Existing regional service structure continues No portability, export or receiving-provider rule No change identified
Receive a complete portable data record Existing provider duties vary No export specification, deadline or enforcement route No change identified
Create or maintain RPKI objects Existing certification and service arrangements continue No new issuance, continuity or review entitlement No change identified
Change reverse-DNS administration Existing registration and service procedures continue No new service duty or completion time No change identified
Preserve service during a dispute or institutional failure Existing legal, contractual and continuity arrangements continue No holder-triggered continuity remedy No change identified
Appeal a registry service refusal independently Existing regional review routes continue No common appellate body or binding review standard No change identified
Require a network to accept or prefer a route Operator policy remains local subject to law and contract No route-acceptance duty No change identified

The repeated result is not a formatting convenience. It is the substantive conclusion. The resolution changed the environment in which these questions may be debated, but not the holder's executable claim in any audited category.

Allocation eligibility did not become a global entitlement

The resolution promotes meaningful connectivity, investment and inclusion. A government or operator may reasonably argue that access to number resources affects those goals. Yet the text does not state that an applicant satisfying a WSIS standard is entitled to an IPv4, IPv6 or ASN allocation.

No global eligibility test was adopted. No reserve was created for developing countries, community networks, public services or underserved groups. No institution was directed to accept applications under a new WSIS category. The resolution does not override regional needs-based rules, waiting-list rules, transfer policy or fees.

This absence matters because the digital divide can be obscured by general infrastructure language. Connectivity finance may fund networks whose ability to obtain or acquire number resources remains governed elsewhere. Capacity programmes may train operators without altering the service decision they face.

A later institution could convert the political goal into an operational entitlement. An RIR community might adopt a policy for a defined applicant class. A government might condition public funding on resource access support. A development bank might finance acquisition or transition costs. Those would be identifiable later acts.

WSIS+20 itself did not perform them. A number-resource applicant left the review with stronger political language about inclusion, but not with a new global claim to an allocation.

Registration correction gained no common clock or remedy

Accurate registration is central to operational trust. A holder may need to correct its legal name, contacts, corporate succession, resource status or an erroneous event. Delay can affect transfers, RPKI, reverse DNS, abuse handling and transactions.

Resolution 80/173 emphasizes information, rights and good governance, but it does not create a number-registry correction right. It names no required evidence, completion time or escalation route. It does not say what happens when a registry disputes the holder's proof or leaves a request unresolved.

Existing rights may still apply. Contract, association law, data-protection law, administrative principles or a regional service commitment may require correction in a particular case. A court may order a change. The point is attribution: those sources existed independently and must be invoked on their own terms.

A new operational right would be easy to recognize. It would identify who may request correction, which records are covered, how authority is proved, when the registry must decide, how security concerns pause the time, what reasons must be given and where an independent review lies. It would also preserve history rather than enabling silent deletion.

The final WSIS+20 text contains no such mechanism. Record accuracy remains an important value governed by existing institutions, not a new post-review entitlement.

Transfer recognition remains where the applicable policy puts it

IPv4 scarcity makes transfer recognition one of the most commercially important registry acts. A buyer and seller may sign a contract, but the operational value of the transaction depends partly on registry updates, recognized contacts, related services and acceptance by counterparties.

WSIS+20 did not harmonize transfer policy. It did not create a global inter-RIR compatibility rule, set documentary standards, limit processing time, establish neutral review or require continuity of RPKI and reverse DNS during handoff. It did not address leasing, delegated use or the treatment of legacy resources.

Regional variation therefore remains. APNIC's Internet number resource policies, ARIN's Number Resource Policy Manual, the RIPE NCC's transfer information and other regional rules continue to supply the relevant conditions.

This is not evidence that transfer reform lacks public importance. Scarcity, cross-border investment and continuity can justify global scrutiny. It is evidence that a diplomatic review did not itself change the transaction rule.

Any claim that WSIS+20 improved transfer rights should name the later policy clause, effective date and covered holders. Without that evidence, the claimed improvement belongs to advocacy rather than the rights ledger.

Provider choice and data export remain absent

A holder may be dissatisfied with service yet unable to change the institution maintaining its recognized record. Regional allocation structures and provider relationships often fuse geography, policy, membership and registration service. WSIS+20 did not separate them.

The final text contains no right to appoint a different registrar, no qualification criteria for a receiving provider and no atomic change of service authority. It does not require the incumbent to deliver a portable account history, disclose dependent services, end active credentials or delete data no longer needed.

This gap is especially visible beside other digital policy developments. The European Union's Data Act contains specific switching and export obligations for covered data-processing services. That instrument is not a number-registry rule, but it demonstrates what operational language looks like: customer request, provider obligation, exportable data, transition and contractual terms.

Resolution 80/173 uses none of those mechanisms for number holders. General support for an open and interoperable Internet does not create provider portability. Interoperability of the network and portability of the registration-service relationship are different propositions.

The absence is a useful agenda item for the future. A Number Resource Society model could make safe provider choice and record export explicit. The 2025 review did not do so, and institutional honesty requires the difference to remain visible.

RPKI service received no new holder guarantee

Resource Public Key Infrastructure connects registry-recognized authority to signed routing-security information. A resource holder may use a hosted service or operate delegated arrangements, depending on the regional service and its status. The holder creates ROAs; repositories distribute signed material; relying parties validate it; operators decide how to use validation state.

WSIS+20 calls for a stable and secure Internet and cooperation against fragmentation. It does not grant a holder a right to obtain or retain RPKI service. No paragraph requires a certification authority to issue a certificate, maintain publication during a billing or governance dispute, preserve entities during a provider change or decide a request within a fixed time.

Nor does the resolution create a remedy for erroneous revocation or delayed restoration. It does not define compensation, independent technical review or emergency continuity. Those questions remain within current service arrangements, technical standards, contracts and applicable law.

The distinction protects against overclaiming on both sides. RIRs cannot cite broad WSIS security language as a new source of discretionary authority over routes. Holders cannot cite the same language as a new enforceable guarantee of every RPKI service outcome.

A future operational right would identify the covered resource status, minimum service, suspension grounds, notice, appeal, continuity period and evidence available to relying parties. No such delta appears in the adopted text or official UN follow-up list.

Reverse DNS remained a service question

Reverse DNS helps map addresses back to domain names and can matter for mail, logging, diagnostics and operational reputation. Administration normally follows number-resource authority through relevant registry and operator arrangements.

Resolution 80/173 neither mentions reverse DNS nor creates a holder entitlement around it. There is no new request method, delegation deadline, continuity rule during transfer or review of a refusal. The text's support for interoperability is too general to perform those functions.

This example is useful because it resists grand interpretation. A high-level outcome may shape the climate of Internet governance while leaving a mundane but consequential service exactly where it was. The holder still needs the credentials, records and provider procedure that applied before adoption.

A later implementation measure could address reverse-DNS continuity as part of portability or transfer reform. If it does, the rights ledger should record the exact instrument. Until then, no change should be inferred from the review's breadth.

Independent appeal did not appear

An operational right is weak when the same institution makes the initial decision, interprets the evidence, controls delay and decides the complaint. RIRs provide different review, reconsideration, membership and legal routes, but there is no universal independent tribunal for number-registration service disputes.

WSIS+20 emphasizes inclusive participation, good governance, rights and effective remedy in several contexts. It does not establish a number-registry appellate body. It does not define standing for holders, review standards, interim protection, evidence access, decision time or binding effect.

The human-rights sections deserve careful treatment. Paragraphs 70 and 71 support safeguards, oversight and remedy for human-rights impacts of digital technologies. Paragraph 74 addresses privacy, surveillance and legal redress. These provisions can strengthen normative and legal arguments. They do not state that every registry service refusal is a human-rights violation or give a holder a new appeal directly under the resolution.

Existing courts and legal remedies remain available where jurisdiction and cause of action exist. Existing organisational review routes continue. The audit finding is not that remedy is impossible; it is that WSIS+20 supplied no new operational appeal for the audited acts.

This is an area where a later institution could make a measurable contribution. A common independent review with narrow standing, deadlines and interim continuity would create a visible rights delta. The 2025 text stops before that point.

Continuity during conflict or failure did not become holder-triggered

Registry continuity becomes most important when institutional control is disputed, a provider fails or a court order affects service. A holder may need public registration, RPKI, reverse DNS and contact functions preserved while ownership or governance questions are decided.

Resolution 80/173 supports a stable and secure Internet but creates no holder-triggered continuity right. It does not define a threshold of service failure, designate a temporary custodian, require usable escrow, protect clean resources during a narrow dispute or authorize emergency transfer to a qualified successor.

Existing continuity arrangements may operate in their own settings. ICANN's Emergency Back-End Registry Operator programme protects specified critical functions for covered generic top-level domain registries. That is an instructive neighbouring example, not a right granted to Internet number holders by WSIS+20.

The continuing NRO and ICANN work on RIR governance and recognition also has its own authority. It should be evaluated by the criteria and instruments through which it is adopted. Chronological overlap with the review does not make every continuity reform a WSIS+20 implementation.

The post-conference result is therefore unchanged: a holder facing number-registry distress must rely on existing regional, contractual, corporate and legal arrangements. The UN outcome created no emergency switch the holder can activate.

Route acceptance remains an operator decision

Registration authority and route operation are related but distinct. A registry record may support a claim; an RPKI object may express authorized origin; a network still applies local routing and security policy subject to law and contract.

WSIS+20 did not require operators to accept, reject or prefer any route. Its open, global, interoperable, stable and secure Internet language expresses a desired condition, not a BGP decision rule. No holder can present paragraph 90 to a network and compel route acceptance.

This limitation is essential for accurate rights accounting. A new registry entitlement would not automatically guarantee reachability. A new routing-security commitment would not automatically correct the holder record. Each operational act needs its own duty-bearer.

The audit does not repeat the full institutional map of Internet operations. It makes one narrower finding: no post-review routing right appeared for number holders. Existing peering, transit, filtering, RPKI validation and route-selection decisions continue under their existing technical, commercial and legal arrangements.

If a government later enacts a lawful non-discrimination or continuity rule for certain networks, that act should be audited separately. The General Assembly resolution itself did not install one.

Permanent IGF status is a real change, but not holder standing

Paragraph 99 deserves full credit. The IGF no longer depends on periodic renewal in the same way; it is made permanent within the UN setting. Paragraphs 98 through 103 seek broader participation, stronger intersessional work, annual reporting, improved transmission of outcomes and a better-supported secretariat.

For operators and number holders, this can improve continuity of access to discussion. A concern about registry accountability, scarcity, routing security or geographic exclusion can be raised in a forum whose institutional future is more secure. National and regional initiatives may carry the issue across years.

Yet participation in the IGF does not create standing before an RIR. The Forum does not approve a transfer, correct a record, issue a resource certificate or order compensation. Its outcome may be taken into account by UN bodies, but paragraph 100 does not make that outcome binding on ICANN, an RIR or an operator.

Calling this distinction cynical would misunderstand it. Discussion has value precisely because it can expose problems and assemble coalitions for later action. Its credibility weakens when entities are told that speaking is equivalent to receiving a remedy.

The rights audit therefore records two entries: institutional continuity for the forum changed; the number holder's operational entitlement did not. Both can be true at once.

Broader participation is opportunity, not authorization

Paragraphs 89, 98, 101 and 102 emphasize participation by developing countries and underrepresented groups. This responds to real inequalities in travel, finance, language, technical capacity and sustained presence. Better participation can change which problems enter the international record.

An opportunity to participate is still different from authorization by affected holders. A fellow, delegate, civil-society speaker, technical expert or government official may offer valuable evidence without holding a mandate from a specific resource holder. Conversely, a holder may possess a service right without attending a global meeting.

The distinction matters in claims about legitimacy. A more diverse room can improve deliberation, but it does not prove that every operator accepted the outcome. Nor does it give attendees power to alter records outside the institutions that administer them.

Future evaluation should measure whether participation leads to a named institutional response. Did an RIR open a proposal? Did ICANN change a binding instrument? Did a regulator adopt a duty? Did a court recognize a claim? Did a provider publish a service commitment? Those bridges would turn voice into traceable action.

In the absence of such a bridge, participation remains a valuable opportunity. It should not be relabelled an operational right.

Human-rights commitments matter without inventing a registry claim

The resolution reaffirms that offline rights must be protected online, calls for safeguards and remedy, supports privacy and freedom of expression, and urges stakeholders to avoid Internet shutdowns and measures targeting access. These provisions are politically and normatively significant.

They may matter to number-resource governance in particular cases. A discriminatory refusal, arbitrary interference, unlawful surveillance demand or shutdown-related order could engage existing human-rights law. A state, court or company may need to assess legality, necessity, proportionality and remedy.

The audit nevertheless rejects an automatic conversion. Holding or applying for IP addresses does not itself create a newly specified human right under Resolution 80/173. The text does not identify RIRs as public authorities, classify every service decision as state action or provide a direct enforcement route against a registry.

This restraint protects genuine human-rights arguments. Overstating the text invites institutions to dismiss claims when the promised mechanism cannot be found. A serious claimant should identify the underlying right, responsible actor, jurisdiction, interference, legal standard and available remedy.

WSIS+20 strengthens the public expectation that digital institutions respect rights. It does not replace the legal analysis needed to make a particular number-resource claim enforceable.

The official follow-up list confirms the implementation focus

UN DESA's official follow-up and review table maps requested actions from Resolution 80/173 to the entities asked to act. It is a useful check against selective readings because it gathers the provisions the Secretariat considers action-oriented.

The list covers accessibility, vulnerable groups, financing, multilingual services, digital skills, environmental sustainability, capacity-building, human rights, surveillance, Internet shutdowns, AI initiatives, IGF development, regional commissions, action-line roadmaps, indicators, UNGIS coordination, biennial reporting and future reviews.

It does not assign ICANN or an RIR a new number-holder duty. It does not ask an institution to adopt portability, transfer, correction, RPKI, reverse-DNS, continuity or appellate rights. It contains no service deadline or compensation rule for a number holder.

This does not prove that no stakeholder will voluntarily pursue reform. It shows what the official implementation account contains. The account is programmatic and coordinative rather than a registry-rights schedule.

The phrase "within existing mandates and resources" in paragraph 122 is especially important. The joint roadmap is intended to improve coherence across UN work, not silently expand the authority of every technical institution. A roadmap could recommend later action; it is not itself a new holder entitlement.

The 2026 implementation check finds activity but no rights delta

By mid-2026, the relevant public implementation record shows the resolution in force, the Secretariat's action mapping, continuing IGF and WSIS activity, and preparation of the joint WSIS-Global Digital Compact roadmap for CSTD consideration. The biennial reporting structure and later review dates remain part of the settlement.

The audit searched for a resulting change in the specific service positions listed above. It found no public instrument deriving a new number-holder right from Resolution 80/173. There is no WSIS-labelled amendment to ICANN's number mission, no global RIR service obligation, no common holder appeal and no UN-issued transfer or RPKI rule.

This finding is bounded. It does not assert that every contract, court decision or regional policy worldwide remained unchanged for every reason. It states that the official final text and identified WSIS implementation actions do not produce the claimed rights delta.

Parallel institutional work must remain separately attributed. ICANN, the Address Supporting Organization and the NRO can revise governance arrangements through their own instruments. RIR communities can change policy. Governments can legislate. A change adopted through one of those routes may be valuable even if WSIS discussion influenced it.

Influence is not the same as legal source. The audit records the instrument that makes the holder's position different. No such instrument was identified as a consequence of the 2025 outcome by the assessment date.

A later right needs an adoption trail

Political outcomes often work indirectly. A declaration establishes language; advocates repeat it; an institution studies the issue; a policy is proposed; a binding text is adopted; systems and contracts change. Only the later stages alter the holder's immediate position.

A credible adoption trail should contain the original recommendation, named recipient, proposal, authority, final text, effective date, implementation evidence and remedy. If the recipient rejects the recommendation, that refusal should also be recorded. Otherwise, recommendations can circulate indefinitely while institutions claim alignment without changing conduct.

For example, if an RIR later adopts a maximum correction time citing WSIS+20, the right begins under the RIR's adopted policy or service terms. The audit can credit WSIS influence while locating enforceability correctly. If a regulator requires portable registry records, the statute or rule carries the duty. If a court applies existing human-rights law to a registry dispute, the judgment supplies the remedy.

This attribution is not pedantry. The holder needs to know where to submit the request, what evidence applies and who can enforce failure. A diplomatic citation alone cannot answer those questions.

The same discipline prevents institutional appropriation. A technical body should not use broad UN language to claim powers the resolution did not grant. Later authority must be adopted through a legitimate route and remain within its stated scope.

A holder scenario exposes the missing elements

Consider an operator that acquired an IPv4 block through a lawful transaction. The source and recipient records sit in different regions. One corporate contact is stale, a hosted RPKI service depends on the current account and the buyer has a deployment deadline. The source registry requests additional evidence, then leaves the case unresolved.

The operator cites WSIS+20's support for an open, interoperable, stable and secure Internet. What must the registry do? The resolution does not say. It does not decide whether the transfer qualifies, which evidence cures the contact issue, how long review may take, whether RPKI service continues, whether clean aspects can proceed or who hears an appeal.

The operator may have strong rights elsewhere. The applicable transfer policies, service agreement, corporate law, court jurisdiction and registry review provisions may yield a remedy. Public authorities may intervene under law. None becomes stronger merely by pretending the UN text contains an absent procedure.

Now change one fact: an RIR adopts a rule requiring a reasoned decision within a defined period and independent review while preserving security service for a bounded interval. The rights delta becomes visible. The holder has a beneficiary definition, duty-bearer, act, trigger, time and remedy.

That contrast is the entire purpose of the audit. It replaces broad claims of progress with the operational detail a real holder needs.

A rights-delta ledger should accompany future reviews

Future high-level digital reviews should publish a separate ledger for executable changes. Each row should identify the affected person or institution, prior position, new right or duty, responsible body, trigger, decision time, evidence, review, remedy, effective date and implementation source.

Rows should distinguish direct changes from recommendations for later adoption. A permanent forum belongs under institutional change. A call for cooperation belongs under political commitment. A binding provider duty belongs under operational right. A future study belongs under pending action.

The ledger should also record zeroes. If no transfer right changed, say so. If no remedy was created, say so. Absence is policy information because it identifies where advocacy and institutional design must continue.

Updates should follow the adoption trail. When a later body acts, the row can move from recommendation to implemented right with a link to the binding instrument and evidence of use. When a deadline passes without action, the row should show delay rather than preserve an indefinite impression of progress.

This method would improve both diplomacy and technical governance. Negotiators could see which commitments remain abstract. Operators could avoid false expectations. Institutions could receive precise requests. Researchers could compare outputs across review cycles without counting paragraphs as if each carried equal consequence.

What a genuine post-WSIS operational package would contain

A meaningful package for number holders need not centralize number registration in the United Nations. It could respect existing institutions while setting measurable rights through the bodies authorized to adopt them.

The package might include a right to a complete, intelligible record export; a correction decision within a published time; narrow reasons for pause; continuity of essential registration and RPKI functions during bounded disputes; provider portability where one-current-authority safeguards are met; independent review; and automatic minimum remedies for defined service failures.

Transfer policy could gain compatible evidence classes and traceable inter-registry handoffs. Public-sector and small-operator cases could receive proportionate support without weakening identity controls. Court restrictions could travel with exact scope rather than freezing whole portfolios. Metrics could show use, delay, refusal and outcome.

Each element would require adoption by the institution with authority: RIR communities, boards acting within their powers, ICANN arrangements, contracts, legislatures, regulators or courts. International forums could convene evidence and compare results without pretending to execute the service themselves.

This is where the Number Resource Society offers a positive future direction. It can define holder-centred rights, provider choice, portable evidence and continuity as an explicit institutional settlement. It should do so through enforceable commitments, not by borrowing legitimacy from WSIS language that did not create them.

No change is a finding, not a failure of attention

Analysts face pressure to discover movement after a major conference. A zero can look unsophisticated beside a long resolution. Yet false positives are more damaging than a plain result. They tell holders that protection exists when it does not and allow institutions to claim reform without surrendering discretion.

The zero also clarifies the value of what did change. Permanent IGF status is easier to appreciate when it is described accurately as continuity of dialogue. Human-rights commitments retain their proper force when they are linked to existing legal duties and later implementation rather than inflated into an imaginary registry remedy. Follow-up roadmaps can be judged by the acts they eventually produce.

Scepticism here is constructive. It asks supporters of WSIS+20 to show the bridge from commitment to service. It asks technical institutions to respond in their own accountable procedures. It asks governments to use law when they intend enforceable obligations. It asks number holders to preserve evidence and invoke the correct authority.

The audit should be reopened when a binding instrument appears. Until then, the accurate number of new operational rights for number-resource holders created by the final text and its identified implementation actions is zero.

Watchpoints through the next review cycle

The first watchpoint is rights inflation. Institutions may describe participation, consultation or reporting as empowerment without identifying an act the beneficiary can compel.

The second is attribution drift. A regional reform may be marketed as WSIS implementation even when it arose independently. Influence can be acknowledged, but the binding source must remain visible.

The third is silent non-implementation. Roadmaps and biennial reports may repeat commitments without recording which institutions accepted, rejected or delayed them. Every action needs a recipient and status.

The fourth is forum substitution. More opportunities to discuss registry harm should not replace correction, appeal or continuity mechanisms.

The fifth is broad security language. Stability and security can justify useful safeguards, but they can also be cited to expand institutional discretion without holder review. New powers need exact authority and limits.

The sixth is uneven regional change. One RIR may improve a right while others do not. Reporting should avoid presenting a regional advance as a universal entitlement.

The seventh is remedy omission. Policies may declare principles while leaving delay and refusal consequences unspecified. The audit should treat a duty without review or remedy as incomplete.

After the applause, count what the holder can invoke

WSIS+20 produced a durable political settlement around the continuation of multistakeholder Internet governance, a permanent IGF, human-rights commitments, inclusion and coordinated follow-up. These outcomes deserve accurate recognition.

For Internet number-resource holders, accuracy leads to a narrower conclusion. No new allocation, correction, transfer, portability, export, RPKI, reverse-DNS, continuity, appeal or route-acceptance right was created by Resolution 80/173. The official follow-up actions do not add one.

That conclusion does not close the subject. It identifies the unfinished work. A forum can surface the demand. A UN roadmap can connect institutions. An RIR can adopt a service rule. ICANN can alter an authorized instrument. A government can legislate. A court can enforce an existing right. NRS can design a holder-centred alternative. Each step should be recorded where it becomes executable.

The standard for the next claim of progress should be simple. Name the holder. Name the duty-bearer. Show the act, trigger, deadline, evidence, review and remedy. If those elements did not change, the operational right did not change.

After the applause, the rights ledger should be allowed to say zero.

Sources