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
791 articles
CASE FILE
The Tree Was Active. One Leaf Still Had No Packet: RFC 10018 and the P2MP Closeout Boundary
The Tree Was Active. One Leaf Still Had No Packet: RFC 10018 and the P2MP Closeout Boundary intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
CASE FILE
The Endpoint Still Spoke TLS 1.2. Its Old Handshake Had to Go: RFC 10015 and the Retirement Boundary
RFC 10015 does not switch TLS 1.2 off. It makes a more exacting intervention: keep the protocol version where it is still needed, but remove the finite-field Diffie-Hellman and RSA key-exchange paths whose risk can no longer be justified. The hard part begins after that sentence…
CASE FILE
W3C Resolved to Change WCAG 3. It Did Not Freeze the Text
On 25 August, the Accessibility Guidelines Working Group adopted three resolutions that pointed editors to a conformance draft and told them to resolve the document's remaining comments before updating WCAG 3. That was a real group decision. It was not approval of every word that…
CASE FILE
The Handshake Combined Two Secrets. The Random Generator Was Still One
RFC 10024 gives TLS 1.3 a precise way to combine a traditional exchange with ML-KEM. The construction protects against the failure of one cryptographic assumption; it does not certify that the two components were executed inside independent operational failure domains.
CASE FILE
The Name Matched. The Key Had No Right to Revoke: RFC 10007 and the Missing `cRLSign` Proof
One certification authority gave the same named subject two different keys. Only one was meant to sign revocation lists. For years, the validation text could let the other key cross that boundary precisely because its certificate said nothing about permitted use.
CASE FILE
The JSON Was Valid. The Trunk Still Needed an Owner: RFC 10006 and the Apply Boundary
A service provider can now describe a SIP trunk in a form an enterprise edge can discover, authenticate for and parse. The consequential question begins one step later: who is entitled to turn that description into running configuration?
CASE FILE
The Boot Loader Identified Itself. The Relying Party Still Had to Decide
RFC 10013 gives a measured component a portable identity and sampled value inside an Entity Attestation Token. That evidence can be fresh, signed and correctly encoded while the final question — what this device may do — remains unanswered.
CASE FILE
The Route Advertised 70. The Local Link Could Carry 50: RFC 10005 and Bandwidth Authority
One upstream says it has 70 units of capacity. The receiving router can reach that upstream only across a 50-unit local link, yet policy assigns it 70% of the traffic. The BGP UPDATE is valid, every session remains established, and congestion is still the expected result. RFC…
CASE FILE
The DNS Said the Domain Was for Sale. It Did Not Have Authority to Close the Deal
RFC 10023 makes a registered domain’s availability visible in DNS. Its compact signal can open a negotiation while the domain remains in use; it cannot identify the rightful seller, bind a price or complete the transfer.
CASE FILE
Internet Society's Resolution 2026-13 Points to Two Different Policies
The Internet Society's public records currently make one resolution number perform two jobs. Its trustee-selection procedures say they were modified by Resolution 2026-13. Its travel policy and formal e-vote register assign the same number to travel-policy amendments approved on…
CASE FILE
The Zone Was Online. One Address Family Could Not Reach Its Authority: RFC 10001 and DNS Partition
The dashboard stayed green because its resolver quietly used IPv4. An IPv6-only resolver followed the same published delegation, reached a missing dependency and stopped. The name had not disappeared; its authority existed on one transport path and not the other. RFC 10001 turns…
CASE FILE
The Route Tree Remembered Every Target It Saw. It Did Not Authorize the Detour
SIP History-Info can show how a request moved from one target to another. That makes it valuable evidence. It does not make the resulting route complete, truthful, permitted or successful.
CASE FILE
The Packet Came Back Complete. The Evidence Set Didn't: RFC 10029 and Authority Across DNS Types
A resolver asks once for an address, an IPv6 address and an HTTPS service binding. One successful packet returns. That packet can still leave one of the three questions unfinished. RFC 10029 makes the missing distinction operational: a shared envelope can reduce transactions, but…
CASE FILE
The Dialog Was Found. The Transfer Was Not Yet Earned: SIP Replaces and the Authority to Move a Conversation
A help-desk console can show “transfer accepted” while the target has refused the new call and the original caller is still hearing hold music. The messages may all be correct. The failure lies in treating a reference, a dialog match and a completed handoff as one event.
CASE FILE
The Login Was Real. The Request Context Wasn't: RFC 10027 and Authority Across Devices
A television asks for an account, a phone displays the authentic service, and strong authentication succeeds. Yet the token can still return to an attacker's device. RFC 10027 makes the missing control visible: the ceremony proved the user, but the unauthenticated path between…
CASE FILE
The Call Refreshed. The Conversation Might Not Have: SIP Session Timers and the Authority to Declare a Session Alive
A voice platform can receive a perfect 200 response to a session refresh while the caller hears silence, the media path has failed and the billing clock keeps running. The signaling record is real. The mistake begins when that one reality is allowed to speak for all the others.
CASE FILE
The Registry Redrew the Range. The Old Allocator Kept Issuing IDs: RFC 10028 and Authority over IPv6 Multicast Coexistence
RFC 10028 gives dynamic IPv6 multicast allocation methods separate numeric territory. That is necessary coordination, but it does not reach into an old appliance, rewrite its pool or show that the intended stream reached a listener. The operational question begins where the new…
CASE FILE
The Session Grouped Four Streams. It Did Not Reconstruct the Scene: RFC 10034 and Authority over a V3C Representation
Volumetric video does not travel as one self-sufficient picture. It can arrive as an atlas plus occupancy, geometry and attribute streams, each with its own packets and failure state. RFC 10034 gives those parts a shared transport grammar. It does not appoint any one green…
CASE FILE
The Header Asked for a Stream. The Proxy Still Owned the Flush: RFC 10036 and the Authority to Release an HTTP Message
A sender can place `Incremental: ?1` at the front of an HTTP message and begin producing useful content immediately. That does not make the path a pipe. Every intermediary still controls a parser, a security decision, a capacity limit and a buffer. RFC 10036 turns the sender's…
CASE FILE
The Server Issued a Locator. The Network Had Not Yet Accepted the Route: RFC 10038 and the Authority to Allocate SRv6 Reachability
A DHCPv6 Reply can make an SRv6 locator administratively real in a few fields: who received it, how it is divided and when it expires. The packet path is harder. A route still has to be installed, advertised, selected, programmed, filtered and joined to a local SID behavior. 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 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