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,341 articles
CASE FILE
The Selectors Matched. The Capacity Did Not: RFC 9611
Several IPsec Child SAs can carry the same Traffic Selectors and still describe very different operating capacity. RFC 9611 creates a protocol vocabulary for grouping per-resource SAs, but deliberately leaves CPU placement, packet steering and performance evidence local. The…
CASE FILE
The Root Answer Was Authoritative. Its Address List Could Still Be Incomplete: RFC 9609
A resolver can receive a clean authoritative answer for the DNS root and still lack part of the address set it needs to use that answer well. RFC 9609 turns that apparent contradiction into an operating rule: bootstrap configuration, authenticated names, supplied addresses and a…
CASE FILE
W3C’s Shorter Status Pointer Leaves a Larger Verification Decision
A new draft pares a credential’s status reference down to a base address and an index. The verifier must still decide what question it is asking and which signed list can answer it.
CASE FILE
The Tunnel Kept the Packet and Lost the Congestion: RFC 9599
A tunnel can deliver every packet in view and still break congestion control. If its egress removes the only header carrying a congestion mark, the packet emerges apparently clean, the sender keeps its old rate, and a successful decapsulation becomes a false report of spare…
CASE FILE
The Domain Was Canonical. The Local-Part Was Not Normalized: RFC 9598
Two email addresses can look identical on a screen and still name different certificate identities. RFC 9598 makes that uncomfortable result deliberate: prepare the domain under IDNA2008, preserve the UTF-8 Local-part exactly, and never let visual similarity stand in for byte…
CASE FILE
The Claim Was Visible Before It Was Trusted: RFC 9597
RFC 9597 lets a COSE entity expose selected CWT claims before decryption or without an attached payload. That convenience can guide key discovery and routing, but it creates a dangerous interval in which a claim can influence the system before the system has earned the right to…
CASE FILE
The Header Named the Object. It Did Not Authorize the Action: RFC 9596
A protected type label can stop one COSE entity from masquerading as another. It cannot tell an application that the payload is true, that the signer was entitled to send this class of entity, or that any requested action should occur.
CASE FILE
W3C Approved Two French WCAG Translations. Their Pages Still Say Candidate
Two newly updated accessibility translations have two status labels on the same W3C pages. The difference is small in typography and large in document control: an adopting organization needs to know whether it is reading a candidate for review or the version W3C has authorized.
CASE FILE
The Token Opened the Door. The KDC Still Had to Admit the Member: RFC 9594
An access token can be authentic, correctly scoped and still prove no group membership at all. RFC 9594 makes that distinction operational: permission is issued at one authority, admission is completed at another, and usable group state exists only after a further exchange.
CASE FILE
The Tao Was Retired. The Web Page Inherited the Change-Control Problem: RFC 9592
Two engineers can follow the same official IETF link six months apart and both truthfully say they read the newcomer guidance. They may not have read the same words. That is not an argument for freezing the page. It is the reason a living page needs a receipt.
CASE FILE
The LIST Command Returned OK. Some Mailbox Metadata Was Still Missing: RFC 9590
A green completion line is comforting because it is exact. It is dangerous when a larger claim is attached to it. RFC 9590 makes that boundary unusually visible: an extended IMAP LIST command may complete successfully even when the server could not return metadata for one of the…
CASE FILE
The Signature Verified. It Did Not Name the Approvers: RFC 9591
An auditor receives a valid Schnorr signature, the group public key and the exact message. The equation checks. The approval list is still missing. RFC 9591 makes that result possible by design: FROST compresses several signing shares into one ordinary-looking signature. The…
CASE FILE
The Capability List Said EdDSA. It Still Had Not Named the Curve: RFC 9864
An algorithm name can look like a complete answer while leaving the decisive parameter somewhere else. A service that advertises `EdDSA` has said less than many capability systems assume: it may support Ed25519, Ed448, or a locally constrained interpretation. RFC 9864 repairs…
Afrinic SAGA
RIPE NCC to AFRINIC: the handover that moved the ledger but never escrowed it
Africa got its own internet registry in 2005. What it did not get, on the evidence available two decades later, was a registry that could outlive its keeper. The entities moved. The guarantee did not.
CASE FILE
SDM4 fixed the fibre. The optical link still has to be built
SDM4 MCF MSA 1.0 is useful precisely because it is narrower than its launch language can sound. It gives four-core fibre suppliers a common passive baseline; it does not make every connector, transceiver, lane map or installed link interoperable by declaration.
CASE FILE
The Backup Restored the Key. It Also Restored Yesterday's State: RFC 9802
Two signing appliances wake from the same clean backup. Each holds the right private-key material. Each produces a signature that validates. Yet if both consume the same one-time index, the apparent recovery has broken the security assumption that made the signatures trustworthy.…
CASE FILE
Petal’s petabit is a design envelope, not yet a delivered route
Petal matters because its two-core fibre design could materially change the density of transatlantic systems. But the most useful reading of its 1 Pbps label begins by refusing to treat a future engineering ceiling as present network capacity.
CASE FILE
The EU KIDS Act Proposal Audits a Plan, Not a Platform's Safety
Brussels wants the largest social and video platforms to show how they would protect children. Its proposed independent audit would make that plan inspectable. A quieter clause says what the audit cannot do: turn a report, or the Commission's silence, into a finding that the…
CASE FILE
SHACL Can Derive a Triple Without Naming the Rule That Made It
A data statement produced by a rule can look identical to one supplied by a source. W3C's new SHACL 1.2 Inference Rules draft provides a way to keep the producing rule attached, but makes that trace optional. The distinction matters wherever a derived statement leaves the rule…
CASE FILE
The Packet With No Payload That Can Move TCP State Backward
Presto’s pseudo-segment solves a hard pipeline problem by turning a backward state correction into another forward pass. That synthetic record can be authoritative inside the transport without being user traffic, a completed socket operation or proof that an application received…
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