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
800 articles
CASE FILE
RFC 9882 Put SHA-512 in the Field. It Did Not Always Use It
A CMS record can truthfully name SHA-512 while that algorithm contributes nothing to the signature being checked. RFC 9882 requires exactly that combination on one of its two ML-DSA paths. The apparent contradiction disappears only when an auditor follows the bytes rather than…
CASE FILE
WebAuthn's Report Has Four Browser Columns. Independence Needs a Key.
W3C's new WebAuthn Level 3 Recommendation links a fixed test report with four browser columns. The transition record adds that part of Chrome's implementation differs from Edge's. That caveat is important—and incomplete. Product names show where tests ran; they do not tell a…
CASE FILE
RFC 9879 Modernised the MAC. It Did Not Retire the Legacy Reader
Two applications can open the same PKCS #12 file and report success for different reasons. One may verify its new PBMAC1 envelope. Another may fail to understand that envelope, ignore the failed check and continue to the encrypted key material. RFC 9879 makes the first path…
CASE FILE
The Header Was Allowed in the ACK. It Did Not Validate the Bill: RFC 9878
RFC 9878 fixes where several 3GPP SIP P-Headers may appear, including a narrow exception for ACK after a successful response. That permission solves an interoperability problem; it does not turn a signalling field into proof of location, route, entitlement or charge.
CASE FILE
W3C's ARIA Implementation Report Says March. Its File Changed in May.
W3C's updated *ARIA in HTML* Recommendation points readers to an implementation report whose visible date is 22 March 2026. The public file history shows a large revision on 20 May and another change on 27 May. Both can be true: March may be the evidence cutoff and May the…
CASE FILE
The Directory Returned a Geofeed Link. It Did Not Prove a Location: RFC 9877
RFC 9877 makes IP-geography data easier to discover through RDAP. Its most important operational lesson begins where that discovery succeeds: a standardized pointer is still several evidence steps away from a defensible location decision.
CASE FILE
The Number Was Registered. The Device Had Not Agreed to Run It: RFC 9876
A compact identifier can cross a constrained network faster than the evidence needed to trust it. RFC 9876 makes the CoAP Content-Formats registry more reliable, but its successful review remains a coordination event—not a production verdict.
CASE FILE
W3C’s Commerce Workshop Has Two ACPs. Its Record Needs Protocol Keys
The W3C and GS1 workshop on e-commerce for humans and AI agents will bring several emerging protocols into one room. Its public pages already expose a small but consequential recordkeeping problem: ACP names two different public artifacts. Before the event turns presentations…
CASE FILE
The Reply Proved One Probe Arrived. It Did Not Certify the Next Datagram: RFC 9869
A matching token can turn silence into a positive measurement. RFC 9869 lets a UDP sender learn that one padded probe reached a UDP Options receiver. Its discipline lies in the boundary: the reply belongs to one packet, one path and one moment, not to every datagram that follows.
CASE FILE
The Bit Said an Option Appeared. It Could Not Say When or How Often: RFC 9870
A thousand packets can collapse into one bit. RFC 9870 makes UDP Options visible in IPFIX, but its most efficient fields preserve set membership, not packet history. The difference matters whenever an alert, audit or policy decision asks more than “was this option seen at least…
CASE FILE
The Route Key Stayed the Same. Its Meaning Changed at the Border: RFC 9871
Domain Two calls low delay C2. Domain One calls it C1. RFC 9871 lets the route cross that border without pretending the two administrations share a dictionary: the route key stays `(E2,C2)`, while a separate Local Color Mapping record carries the receiving domain's meaning.
CASE FILE
The Prefix Was Right. The Packet Took the Wrong Uplink: RFC 9872
A multihomed host can learn a perfectly valid NAT64 synthesis prefix and still send the resulting address toward the wrong provider. RFC 9872's consequential move is therefore not a new prefix format; it is to prefer a signal that can retain which first-hop router supplied the…
CASE FILE
The Registry Marked a Second Email Primary. It Still Had No Delivery Receipt: RFC 9873
RFC 9873 gives an EPP contact a second address and lets the extension call it primary. That is useful coordination, but it is easy to promote a preference flag into a claim the protocol never makes: neither address has thereby been shown to exist, receive, forward, be read or…
CASE FILE
The Registrar Deleted One Domain. Other Domains Inherited the Risk: RFC 9874
A registrar can be entitled to delete its own domain and still be unable to contain the consequences. RFC 9874 exposes the awkward case: a subordinate host sponsored by one client can remain the name server for domains sponsored by others, so a local disposal request reaches…
CASE FILE
The Response Named a Group. The Cache Fleet Received No Common Order: RFC 9875
An origin can label related HTTP responses and ask a receiving cache to invalidate the group after a state-changing request. RFC 9875 makes that local relationship legible; it does not turn one header into a synchronized purge across a hierarchy, a mesh or the user's screen.
CASE FILE
W3C’s New Agent Benchmark Group Needs More Than the Same Score Twice
The new Agent Conformance and Benchmarking Community Group gives itself a crisp test: two independent parties should be able to reproduce a published score to the same value. That would be useful evidence that a procedure can be rerun. It would not yet answer whether the…
CASE FILE
The Package Held Both Forms. They Were Not Yet One Key: RFC 9935
An ML-KEM key package can carry a compact seed and a full decapsulation key together. That convenience creates an import decision: until the recipient regenerates one from the other and compares them, a well-formed package has shown two values, not one coherent key.
CASE FILE
The Hash Was Fast. Collision Recovery Was the Real Control: RFC 9923
FNV can put an item into a table quickly and consistently. It cannot promise that hostile inputs will remain evenly dispersed. RFC 9923 turns that narrow limitation into an operational question: can the operator see concentration early, change the hashing epoch and rebuild the…
CASE FILE
The Diagram Had a Bit. The Registry Did Not: RFC 9927’s C-Flag Repair
RFC 8928 drew a C-flag into a compact wire field without registering its position. A later standard properly allocated that same position to another field. RFC 9927 repairs the collision before known deployment made compatibility expensive—but publication cannot update a parser…
CASE FILE
The Cache Header Said Fresh. RFC 9919 Says the Signed Response Decides
A cached OCSP response can arrive without the client ever touching the responder. Its HTTP envelope can announce that the entity is fresh, public and reusable. RFC 9919 permits that efficiency at immense scale, then draws a hard evidentiary line: those headers guide the cache…
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