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
1,347 articles
CASE FILE
PNODI's Consultant Will Synthesize and Contribute. The Draft Needs Two Source Lanes
A consultant is about to inherit a mailing-list archive, a compressed calendar and an unusually delicate verb: synthesize. PNODI also expects that consultant to research and contribute suggestions of their own. Both tasks can improve the Internet Governance Forum's first…
CASE FILE
The EPP Extension Registry Records Coexistence, Not a Winner
Two extensions can solve much the same provisioning problem, use different XML namespaces and both deserve a place in the same public registry. That is not a defect in the catalogue. It is the governance fact the catalogue must preserve.
CASE FILE
The IGF Is Designing Crisis Connectivity. Start With an Activation Ledger
A coalition may be able to reconnect civilians after a shutdown or damaged network. Its first hard problem is not the satellite terminal, fibre route or radio link. It is deciding who may ask the coalition to act, who can lawfully say yes, what may be done, and how the public…
CASE FILE
Every Outer Bundle Was Delivered. The Inner Bundle Still Had Not Been Received
Bundle-in-Bundle Encapsulation gives a delay-tolerant network two journeys to observe. The outer bundles can reach their configured endpoint one by one, each with a valid delivery report, while the bundle carried inside them never reaches the Bundle Protocol Agent. The new DTN…
CASE FILE
A DNS Filtering Notice Is a Chain of Three Decisions, Not One Explanation
A link that explains why a name was filtered looks like a simple act of transparency. By the time it reaches a user, however, a resolver, an application and the user have each made a different decision. The record must preserve all three.
CASE FILE
The Firewall Matched the Return Flow. The Source Still Was Not an Identity
A new SPRING working-group draft proposes a neat repair for a stubborn SRv6 middlebox problem: put the service SID in the outer source address so the two directions form the pair a stateful firewall expects. The packet may then pass. What the address proves, however, has changed.…
CASE FILE
WTPF-26’s Space Opinion Keeps Technology Choice Open. Outcomes Need One Scorecard
A village reached by fibre and an island reached by satellite can both be marked “connected”. The label is useful only if it preserves what the connection actually delivers. WTPF-26’s new space-connectivity Opinion encourages technology-inclusive targets and local choice. That…
CASE FILE
HTTP 200 Is Not an EPP Registry Decision
Putting a registry protocol inside HTTPS creates two answers to one request: what happened to the web exchange, and what happened to the registry command. Governance fails when an operator stores only the easier answer.
CASE FILE
The Algorithm Name Matched. The Hash Receipt Did Not: RFC 9861
KangarooTwelve and TurboSHAKE give operators fast, extendable cryptographic output, but the label on a library call is only the beginning of the evidence. Reproduction depends on the exact function, byte stream, domain or customization input, output length and execution path that…
CASE FILE
Who Gets to Ask the User to Authenticate Again?
An API can reject a perfectly usable token because the user's authentication does not meet the needs of this particular request. RFC 9470 gives that refusal an interoperable language. It does not settle a more consequential question: who may turn a local risk decision into…
CASE FILE
A Public Sponsor for a Private Namespace
An enterprise can need outside confirmation of an internal DNS arrangement without wanting to publish its internal directory. RFC 9704 offers a way to separate those disclosures. The difficult decisions concern what remains visible, how much authority one approval covers, and who…
CASE FILE
A Working Group Can Say a Wider IETF Principle Does Not Apply. The Environment Assumption Must Expire
The architecture review ends with a narrow sentence: this principle does not apply because the protocol can only operate inside a controlled environment. Five years later, the protocol sits behind a gateway, ships in a product and crosses an administrative boundary. The sentence…
CASE FILE
A Private Address Can Be a Familiar Address
A Wi-Fi identifier can be randomly chosen and remain recognizable for years. RFC 9724 makes that distinction explicit. The managerial question is how much continuity a service needs, within which boundary, and who decides when it ends.
CASE FILE
The Voice Agent Made a Sound. That Was Not Yet an Answer.
A voice system can win a latency chart by emitting a breath, an earcon or a filled pause before its useful response is ready. A new individual Internet-Draft proposes a harder comparison: keep the first sound, but also measure when uninterrupted speech begins, where the packets…
CASE FILE
The Check Moved. The Requirement Did Not.
RFC 9682 allows a CDDL source file to contain no rules. The completed model still needs an entry point. Between those two statements lies a consequential question for anyone buying, assembling or approving modular systems.
CASE FILE
An Operational Considerations Section Cannot Accept the Risk It Names
The change board has read the new protocol’s operational section. It names scale limits, monitoring gaps and a migration hazard. Everyone agrees that the document is unusually candid. Then the chair asks who is authorised to accept those limits for the production network, and the…
CASE FILE
The Verification That Will Not Come Again
A JMAP subscription can be accepted just as its authentication assumptions expire. RFC 9749 puts recovery on the client—and a reported error in its optional warning path makes that hand-off worth examining closely.
CASE FILE
The Failure Event Was Signed. Its Second Arrival Was Still a Replay.
A vendor outage alert enters an agent session, passes signature verification and triggers a fallback. The receiver loses its acknowledgement, so the same alert arrives again. Every cryptographic check can still be green while the second delivery repeats a real-world response.…
CASE FILE
Cancel the Second Checklist
Closing a redundant register should end a redundant obligation. RFC 9751 offers a precise example of administrative subtraction—and a test for organisations whose paperwork can outlive the procedure it describes.
CASE FILE
Who Keeps the Original Mail?
A legacy inbox can show a readable substitute while losing the address, context or verification that made the original useful. RFC 9755 turns compatibility into a question of custody.
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