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,355 articles
CASE FILE
The Packet Carried a Resource ID. The Path Did Not Promise to Obey
An IPv6 packet may name the resource partition it wants at every hop and still emerge without proof that every router recognized the request, used the intended queue or preserved the promised isolation.
CASE FILE
The Certificates Were Related. The Verifier Still Owned the Decision: RFC 9763
A certificate authority can attest that two credentials belong to the same end entity. It cannot make two private keys act in a live exchange, choose a peer’s trust anchors or decide whether one successful authentication is enough. RFC 9763 is valuable because it draws that line…
CASE FILE
The Cache Could Stay. The Old Answer Could Not
An NFS client may re-read a busy directory, see the same names and still tell an application that a growing file has its old size. Revision 11 of a working-group draft answers that failure without pretending to abolish caching: it limits which answer the client may expose after…
CASE FILE
The Authorization Server Said Active. The Resource Server Still Had to Decide
One green boolean can look like permission. RFC 9767 is more disciplined: `active: true` is an authorization server’s answer to a resource server’s specific question about a token, a proof method and, sometimes, minimum access. The resource server still owns the application…
CASE FILE
One Subscription, Many Publishers: The Parent Owns the Split
A collector can ask one network node for one stream of updates and receive data from several publishing processes hidden behind the same address and subscription identifier. Revision 21 of the NETCONF distributed-notification draft corrects the authority that makes this possible…
CASE FILE
A SLSA Attestation Is Evidence, Not the Acceptance Decision
A SLSA provenance statement can say something precise about one artifact and the build that produced it. That precision matters. But it does not choose which builders a verifier trusts, define a package’s expected source and parameters, declare a release complete, or decide what…
CASE FILE
QUIC's Partial Reset Gained a Permission Gate. Its Delivery Promise Can Still Shrink
Revision 11 of QUIC Stream Resets with Partial Delivery closes an important permission gap: an endpoint may not send `RESET_STREAM_AT` unless its peer advertised support. That rule says the receiver can parse the extension. It does not make the sender's first Reliable Size…
CASE FILE
The Receiver Counted the Marks. It Did Not Choose the Sender’s Response
An acknowledgment disappears. The next one arrives with a three-bit counter advanced, but perhaps not by as little as it seems: the counter may have wrapped while the evidence was missing. RFC 9768 gives TCP a better congestion receipt, not an oracle. The receiver reflects marks…
CASE FILE
The Beacon Anchor Became Verifiable. Its Quantum Timeline Still Needed Another Archive
Revision 01 of Wathīqa repairs an important weakness in its evidence record: the first beacon value is no longer merely a time-shaped field but a signed pulse tied to a pinned certificate, with an optional successor that can prove immediate chain continuity. The repair is real.…
CASE FILE
The Receiver Lowered the Window. The Sender Never Changed Its Algorithm
A small advertised TCP window is often read as proof that the receiving application cannot keep up. RFC 9840 makes that shortcut unsafe. It gives the receiver a second reason to limit the window—deliberate low-priority transport—while leaving the sender’s congestion-control…
CASE FILE
The Reference Was Well-Formed. It Was Not Yet Evidence
A digest can look precise enough to end an argument. Revision 03 of the Canonical Payload Binding draft instead turns that apparent certainty into a sequence of accountable tests: the reference must be admissible, one authorized digest context must be selected, the artifact must…
CASE FILE
The Maximum Metric Kept the Link. Missing Data Could Keep It or Remove It
A routing value can look catastrophic without withdrawing a link, while an empty field can either remove that link or leave it eligible. RFC 9843 makes those outcomes deliberate. Operations fail when telemetry turns three different protocol states into one red icon.
CASE FILE
A RISC-V Profile Is a Compatibility Vocabulary, Not a Hardware Mandate
A RISC-V profile makes a useful promise of language, not a universal promise of hardware. It tells hardware and software communities which bounded instruction-set surface they can discuss together. It does not, by itself, tell a buyer what is on a particular chip, tell a…
CASE FILE
The Cipher Was Approved. Its Key Budget Still Had to Be Counted
An AEAD name in a configuration proves which construction was selected, not how much cryptographic authority remains under the live keys. Revision 13 of CFRG’s usage-limits draft makes the missing control plane visible: applications choose the risk target, deployments count the…
CASE FILE
The Interface Name Was Required Locally. It Had to Vanish Before Transmission
An IPv6 link-local address can be perfectly valid and still fail to identify a usable path. RFC 9844 supplies the missing local selector—a zone identifier—while imposing an equally important limit: the label has meaning only inside one node and must not become identity on the…
CASE FILE
Unicode 18’s Beta Is a Review Surface, Not a Release Commitment
Unicode’s public Version 18 page says its beta review has closed and lists 16 September 2026 for a final release. That is a useful planning signal. It is not yet evidence that Unicode 18 has been released, that a particular file is final, or that any implementation has adopted…
CASE FILE
The URL Found the Token Authority. It Did Not Make the Issuer Trusted
An ACME client can be told where to fetch an Authority Token without giving the ACME server any reason to trust the token’s signer. Revision 05 of the JWTClaimConstraints profile draws that line sharply, then builds a separate chain of receipts for issuer trust, exact constraint…
CASE FILE
The Shared Dictionary Saved Bytes. It Joined the Secret Boundary
A compression dictionary may look like a performance asset, but RFC 9841 makes it part of the decoder's effective input. Once exact dictionary bytes can change the recovered content—or reveal secrets through output size—the optimisation belongs inside integrity, provenance and…
CASE FILE
Kubernetes’ Third-Party Slack Debate Is Not Yet a Continuity Policy
Kubernetes can decide that a related open-source project belongs in its Slack workspace. It can approve a channel request, and it can delegate the daily management of a group of channels. None of those acts says what happens to the discussion record if a provider changes terms, a…
CASE FILE
The Parser Accepted the String. The Protocol Still Had to Refuse It
A green check from a JSON parser can be the beginning of validation, not its end. RFC 9839 shows why a syntactically conforming envelope may still carry character content that no robust protocol should admit, preserve or silently erase.
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