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,392 articles
CASE FILE
One Validated Mailbox, One Unresolved Holder: Reading NEXGENET's Accountability Surface Directly
APNIC's own whois confirms that the abuse mailbox behind three autonomous systems was validated on 7 July 2026 — but the holder of one of those systems is now written differently by different public mirrors, and the registry of record still cannot be read first-hand.
CASE FILE
The Manifest Was Signed. Support Was Still an Out-of-Band Fact
A device receives an authentic update manifest, the operator console shows a plausible required version, and the rollout remains motionless. The missing fact is not in the signature: whether that Recipient implements the optional command, which local profile gives the command…
CASE FILE
The Server Was Healthy. The Dashboard Counted Its Prefetch Refusal as an Outage
A speculative request arrived before any reader had asked for the page. The server chose not to spend resources on that wager. Nothing had failed—yet the familiar status code made the refusal look exactly like a service incident.
CASE FILE
The Subscription Kept Running. Its Schema Had Changed Underneath It
The telemetry graph never went dark. Counters arrived on schedule, the subscription identifier stayed familiar, and the collector reported no transport break. Yet an upgrade had changed the schema that gave those values meaning. Continuity of delivery had concealed a…
CASE FILE
Seven W3C Directors Elected by Members Are Not Standards Delegates
W3C's 2026 election changes the people who oversee its corporation. It does not hand seven employers the Web's technical agenda. The consequential question is how the incoming directors distinguish the organizations that put them forward from the institution to which they now owe…
CASE FILE
The Value Was the Same. The Reconstructed Bytes Were Not: Deterministic CBOR
The signer and verifier held the same decoded map, agreed on every field and still computed different signature inputs. Nothing in the value had changed. One encoder had merely exercised freedoms that the other had silently removed. The failure was not “CBOR versus cryptography.”…
CASE FILE
The Proof Was Unlinkable. The Envelope Was a Fingerprint: BBS Signatures
Two BBS proof values arrive at different verifiers. The bytes do not betray that they came from the same signature. Yet both presentations carry the same rare header, the same ten-slot credential shape, the same unusual disclosed indexes and a public key used for only twelve…
CASE FILE
The Registry Said `co`. The Handshake Had Said Nothing: RFC 9952
The same two bytes appear in an IANA row, a DNS service advertisement and an endpoint configuration. Yet the packet trace contains no ALPN extension. All three records may be accurate. None can be promoted into the missing wire event.
CASE FILE
The Primitive Kept Its Name. The Reuse Rule Changed: RFC 10032
Three adjacent functions accept an AEGIS key and nonce. One encrypts and authenticates, one emits a keystream after discarding authentication, and one creates a MAC under the only reuse exception in the document. The shared primitive name is technically accurate. Treating it as…
CASE FILE
One Sequence Number Was Asked to Tell Two Histories: RFC 9721
EVPN can advertise a MAC address and an IP address together, then attach one number to say which reachability is newer. That bargain works until the two identities stop moving as a pair. RFC 9721 preserves the compact wire record, but only by creating a deeper operational duty…
CASE FILE
The Complaint That Never Reaches the Registry: Who Answers When You Report Abuse in the RIPE Region
Every spam wave, phishing kit and botnet C2 eventually produces a human being who clicks "report abuse" and waits. In the RIPE service region, the routing of that report — and the removal, in May 2026, of a paper notification channel from the registry's enforcement procedure…
CASE FILE
The Name Was Allowed. Yesterday’s Address Blocked the Device: RFC 9726
A manufacturer can put the right service name in a MUD policy while a firewall enforces the wrong moment of that name. RFC 9726 exposes the hidden translation between DNS intent and packet rules—and why a clean policy file is not proof of a working or safe IoT device.
CASE FILE
The Signature Verified. The Resource Server Still Had a Decision to Make: RFC 9701
A signed token-introspection response can prove which authorization server issued a particular answer for a particular resource server. It cannot decide what that server should let a caller do now. RFC 9701 strengthens the receipt between two authorities; it does not merge them.
Afrinic SAGA
RIPE NCC to AFRINIC: what the instruments actually certified
Africa's registry handover is usually narrated as an act of recognition. The dated instruments say something narrower, and for anyone who has to rely on them, more useful: what each deciding body actually certified, what it attached as a condition, and which body was positioned…
CASE FILE
The File Was Routed to Haptic Hardware. That Does Not Mean the Effect Survived: RFC 9695
A media label reaches the one subsystem whose output can push back on the body. The registry can say where the entity belongs; only the endpoint can show what it understood, what it discarded, how it adapted the request, and whether the machine returned safely to rest.
CASE FILE
The Successor Key Waited 30 Days. The Validator Fleet Did Not Share One Clock: RFC 9691
Day 30 can arrive on an operator’s calendar while thousands of RPKI validators are still on day 12, day one, or no timer at all. RFC 9691 gives a trust anchor a careful way to stage a successor key; it does not turn a dispersed relying-party population into one synchronized…
CASE FILE
The Certificate Carried the Key. It Did Not Carry the Recipient's Yes: RFC 9690
An RSA public key can be valid, correctly encoded and usable for familiar RSA operations while saying nothing about whether its owner will accept RSA-KEM today. RFC 9690 makes that separation unusually explicit. For an operator, the result is not a cryptographic footnote but a…
CASE FILE
The Proxy Joined the Path. It Did Not Join the Control Planes: RFC 9689
A legacy router can signal its half of an MPLS path while a controller programs the other half hop by hop. RFC 9689 shows how a PCECC proxy can make that migration path continuous. The dangerous shortcut is to let continuity erase the seam: one LSP may still contain two kinds of…
CASE FILE
The OID Was Right. One Missing NULL Changed the CMS Contract
Two systems can display the same friendly label—“RSA with SHA3-256”—and still disagree about the entity in front of them. RFC 9688 makes the reason unusually crisp: in CMS, the algorithm number is only one part of the wire contract, and the presence, absence or exact contents of…
CASE FILE
The Subscription Was Accepted. The Multicast Packet Still Had No Delivery Receipt
RFC 9685 lets a low-power IPv6 node subscribe to multicast or anycast service through Neighbor Discovery and lets a router redistribute merged listener state through RPL. Acceptance is a precise protocol receipt; it is not evidence that route state propagated, the right branch or…
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