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.
IETF
The Composite Signature Passed. The Envelope Named a Different Algorithm.
Composite ML-DSA combines post-quantum and traditional signatures behind one interface. Its CMS profile shows why that single verdict still depends on several algorithm identifiers, exact encoded bytes and a content digest agreeing across the envelope.
IETF
The Capsule Recorded a Disagreement. It Had No Right to Block Anything.
A new SCITT profile proposes an immutable third-party comparison between what a subject declared and what an observer found. Its most important design choice is not the hash or the Merkle tree, but the refusal to let measurement quietly become authority.
History
The End-of-Frame Bit Could Be the Packet That Vanished: RFC 3189
The receiver wanted one clean fact: the picture was finished. RFC 3189 put that news in the marker bit of the last packet, then warned that the packet carrying the news might be the one the network lost. The convenient signal could shorten delay. It could not be the authority for…
IETF
The Final Filter Was Correct. The Update Still Leaked a Route.
Revision 03 of an IETF GROW draft turns BGP security from a static configuration question into a transaction question. A router may begin and end with the intended policy while briefly enforcing something else between commands.
IETF
The Tool Knew the SID. It Still Did Not Own the Actuator.
CORECONF-M2M proposes a compact route from YANG models and SID identifiers to MCP tools that an AI agent can call. The route can remove bespoke serialization without removing the harder boundary: who may act, what the device accepted and whether the physical world actually…
IETF
The Key Changed. The Instance Stayed the Same Because Someone Kept the Ledger.
OAuth attestation can prove that a client instance holds a current key. A new profile tries to preserve that instance's identity when the key changes. The continuity does not live in the identifier string: it lives in an attester's enrollment records, lifecycle rules and custody…
IETF
The Chain Proved a Clock Was Wrong. It Did Not Name the Culprit.
Roughtime can seal an inconsistency into portable evidence without pretending that cryptography has already decided whom to distrust.
IETF
The ICV Was Valid. The Path Record Could Still Be False.
IOAM can carry a cumulative integrity chain across the network and let a Validator confirm that protected fields were not modified. That is valuable evidence. It is not the same as proving that every expected record arrived, every participating node told the truth, or the…
IETF
No One Reported Progress. Why Did the Task Look Complete?
A task with entities but no progress reports should preserve the absence of evidence, not turn an empty column into a green completion state.
IETF
The Controller Reported Both Directions Done. The Network Had Not Proved Hitless
Fine-grain optical transport can change a low-rate service’s bandwidth without a planned interruption. Yet the green completion event at the multi-domain coordinator is only one controller’s conclusion. It is not a receipt for every direction, domain, protection path, tributary…
IETF
The ACME Order Named a Profile. The Certificate Still Had to Prove It.
ACME Profiles gives certificate authorities a cleaner way to expose policy choices and lets clients bind one choice to an Order. The new string is useful coordination, but leaders should resist turning it into a compliance badge: the issued certificate, its deployment and the…
IETF
The `at://` Address Works. Its Current Syntax Cannot Earn Permanent Registration.
A live identifier can resolve real records and still fail a different test: whether its syntax fits the common URI contract well enough to receive permanent registration.
IETF
You Paused the Viewer. The Relay May Still Be Fetching the Stream.
MOQT revision 22 gives “paused” a deliberately local meaning: stop sending Entities on this subscription. It does not promise that control state, upstream acquisition or relay caching has stopped.
IETF
The Child Token Was Valid. The Chain Still Had to Authorize It.
A delegated token can carry a perfect signature and still have no usable authority. The proposed OAuth chain works only when every parent, every narrowing step, the leaf key, current status and the resource server’s own policy agree on the same bounded operation.
History
The Server Did Not Need the Plaintext. It Still Controlled Availability: RFC 3157
In August 2001, RFC 3157 asked how one cryptographic identity could follow a user or router from one device to another. Its answer began with confidentiality but did not end there. A credential server might store an entity it could not use as plaintext and still decide whether…
IETF
The Manufacturer Signed the New Trust Roots. The Delivery Server Was Still Untrusted.
A factory-installed key can let a device accept a new operational CA bundle from an endpoint it cannot yet authenticate. That is not a paradox if every grant stays narrow: the signature authorizes the entity, the entity changes a local trust store, and only a fresh validated…
History
The Sender Saw Loss. It Could Not See the Cause: RFC 3155
In August 2001, RFC 3155 confronted a problem hidden inside one of TCP's most useful habits. A missing acknowledgement told the sender that progress had failed, but not why. A congested queue, a corrupted radio transmission, reordered packets and a damaged acknowledgement could…
History
The Receiver Offered Multiplexing. The Sender Still Chose Whether to Use It: RFC 3153
In August 2001, RFC 3153 offered a way to make small PPP packets spend fewer bytes on envelopes. Several packets could travel as subframes inside one multiplexed frame. Yet the standard drew an unusually useful line: a receiver could negotiate the ability to understand that…
History
The New Reverse Tree Existed Before the Old One Disappeared: RFC 3152
In August 2001, the Internet moved IPv6 reverse naming from `IP6.INT` toward `IP6.ARPA` without pretending that a sentence in an RFC could move every resolver at once. RFC 3152 chose the infrastructure root, requested its delegation and aligned the hierarchy with address…
IETF
The Mapping System Did Not Know the Destination. It Still Returned an Exit.
A new LISP proposal turns an unknown or unregistered destination into an actionable gateway choice. That can remove static configuration and speed failover. It can also make an authoritative-looking map conceal its most important fact: the system selected where to send the packet…