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
748 articles
CASE FILE
The SID Chose a Member Link. It Did Not Own the Bundle.
One peering interface was really three physical links. The ordinary Peer Adjacency SID sent traffic to the logical bundle and let its own balancing choose a member. The new member SID could instead place one flow on the lane that looked emptiest. That sharper instruction did not…
CASE FILE
The Certificate Named an Interface. It Did Not Prove the Device.
The commissioning test produced two honest identifiers. The certificate named the factory address of one Wi-Fi interface. The frame arriving at the access point used a private address chosen for that network. Rejecting the connection would punish a real device for using a privacy…
CASE FILE
Two Answers Said NOERROR. Only One Carried the New Zone
RFC 9660 can bind a DNS answer to the zone version that produced it. That makes a mismatch visible without pretending that one version token proves the zone is correct, the fleet has converged or users saw the same path.
CASE FILE
Internet Society Has a $329,000 Board Budget. Payment Disclosures Stay Internal
Internet Society's 2026 plan gives the public one Board number: $329,000. Its newly revised policies create real controls over trustee travel and other funding, but the disclosure chain ends with the Chair and the Board. The missing record is not a receipt folder on the open web.…
CASE FILE
The Timestamp Got Sharper. The Clock Did Not Gain Authority.
Send one NTP request through ordinary UDP port 123 and its arrival may be timestamped after software and queueing have already left fingerprints on the measurement. Wrap the same logical request in a PTP event message, and a compatible network card can timestamp it at the wire.…
CASE FILE
The Service Vanished. Its DNS Lease Did Not
A DNS Update Lease can make stale records expire without a cleanup command. It can also keep an authoritative answer valid long after the advertised service has stopped, because the server—not the requester—sets the operative publication horizon.
CASE FILE
The Message Had Expired. The Mailbox Had Not.
At noon, an offer in the inbox reaches the date chosen by its sender. At 12:01, the mail reader dims it. Search still finds it, the archive still holds it, and no deletion has occurred. That small separation is the point of the IETF’s newly approved work on the email `Expires`…
CASE FILE
The Catalog Went Empty. The Servers Obeyed
A DNS catalog zone can turn one compact, authenticated change into a new operating perimeter for an entire authoritative fleet. That efficiency is precisely why the catalog must be governed as executable authority rather than treated as a harmless list.
CASE FILE
The Route Said Valid. The Evidence Was Local.
One RPKI service fails. A customer network changes its view a second before its provider; the provider changes next, about five minutes later. If both networks export validation results as route attributes, one dependency failure becomes two waves of BGP UPDATEs. Nothing about…
CASE FILE
The signed chain skipped a delegation that still existed
NSEC3 Opt-Out allows a large parent zone to leave eligible insecure delegations out of its signed hash chain. That omission can be fully valid. It is also why the chain cannot serve as a complete delegation register: the proof authenticates a limited statement about a hash…
CASE FILE
The Revision Was Newer. It Was Not a Descendant.
A resolver needs a capability introduced on one branch of a YANG module. It accepts a revision dated later than the recommended minimum, yet that revision belongs to the sibling branch and never inherited the capability. The calendar comparison worked. The ancestry test never…
CASE FILE
The Version Number Promised Compatibility. It Had Not Tested the Device.
A controller sees a YANG module version above its recommended minimum and admits a change. The target then lacks the node the workflow expected—not because the version comparison lied, but because it answered a question about artifact lineage rather than the exact schema and…
CASE FILE
The files matched. The authority did not
An RPKI Signed Checklist can bind exact file bytes to a declared set of Internet Number Resources. That is a useful and unusually precise proof. It is also much narrower than the green result can appear: the entity does not identify a company, certify a document's truth, prove a…
CASE FILE
The Counter Named the Discard. It Had Not Proven the Cause.
Two interfaces report the same standardized discard class during one service degradation. At the first, a deliberate access rule is doing precisely what its owner intended. At the second, an old rule is catching valid traffic after a routing change. The labels agree; the…
CASE FILE
The Extension Was in IANA’s Registry. The Server Still Had Not Promised to Accept It.
A registrar’s integration system finds an `Active` EPP extension in IANA’s public registry and enables the command path. The next registry server’s greeting does not advertise the extension namespace. The specification is real and the catalogue is correct; the automation has…
CASE FILE
Two validators agreed on the version. They did not agree on the routes
Two RPKI validators can report the same RRDP session and newest serial while retaining different repository histories. The disagreement becomes visible only if they remember what hash an already-seen delta carried before. RFC 9697 turns that memory into an operational control…
CASE FILE
The Packet Carried the Action. One Router Could Not Read Far Enough to Perform It.
A correctly formed MPLS packet enters a path with a hop-by-hop action in a post-stack header. The first router finds and performs it. A middle router sees the in-stack indication but cannot read the entire post-stack container, so it skips that processing and forwards the packet.…
CASE FILE
The Device Said “Adult.” It Did Not Prove Who Was Holding the Family Tablet.
A child resumes a browser session left open under an adult profile on a shared tablet. The site requests an over-18 signal; the device returns a valid affirmative answer. No identity dossier crosses the network, yet the answer describes the enrolled context rather than the person…
CASE FILE
The Header Asked the Proxy to Stream. It Did Not Prove the First Event Moved.
An origin opens a Server-Sent Events response, sets `Incremental: ?1` and emits its first event. One proxy understands the field and forwards every arrival. The next proxy has never heard of the field, so it waits for the complete response. The response is designed never to…
CASE FILE
The Library Named a Direct Modifier. It Did Not Calculate the Dependency Graph.
Module B inserts a container into Module A. Module C then inserts a leaf into B’s new container. RFC 10035 lets the server report B as a direct augmenter of A and C as a direct augmenter of B. It deliberately does not place C on A’s list. The new inventory exposes immediate…
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