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.
History
The Address That Grew Old Before It Died
A control room can stop assigning new work to a console without pulling power from the job already running there. IPv6 gave an autoconfigured address the same kind of staged retirement. One clock ended its claim on future communication; another ended the address itself. The gap…
History
The Acknowledgment That Arrived Before the Answer
The phone can still be ringing when a network announcement begins. To a listener, the moments run together. To SIP, they are separate claims: a provisional message was received, media parameters may have been negotiated, early audio may be flowing, and the invitation still has no…
Global Cloud Services Trends
Rubrik's 39% Cloud ARR Growth Includes Customers It Already Had
Rubrik ended fiscal Q2 with US$1.48 billion of Cloud ARR, 39% more than a year earlier. That is a meaningful measure of hosted subscription scale. It is not a clean count of newly won demand: the company's definition also admits customers migrating from products and commercial…
History
The Message That Chose Failure Over Cleartext
Two messages could wait in the same relay queue for the same domain and deserve different outcomes. One might travel without TLS when security negotiation failed. The other carried `REQUIRETLS`, turning non-delivery from an accident into the only permitted result.
IETF
Ten Segments Before the Network Answers: TCP's Initial Window Bet
A new TCP sender once waited for the path to reveal itself three or four segments at a time. RFC 6928 permitted a first flight of ten. That shortened many small transfers, but it also concentrated more traffic in the only moment when the sender had almost no evidence about the…
History
The Exit That Was Also a Delete: Why IMAP Needed UNSELECT
A mail client wanted to release one open mailbox. The most obvious command would also erase every message already marked for deletion. IMAP's later `UNSELECT` extension separated an ordinary state transition from an irreversible act.
History
The Date That Could Not Reserve Disk: How Expires Let Usenet Separate Relevance from Retention
An article can carry a precise date and still make no promise about how long it will remain available. Usenet's `Expires` field let a poster say when a notice would stop being useful. The disks, deletion rules and archive exceptions remained under each serving site's control. The…
History
The Session Ticket Could Not Remember the Protocol
A resumed TLS connection could reuse evidence from an earlier cryptographic session, but it could not inherit the grammar spoken over the old wire. ALPN made application-protocol choice a fresh, bounded decision: the client named what it could accept, the server chose one common…
History
The Timeout That Could Speak Only After Fragment Zero
The receiver had pieces of the datagram, an identity for the unfinished whole and a timer measuring how long its memory would remain committed. What it did not have was the beginning. When the timer expired, IPv4 required the state to disappear; whether the failure could speak…
History
The Filename the Sender Was Not Allowed to Choose
FTP’s `STOU` command made a remote server allocate a collision-free pathname and report it before transfer, turning one line of reply text into a narrow receipt for a naming decision—not proof that the upload finished, remained stored, or belonged to anyone.
IETF
The Proposed RFC SLA Can Pass While Authors Still Wait
An RFC publication service can meet every target assigned to the time it controls and still deliver a slow end-to-end result. That is the central governance problem inside the IETF Administration LLC’s proposed replacement service-level agreement for RFC editing and publication.…
History
Repairing the Instrument Did Not Replay the Performance
RTP MIDI gave a receiver enough history to correct a note that would not end, without promising to replay every note that had gone missing. Its recovery journal drew a useful boundary for the real-time Internet: the state of a performance could be repaired, but the time in which…
History
The Offset That Could Not Name the File: How FTP Restart Assumed an Unchanged Object
After a large transfer breaks, a saved number feels like proof of progress. FTP could use that number to avoid sending the beginning again. But the number named a position, not the file version occupying that position. Resume worked only because both endpoints supplied an…
IETF
The IAB Wants Age Rules to Name Outcomes, Not Freeze a Gatekeeper
Moving an age check from a website or a network into a personal device does not make governance disappear. It changes who holds the lever. In a statement published on 24 August 2026, the Internet Architecture Board argued that device-based age signals look more promising than…
History
A Return Label Was Not a Shared Instruction
A RADIUS proxy could carry another proxy's private state without knowing what it meant. The common agreement concerned preservation, relative order and return, not a universal interpretation of every value. That small distinction left room for independent implementations while…
North America Cloud Services Trends
CrowdStrike’s Five-Year Commission Clock Lowered Q2 Expense by US$25.5m
CrowdStrike’s fiscal second quarter delivered real growth, stronger cash flow and a smaller operating loss. It also benefited from a longer accounting clock for sales commissions. That estimate is neither scandal nor footnote trivia: it is a measurable claim about how long a…
History
A Reservation Could Survive Without Being Rechecked
RSVP learned to keep previously advertised state alive by naming it instead of repeating its description. That reduced routine work, but changed what the routine could discover. A missing record could ask for repair; a recognisable record with the wrong contents was a different…
North America Cloud Services Trends
Nutanix’s US$1.51bn Profit Carries a US$1.18bn Tax Benefit
Nutanix finished fiscal 2026 with genuine operating progress and genuine cash generation. It also reported a profit number dominated by a tax-accounting event. Reading all three facts at once is more useful than choosing either the celebratory headline or the cynical dismissal.
History
The Reply SMTP Could Not Divide: How LMTP Made Local Delivery Per-Recipient
One message reaches the local-delivery boundary with two accepted recipients. One mailbox can take it; the other is temporarily over quota. SMTP has one final answer for that transaction, so the receiver must own what happens next. LMTP changed the shape of the answer: one…
History
The Knock That Brought the Client Back
A DHCP server could know that a setting should change while its client had no reason to ask again. FORCERENEW gave the server an opening in that quiet interval. It did not give the opening message the power to complete the change.