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.
CASE FILE
The Receiver Lowered the Window. The Sender Never Changed Its Algorithm
A small advertised TCP window is often read as proof that the receiving application cannot keep up. RFC 9840 makes that shortcut unsafe. It gives the receiver a second reason to limit the window—deliberate low-priority transport—while leaving the sender’s congestion-control…
History
The Number IPv4 Could Not Freeze: How the Protocol Field Became a Live Registry
IPv4 devoted one octet to a deceptively simple question: what protocol should receive the payload next? The answer could not live in the packet format alone. It required a shared assignment system that could change while the eight bits on the wire stayed fixed.
Leaders
Cristiano Amon and Qualcomm's Two-Engine Bargain
Cristiano Amon's defining leadership test before becoming CEO was not simply to accelerate Qualcomm's chip roadmap. It was to keep product execution credible while a legally distinct licensing business faced customer conflict, litigation and regulatory pressure.
History
The Header Shrunk to One Octet. The Missing Bytes Moved into Shared State: RFC 1553
A packet crosses a slow link with a one-octet compression header. Its ordinary thirty-octet IPX header is absent. Nothing has been lost—if the receiver still holds exactly the right prior header in exactly the right slot. Let one earlier packet vanish, however, and the same…
History
Why IPv4 Checksums Only Its Header
A packet can carry an undamaged payload and still be dangerous to forward if a bit error changes its destination, length or remaining lifetime. IPv4 therefore checks the control surface routers must trust: its header, and only its header.
CASE FILE
The Reference Was Well-Formed. It Was Not Yet Evidence
A digest can look precise enough to end an argument. Revision 03 of the Canonical Payload Binding draft instead turns that apparent certainty into a sequence of accountable tests: the reference must be admissible, one authorized digest context must be selected, the artifact must…
CASE FILE
The Maximum Metric Kept the Link. Missing Data Could Keep It or Remove It
A routing value can look catastrophic without withdrawing a link, while an empty field can either remove that link or leave it eligible. RFC 9843 makes those outcomes deliberate. Operations fail when telemetry turns three different protocol states into one red icon.
CASE FILE
A RISC-V Profile Is a Compatibility Vocabulary, Not a Hardware Mandate
A RISC-V profile makes a useful promise of language, not a universal promise of hardware. It tells hardware and software communities which bounded instruction-set surface they can discuss together. It does not, by itself, tell a buyer what is on a particular chip, tell a…
Leaders
Vint Cerf and the Deadline Behind the TCP/IP Cutover
The decisive test was not whether TCP/IP worked in a document. In Vint Cerf's recollection, rehearsed NCP shutdowns in 1982 exposed mail disruption and showed how much operational work remained before the ARPANET could change protocols. The transition became credible through…
IETF
The Namespace Stayed Put: RFC 9911 Makes Common YANG Types a Migration Surface
A server can import the same `ietf-yang-types` namespace yet validate a timestamp differently when the common module revision changes. RFC 9911 keeps the familiar module identity while revising accepted values, canonical forms, and descriptions—turning a shared typedef library…
History
When IPv4 TTL Stopped Being a Clock
IPv4 gives every datagram a field called Time to Live, measured in seconds. Yet the forwarding rule subtracts at least one even when less than a second has passed. That mismatch turned a nominal lifetime timer into the Internet's practical hop budget.
History
The Formatting Could Disappear. The Message Still Had to Be Readable: RFC 1523
A reader that understood no boldface, centring or indentation could still recover the prose. RFC 1523 made that outcome a property of the format itself: presentation commands were disposable, while their limits, nesting and whitespace rules made the remaining text predictable…
History
Why IPv4 Options Carry a Copy Bit
Two fragments of the same IPv4 datagram can legitimately carry different option sets. That is not an accident of implementation. A single bit inside every option type tells a fragmenter whether the option must follow all fragments or remain only with the first.
History
The Link Was Open. Configuration Still Belonged to a Second Negotiator: RFC 1552
In one 1993 PPP design, reaching `Opened` could mean the network protocol was ready. In another, the very same state was only permission for a second negotiator to begin. RFC 1552 made that difference explicit—and showed why a state name is never a complete receipt.
IETF
The Review Is the Interface: RFC 9907 Turns YANG Documents into Operational Controls
A YANG module may parse cleanly yet still create incompatible operations when its specification leaves lifecycle, datastore, or registry authority ambiguous. RFC 9907 makes authoring and review discipline part of the control surface for management specifications.
CASE FILE
The Cipher Was Approved. Its Key Budget Still Had to Be Counted
An AEAD name in a configuration proves which construction was selected, not how much cryptographic authority remains under the live keys. Revision 13 of CFRG’s usage-limits draft makes the missing control plane visible: applications choose the risk target, deployments count the…
CASE FILE
The Interface Name Was Required Locally. It Had to Vanish Before Transmission
An IPv6 link-local address can be perfectly valid and still fail to identify a usable path. RFC 9844 supplies the missing local selector—a zone identifier—while imposing an equally important limit: the label has meaning only inside one node and must not become identity on the…
History
Why IPv4 Fragment Offsets Count in Eights
An IPv4 Fragment Offset is not a byte number. Its 13 bits count blocks of eight octets, turning a compact header field into a coordinate that can span the protocol's full datagram size. That economy comes with a precise cost: every fragment that is not last must end on an…
IETF
Every Cell Says Stop: RFC 9906 Completes ECC-GOST’s DNSSEC Retirement
Every affected ECC-GOST registry cell now says **MUST NOT**: RFC 9906 closes both the production and validation lanes, unlike RFC 9905’s SHA-1 compatibility transition. The result is not merely a recommendation to stop signing; it is a coordinated retirement covering signing…
CASE FILE
Unicode 18’s Beta Is a Review Surface, Not a Release Commitment
Unicode’s public Version 18 page says its beta review has closed and lists 16 September 2026 for a final release. That is a useful planning signal. It is not yet evidence that Unicode 18 has been released, that a particular file is final, or that any implementation has adopted…