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
734 articles
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.
CASE FILE
The Router Set the P Flag. No Prefix Had Been Delegated Yet: RFC 9762
An IPv6 Router Advertisement can now tell a capable host to prefer a delegated prefix over another address from the shared link. That one bit arrives early enough to prevent a disruptive double start. It still cannot stand in for the DHCP exchange, the relay route or a packet…
CASE FILE
An SPDX License Expression Is Not a Compliance Verdict
An SPDX expression can make a licensing statement easier to exchange, compare and correct. That is valuable precisely because the statement has limits. A syntax-valid string can identify information that an author declared, information someone found in a file, or a conclusion…
CASE FILE
A Rust Trademark Permission Is Not a Rust Project Decision
A permission to use the Rust name or logo can be important: it tells a reader something constrained about how an identity claim may be presented. It cannot, by itself, make its holder part of the Rust Project, establish that a team reviewed code, turn a repository into an…
CASE FILE
The Large BFD Packet Stayed Up. The Whole Path Was Not Proven: RFC 9764
A green BFD session can now say something useful about packet size, but only if the claim stays as narrow as the packets that earned it. RFC 9764 turns padded control traffic into a recurring lower-bound test. It does not turn one forwarding treatment into a certificate for every…
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.
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