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.
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,399 articles
CASE FILE
The Root Verified. The Proof Still Could Not Name the Leaf
A one-bit path can point to leaf 1, 2, 4 or 8, depending only on how large the tree was. The current SCITT profile can still prove that a candidate statement belongs under a signed CCF root. What it cannot always do, from the proof alone, is say where that statement sat.
CASE FILE
The Message Fit the Schema. That Still Did Not Make It True: RFC 8927
RFC 8927 builds a deliberately narrow gate for JSON messages. A message that passes has the declared shape; identity, authority, freshness and real-world effect still wait on the other side.
CASE FILE
A Dismissed Dependabot Alert Is Not a Remediation Verdict
A dismissed Dependabot alert records a triage decision about a repository-facing signal. It can be sensible and well documented. It still does not prove that vulnerable code is absent from a deployed system, that an upgrade was accepted, or that a remediation has happened.
CASE FILE
The Relay Appeared on the Local Network. Who Authorized the Advertisement?
A MOQT client can now be told how to find a nearby relay, which protocol label to offer and which name to check in its certificate. The new draft is precise when DNS moves the socket. It is not yet precise about who may put the local relay in front of the client.
CASE FILE
The Client Reported the File Attributes. The Metadata Server Could Still Verify Them: RFC 9766
RFC 9766 gives an NFS client a cheaper way to carry data-file observations back to the metadata server. The design is valuable because it refuses to make that report final: weak evidence can save work without becoming metadata sovereignty.
CASE FILE
A Yanked PyPI Release Is Not a Package Withdrawal Verdict
A PyPI yank changes how a repository presents a release to selection tools. It can be an important signal for maintainers and consumers, particularly when a release is broken or violates a compatibility promise. It is not, by itself, a record that a package has been deleted, that…
CASE FILE
A Kubernetes NetworkPolicy Is Not a Network-Flow Verdict
A Kubernetes `NetworkPolicy` can be a disciplined way to declare which layer-3/4 connections should be allowed for selected Pods. It is not a transcript of a particular connection. It cannot, by its existence, prove that a CNI implementation enforced it at a stated instant, that…
CASE FILE
The Second Approval Could Be Prepared Before the First Was Signed
Revision 04 of EP-QUORUM fixes an unusually revealing defect: its earlier “strong” approval chain linked contexts that could all exist before any human signed. The replacement makes each successor depend on the completed predecessor proof. That repairs cryptographic causality…
CASE FILE
One Durable Name, a Fresh Route at Every Hop: RFC 9758
RFC 9758 gives a resource a compact name that can survive movement. That durability comes from what the name refuses to contain: no location, no reachability promise and no route. Each relay must still decide what the identifier means here and now.
CASE FILE
A GitHub Ruleset Bypass Actor Is Not a Bypass Event
A repository can deliberately name the people, roles, teams, apps or keys that may bypass a GitHub ruleset. That is an important control decision. It is not a record that any one of them did so on a particular ref, and it is not a substitute for the separate records of review…
CASE FILE
The Hashes Matched. That Did Not Prove the Network Was Right
Revision 01 of the proposed IS-IS Aggregated SNP Hash exchange can make a million-fragment database cheaper to compare. Its restraint matters more than its speed: a matching summary ends a search for differences, but does not authenticate the state, validate the topology or prove…
CASE FILE
Removing a PyPI Collaborator Is Not Trusted-Publisher Revocation
Taking a name off a project’s collaborator list is a real access decision. It should not be described as a complete release-channel revocation when the publishing identity is governed on a separate surface.
CASE FILE
The Grandmaster Won the Election. That Did Not Prove the Time Was Right: RFC 9760
The Best timeTransmitter can be selected exactly as the profile requires while the winning clock, its external reference or the path to it remains wrong. RFC 9760 gives enterprise PTP a disciplined way to interoperate at scale. It does not turn an election result into proof of…
CASE FILE
A Kubernetes Admission Policy Binding Is Not an Enforcement Outcome
A policy binding is a useful public declaration of intended admission behaviour. It becomes misleading only when it is allowed to stand in for the request, evaluation and response that it does not itself record.
CASE FILE
RDAP Can Name the Assessor. It Cannot Authenticate the Result
Revision 02 turns a lone score into a time-bounded, contestable set of claims from multiple issuers. Yet its most important field, `scoreIssuer`, supplies attribution rather than in-band proof that the named assessor actually made the assertion.
CASE FILE
An Archived GitHub Repository Is Not a Retirement Decision
GitHub’s archive control has a clear and useful job: it changes a repository’s platform state to read-only and signals that its owner no longer presents the project as actively maintained. That visible state can start a dependency review. It cannot decide, for a different…
CASE FILE
The Firewall Did Not Recognize the TLS Parameter. Blocking It Would Have Broken Extensibility: RFC 9761
A new ClientHello value can mean malware, a legitimate update, deliberate GREASE or simply that the firewall is older than the endpoint. RFC 9761 makes that uncertainty operational: compare the device's declared profile with what the firewall actually understands, then keep…
CASE FILE
An OpenSSF Scorecard Is Not a Dependency Decision
OpenSSF Scorecard turns selected repository signals into a compact public measurement. That is useful precisely because it is narrow. A number can focus a dependency conversation; it cannot decide whether a particular release belongs in a particular system.
CASE FILE
A CODEOWNERS File Is Not a Review Receipt
A `CODEOWNERS` file can tell GitHub where review responsibility should be routed for a changed path. That is useful machinery. It is not a historical record of who was selected for a particular pull request, whether the eligible person received or completed a review, or whether…
CASE FILE
The Chain Passed. The Header That Said So Was Unsigned
A new DKIM2 draft gives mail systems a compact way to report a verified custody chain. Its sharper contribution is the warning attached to that convenience: the report is a local, unprotected memo, not evidence that can be inherited by the next hop.
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 IP-asset owners and leadership teams: alliance briefings, private reports and direct analyst support.
Join Leadership AllianceSession Map
Active Dossiers
AFRINIC Saga
Multi-year governance and legal crisis with implications for RIR accountability worldwide.
Open AFRINIC Saga