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.
CASE FILE
The Registry Redrew the Range. The Old Allocator Kept Issuing IDs: RFC 10028 and Authority over IPv6 Multicast Coexistence
RFC 10028 gives dynamic IPv6 multicast allocation methods separate numeric territory. That is necessary coordination, but it does not reach into an old appliance, rewrite its pool or show that the intended stream reached a listener. The operational question begins where the new…
History
The Link That Never Left the Message: How MIME Content-ID Named Embedded Parts
An HTML message could point to a picture using something that looked like a URL, yet no browser had to leave the message to fetch it. MIME made that possible by giving each body part a label, letting another part spell the label as `cid:`, and leaving the receiving application to…
History
One Call-ID, Several Dialogs: How SIP Tags Named a Fork
An invitation sent to one address could ring at several endpoints and return several answers. SIP's durable solution was not to give each answer a new call number, but to let each peer complete a two-sided name for the state that would outlive the invitation.
CASE FILE
The Session Grouped Four Streams. It Did Not Reconstruct the Scene: RFC 10034 and Authority over a V3C Representation
Volumetric video does not travel as one self-sufficient picture. It can arrive as an atlas plus occupancy, geometry and attribute streams, each with its own packets and failure state. RFC 10034 gives those parts a shared transport grammar. It does not appoint any one green…
History
The Connection Died. The Session Did Not: How RTSP Put State Beyond TCP
A media server could lose the socket that carried PLAY and still remember what the client had set up. RTSP made that possible by giving server state its own expiring identifier—then carefully refusing to treat the identifier as the resource, the media path or the user's…
CASE FILE
The Header Asked for a Stream. The Proxy Still Owned the Flush: RFC 10036 and the Authority to Release an HTTP Message
A sender can place `Incremental: ?1` at the front of an HTTP message and begin producing useful content immediately. That does not make the path a pipe. Every intermediary still controls a parser, a security decision, a capacity limit and a buffer. RFC 10036 turns the sender's…
History
The Flag That Made Ignorance a Validation Failure: How X.509 Critical Extensions Governed Change
A certificate could acquire a new signed rule long after old software had shipped. X.509 v3 made that growth possible with an extension identifier, a value and one Boolean. The Boolean did not announce importance. It decided whether a validator that could not understand the rule…
CASE FILE
The Server Issued a Locator. The Network Had Not Yet Accepted the Route: RFC 10038 and the Authority to Allocate SRv6 Reachability
A DHCPv6 Reply can make an SRv6 locator administratively real in a few fields: who received it, how it is divided and when it expires. The packet path is harder. A route still has to be installed, advertised, selected, programmed, filtered and joined to a local SID behavior. RFC…
History
One XID, Two Executions: Why RPC Needed Memory Beyond the Reply Number
A remote call can be repeated with exactly the same number and still perform its work twice. ONC RPC made replies attributable; the harder task was preserving enough server-side history to say whether a retry was new.
CASE FILE
The Token Matched. Permission Still Had to Be Checked: WebDAV Lock Tokens and Write Authority
A WebDAV client can present the exact token for a live lock and still be correctly refused. That is not a contradiction in the protocol. It is the point at which a coordination marker stops and authority begins.
Global Cloud Services Trends
Veeva's Salesforce CRM Has a 150% Per-Customer Cap and 2030 Exit
The legacy platform is neither open for ordinary growth nor scheduled to disappear tomorrow. Veeva's agreement with Salesforce has turned the old CRM into a bounded migration corridor: existing customers can still operate and expand within a fixed ceiling, while new customers and…
CASE FILE
The Cache Told You It Was a Hit: Cache-Status and the Authority to Explain a Response
Cache-Status gives every cache in an HTTP path a common way to describe its part in delivering a response. That makes incidents easier to investigate, but it also creates a tempting mistake: treating the system's own explanation as if it were independent proof.
CASE FILE
The Message Was Accepted Before It Was Released: IETF's Mail Transition and the Authority to Hold, Rewrite and Relay
On 11 September, a first-time sender may hand a message to the IETF's mail system and receive an apparently ordinary SMTP outcome while the operational copy waits elsewhere for a challenge response. That gap between acceptance and release is the real story in the IETF's new email…
History
The Bytes That Did Not Belong to the Value: How XDR Made Machines Agree
XDR made unlike computers meet on a four-byte grid. Its most revealing rule concerned the blank spaces: zero octets could be required on the wire while remaining outside the value, a small distinction on which deterministic decoding depended.
CASE FILE
The Network Changed Before the Decision Became Final: NETCONF Confirmed Commit and Rollback Authority
NETCONF can place a candidate configuration into active use while a timer still gives the server authority to restore the previous state. That provisional success is useful precisely because a protocol acknowledgement, a final datastore and a functioning network are different…
History
The Number That Belonged to the Operation, Not the Packet: How LDAP Message IDs Let Replies Interleave
LDAP put a client-chosen integer on every request and echoed it across every response belonging to that operation. That small envelope field made one search into a recognizable stream, allowed several streams to cross on one connection, and exposed why identifying work is not the…
History
The Cookie That Changed the Matching Law: Why SIP Branches Begin with z9hG4bK
Seven conspicuous characters in a SIP Via branch do not hide anything. They tell the receiver which generation of transaction evidence it is allowed to trust.
CASE FILE
The Token Was Bound to a Key. The Action Was Still Unauthorized: DPoP and the Authority of a Sender Constraint
DPoP can stop a copied OAuth token from becoming a portable credential. It cannot decide whether the key holder is the right client, whether the token still carries the right audience and scope, or whether today's resource state permits the requested effect.
CASE FILE
The Signature Verified. The Command Was Still Unauthorized: HTTP Message Signatures and the Authority of Covered Components
RFC 9421 can prove that selected parts of an HTTP message survived in a defined semantic form. It cannot decide whether the signer was entitled to issue the command, whether an omitted field changed its meaning, or whether a valid request has already been used.
CASE FILE
The Counter Hit Its Ceiling. The Filename Opened a New Epoch: RPKI Manifests and Recovery Authority
A correctly signed RPKI manifest can become unusable because a relying party remembers an impossible predecessor. RFC 9981 gives the issuer a narrow way out: change the manifest filename, start a new comparison epoch and preserve every other freshness, location and integrity…