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 Router Repaired the Path. It Did Not Restore the Service: RFC 9855 and TI-LFA’s Local Boundary
A router can react to a directly attached failure in milliseconds and still know nothing about whether a customer service has recovered. RFC 9855 gives Segment Routing deployments a disciplined way to precompute and activate a loop-free repair path at the Point of Local Repair.…
CASE FILE
The Collector Received a Delay. It Did Not Receive a Verdict: RFC 9951
At 09:17, a collector receives a Flow Record with a mean delay, a maximum delay and an identifier for the transit point that exported them. By 09:20, someone wants the record to settle three larger questions: whether a customer suffered, whether a path changed, and which team…
CASE FILE
The Resource Named Its Authorization Server. It Did Not Grant a Right: RFC 9728’s Discovery Boundary
A resource can accurately publish where a client should look next and still have made no decision to let that client do anything. RFC 9728 gives protected resources a disciplined way to publish OAuth metadata. Its value is coordination: it narrows a discovery problem. It is not…
CASE FILE
The Authorization Conversation Was Still Pending. It Was Not an API Right: GNAP’s Continuation Boundary
A client can be entitled to continue an authorization conversation without being entitled to call the API it asked about. RFC 9635 makes the distinction unusually explicit: a continuation credential advances one grant request at the authorization server; a resource right appears…
IETF
Adrian Farrel and the Implementation Receipt That Disappeared Before Publication
One of the most useful sections in an Internet-Draft is written with an expiry condition. It can name the code, version, coverage, licence, test contact and interoperability evidence that made a proposal real. Then, if the proposal becomes an RFC, the section is supposed to…
CASE FILE
After a Reboot, “Secure” Must Not Mean “Resume”: RFC 10021 and Group OSCORE Recovery
A controller can regain a safe cryptographic footing after a power loss without regaining permission to continue the process it interrupted. RFC 10021 makes that distinction operational: restore the security context first; decide separately whether anything should resume.
Story
RIPE Rebuilt LatencyMON. A Chart Still Needs Its Own Interpretation Receipt.
RIPE NCC has rebuilt LatencyMON, the RIPE Atlas view used to compare latency trends across probes. The update makes a great deal more of the measurement surface visible: more test types, a choice of grouping logic, an option to reach beyond the aggregated time range and a…
CASE FILE
The Benchmark Found a Limit. It Did Not Grant a Capacity Claim: RFC 9971
A network benchmark often arrives in a meeting as a single number. That number then begins doing work it was never designed to do. It is used to imply that a cloud function has production headroom, that a supplier has met an obligation, that a release is safe, or that a customer…
CASE FILE
The Hybrid Signature Arrived. The Verification Rule Still Had to Be Chosen: RFC 9955
Two signature components can travel together without forcing every receiver to treat them as one indivisible verification event. RFC 9955 makes the distinction useful: a hybrid artifact records a design choice; the receiver's verification rule still decides what was actually…
IETF
Qin Wu and the Registry Rule That Had to Catch Up With Practice
The same YANG module name appears three times in IANA’s register, attached to three dates and one XML namespace. That is not a uniqueness failure. It is the evidence needed to distinguish a stable identity from the revisions that change inside it.
CASE FILE
The Queue Found a Flow. It Did Not Find a Culprit: RFC 9957 and DOCSIS QProt
When a low-latency queue begins to grow, an operator wants a fast answer to a hard question: which traffic should lose the privileged path first? RFC 9957 describes a careful local answer for DOCSIS. It is not an answer to the wider and more tempting questions. A Queue Protection…
CASE FILE
The Packet Carried a Mark. It Did Not Deliver an Operations Verdict: RFC 9947 and SRv6 Measurement Authority
A marked packet is compelling because it seems to turn an invisible path into a fact. A loss bit, a delay bit, an identifier, a timestamp and a sequence value can all travel inside the same Segment Routing Header that tells the packet which segment endpoint to visit next. That is…
History
The Tunnel Made One Network. Discovery Still Had to Reach Everyone: RFC 1234
In June 1991, RFC 1234 offered a compact way to carry IPX across an IP internet: place the IPX datagram inside UDP and let an implementation regard the IP internet as one IPX network. It is tempting to read that sentence as a story of effortless unification. The rest of the RFC…
CASE FILE
The Device Left SCIM. Its Network Access Still Needed a Decision: RFC 9944
A deleted Device record can settle what a SCIM service will show. It cannot, on its own, settle what a network will enforce. RFC 9944 makes that distinction unusually plain: removal is an application's signal of intent, while a SCIM server and its back-end policy decide whether…
CASE FILE
The Map Reached a Router. It Did Not Decide the Path: RFC 9962 and LISP-Decent
A network can reduce a control-plane dependency and still retain a decision boundary. RFC 9962 makes that distinction unusually visible. It lets LISP Tunnel Routers participate in distributing the EID-to-RLOC mappings they use, rather than leaving all mapping state with a…
North America Cloud Services Trends
Guidewire's US$5.9m Services Allocation Does Not Change ARR
Guidewire placed US$5.9 million of recurring licence-and-support or subscription contract value in services revenue during the first nine months of fiscal 2026. Its ARR calculation did not follow that allocation. The distinction is neither an error nor an extra pot of revenue…
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…