AFRINIC saga currently tracked end-to-end.
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
Institution legitimacy and continuity risk mapping.
Primary-source based timeline and risk analysis.
Used for continuity and policy exposure planning.
Latest Coverage
Latest from CASE FILE
748 articles
CASE FILE
The Signature That Demanded Every Key: What KeyTrap Revealed About the Cost of Trust
KeyTrap turned a valid-looking DNSSEC workload into a claim on somebody else’s processor, exposing the point at which faithful verification must yield to a locally governed budget.
CASE FILE
The Root That Wasn't Sold: What Symantec's Exit Revealed About Transferable Trust
Symantec could sell its certificate-authority business, but it could not sell a command to keep trusting the old roots. That decision remained inside independently operated clients.
CASE FILE
The Route That Borrowed a Name: What the MyEtherWallet Hijack Revealed About Layered Authority
A route accepted elsewhere let false DNS answers arrive locally, but the 2018 MyEtherWallet attack still had to cross a chain of independent technical vetoes.
CASE FILE
A Verified RFC Erratum Corrects the Record Without Rewriting It
An RFC erratum can identify a real defect, supply corrected wording and be verified by the responsible parties. It still does not silently replace the published specification. That separation lets implementers learn from mistakes while preserving the text the community actually…
CASE FILE
DNSSEC Can Prove Absence Without Deciding Entitlement
A signed negative DNS answer can establish that a name or record type was absent from a particular signed zone during a bounded validity period. It cannot establish why the entry is absent, who deserves the label, whether a registrar should create it, or whether an Opt-Out…
CASE FILE
Mozilla’s Hidden Security Boundary: How the Public Suffix List Becomes Running Code
Mozilla began the Public Suffix List, and Firefox still turns a version of it into browser behaviour. The DNS can tell software that `whatwg.github.io` exists beneath `github.io`, but not whether those names belong to one organisation or mutually untrusting tenants. This article…
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.
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…
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.…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
Member Unlock
Restricted Profile Intelligence
Login is required to unlock full profile briefings and deep-dive sections.
Strategic Circle Briefing
Join to unlock strategic briefings after signing in.
Join Strategic CircleLeadership Alliance Briefing
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership AllianceSession Map
Active Dossiers
AFRINIC Saga
Multi-year governance and legal crisis with implications for RIR accountability worldwide.
Open AFRINIC Saga