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
805 articles
CASE FILE
The Indicator Was Defanged. Its Next Consumer Could Still Arm It
A security analyst pastes a bracketed address into a ticket. It looks inert, and in that surface it may be. Minutes later, a preview worker extracts the same string, restores its URI form and fetches it for inspection. The analyst never clicked. The ticketing chain still crossed…
CASE FILE
The HTTP Request Returned 200. The Certificate Decision Was Still Inside: RFC 9811
A green transport result is tempting because it is immediate, familiar and easy to graph. RFC 9811 makes that result useful without letting it impersonate the certificate-management decision carried inside it. The distinction is small enough to fit in one response and important…
CASE FILE
The Device Can Last for Years. Its Trust Anchor Cannot Be Treated as a Lifetime Constant
A field sensor can remain bolted to a bridge long after its manufacturer changes owners, its issuing CA rolls over and its original algorithm becomes uncomfortable. The device still has power. The network still reaches it. Yet whether it can trust the next service chain depends…
CASE FILE
The Space Was Reserved. One Executive Approval Was Still Too Weak: RFC 9812
Nearly seven-eighths of IPv6 address space was being held for a future that had not arrived. The registry called it reserved, but the rule for releasing a major piece could still be satisfied by an executive approval with no RFC. RFC 9812 repaired that mismatch without pretending…
CASE FILE
The IETF Approved Stateful NAT64 as an Internet Standard. The Shared IPv4 Pool Still Needs a Claim Ledger
An IPv6-only subscriber opens an ordinary connection to an IPv4 server. For a few minutes, a public IPv4 address and port become that subscriber's usable external identity. The address is shared, the claim expires, and the proof lives inside a translator. The IETF has now…
CASE FILE
The Server Never Saw the Password. Its OPRF Seed Still Defined the Blast Radius: RFC 9807
OPAQUE gives password authentication an unusually valuable property: the server need not learn the password, even when the account is registered. RFC 9807 also makes the harder truth visible. A secret can disappear from one side of a protocol while authority remains concentrated…
CASE FILE
The Registry Closed, but the Packets Still Knock: RFC 9805 and Router Alert's Residual Authority
The IETF has stopped future protocols from asking IPv6 routers for special attention through Router Alert. It has not stopped the installed protocols that already ask. That distinction turns a small registry change into a case study in how the Internet freezes a dangerous…
CASE FILE
The CDN Advertised a Ceiling. It Did Not Reserve the Service: RFC 9808
A new interconnection vocabulary lets one CDN publish capacity limits and aligned telemetry to another. The useful fact is narrower than the comforting one: the numbers can discipline delegation without guaranteeing that capacity has been reserved, a request will be admitted or…
CASE FILE
The Certificate Named Four Purposes. The Relying Party Still Had to Separate Them: RFC 9809
A new X.509 vocabulary distinguishes configuration, trust-anchor changes, update packages and safety-sensitive communication. Its value begins where its authority ends: the names travel, while combination policy, operational permission and proof of outcome remain local.
CASE FILE
The Standard Froze TLS 1.2. The Estate Did Not Disappear: RFC 9851
A feature freeze changes what a standards body will design next. It does not reach into a load balancer, find a dependent client or produce the receipt that says a protocol has left production.
CASE FILE
The Server Set `$istrusted`. The User Still Needed to Know Why: RFC 9979
A synchronized mailbox label can carry a useful judgment across clients. It cannot carry the evidence, actor, time and external result that the judgment leaves behind.
CASE FILE
The Domain Published “Reject.” The Receiver Still Owned the Decision: RFC 9989
A DNS record can travel farther than the authority that published it. Under RFC 9989, `p=reject` tells a receiving organization how a Domain Owner wants failed mail treated. It does not operate the receiver's gate. That separation is not a loophole in DMARC; it is the control…
CASE FILE
The Ping Passed One Tree Instance. The Policy Still Had Other Paths: RFC 9961
RFC 9961 gives an operator a sharply addressed test: one Root, one Tree-ID and one Instance-ID. That precision is valuable because an SR P2MP Policy can contain several candidate paths and each candidate can hold more than one tree instance. The same precision also limits the…
CASE FILE
The Auth Key Matched. The Packet Was Still Not Authenticated: RFC 9986
A 32-bit value can show that a peer reproduced the expected ISAAC sequence. It cannot turn the rest of a BFD control packet into authenticated evidence.
CASE FILE
The Decoder Named a Profile. Its Level and Band Still Set the Workload: RFC 9924
RFC 9924 makes “APV supported” an incomplete sentence. A profile identifies required coding features; a level bounds picture and tile workload; a band caps coded data rate. Only the three together describe the decoder claim that a professional workflow can test.
CASE FILE
The Product Was “CMC Compliant.” Nobody Had Named Its Role: RFC 10004
A certificate platform can pass a CMC checklist and still leave the decisive question unanswered: compliant as an end entity, registration authority, certification authority, client, server—or several of those roles on different edges?
CASE FILE
The Controller Built the Recovery Graph. The Next Packet Still Needed a Local Decision: RFC 9912
RFC 9912 gives unreliable radio conditions a bounded set of protection choices, then separates that prepared optionality from the path an upcoming packet actually takes. The distinction is operationally decisive: a green controller state is not a packet receipt.
CASE FILE
The Recovery Graph Contained Every Feasible Path. It Did Not Record the Packet Journey: RFC 9912
RFC 9912 gives unreliable media a disciplined space of recovery choices. It also draws a harder evidentiary line: the graph describes where a packet could go, while distributed forwarding decisions determine where each packet actually went.
CASE FILE
The OID Was Recognized. The SLH-DSA Certificate Still Failed the Mode Check: RFC 9909
RFC 9909 gives X.509 a precise vocabulary for SLH-DSA keys and signatures. That vocabulary is intentionally unforgiving: a parser recognizing the family does not excuse a Pure/Hash mismatch, present parameters, wrong key use or an unproved trust decision.
CASE FILE
The Classifier Named the Flow. It Did Not Prove the Treatment: RFC 9892
A DLEP modem can tell its router which header patterns belong to a flow, but RFC 9892 keeps that description separate from the extension that uses it, the data-plane state that follows and the service result an operator may later claim.
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