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
Abdiel Marin and the Workflow Architecture Behind Specialty Eye Care Software
Abdiel Marin built EyeMD EMR around a practical premise: ophthalmology software has to follow the clinic's real work, not force clinicians into a generic record system. His operating decisions connected specialty imaging, interoperability standards, edge computing and patient…
History
The Version Number Survived. The Security Framework Did Not: RFC 1441
In one of SNMP's durable historical jokes, the integer `1` in a message wrapper can mean community-based SNMP version 2. The arithmetic is harmless. The assumption it invites is not. A version field tells a receiver how to process a message; it does not, by itself, reveal which…
History
The Alarm Survived. Its Route to the Other Manager Had Expired: RFC 1451
The monitoring station was still sampling. The threshold still meant what its operator had configured. The event definition was still present. Yet the row that told the station how to notify another manager could count itself down to destruction. RFC 1451 made operational…
History
The Username Looked Like a Person. The Namespace Only Promised a Slot: RFC 1439
In 1993, a tidy rule for turning names into email accounts met a problem that no directory card could hide: two people could produce the same string, and a successful delivery could still reach the wrong human. RFC 1439 treated the collision not as clerical untidiness but as a…
CASE FILE
The Secure Channel Failed. The Client Was Not Allowed to Fall Back: RFC 9887
RFC 9887 turns a secure-transport upgrade into a rule about authority: when the protected TACACS+ path fails, reachability of the older path does not authorize the client to use it.
History
The File Arrived. The Recipient Had Not Accepted It: RFC 1440
In 1993, an experimental Internet protocol tried to deliver a file the way a network might deliver a parcel: the sender pushed it without logging into the destination, the receiving host put it aside, and the named recipient decided what to do later. That convenience depended on…
Global Institutional
Batfish and the promise of checking a network before change
Batfish turns multi-vendor configurations into a common routing and forwarding model so operators can test reachability, policy and selected failures before production changes. Its value still depends on snapshot completeness, parser coverage, explicit intent and post-deployment…
History
The WAN Session Was Up. The End Stations Still Had Two Links: RFC 1434
In an early-1990s network, a terminal could believe it was talking to a distant peer while every acknowledgement it saw came from a router in the same room. RFC 1434 made that split deliberate: keep fragile local link timing local, build another circuit between switches, and…
Global Cloud Services Trends
Netskope’s Annual Billing Shift Moves the Cash Test to the Second Half
Revenue guidance has risen, but the cash-flow target has narrowed. A change in payment terms helps explain why subscription growth and the money available to fund it can move on different schedules.
Global Institutional
Batfish and the promise of testing a network before it changes
Batfish turns multi-vendor configurations into a model of routing and forwarding so operators can ask whether reachability, policy and failure behaviour survive a proposed change before touching production. Its answers can be exhaustive inside the model, but their operational…
History
The Route Named a Next Hop. The Link Still Had to Agree: RFC 1433
Two machines could occupy the same data-network service and still be unable to exchange a frame. RFC 1433 began from that uncomfortable fact: routing could identify a shorter next hop, while address resolution and link filters retained the power to make the route usable—or turn…
IETF
CATS OAM Can Verify a Steering Policy. It Cannot Choose a Remedy.
The active CATS OAM draft is trying to close a real visibility gap. A service instance can remain reachable at the network layer while the application behind it is slow, exhausted or unavailable. A system that steers traffic only by network reachability may therefore send clients…
CASE FILE
The Capability Was Advertised. The Protocol Was Not Authorized: RFC 9885
A zero-length IS-IS capability can be visible on every change-board screen and still be limited public evidence to authorize one configuration command. RFC 9885 makes that limit explicit: the advertisement is management information, not a protocol trigger, while safe MP-TLV…
History
The Interim Fix Bought Time. It Could Spend the Future: RFC 1380
The Internet of 1992 had more than one deadline. Router tables and Class B allocations were under immediate pressure; a larger address space and a richer Internet layer demanded slower architectural work. RFC 1380 refused to hide that mismatch inside one programme. It recommended…
History
The Network Found the Book. It Could Not Keep the Shelf Current: RFC 1432
In March 1993, a bibliography about the Internet carried an unusually revealing provenance: much of its detail had arrived through the Internet itself. The network could help a reader discover a book, yet RFC 1432 also preserved the reasons discovery could never certify the…
CASE FILE
The Path Label Reached the Egress. The Transit Route Stayed Unseen: RFC 9884
One green LSP Ping result can answer a narrow and valuable question: the egress processed a Path Segment Identifier in the control-plane context named by the probe. It cannot reveal the transit route that delivered it. RFC 9884 makes that boundary operationally useful—provided…
IETF
IETF Separates Training Scripts From Slides. Now Test the Handover.
The IETF's latest training-procurement answers make captions, transcripts and narration scripts separate source assets. That is a useful move toward maintainable course material. Its value will become visible when someone other than the original producer has to correct a module.
History
The Transport Opened a Connection. SNMP Still Owned the Retry: RFC 1283
A connection is an enticing piece of evidence. It has a beginning, a lifetime and an end. In 1991, RFC 1283 placed SNMP on an OSI connection-oriented transport and then warned implementers not to read too much into that new structure. The connection could carry one or more…
CASE FILE
The Request Was Signed. The Other Private Key Was Still Only Asserted: RFC 9883
A certificate request can carry a valid signature and still offer no technical proof that the requester holds the private key named by its new public key. RFC 9883 does this deliberately. It turns the gap into an explicit policy choice—and a revocation dependency that operators…
History
The Client Found the Person. The Score Still Belonged to One Directory: RFC 1431
A successful search can be the beginning of an evaluation rather than its conclusion. In February 1993, RFC 1431 asked what an X.500 directory client had actually accomplished when a person's entry appeared—and what the answer had cost inside one particular directory.