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 Network Came Back Before Its Old Prefix Left
The home-control app found the lamp again. A fresh Router Advertisement had arrived, service discovery had repopulated the screen, and the replacement border router looked healthy. Yet the next command went to the lamp's previous address and disappeared. The network had returned…
History
The Transaction Was Atomic. The Remote Call Was Not Reversible: RFC 3018
RFC 3018 imagined a network in which software could read memory, allocate storage and transfer control across machines as if the distance had disappeared. Its transaction could release a bundle all at once. Once a remote call ran, however, the protocol offered no universal road…
IETF
The Tunnel Answered. The Traffic Still Had to Prove Itself.
An encrypted Echo can return on a healthy IPsec Security Association while the business flow beside it still fails. The useful question is therefore not whether the tunnel is “up”, but which directional SA carried which packet, which return SPI was requested, which one actually…
History
The Phone Book Had a New Version. The Traveler Still Had No Freshness Proof: RFC 3017
A roaming dialer could hold a well-formed XML book, see that its counter had increased and still act on the wrong operational state. RFC 3017 standardized the bundle that selected and configured access; it deliberately left delivery, authentication, commit and observed service to…
History
The Codec Survived. The Packetizer Chose What One Loss Could Destroy: RFC 3016
An MPEG-4 encoder could preserve every syntax rule and still hand the network a fragile unit. RFC 3016 made the overlooked decision visible: before redundancy, retransmission or decoding, someone had to decide which pieces would fail together.
IETF
SCHClet Draft Puts the Safety Boundary in the Configuration
A smaller network implementation can support less than the whole framework. Its security story turns on what happens when an input falls outside that declared subset, not on the reassuring sound of “compatible.”
IETF
The Registry Accepted the New Delegation. The Parent Still Had Two Answers
An EPP success response can close a registry transaction while leaving the DNS change open. Revision 03 of the proposed EPP mapping for DELEG records makes that distinction operationally urgent: one command can remove every DELEG record, even as traditional NS data continues to…
History
The New Tag Fit the Packet. It Still Could Weaken the Protocol: RFC 2440
A free value in a packet header looks like an invitation. In 1998, OpenPGP's specification made the harder point: parsing a new tag was not the same as proving that the feature it named could coexist safely with the rest of a cryptographic system.
IETF
The Recovery Was Ready. Its Receipt Was Still Only a Promise.
A reconstructed asset can be usable before the evidence intended to witness its recovery exists. A new individual IETF draft gives that interval a precise name—unwitnessed—and forces operators to decide whether availability or auditability controls the release gate.
History
The Context Was Connected. The Call Was Not Proven: RFC 3015
Megaco gave a decomposed media gateway a precise local model of who could hear or see whom. RFC 3015 also showed why a successful command, a visible Context and a returned statistic were not yet receipts for an end-to-end conversation.
North America Cloud Services Trends
BRC’s Sangoma deal promises a brand, not a product roadmap
BRC says Sangoma will join its communications portfolio while keeping its brand. That is an announced ownership plan, not yet a customer-continuity commitment: the deal has not closed, and the public materials do not specify what happens to product roadmaps, support or contracts.
IETF
The Rule Said It Could Be Modified. It Did Not Say Who Could Modify It
SCHC's new access-control draft draws a useful boundary around the parts of a compression rule that may change. Leadership still needs a separate, authenticated answer to the question of who may exercise that permission, on which Context, and under what transaction.
History
The Notification Was Lost. The Backup Log Could Lose It Too: RFC 3014
A trap could disappear on the wire, so RFC 3014 gave the device a second memory. Then it did something rarer: it specified how that memory could be filtered, shortened, overwritten, reset and contested—and how an operator might notice the resulting hole.
History
The Gate Issued a Challenge. Trust Still Had to Arrive: RFC 3012
In a visited network, the first useful question was not yet “Who are you?” It was narrower: “Are you answering something I just said, or replaying an old registration?” RFC 3012 made that distinction visible without pretending it had completed the work of trust.
IETF
The Decision Crossed the Boundary. Only One Request Could Carry It
The permit is authentic. The presenter is known. Yet the payment body differs by one cent from the action the policy engine approved. A new Internet-Draft makes that tiny change decisive: the remote recipient should refuse before the permit is consumed, because a signed decision…
IETF
IPv6 App Testing Draft Adds a Condition to the Shortcut
An application can pass a network test while one of its own messages still points a component toward the wrong endpoint. A revised IETF testing draft makes that distinction more difficult to overlook.
History
The Packet Came from One Subnet. The Address Was for Another: RFC 3011
DHCP once treated a packet’s arrival path as a practical clue to the address pool it needed. RFC 3011 made that clue overridable—and forced operators to decide who was allowed to point beyond the local pool.
IETF
The Engine Said `allow_unresolved`. Nothing Was Authorised Yet
A policy engine recognises a time window, lacks a trusted clock and returns a structured list of unfinished obligations. The integration layer sees the word “allow”, converts the enum to a successful Boolean and releases the action. No rule was broken inside the engine. The…
IETF
NFSv4 ACL Draft Moves a Number, but Capability Still Needs a Test
An IETF draft has shifted its proposed access-control attribute out of two neighbouring drafts' way. The interesting question is not which integer won; it is what an implementation can safely infer from a number and an error.
History
The Server Forgot the Lock. Recovery Began by Refusing New Ones: RFC 3010
NFS version 4 turned a crash into an argument over remembered rights. RFC 3010 answered with a bounded order: identify the returning client, let old state be reclaimed, and keep new conflicts outside until that opportunity had passed.