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
799 articles
CASE FILE
W3C Put Peer-to-Peer Inside WebTransport’s Scope, Not Its Deliverable List
A new WebTransport charter gives peer-to-peer work a legitimate place to be explored, but not yet a named standards output. That distinction is the useful part of the decision. It lets engineers test local-network and NAT-traversal ideas without asking readers to confuse an…
CASE FILE
The CA Was Trusted. Its Other Certificates Entered the Control Plane: RFC 9918
A NETCONF server can trust the right certification authority for the wrong breadth of purpose. RFC 9918 warns that if the listed CA also issues certificates for unrelated uses, those certificates can be accepted into the management channel. The TLS chain may validate perfectly…
CASE FILE
The Error Was Seen in Reverse. The Forward Link Was Removed: RFC 9917
A router at the far end records receive-side errors. Policy turns that observation into a colour on the reverse directed edge. Another router can then remove the forward edge from a Flex-Algorithm topology. RFC 9917 makes this chain computable; it does not make the colour a…
CASE FILE
APA Wants One W3C Charter-Review Queue, Not Two. The Review Duty Remains.
W3C’s accessibility reviewers have asked to stop receiving duplicate charter-review tickets because they already work from the central Strategy queue. Privacy reviewers, meanwhile, say their local copies are useful. The disagreement is not about whether horizontal review matters.…
CASE FILE
The Reply Omitted the Option. Retirement Was Still Unproven: RFC 9915
The NTP option was gone from the new DHCPv6 Reply, yet the client kept sending packets to the old time server. That is not a contradiction in the standard. It is a warning that a server-side withdrawal, a client-side state change and an observed service outcome are three…
CASE FILE
The Latest TLS Version Won. The First PCEP Message Still Had to Wait: RFC 9916
RFC 9916 makes a narrow security judgment with large operational consequences: PCEPS should negotiate the newest TLS version it can, but it must not let PCEP application data travel before the handshake is complete.
CASE FILE
The Track Was Acknowledged. No Packet Had Used It Yet: RFC 9914
RFC 9914 gives constrained networks a disciplined way to project a routed Track through an RPL topology. Its acknowledgments establish specific control-plane facts. They do not certify that traffic has traversed the Track, met a deadline or reached an application.
CASE FILE
W3C’s Data-Governance Workshop Can Reroute a Proposal. That Is an Agenda Decision.
W3C’s call for a TPAC 2026 mini-workshop on Data Governance & Ownership asks a useful question: what is broken, and what should Web standards do next? It also reserves a quieter power. Because the subject overlaps AI and Society and Age Assurance, organisers may ask a contributor…
CASE FILE
The Link Named the Parent. It Had Not Frozen the Hierarchy: RFC 9910
RFC 9910 gives RDAP clients typed paths through number-resource hierarchies. Those paths are useful navigation, but they are not sealed records of what the registry would have returned at an earlier time.
CASE FILE
The Module Passed Validation. The Registry Had Already Changed: RFC 9907
RFC 9907 draws a line automation teams often blur: an IANA-maintained YANG module is a useful machine-readable representation, but the IANA registry remains the unique authority. Green syntax is not a freshness receipt.
CASE FILE
The Server Described the CSR. It Had Not Approved the Certificate: RFC 9908
RFC 9908 lets an EST server describe a certificate request with far greater precision. That instruction is valuable precisely because it remains separate from possession, authentication, authorization, issuance and deployment.
CASE FILE
AGWG’s Public Charter Date Passed. Its Minutes Still Recorded a WCAG 3 Resolution.
The public page for W3C’s active Accessibility Guidelines Working Group charter ends on 28 August 2026. Four calendar days later, draft minutes record the group accepting a new set of WCAG 3 updates and freezing the reviewed document while preparing a Call for Consensus. That…
CASE FILE
The Registry Released the Port. The Appliance Did Not Hear: RFC 9900
RFC 9900 correctly returns three unused NETCONF port assignments to the registry. That global record cannot by itself retire a listener, a firewall entity or an old image inside an operator's estate.
CASE FILE
The Registry Said Stop Signing. The Zone Still Needed a Rollover: RFCs 9904 and 9905
RFC 9904 made IANA's DNSSEC algorithm tables the living recommendation record. RFC 9905 used that record to stop new SHA-1 signing while preserving validation support. Neither action remotely changes a live zone.
CASE FILE
The Rule Did Not Change. What It Matched Did: RFC 9899
An ACL can remain byte-for-byte unchanged while the named set behind it gains or loses members. RFC 9899 makes that separation useful for operations—and impossible to ignore in an audit.
CASE FILE
The Second Subflow Joined. Resilience Was Still Unproven: RFC 9897
RFC 9897 can authenticate another DCCP subflow into one multipath connection. That is a precise control-plane achievement, not evidence that the path carried useful traffic or rescued a service.
CASE FILE
The Router Could Reach the Address. It Still Could Not Name the Subscriber: RFC 9898
An IPv6 neighbor-cache entry is executable forwarding state. It can tell a router where to send the next frame and whether recent reachability has been confirmed. It cannot, by itself, tell an investigator who was entitled to use the address.
CASE FILE
SVG Accessibility Published Again After Eight Years. Its Testing Milestone Is Still Missing
The return of SVG Accessibility API Mappings to the W3C publication track is not a ceremonial event. A new Working Draft appeared on 27 August 2026, 3,031 days after the previous one, with substantive changes to how accessible names, roles and properties are exposed from SVG. Yet…
CASE FILE
The Diagram Entered the Definitive RFC. The Text Still Owned the Meaning: RFC 9896
RFC 9896 lets the RFC Production Center change SVG tooling without freezing one implementation forever. It keeps a harder invariant: the concept must survive in text, and every image path must remain consistent with it.
CASE FILE
The Modem Granted Credit. The Link Still Owed a Delivery: RFC 9893
A DLEP credit window tells a router how many octets it may send toward a modem queue. It does not tell an operator what happened after that boundary. Treating permission as delivery turns a useful control into a false service receipt.
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