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 Same Service Held Two Neighbors. A Router Still Stood Between Them: RFC 1209
Sharing a carrier service can make two machines look like immediate neighbors. RFC 1209, published in 1991 for IP over SMDS, made a deliberately narrower promise. A logical IP subnetwork was an administratively closed group on that shared service. Hosts could communicate directly…
CASE FILE
The Alarm Changed State. The Cause Still Had to Be Found: RFC 9940 and the Evidence Boundary
An alert can be prompt, honest and operationally useful without being a verdict. RFC 9940 gives network teams a vocabulary for that restraint: a measurement, an event, a fault, a problem, a suspected cause and a decision are related, but they are not interchangeable.
History
The NIC Looked Continuous. Its Registry Writes Had Paused: RFC 1261
In a service migration, the most reassuring things are often the things that travel cleanly: a familiar hostname, a working mailbox, a Help Desk number, a screen that resembles yesterday’s screen. RFC 1261 made a more sober distinction when the Network Information Center changed…
CASE FILE
The DNS ID Was Zero. The Cache Still Needed a Clock: RFC 9953 and DoC Evidence
A cache can make a constrained network quieter without becoming the authority that decided what the answer means. RFC 9953 makes that line unusually precise: it lets equivalent DNS-over-CoAP requests share a representation, then requires a separate clock before anyone may rely on…
CASE FILE
The Receipt Put a Statement on the Ledger. It Did Not Decide to Trust It: RFC 9943 and SCITT
A software-supply-chain record can look like a conclusion when its machinery is working well. A statement is signed. A transparency service accepts it. A receipt carries a verifiable proof. An auditor can replay a sequence and a dashboard can show a reassuring green line. The…
CASE FILE
W3C's 2026 XML Namespace Points to a Moving Draft Without a Change Policy
W3C dated a new XML Security namespace on 19 August 2026. The first archived Internet-Draft revision to use it appeared two days later, replacing a placeholder while the document was still adding material. Early allocation is useful; the unresolved governance question is what…
CASE FILE
The Token Named the Chip. It Did Not Decide the Door: RFC 9783 and PSA Attestation Authority
A signed attestation token can arrive at a policy boundary looking more decisive than it is. Its nonce matches the challenge. Its client identifier is familiar. It describes an instance, an implementation, a lifecycle state and the software components in the measured PSA scope. A…
History
The Queue Accepted a Job. It Had Not Printed a Page: RFC 1179’s Two Acknowledgements
In a networked print system, the easiest status word is usually the least useful one: accepted. A client has opened a connection, named a queue, sent files and received zero-valued acknowledgements. That is real evidence. But it is evidence of a bounded exchange with a line…
History
HEMS Left the Protocol Race. Its Data Model Stayed in the Room: RFC 1076
In 1988 the Internet chose a short-term management protocol, and one rival stepped aside to make agreement possible. Seven months later, that rival published a remarkably rich query language anyway. RFC 1076 is the record of what selection can retire, what it can preserve, and…
History
The Ring Could Share a Filter. It Could Not Prove a Group: RFC 1469’s Multicast Boundary
In the early 1990s, IP multicast met a local medium with an awkwardly small vocabulary. A Token-Ring adapter could be told which hardware destinations to accept, but its scarce functional addresses could not give each IP group a private physical label. RFC 1469 solved the…
CASE FILE
The Contact Lost Its UID. It Did Not Lose Its Boundaries: RFC 9982 and Record Identity Authority
A contact card without a globally convenient identifier can make a synchronization team uncomfortable. The usual reflex is to manufacture one: a string is easy to add, relational tables prefer stable keys, and downstream software wants a value to point at. RFC 9982 takes a more…
CASE FILE
The Forum Could Suspend a Post. It Could Not Claim the Network: RFC 9945 and the Boundary of IETF Moderation
A forum needs a way to stop disruption without mistaking that housekeeping power for a title over everything discussed there. RFC 9945 makes that distinction unusually visible: it gives the IETF a shared procedure for its public online spaces, while repeatedly locating the…
IETF
Carlos Pignataro and the Watt Reading That Did Not Prove a Greener Network
A power meter can report a precise number while leaving the environmental claim undecided. Turning that number into energy, emissions or permission to switch off spare capacity requires separate evidence—and a record of who accepted the trade.
History
The Domain Drew a Technical Boundary. It Did Not Draw Ownership: RFC 1136’s AD/RD Model
In 1989, as the Internet outgrew a single privileged core, RFC 1136 offered a vocabulary for a problem that diagrams often conceal. A network could be one thing for routing procedure and another for administration. The distinction did not decide who owned a network, prove a path…
CASE FILE
The Multicast Request Reached the Group. It Did Not Authorize the Action: RFC 10020 and CoAP Evidence
One protected request can look wonderfully decisive. A controller addresses a CoAP group, the network fans it out, several endpoints answer, and the panel records a quiet burst of acknowledgements. In a constrained environment, that economy matters. It is also exactly where an…
CASE FILE
The Group Key Reached the Devices. It Did Not Assign the Act: RFC 10020 and CoAP Group Authority
A protected message can leave one sender and be intelligible to a group. It cannot make five receivers one decision-maker. RFC 10020 matters because it gives constrained systems a disciplined way to speak to a group without erasing the separate evidence required for membership…
CASE FILE
The Model Named an Endpoint. It Did Not Start a Service: RFC 10009 and HTTP Configuration Authority
An HTTP endpoint can look settled long before it exists in practice. A URI is present in a management tree; permitted versions are listed; TLS parameters and a proxy are named; a server has a name and an apparent stack. Those are useful, reviewable decisions. RFC 10009 makes…
History
The Name Was Local. The Number Still Needed a Record: RFC 1101’s DNS Mapping Boundary
In 1989, DNS could already distribute host information, but it did not yet offer a standard way to ask what a network number was called. RFC 1101 proposed a small answer: use PTR records, host-zero names and masks in `IN-ADDR.ARPA`. Its lasting discipline is equally small. A…
CASE FILE
What the Aggregate Report Actually Knows: RFC 9990 and the Boundary Before Enforcement
A DMARC dashboard can make a narrow observation look like a verdict. One receiver reports a large count from a source range, records an evaluated policy and shows a disposition. That is valuable operational evidence. It is not a global traffic census, proof of a sender's intent…
CASE FILE
The Preference Was Published. It Was Not an AI Control: RFC 9969
RFC 9969 records an Internet governance problem without pretending to solve it by publication. A preference attached to content can tell another actor what an owner wants considered. It does not identify that actor, bind a downstream model, prove a use was compliant, create an…