Topic
Software Lifecycle and Lock-in
Within the Topic facet, Software Lifecycle and Lock-in topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
Leaders
John Ousterhout and the Fast Write That Became Cleaning Debt
The log-structured file system made a small write look almost effortless by turning it into part of a long sequential transfer. Its deeper lesson was not that the cost had vanished, but that systems must account for where the cost returns: in cleaning, spare capacity…
IETF
The Hash Looked Expensive. The Login Fleet Had Not Been Measured
RFC 9106 makes Argon2id's memory, passes and lanes explicit. That is the start of an engineering decision, not evidence that a verifier can carry its real login load or that a stolen hash will cost an attacker what the defender imagines.
IETF
The Link Colour Arrived. The Policy Decision Did Not: RFC 9104
A controller can receive a perfectly formed Extended Administrative Group through BGP-LS and still lack the evidence needed to say what the bits mean, which policy used them, which path won or what happened to traffic. RFC 9104 standardises carriage across that boundary—not the…
History
The Green Tunnel Light Is Not a Service Receipt: Reading RFC 2341 Precisely
An operations screen can show a tunnel as open while the user's application is still waiting. RFC 2341 makes that gap unusually easy to see. Its Layer Two Forwarding protocol coordinates a tunnel between an access provider's Network Access Server and a Home Gateway, then carries…
History
The Server Drew Three Mail Maps. It Did Not Prove a Mailbox Was There: RFC 2342
RFC 2342 let an IMAP server disclose the naming conventions for personal, other-users and shared mailboxes. A prefix and hierarchy delimiter could tell a client how to ask the next question. They could not answer whether a particular mailbox existed, appeared in a list, accepted…
History
The Packet Contained Picture and Sound. It Did Not Prove a Programme Played: RFC 2343
RFC 2343 put MPEG-2 video slices and audio frames into one RTP payload so that a stored programme could travel as one coordinated stream. The packet carried useful timing and boundary evidence. It still could not testify for the network, decoder, renderer, loudspeaker, screen or…
IETF
A Standard Can Open the Exit Without Decentralising the Market
An open interface can make departure technically possible. It cannot, by itself, create a viable destination, preserve the relationships that give a service value or compel an incumbent to cooperate. RFC 9518 supplies a disciplined way to separate a useful switching affordance…
History
The Error Terms That Made a Promise Calculable: RFC 2212
Guaranteed Service did not promise that a network would behave like a perfect wire. RFC 2212 did something more useful: it required every participating element to put a maximum price on its departure from that ideal, then showed how those prices could be added into a delay bound…
History
The Alias Reached the Child Zone. Nothing Else Was Proven: RFC 2317
A reverse query for one address can cross two administrative boundaries before it returns a name. RFC 2317 made that path possible for IPv4 blocks smaller than a /24, but the records along the path remain narrow receipts: they show how DNS reached a PTR answer, not who owns the…
CASE FILE
The Packet With No Payload That Can Move TCP State Backward
Presto’s pseudo-segment solves a hard pipeline problem by turning a backward state correction into another forward pass. That synthetic record can be authoritative inside the transport without being user traffic, a completed socket operation or proof that an application received…
History
When a Successful ESRO Result Still Ends in Failure
In ESRO, a performer could finish an operation, send a successful result, and later receive a failure indication even though the invoker had already accepted that result. RFC 2188 made room for both observations to be true. Its most durable lesson is not about a forgotten 1990s…
CASE FILE
WebAuthn’s Remote Client Can Validate the RP ID. The Local Permission Cannot Prove It Did
The first public draft of WebAuthn Level 4 proposes a careful handoff for remote-desktop sign-ins: a local browser may use client data supplied by a remote machine, but only after a per-origin grant. That grant opens the local capability. It does not preserve evidence of the…
History
The Backup Route’s Invoice
A second Internet provider promised resilience, but the extra route appeared only after the first path failed. RFC 2260’s enduring insight was that multihoming never removed the bill for reachability; it decided whether that bill would be paid in global routing state, provider…
Leaders
Cristiano Amon and the Missing Receipt in Qualcomm's Oryon Story
Qualcomm closed its Nuvia acquisition in March 2021, put Oryon inside Snapdragon X Elite in October 2023 and reached retail shelves with a multi-OEM PC wave in June 2024. A court ruling arrived later. Each event strengthens Cristiano Amon's strategic case, but none proves the…
History
RFC 2187’s Cache Hierarchy Was About Authority, Not Distance
The words *parent* and *sibling* make an Internet cache hierarchy sound like a family tree drawn across the network. RFC 2187 described something less geometric and more operational: a division of authority over what happens after a cache miss. Both kinds of neighbour might…
History
RFC 2277 Put UTF-8 and Language on the Review Form. Understanding Was Still Elsewhere
A protocol specification arrives for review with three reassuring statements: its text is UTF-8, its natural language can be tagged, and its internationalization choices have their own section. In 1998, RFC 2277 made those statements part of the IETF's standards discipline. They…
History
RFC 2186 drew a strict boundary between a fast cache hint and proof
In 1997, ICPv2 addressed a narrow operational problem: a Web cache sometimes had to choose among neighbours before a heavier exchange could justify its own delay. The protocol therefore compressed uncertainty into quick, bounded signals. Its historical interest lies as much in…
History
The KWIC Output Matched. The Change Cost Did Not
Run two programs against the same lines and both print the same alphabetized circular shifts. The acceptance test is green. Now change how a line is stored. In one design, the decision leaks through several work assignments; in the other, it remains behind one boundary. David L.…
IETF
The Registry Split. The Collector Still Has to Prove What It Read: RFC 9736
RFC 9736 removes an ambiguity from the BGP Monitoring Protocol by giving Peer Up information its own TLV registry. That is good protocol stewardship. It is not evidence that a production collector has understood, retained or acted on a Peer Up message correctly.
IETF
An ACME profile name can open an order. It cannot promise a certificate
The same profile name can be visible in a CA’s Directory today, accepted under a private arrangement while absent from that Directory, or rejected when an already-created order reaches finalization. That flexibility makes profile selection explicit; it also makes the surrounding…