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 Old Name Became a URN. It Still Did Not Resolve Itself: RFC 3151
XML inherited public identifiers that could outlive a machine but could not enter every URI-only interface. RFC 3151 gave those strings a precise `urn:publicid:` transcription. The bridge preserved a name's visible structure and made normalized outputs comparable. It did not…
IETF
The DHCP Reply Said 1 Gbit/s. The Bottleneck Had Not Moved.
A proposed DHCP option can tell a router which service rate an operator wants it to use. That is a valuable coordination signal. It is not a measurement of the access path, a receipt from the shaper, or proof that the queue carrying the next packet sits where the policy assumes.
History
The Call Agent Controlled the Features. The Mute Button Stayed Local: RFC 3149
MGCP placed call-control intelligence outside the phone, yet RFC 3149 refused to send every touch across the network. A numbered feature key could acquire its meaning from a remote Call Agent, and an XML display could become a separately addressed endpoint. But volume, the…
History
The New Management Network Had to Cross the Old One: RFC 3147
A network migration is usually drawn as an arrow from old to new. RFC 3147 captured the harder topology hidden beneath that arrow: a newly IP-managed device could stand on the far side of a CLNS network that operations could not yet remove. The proposed bridge—GRE carried inside…
IETF
The Link Was Listed as Sleeping. No One Had Proved It Could Wake.
An IS-IS database can retain a link that is unavailable for forwarding and describe the power that might be saved while it sleeps. That is useful control-plane memory. It is not evidence that two endpoints completed a physical transition, preserved a separate wake path, restored…
North America Cloud Services Trends
Thryv’s 76% SaaS share still turns on a 24-month print clock
Thryv’s software now supplies most reported revenue, but the 76% headline is a mix ratio—not a growth rate. SaaS dollars were nearly flat in Q2 2026 as legacy marketing revenue collapsed; print-directory delivery timing moves that denominator, while normalized directory economics…
IETF
The Envelope Was Signed. The Detached Ciphertext Was Outside the Signature.
The verifier returned green, the COSE entity was intact and the recipient decrypted a plausible message. None of those facts, alone, proves that the separately stored ciphertext was inside the outer signature. Detached content turns a neat security diagram into a custody problem…
IETF
The Calendar Called Them the Owner. It Had Not Granted Control.
A portable calendar record can call a entity an owner without making that person an authorized editor. The label describes a role; the exchange protocol still decides who may reschedule the event, change its entities, or send an update in its name.
IETF
The Redirect Succeeded. The Credential Had Already Crossed in Plaintext.
The final URL was HTTPS, the API returned useful data and every dashboard showed green. Yet the credential had already travelled in the first cleartext request. A redirect can repair where the client goes next; it cannot recall bytes the network has already seen.
IETF
The Chain Validated Against the Anchor It Carried. The Relying Party Had Not Trusted It.
The did:x509 resolver can finish every check it was asked to perform and still leave the decisive question untouched. A supplied certificate chain may be internally valid, its CA fingerprint exact and its leaf predicates true, while the relying party has not yet accepted the…
IETF
The Backup Lost Sight of the Primary. The Multicast Path Was Still Alive.
A BIER backup ingress can lose its monitoring path to the selected ingress while every protected receiver path still works. If that narrow observation is allowed to command a takeover, resilience creates the very duplicate traffic it was meant to contain.
History
Long-Term Proof Had to Outlive the Key: RFC 3126
RFC 3126 treated an old signature as an evidence-preservation problem. A valid calculation made in 2001 would not explain itself decades later if certificates, revocation records, exact signed bytes or trustworthy algorithms had disappeared. Its answer was a ladder of timestamps…
IETF
It Opened the Handshake. It Still Needed the Group's Memory.
An MLS external receiver can open the same commit or proposal seen by group members and still lack the state needed to authenticate who sent it. The missing receipt is not more ciphertext. It is the current GroupContext that joins an epoch, a sender leaf, a credential and an…
IETF
The Protocol Admitted the Number. The 32-Bit Field Did Not.
A LAKE extension value can be valid in the proposed registry range and perfectly formed on the wire, yet still fall outside the integer type chosen by an implementation. That is not a parsing footnote. It is the point where two peers can authenticate the same exchange while…
History
A Valid Signature Still Needed a Policy: RFC 3125
RFC 3125 tried to make the rules around an electronic signature addressable as data. A correct cryptographic calculation remained only the first gate: validity under a transaction still depended on which policy bytes were referenced, which commitments and trust conditions…
History
A Send Grant Was Not a Packet Queue: RFC 3124
The Congestion Manager proposed one place where a host could decide when competing applications should transmit. Its sharpest boundary was equally important: the manager granted an opportunity, while the application still chose the bytes and the network still determined their…
IETF
The Active Key Signed Its Successor. That Was the Problem.
A signature can show that the key accepted by yesterday’s policy approved a change. It cannot answer the harder question: should that key, acting alone, have been allowed to decide every key that will control the identifier tomorrow?
History
A Prefix List Was Not Yet an Access Policy: RFC 3123
DNS could publish a compact list of network prefixes. RFC 3123's more important choice was to refuse to say what that list commanded: the record preserved representation, while applications still had to supply meaning, authority and action.
History
A Delay Number Was Also a Clock Claim: RFC 3116
In an ATM laboratory, subtracting one timestamp from another looked like the easy part. RFC 3116 made the harder truth visible: before the switch could be judged, the clocks, counters, traffic and measurement boundary had to testify too.
IETF
Every Neighbor Authenticated the Node. They Still Received Different Maps.
Two receivers accept integrity-protected bundles from the same delay-tolerant networking node. One learns an IPv6 convergence-layer instance and a small neighbor set. The other learns a private credential, another transport and no overlapping topology. The disagreement is not…