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
1,340 articles
CASE FILE
NIST’s Multi-Cloud Draft Exposes the Boundary a Service Bundle Cannot Prove
A managed bridge between cloud providers can move integration work away from a customer. It cannot, by itself, establish which system, control and evidence an authorizing decision actually covers. NIST’s draft asks readers to confront that distinction.
CASE FILE
One Packet Finished the Handshake and Carried the Command. Silence Could Mean Eight Different Things
RFC 9668 lets a constrained client append EDHOC message_3 to its first OSCORE request, reducing key establishment plus one protected transaction to two round trips. The optimization saves airtime. It does not make handshake completion, request verification and application…
CASE FILE
NIST’s Final Token Guide Puts Revocation Limits at the Cloud Handoff
A provider can stop issuing fresh credentials without instantly extinguishing every access token already accepted elsewhere. NIST’s final IR 8587 asks cloud providers and agencies to make that boundary knowable.
CASE FILE
The Outside Network Saw One Perfect Router. The Fabric Behind It Had Already Split
RFC 9666 lets an IS-IS area appear to Level 2 as one proxy node. That compression can save a network from carrying an entire leaf-spine topology twice, but it also hides the machinery that must honor the advertised transit. A clean Proxy LSP is a control-plane promise, not a…
CASE FILE
A SPARQL Graph Store Draft Makes Two Client Defaults Visible
W3C’s September revision widens the RDF format a server may return when a client omits `Accept`, and spells out UTF-8 decoding for an indirectly named graph. Neither change gives a client permission to write.
CASE FILE
The Printer Kept Its Name After the Reset. The Key That Owned It Did Not
RFC 9665 makes automatic service registration workable by letting the first accepted device key defend a DNS-SD name. That useful continuity is narrower than identity: a valid signature can preserve a name while the owner, registrar, published answer or service behind it has…
CASE FILE
A Quantum Source Is Not a Randomness Receipt
ETSI has drawn attention to a gap between the origin of random bits and the assurance a cryptographic service can actually use. A quantum label describes the source; it does not account for every step that follows.
CASE FILE
The Handshake Was Modern. The Incident Log Was Still Missing: RFC 9662’s Delivery Boundary
RFC 9662 repairs the cryptographic floor for secure syslog, but a preferred cipher suite is only one state in a longer evidence chain. Leadership needs to know what was offered, negotiated, authenticated, transmitted, accepted and retained for each event—not infer delivery from a…
CASE FILE
The Script Was Active. The Next Message Obeyed an Older Rule: RFC 9661’s Missing Receipt
RFC 9661 can prove that a JMAP entity changed from one active Sieve script to another. It cannot, by itself, prove which blob every delivery worker loaded or what happened to the next message. Leadership needs a chain that joins entity state to running code and the final mailbox…
CASE FILE
EPUB’s Portable Notes Arrive Without Portable Trust
The latest EPUB Annotations draft gives reading systems a sharper security warning. A note can move between devices; the evidence that it belongs to a particular book and author does not move automatically with it.
CASE FILE
The Canary Decoded. The Cached Variant Still Asked for More Memory: RFC 9659’s Missing Receipt
An eight-megabyte ceiling can make HTTP compression interoperable only when the bytes that reached the client were produced under that ceiling. RFC 9659 defines the contract; it does not certify every origin worker, recompressing intermediary, cached variant or recipient process…
CASE FILE
NIST’s Open RAN Draft Exposes the Gap Between a Component Claim and Agency Risk
A radio component may meet a specification while the network around it still lacks an accountable risk decision. NIST’s new federal Open RAN profile puts that handoff in plain view.
CASE FILE
The Root Address Was the Same. The Tree Was Not: RFC 9658 and Multipoint Identity
Two multipoint trees can begin at the same router and carry the same opaque value yet be different forwarding entities. Change the topology or the algorithm, and the eligible path and branches can change with it. RFC 9658 gives that difference a wire identity. It does not prove…
CASE FILE
NIST’s OT Draft Puts Version Custody Inside the Risk Decision
NIST plans to separate parts of its operational-technology guide into updateable web resources and companion documents. That may keep guidance fresher, but a plant’s risk record will need to say which versions actually informed its decision.
CASE FILE
The Contact Was on the Schedule. The Adjacency Never Arrived: RFC 9657 and Forecast Authority
A route engine can know that a satellite should cross a ground station's view at 12:03, reserve that contact and hold data for it. At 12:03, the clock may be wrong, the terminal may not acquire, the data rate may collapse or the adjacency may never form. RFC 9657 makes…
CASE FILE
The Model Said 800 Megabits. The Air Did Not: RFC 9656 and the Microwave Capacity Boundary
A path engine can ingest a microwave link's nominal bandwidth, select the route and produce a coherent topology explanation. Meanwhile, the carrier's actual signal-to-noise-and-interference ratio can deteriorate and the usable service capacity can fall. RFC 9656 makes the radio…
CASE FILE
The Reply Came from an Egress. It Did Not Prove the Path: RFC 9655 and the Nil FEC Boundary
A green MPLS echo reply can be perfectly real and still answer a smaller question than the dashboard claims. RFC 9655 lets a headend verify that the final receiver owns the intended egress address when Nil FEC hides the rest of the forwarding equivalence. That closes a dangerous…
CASE FILE
The Nonce Matched. The Status Could Still Be Wrong: RFC 9654 and the Freshness Boundary
An OCSP client receives exactly the random value it sent, validates the response envelope and turns its dashboard green. Yet the responder may have signed from a delayed revocation feed. RFC 9654 gives the client strong evidence that this is the answer to this request. It does…
Afrinic SAGA
Undischarged: what AFRINIC's instruments certify — and what they still await
Eleven months after the Receiver of AfriNIC Ltd asked the Supreme Court of Mauritius to end the receivership he administers, the retrievable public record still shows no judgment granting or refusing that request. What the record does show — in the registry's own communiqués…
CASE FILE
The Bit Was Available. The Protocol Was Not Approved: RFC 9650 and the Limits of Expert Review
Two experimental teams can each make a locally sensible choice and still produce a shared failure: both take the same apparently unused bit. RFC 9650 reduces that collision risk by making a public allocation easier to obtain. It does not convert the registry into a deployment…
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