Skip to main content

Governance / Case File

CASE FILE

Case File governance intelligence tracks institutions, policy processes, standards activity, registry operations, accountability disputes, and implementation signals that affect internet infrastructure. BTW.

Institutional BreakdownLegal and Policy ConflictElection and Control Risk
CASE FILE signal visual
Governance / Case FileCASE FILE
Active Dossiers1 Live Case

AFRINIC saga currently tracked end-to-end.

Primary DomainGovernance

Institution legitimacy and continuity risk mapping.

MethodSignal + Timeline + Failure Paths

Primary-source based timeline and risk analysis.

Decision ValueHigh

Used for continuity and policy exposure planning.

Latest Coverage

Latest from CASE FILE

762 articles

Conceptual private corporate record room with an unmarked meeting folder, a nine-slot assent tray with one neutral empty slot and one closed absent slot, and a separate sealed resolution sheet entering an archive

Afrinic SAGA

After the Silence: What AFRINIC’s 2017 Written Cure Needed to Prove

AFRINIC’s members heard the audited statements without recorded objection, yet the annual meeting never adopted them. A later 78 per cent resolution offered a sensible repair—but only a distinct, traceable member act could close the gap left by silence.

Aug 12, 2026
A registry records desk separated from independently operated network rooms.

CASE FILE

IPv4 scarcity is becoming a chain-of-control problem

The immediate operational issue in **How RIR powerlessness impacts IPv4 scarcity and digital asset management** is no longer simple address exhaustion. RIRs can coordinate registration and recognise transfers, but those records are not the same thing as a globally enforceable…

Aug 12, 2026
A registry records desk separated from independently operated network rooms.

CASE FILE

RIR enforcement stops where the contract ends

The practical question behind **Why RIRs lack enforcement power** is not whether regional registries can take administrative action. They can. The sharper question is what happens when policy expectations reach an organisation that is not legally bound by the registry’s contract.…

Aug 12, 2026
Text-free premium editorial still life of an abstract ledger, receivables slips and three separated approval plates beside closed membership drawers, representing the write-off, approval chain and an unproven closure link.

Afrinic SAGA

AFRINIC’s USD 107,994 Write-Off: The Missing Reconciliation Behind a Material Loss

AFRINIC’s 2012 accounts recorded USD 107,994 in bad-debt expense, rounded in the annual report to USD 108,000. The disclosure matters not because a write-off proves wrongdoing—it does not—but because it joins three institutionally different acts in one compact passage: removing…

Aug 11, 2026
Broadcast application folders stop at a procedural gate while a separate contract and technical route leads toward registry infrastructure.

CASE FILE

Who Could Challenge EBU’s .RADIO—and Who Could Enforce Its Rules

EBU’s community-priority victory did not itself award an operating right, and the losing applicants’ access to ICANN accountability procedures did not entitle them to a fresh evaluation. The history of .RADIO is instead a sequence of distinct institutional gates: an outsourced…

Jul 31, 2026
An institutional auction chamber separates bidding positions, escrow custody, contract execution and the route to root-server racks.

CASE FILE

The .SHOP Clock: Bidder Exit, a $41.5 Million Price and Control of ICANN’s Proceeds

The price attached to .SHOP was produced by a public rulebook and a largely private sequence of bidder instructions. That distinction matters. Nine applications were listed in the contention set, but deposits were submitted for only seven, creating seven eligible bidders in…

Jul 31, 2026
Professional-licence dossiers pass through separate credential, registry, registrar and dispute-review stations.

CASE FILE

Who Decides Who Is a CPA Online? AICPA's Failed Community Bid, the Contract Without Specification 12, and the .CPA Appeal Chain

A failed community-priority application, a later non-sponsored registry contract and a registry-specific eligibility appeal now sit in the same institutional history. Reading them as one continuous grant of authority obscures the central governance question: which instrument lets…

Jul 31, 2026
Vineyard-origin evidence and sealed samples face a contract folder while custody tags lead toward root infrastructure.

CASE FILE

When Wine-Origin Claims Reached the Root: .WINE, .VIN and the Contract Path to Identity Digital

The argument over .WINE and .VIN did not ask ICANN to decide who could lawfully use names such as Champagne, Rioja or Bordeaux. It asked whether a global naming contract could carry protections for wine-origin claims before international and national law had produced a single…

Jul 31, 2026
A failed-query path is diverted inside a DNS operations room while a separate review station controls service approval.

CASE FILE

Who Could Stop Site Finder? VeriSign’s Wildcard and the Birth of Registry-Service Preclearance

When VeriSign changed the answers returned by the authoritative .COM and .NET servers in September 2003, the registry operator controlled the technical switch. ICANN did not itself edit the zones: it could demand rollback, invoke the contracts and threaten enforcement. Technical…

Jul 31, 2026
Contract folders and root-server conduits remain behind a chain of governmental review files and physical approval seals.

CASE FILE

Who Could Authorise .AMAZON? From GAC Objection to Enforceable Safeguards and Root Delegation

The dispute over .AMAZON was not resolved by a single veto, judgement or bargain. It advanced only when distinct powers aligned: governments advised, an accountability panel identified defective decision-making, the ICANN Board changed programme status, negotiators converted…

