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
747 articles
CASE FILE
The Algorithm Label Changed. The Key Refused to Follow: RFC 9709
An attacker can rewrite a cryptographic label without breaking the advertised cipher. RFC 9709 answers that awkward fact by making the complete encoded algorithm identity part of the key itself—and by forcing operators to separate successful processing from evidence they can…
CASE FILE
The IG Lab May Use AI to Organise Proposals. It Must Not Let AI Judge Them
The first Internet Governance Lab closes its call with a useful rule and an unfinished method. AI-assisted tools may help the IGF Secretariat organise or analyse submissions, but may not evaluate them. That boundary will matter only if the administrative outputs can be followed…
CASE FILE
A Preference Can Exclude a City Before the Evidence Arrives: RFC 9712
A candidate city can disappear before a site visit, not because it failed a test but because a preference was treated as one. RFC 9712 is a compact repair to IETF meeting policy with a larger governance lesson: discretion becomes accountable only when the decision owner…
CASE FILE
Four VPN Restrictions, One Label, No Shared Authority
On 9 September, the Internet Society grouped four very different interventions under the heading “VPN restrictions”. The taxonomy is useful; the label is dangerous. An age rule, a blocking order, a logging duty and a prohibition do not regulate the same actor or need the same…
CASE FILE
The Registry Marked the Version. It Did Not Supply the Meaning: RFC 9713
RFC 9713 added one small column to an IANA table and, by doing so, exposed a large operating mistake. A code point can be allocated, valid for BPv7 and safely clear of the public assignment pool while still saying nothing about whether this receiver knows its content, shares the…
CASE FILE
ICANN87 Registration Stops Before the Sched Account
ICANN's newly published meeting schedule exposes a small boundary with large consequences: registering for ICANN87 does not create the separate Sched account used to navigate the programme. That distinction should govern the numbers reported after the hybrid meeting.…
CASE FILE
The Public Record for the Auckland Declaration Cannot Yet Route an Incident
Four research-network leaders have signed a regional cyber-resilience declaration built around trust, preparedness, information sharing, incident coordination and mutual support. The promise matters. The pages now available to a member or partner still do not show who can receive…
CASE FILE
One Color Crossed Three ASes. It Never Became an SLA: RFC 9723
A low-latency color can survive every BGP hop and still fail to buy low latency. RFC 9723 gives SRv6 operators a compact way to propagate intent through colored locator prefixes; it does not merge the intent dictionary, route installation, packet path and customer outcome into…
CASE FILE
An IXP Classifier Cleared 90% on Tested Exchanges. That Is Not a Global Map
A new model can distinguish route-server exchange from bilateral interconnection with better than 90% accuracy on the exchanges used for its transfer test. That is a promising result. The public record still needs to say which exchanges, relationships and errors sit behind the…
CASE FILE
Let’s Encrypt’s 99.21% IP-Certificate Signal Came From Three Days
A new study found Let’s Encrypt behind 99.21% of the IP certificates in one July 2026 stream. Its full-year 2025 data put ZeroSSL first. The apparent reversal is useful news, but only if the time window, counting unit and attribution chain travel with the percentage.
CASE FILE
The Stream Was Created. The Broadcast Was Not: RFC 9725
A WHIP endpoint can return `201 Created` while the programme remains black. RFC 9725 makes low-latency contribution easier to start; it also makes it essential to distinguish the HTTP resource from the media path, the production chain and the audience result.
CASE FILE
RFC 9727 Put the APIs in a Catalog. It Did Not Put the Catalog in Charge
The most dangerous API inventory can be perfectly formatted. Its links validate, its cache is warm, and its obsolete interface is gone from the list. None of those facts says what is still listening on the network.
CASE FILE
The Resource Disappeared. So Did the Diagnosis: RFC 9729’s Concealed Authentication Boundary
Concealed authentication removes a useful signal from an intruder: the server no longer has to advertise a challenge before an authorized client can prove itself. The same silence can also erase the evidence an operator needs when a key is revoked late, a gateway exports the…
CASE FILE
The Log Filter Made Tomorrow’s Evidence Decision
RFC 9742 gives network operators a common language for configuring syslog. The harder question is whether that language preserves the particular evidence an incident will make valuable.
CASE FILE
RFC 9744: the circuit identities a shared tunnel must retain
Fewer service labels can make a carrier network cheaper to operate. The saving becomes less convincing when the remote edge can no longer tell which customer circuit needs a different path.
CASE FILE
RFC 9746: the compatibility cost of choosing EVPN split horizon
A default-method entity can send an upgraded Ethernet segment back to its encapsulation baseline. The operational question is whether the network has kept the resources and evidence needed to make that return safely.
CASE FILE
RFC 9747: the neighbour returns a packet, not a health declaration
Unaffiliated BFD Echo removes the need for the far end to speak BFD. That useful simplification leaves the local operator owning both the test and the decision made from its result.
CASE FILE
The Private Number Was Valid. The Instruction Was Still Unowned: RFC 9752
A vendor payload can cross a stateful PCEP session with a real enterprise number and perfect framing while leaving the decisive questions unanswered: who published its meaning, what the PCC was allowed to do, what the device installed, and what the traffic experienced.
CASE FILE
The Message Continued. The Constraint Went Missing: RFC 9753
RFC 9753 lets stateful PCEP peers keep working when selected entities are optional. That is a useful availability mechanism. It is not evidence that the ignored meaning survived, that the replacement LSP is equivalent, or that forwarding remained safe.
CASE FILE
The Server Accepted the Message. The User Still Could Not Find It.
RFC 9755 gives IMAP a precise UTF-8 handshake, but a capability banner and a successful APPEND are only the first receipts in a much longer chain from stored octets to usable mail.
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