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.

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
183 articles
CASE FILE
The Hybrid Secret Was Derived. The Client Still Had to Trust the Host: RFC 10042
RFC 10042 gives SSH a precise way to combine ML-KEM and classical ECDH into a fresh session secret. It makes a key-establishment transcript stronger against a defined class of cryptographic risk; it does not make the client’s host-trust decision, authenticate a user, grant an…
CASE FILE
W3C’s Web Performance Charter Separates Implementer Interest From Interoperability
W3C has approved a new charter for the Web Performance Working Group through August 2028. Its most consequential governance choice is a distinction, not a deliverable: two implementors may express interest in a feature before it enters a specification maintained as a Candidate…
CASE FILE
The TACACS+ Server Was Configured. Its Authority Was Not: RFC 9950
RFC 9950 gives a device a precise YANG surface for configuring TACACS+ servers, credentials and safeguards. That configuration can change a powerful future control path; it is not an authentication event, an authorization result or a proof that a server may decide for anyone.
CASE FILE
The Test Was Authenticated. The Capacity Claim Was Not: RFC 9946
UDPSTP can authenticate its control exchange, limit a short diagnostic test and feed status back to a sender. RFC 9946 does not convert any resulting number into a capacity entitlement, a service guarantee or an operator verdict.
CASE FILE
The CMC Message Arrived. It Did Not Arrive With Certificate Authority: RFC 10003
One CMC entity can travel by file, mail, HTTP or TCP. RFC 10003 makes that portability useful without turning any carrier, delivery receipt or listener into proof that a certificate authority made a decision.
CASE FILE
The Key Became Portable. Custody Did Not: RFC 9964, ML-DSA and the AKP Boundary
Post-quantum migration often arrives in a deceptively tidy form: choose a new algorithm, register an identifier, put a key in the familiar container, and continue signing. RFC 9964 does something more useful and more limited. It defines how ML-DSA keys and signatures can travel…
CASE FILE
A Completed SCIM Request Is Not a Completed Cross-Domain Decision: RFC 9967
An asynchronous identity request is easy to over-read. A provider accepts a SCIM change, returns 202, and later emits a Security Event Token that carries the same transaction value. The trail is valuable: it gives two parties something specific to correlate. But it does not…
CASE FILE
The Legacy Code Point Reached the Client. It Did Not Reauthorise the Server: RFC 9963
An IANA code point can look like a broad permission slip when it appears in a migration review. RFC 9963 is deliberately narrower. It gives TLS 1.3 three legacy RSASSA-PKCS1-v1_5 signature values, but only for a client proving possession of a client-certificate key after a server…
CASE FILE
The Reverse Socket Arrived. The Device Had Not Yet Identified Itself: RFC 10011 and RESTCONF Call Home
A controller can receive a connection from the direction it expected, on a listener it deliberately opened, after a device has been configured to call home. That is useful evidence. It is not yet the same thing as knowing which device has arrived, establishing a RESTCONF session…
CASE FILE
W3C’s WebAppSec Charter Draft Gives 16 of 17 Deliverables No Completion Date
W3C’s proposed Web Application Security charter is unusually candid about time: almost every normative deliverable says its expected completion is undetermined. That is not evidence that sixteen specifications are late. It is evidence that the charter maps authority better than…
CASE FILE
The Quantum-Safe Key Was Added. The Classical Recipient Still Opened the Mail: RFC 9980
RFC 9980 gives OpenPGP a post-quantum vocabulary, including composite encryption keys that combine ML-KEM with X25519 or X448. That is an important interoperability step. It is also easy to overstate. A message can carry a genuinely PQ/T-capable recipient key and still be…
CASE FILE
APT’s PP-26 Common Proposals Can Advance Without Regional Unanimity
The Asia-Pacific Telecommunity has finished its last scheduled preparatory meeting before ITU’s 2026 Plenipotentiary Conference. What happens next is easy to compress into a misleading phrase: “the region’s proposals.” APT’s own rules are more precise. They create a preliminary…
CASE FILE
W3C Is Considering Web Speech for Audio. The Charter Draft Still Excludes It
W3C has publicly opened a route for Web Speech API to enter the Audio Working Group, but the document that would confer that authority has not caught up. The recharter issue calls adoption a substantive scope change; the draft charter still says speech recognition and synthesis…
CASE FILE
The BFD Counter Rose. The Service Path Was Still Unproven: RFC 9978 and Stability Evidence
A BFD session can stay Up while control packets disappear inside its Detection Time. RFC 9978 makes that early deterioration observable. It does not turn a control-packet counter into proof of data-plane loss, a failed route, or a customer-facing outage.
CASE FILE
W3C Proposes Dropping AT Driver Before ARIA Has Adopted It
W3C has published a clear departure document for AT Driver: the proposed next charter for Browser Testing and Tools removes the specification. The arrival document is not ready. ARIA's current charter does not list AT Driver, its receiving issue remains open, and its own public…
CASE FILE
W3C's WoT Registry Requires Two Reviews—Not Necessarily Two Reviewers
A proposed Web of Things charter would turn protocol bindings into a maintained W3C Registry. Its pilot rules make a revealing distinction: moving a binding to `Current` requires one review of the underlying protocol mapping and another of its fit with WoT, but the same qualified…
CASE FILE
W3C Rechartered WebAssembly. Its Component Model Remains at Community-Group Phase 1
W3C approved a new WebAssembly Working Group charter on 20 August. The charter names the Component Model as a possible normative deliverable, but does not admit it unconditionally: the WebAssembly Community Group proposal must first reach Phase 4. The public proposal registry…
CASE FILE
Internet Society Reaffirmed a NomCom Liaison Rule That Still Cites RFC 3777
On 10 July, the Internet Society Board reaffirmed its instructions for the trustee who may sit as liaison to the IETF Nominating Committee. The Board proposed no revisions. That decision made the instruction current again—but the text still tells the liaison to follow RFC 3777, a…
CASE FILE
W3C's Second Screen Patent Panel Is Done. Its New Charter Is Not Public Yet
W3C gave its latest Second Screen charter extension a precise dependency. On 18 August, it said the Working Group was waiting for a Patent Advisory Group's recommendations before beginning a new draft charter. Six days later, the PAG recommended that the Open Screen Application…
CASE FILE
W3C's Interim CEO Also Sits on the Board That Oversees the Office
W3C restored executive continuity in one sentence on 28 May: its Board appointed Dominique Hazaël-Massieux Interim CEO with immediate effect. The current public roster adds a second fact. He is also a Partner-selected Director on the Board that oversees W3C Management and the…
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