Jul 31, 2026
A registry contract, DNS route, certificate checkpoint and browser-build station form separate links in a secure application chain.

CASE FILE

When a Registry Policy Became Browser Code: The .APP Contract, Delegation and HSTS Preload Chain

.APP did not become an HTTPS-enforced namespace through one decision by one institution. Its path ran through a governmental warning, an amended application, evaluation, a twelve-party auction, an ICANN contract, a root-zone change, a registry-to-registrar notice rule and…

Jul 31, 2026
A closed evaluation gate stands apart from contract folders, a technical checkpoint and illuminated root-server racks in a music-sector operations room.

CASE FILE

After the Failed CPE: How DotMusic Reached the .MUSIC Root

A failed community-priority score did not end DotMusic Limited’s application, and a later delegation did not erase that failure. The route from 10 points in 2016 to a live top-level domain in 2021 ran through separate institutions, separate legal instruments and separate…

Jul 31, 2026
Medicine packages, jurisdictional licence files and reserved-label objects are examined beside registry and root-zone equipment.

CASE FILE

The Domain ICANN Did Not Order: .PHARMACY’s 2018 Contract Cure

A Public Interest Commitment Dispute Resolution Procedure standing panel found that the National Association of Boards of Pharmacy had not transparently applied its published eligibility rules to one rejected applicant. ICANN then issued a breach notice and later recorded the…

Jul 31, 2026
Two fibre routes diverge toward separate server cabinets beside distinct auction, contract and root-zone control objects.

CASE FILE

Why Booking.com’s .HOTELS Contended with .HOTEIS but Not .HOTEL

Two decision processes within ICANN’s new-gTLD programme could compare similar-looking top-level-domain strings and produce opposite-looking outcomes because they were not answering the same procedural question. Booking.com’s route to .HOTELS shows how a visual screen…

Jul 31, 2026
Two territorial contract archives converge visually toward a single fibre node and root-server cabinet.

CASE FILE

When Territorial Coexistence Met a Single Root: Merck KGaA, .MERCK and the Limits of ICANN Review

For decades, private agreements divided use of the Merck name by territory. ICANN’s root could not. The .MERCK record shows how contractual history could enter objections and accountability proceedings without giving any one forum power to partition a globally unique label, award…

Jul 31, 2026
Two linked registry systems are inspected against incorporation records before their shared operating connection is released.

CASE FILE

Verified, Bundled, Released: How .NGO/.ONG Turned NGO Eligibility into Registry Enforcement

Behind .NGO and .ONG’s verification promise was a contractual machine: a name could be created before documentary review finished; linked commands once moved matching labels across two top-level domains; and different failures could lead to lock, hold, termination, deletion or…

Jul 31, 2026
Application files move toward a registry contract while a judicial clamp interrupts a separate fibre route to an Africa-shaped root-zone node.

CASE FILE

Registry.Africa and the Remedy Gap: Why DCA’s IRP Victory Did Not Reverse the .AFRICA Delegation Chain

DotConnectAfrica secured a consequential finding that ICANN had mishandled its `.AFRICA` application, but the ruling neither transferred the string nor erased the rival operator’s contract. The result becomes intelligible only when the dispute is followed across the separate…

Jul 31, 2026
Engineers transfer encrypted registry data from a failed rack into a guarded temporary operations rack while DNS service continues.

CASE FILE

Emergency Custody, Not Ownership: The .WED Failure and ICANN’s EBERO Chain

The .WED case is not chiefly a story about a failed registry. It is a test of how contractual emergency powers, escrowed records, root-zone changes and a temporary operator can preserve a top-level domain without deciding who may hold its permanent registry role next. The record…

Jul 31, 2026
An equity-transfer folder stops at a contractual approval gate while court and investigation files remain on separate desks and registry operations continue.

CASE FILE

Who Could Stop the .ORG Sale? PIR, ICANN and the Legal Objects Behind the Ethos Capital Rejection

The proposed transfer of Public Interest Registry to an Ethos Capital affiliate drew petitions, government scrutiny and accountability challenges, but none operated as a freestanding veto. The deal failed because authority was divided among a private purchase agreement, corporate…

Jul 31, 2026
Registry contracts sit inside a boardroom while public submissions, review files and court orders remain outside the operational root-server chain.

CASE FILE

Who Could Restore the Caps? Namecheap and the .ORG/.INFO Accountability Chain

The removal of historical wholesale price caps from the .ORG and .INFO registry agreements produced thousands of objections, a successful accountability challenge and a court-confirmed award, yet none of those events rewrote the contracts. The case shows why public participation…

Jul 31, 2026

Member Unlock

Restricted Profile Intelligence

Login is required to unlock full profile briefings and deep-dive sections.

Only for Strategic Circle

Strategic Circle Briefing

Join to unlock strategic briefings after signing in.

Join Strategic Circle
Only for Leadership Alliance

Leadership Alliance Briefing

For qualified IP-asset owners and management; sign in to unlock alliance briefings.

Join Leadership Alliance

Session Map

Active Dossiers

AFRINIC Saga

Multi-year governance and legal crisis with implications for RIR accountability worldwide.

Open AFRINIC Saga