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
Adele Goldberg and the Contract That Let Smalltalk-80 Travel
The Blue Book turned a live system into a portable agreement: preserve the image, implement the entity memory, bytecodes, contexts and primitives, and let unlike machines run the same Smalltalk-80. The agreement made reimplementation possible; it never promised equal speed…
History
The Join Had No Receipt. The Tree Survived by Refresh: RFC 2117
RFC 2117 did not build a sparse multicast tree as one transaction. A local membership indication created one record; a Join/Prune refreshed records hop by hop; a source initially reached a rendezvous point inside Register messages; a branch could later move to source-specific…
IETF
RFC 9787 and the Moment a Draft Becomes a Message: Encryption, Commitment and Cross-Device Custody
A protected email draft is not merely an early copy of a sent message. RFC 9787 treats it as a different authority state: unfinished text may need confidentiality from the mailbox service while remaining unreadable to intended recipients and unendorsed by the user's ordinary…
History
The Browser Remembered the Session. It Did Not Prove the Person: RFC 2109
In RFC 2109’s model shop, a server called a browser-held value `Customer="WILE_E_COYOTE"`. Later requests returned that value while separate cookies accumulated for a rocket launcher and a shipping method. The exchange made stateless HTTP remember a sequence. It did not make the…
History
The MIB Located the Address. The Repeater Still Had No MAC
A management station could ask which hub port had carried a source address, rank the busiest ports and reconstruct a shared-Ethernet topology. RFC 2108 made those answers comparable without pretending that the repeater itself understood a packet.
History
Kathleen Booth and the Line Between a Symbol and a Machine Order
In 1947, Kathleen Britten and Andrew Booth described a way to move from a mathematical plan to the exact fields their calculator would obey. The abbreviated notation made that crossing legible. It did not make the machine understand what the calculation meant.
History
The Address Said Home. The Dial-Up Line Said Away: RFC 2107
RFC 2107 let a remote dial-in client borrow the routing appearance of home. The illusion depended on a Foreign Agent, a Home Agent, a shared secret, a Tunnel ID and state that had to be created and destroyed in the right order.
History
Karen Spärck Jones Made Rarity Count; IDF Did Not Make It True
The same word can be commonplace in one document collection and unusual in another. Karen Spärck Jones turned that difference into a useful retrieval signal. Her achievement was not to discover a universal measure of importance, but to show how a collection can disclose which…
History
The Router Gave the Workstation an Address. It Did Not Give It an Identity: RFC 2106
RFC 2106 solved a real scaling problem by placing many remote SNA and NetBIOS workstations behind one DRAP server. The bargain was precise: fewer backbone peers, more state and judgment concentrated at the boundary.
History
The Tag Moved the Packet. It Did Not Prove the Path: RFC 2105
A packet entered a switch carrying a short tag. The machine used that value as an exact index, selected an interface, replaced the tag and sent the packet onward. That was the elegant part of Cisco’s 1997 Tag Switching proposal. The harder truth sat elsewhere: routing protocols…
CASE FILE
W3C’s Browser Portability Group Starts With a Report, Not a Standard
An iPhone user can now move selected Safari data into another browser through a documented export-and-import path. That is a real product capability. The W3C Browser Data Portability Community Group, launched on 15 September, is something else: a place to discuss principles and…
IETF
When Fast Reroute Must Stop: RFC 9791 and the Responsibility Boundary Behind NFFRR
RFC 9791 gives a deceptively simple answer to a hard failure problem: once fast reroute has already redirected a packet, a downstream node may need to refuse another local repair. The difficult part is not the idea of a marker. It is the authority embedded in that marker—the…
CASE FILE
The Grammar Changed. Your Acceptance Boundary Might Not.
RFC 9682 repairs CDDL’s collected grammar and adds a cleaner hexadecimal escape form, but the important compatibility boundary is not the publication date of the RFC. It is the point at which a particular source model meets a particular parser, becomes a particular validator…
History
Two Hash Passes Made a Reusable MAC. The Tag Did Not Make a Trust Decision: RFC 2104
RFC 2104 gave protocol designers a compact way to turn existing iterative hash functions into a message authentication code: one keyed inner pass, one differently keyed outer pass, and an interface that could survive replacement of the hash beneath it. What endured was the…
History
The Locator Moved. Then the Network Moved: RFC 2103
Nimrod’s mobility paper began with an elegant separation: keep the endpoint’s identity stable and update the locator that says where it can be reached. Then it found the case that broke the elegance—a network could move while the endpoint’s locator stayed the same, leaving the…
History
The Tree Was Not Standardized. The Forwarding State Was: RFC 2102
Nimrod declined to choose one multicast tree algorithm. Its narrower bargain was more durable: different methods could coexist if routers agreed on the shape and meaning of the state that actually replicated packets.
History
The Cell Skipped the Router’s Work. It Did Not Inherit the Route: RFC 2098
At a Cell Switch Router, one tiny lookup decided whether an arriving ATM cell stayed a cell or became an IP datagram again. A matching VPI/VCI entry sent it straight through the switch; a miss returned it to reassembly and IP forwarding. RFC 2098 built a fast path from that…
History
The Link Was Open. Each Name Still Needed Admission: RFC 2097
PPP could bring a remote machine to the edge of a NetBIOS Frames network, but RFC 2097 did not treat link-up as reachability. Before NBF traffic flowed, NBFCP let the remote side ask a peer to project particular sixteen-octet names, return a result for every name, identify its…
IETF
The New Name Left of the Slash Was Registered. Nothing Else Was Proven
RFC 9694 turns a rare naming decision into an operating commitment. A new top-level media type can change how software groups unknown formats, chooses handlers and presents content to users. The registry entry is real, but it is only the first receipt in a much longer chain from…
History
The Fourth Letter Decided What the Editor Could Keep: RFC 2083
An editor can change every pixel in a PNG and still face a question that no preview answers: what should happen to a chunk it does not understand? RFC 2083 put part of that decision into the capitalization of four bytes. The last letter governed copying after edits, while the…