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.

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 URL Found the Token Authority. It Did Not Make the Issuer Trusted
An ACME client can be told where to fetch an Authority Token without giving the ACME server any reason to trust the token’s signer. Revision 05 of the JWTClaimConstraints profile draws that line sharply, then builds a separate chain of receipts for issuer trust, exact constraint…

CASE FILE
The Shared Dictionary Saved Bytes. It Joined the Secret Boundary
A compression dictionary may look like a performance asset, but RFC 9841 makes it part of the decoder's effective input. Once exact dictionary bytes can change the recovered content—or reveal secrets through output size—the optimisation belongs inside integrity, provenance and…

CASE FILE
Kubernetes’ Third-Party Slack Debate Is Not Yet a Continuity Policy
Kubernetes can decide that a related open-source project belongs in its Slack workspace. It can approve a channel request, and it can delegate the daily management of a group of channels. None of those acts says what happens to the discussion record if a provider changes terms, a…

CASE FILE
The Parser Accepted the String. The Protocol Still Had to Refuse It
A green check from a JSON parser can be the beginning of validation, not its end. RFC 9839 shows why a syntactically conforming envelope may still carry character content that no robust protocol should admit, preserve or silently erase.

CASE FILE
Both Instances Scored Eight. The Numbers Did Not Mean the Same Thing
Computing-aware traffic steering can compress a processor, a queue and a path into one convenient score. The new operational section of an IETF working-group draft makes the hidden condition explicit: before a selector compares two eights, every component must agree on how an…

CASE FILE
The Member Was Removed. Exclusion Still Needed Two Rekeys
A group controller can delete a name from its membership state in one administrative act. RFC 9838 shows why the cryptographic consequence is not equally instantaneous: the old key protects the first transition, the new key must protect what follows, and multicast delivery does…

CASE FILE
The Certificate Restricted the User. The Older Server Ignored It
A certificate can carry a narrower RPC identity without making the fleet obey it. A new NFSv4 draft turns that compatibility gap into an operational control question: which server actually replaced the credential in the request header, and which merely authenticated the peer…

CASE FILE
The VPN Number Arrived. Admission Was Still Open
RFC 9837 puts a 32-bit VPN service selector inside an IPv6 packet. The field can tell an egress router which forwarding entry to use. It cannot tell that router whether the sender had the right to choose it. That second claim belongs to the tunnel and the domain boundary.

CASE FILE
The Circuit Was Ordered. The Network Had Not Built It
RFCs 9833–9836 give an attachment circuit several linked identities instead of pretending that an accepted customer order is already a working path. Their most useful operational lesson is the distance between the service request, the provider’s network realization and the…

CASE FILE
The Registry Said 200. The Domain Command Failed
The newest EPP-over-HTTPS draft makes a deceptively simple distinction operationally unavoidable: `200 (OK)` can mean the command reached the registry application, not that the registry accepted it. Once registration traffic passes through load balancers, retries and distributed…

CASE FILE
The Signature Still Verified. The Identifier Had Changed
A new measurement submitted to the IETF shows how 64 different CBOR encodings can preserve one valid COSE signature while producing 64 different hashes of the transmitted statement. The cryptography did not fail. The storage boundary did: a system that reads and re-encodes before…

CASE FILE
The SID Field Was Present. The SID Was Still Missing: RFC 9831
A controller sent a Segment Type I with its SID-present flag set. The receiving headend could count all 16 octets of the field. Every octet was zero. That was not malformed silence: RFC 9831 permits the controller to describe the behavior it wants while leaving the executable SID…

CASE FILE
At Mozilla, a Module Owner’s OK Is Neither Commit Access Nor a Firefox Release Promise
Mozilla’s public governance material makes a useful distinction that reporting often erases. A module owner or peer can approve a change for a module; a person can separately be granted repository access; a change can be checked in or landed; and Firefox can later move code…

CASE FILE
The Parody Began After the Address Bar: PETA v Doughney
A joke can be obvious on a page and absent from the address that brought the reader there. That timing problem sat at the centre of *PETA v Doughney*. Michael Doughney said his “People Eating Tasty Animals” site parodied People for the Ethical Treatment of Animals. The Fourth…

CASE FILE
WTPF-26 Adopted Five Opinions. Each Final Text Matches Its Last Public Draft
Five documents left WTPF-26 with new numbers, new dates and the word `DRAFT` removed. Their authority state had changed: the Forum had adopted them. Their substantive English text had not. A pairwise comparison of the last public temporary documents with the five final Opinions…

CASE FILE
The Two Letters Were Not the Whole Case: Virtual Works v Volkswagen and the Call About `vw.net`
A two-letter domain can look like a conclusion. `vw.net` resembled Volkswagen's famous mark, and short addresses were scarce. But the Fourth Circuit refused to make resemblance do all the work. Its judgment followed a sequence: what Virtual Works' principals discussed when they…

CASE FILE
The Notification Arrived. One Backend Still Had Nothing to Serve
The IETF is asking for final comments on a proposed operating guide for RPKI publication services. Its sharpest rule is also the easiest to violate during a routine rollout: do not expose the new notification until every snapshot and delta it names is already available. An index…

CASE FILE
The Candidate Path Reached BGP. The Forwarding Plane Had Not Voted: RFC 9830
A controller advertises two Segment Routing candidate paths to a headend. Both arrive over valid BGP sessions. One wins BGP's comparison for its advertisement; the other remains a distinct route because its Distinguisher differs. Neither fact says which candidate the SR Policy…

CASE FILE
The Challenge Released the Message. It Still Had Not Reached the List
The IETF plans to replace the machinery behind its email services on 11 September. The design usefully separates challenges, list handling, identity rewriting, signing and outbound transport. It also makes the central operating question unavoidable: when one component reports…

CASE FILE
The CRL Number Was Higher. RPKI Still Had to Ignore It: RFC 9829
A relying party retrieves two signed revocation lists from one publication point. The first carries the larger CRL Number. The second is the file named by the certificate and hashed on the issuer’s current manifest. A generic PKI instinct says to trust the larger counter. RFC…
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