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
One Direction Lost the Dictionary. The Other Kept Moving: RFC 1962
A PPP link in 1996 could agree to compress traffic without pretending that its two directions were identical. RFC 1962 let each receiver say what it could decompress, let the reverse path make a different choice, and gave a damaged direction a reset exchange of its own. That…
CASE FILE
The Controller Received the State. It Still Needed a Clock: RFC 9857
RFC 9857 gives external controllers a structured view of Segment Routing candidate-path state. The harder operational question begins after receipt: whose observation was it, which generation did it describe, and what later evidence shows that the reported state still governed…
Creators
Cricket Liu: how DNS became managed infrastructure
Cricket Liu's career traces the path of the domain name system from a specialised service handled by a small group of operators to an enterprise control plane and, increasingly, a security sensor. His significance lies not in inventing protocols but in explaining how names…
History
No Memo Could Command the Network: RFC 1958 and the Right to Change
The most durable sentence in a document about architectural principles may be its warning that the principles will not endure. RFC 1958 treated the Internet less as a monument to be defended than as a city whose streets had to remain open while each block was rebuilt.
IETF
Fresh Entropy Entered the Session. Recovery Still Needed Proof in Both Directions
TLS 1.3's ordinary KeyUpdate advances a secret already known to the current chain. The active Internet-Draft for Extended Key Update proposes something stronger: rerun the negotiated key exchange inside a live session and mix fresh input into the next traffic secrets. That can…
History
The URL Carried a Query, Not Its Authority: RFC 1959
In 1996, a directory lookup could be folded into a string short enough to paste into a document or hand to a web client. That convenience was exact but narrow. RFC 1959 could name a server, a place in the directory, the attributes to request, a search scope and a filter. It could…
CASE FILE
The Parameter Set Verified. The Signing State Did Not: RFC 9858
RFC 9858 gives HSS/LMS implementers more hash and security-strength choices. It does not make the stateful part of a stateful signature disappear. The operational question is therefore not only whether a verifier can parse the new typecodes, but whether the signer can prove that…
Creators
Cricket Liu and the long work of making DNS operable
Cricket Liu’s career follows the Domain Name System from a specialist service run by a small group of operators to an enterprise control plane and, increasingly, a security sensor. His importance lies less in inventing protocols than in explaining how names, addresses, leases and…
History
The Space the Standard Never Required: How POP3 Software Made Compatibility Law
A single blank character can look too small to deserve a history. RFC 1957 showed why it did: once a common server emitted that character on every response, clients learned to depend on it, and a conforming shorter reply became the dangerous case.
CASE FILE
The Repair Path Was Ready. The Multicast Service Was Not Yet Proven: RFC 9860
RFC 9860 gives multicast operators a more capable way to build a standby tree from a TI-LFA repair list. It also draws a useful boundary: a route calculation can accelerate local recovery, but the service verdict still belongs to evidence collected after the calculation.
History
The Proposal Added a Header. It Refused to Rewrite the Address: RFC 1955
RFC 1955 described a way to make the Internet's routing problem look smaller without pretending that its addressing problem had disappeared. At an entrance border, the proposal would place the original IPv4 datagram inside a second IP header addressed to an autonomous domain. At…
History
The Cell Carried a Label. It Did Not Carry a Verdict: RFC 1954
In Ipsilon's 1996 ATM design, a flow label did not decorate an IPv4 packet. It changed the virtual channel and, for two flow types, changed which IPv4 fields crossed the link at all. That economy made forwarding state executable—and made the limits of the resulting evidence…
History
The Switch Offered a Shortcut. The Router Could Refuse: RFC 1953
In RFC 1953, the faster path began as a neighbor's request, not a command. A downstream node chose a label from its own local space and asked the upstream node to attach it to a defined IP flow. The upstream node could ignore the request. Even acceptance lasted only for a stated…
North America Institutional Trends
Chime’s $590 Million Bank Deal Has an 18-Month Contract Fallback
Chime wants to replace a sponsor-bank relationship with ownership. Yet its merger agreement also prices the possibility that regulators prevent that change: under a narrow failure pathway, three agreements with Stride Bank do not expire on schedule but roll forward for at least…
History
The File Ended, Then Continued: RFC 1952 and Gzip's Member Boundary
A `.gz` filename suggests one entity. RFC 1952 describes something more interesting: a procession of self-closing members. Finish one, place another immediately after it, and a decompressor can continue as though the file had acquired a new chapter. The old compressed bytes need…
History
The Key Centre Disappeared into the Tree. Its Authority Did Not: RFC 1949
Scaling usually sounds like subtraction: remove the bottleneck, spread the work, let the network carry the rest. RFC 1949 did spread multicast key distribution, but it could not subtract trust. By letting authenticated tree nodes pass group secrets and authorise later joins, the…
Story
RIPE Atlas's Upgrade Reminder Still Needs a Maintenance Route
The planned notices put old software versions in front of probe hosts. They do not make every host's installation path the same.
IETF
OpenPGP’s New Algorithm Numbers Rewrite the Test Vectors
Eight numbers are moving through OpenPGP’s standards machinery. In the published draft they are experimental values 100 through 107; in an open editing branch they are 37 through 44; in the public IANA registry those lower slots remain unassigned. The discrepancy is not cosmetic.…
History
The Password Was Correct Once. Acceptance Changed What Correct Meant: RFC 1938
Passwords usually sound like facts: either the claimant knows the right string or does not. RFC 1938 made that description incomplete. In its one-time-password system, a correct answer was consumed by success. The server replaced the value against which the next answer would be…
History
The Server Pool Was Redundant. The Address Authority Was Singular: RFC 1931
A workstation with no configured address asks a question that looks deceptively small: which IP address may I use? RFC 1931 answered with several servers, but not several truths. Dynamic RARP separated the machines that could hear and answer a request from the authority allowed…