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 Server Carried the Proof: How OCSP Stapling Moved Evidence, Not Authority
A website could hand a visitor a signed answer about its own certificate without becoming entitled to write that answer. OCSP stapling made that separation useful—and left a less visible bargain over freshness, silence and who must keep the evidence available.
Global Cloud Services
Datadog’s Observability Pipelines Move the Cost Cut Upstream
Datadog offers a way to reduce telemetry volume before it leaves a customer’s environment. That can lower a downstream bill, but it also moves the authority to discard operational evidence to a point where a later search cannot recover it.
IETF
The Timer the Peer Could Hear: TCP User Timeout Without Negotiated Patience
One TCP endpoint could decide how long unanswered data was worth keeping, but the other endpoint could not hear that decision. RFC 5482 put the timeout on the wire as advice. The difficult part was preserving the distinction between a useful warning and a promise neither side had…
Global Cloud Services Trends
A Certificate Transparency Receipt Is Not Browser Acceptance Until the Log Set Is Reconciled
A certificate authority can return a certificate carrying several valid log receipts and still leave an operator with a failed browser handshake. Certificate Transparency becomes operational evidence only when the receipt is reconciled with the policy and log set used by the…
Global Regional ISP Trends
IPv4-as-a-Service Makes Translation State an Operating Contract
An IPv6-only access line can look perfectly healthy while one old application, one literal IPv4 address or one changed resolver loses the IPv4 Internet. IPv4-as-a-Service saves scarce addresses by moving compatibility into a chain of synthesis and translation; it also moves the…
Europe and Middle East Regional ISP
Gigaclear’s Wi-Fi guarantee stops at the broadband contract
A room-level speed promise sounds like protection for the whole broadband purchase. Gigaclear’s current terms draw a narrower boundary: a failed Smart WiFi test can release the mesh add-on and produce one month’s broadband credit, while the underlying broadband service continues…
IETF
The Field That Meant More After the Handshake: TCP Window Scale
TCP kept a 16-bit receive-window field even after fast, long-distance paths needed far more than 65,535 bytes in flight. Window Scale did not enlarge that field. It made the handshake establish how each endpoint would interpret the field for the life of one connection.
Global Cloud Services
GitHub's Attestation Proves a Build Path, Not a Safe Binary
A valid signature can establish where a binary came from while leaving the deployment decision unresolved. GitHub’s artifact attestation becomes a security control only when the consumer tests the recorded build route against an explicit trust policy.
IETF
The Request Arrived Before the Handshake: TCP Fast Open's Replay Bargain
TCP Fast Open let a returning client put its first application bytes in the packet that asked to open a connection. The saved round trip was real, but so was the bargain: replay tolerance, cookie rotation, bounded pre-handshake work and reliable fallback became part of operating…
Global Cloud Services Trends
From 200 Days to 47, TLS Renewal Becomes Runtime State
Public TLS certificates are getting shorter. The consequential change is not a busier expiry calendar; it is that authority, issuance, deployment and external verification must now behave like one continuously observed production system.
Global Regional ISP Trends
NQB Turns Low-Latency Broadband Into a Behavioural Contract
A gigabit access line can look idle while a short game update, voice packet or DNS reply waits behind a bursty upload at the home’s actual bottleneck. The new NQB standard offers a shallow queue, but only to traffic whose sending pattern can justify the privilege without turning…
IETF
When the Receiver Drew a Map: How TCP SACK Changed Loss Recovery
TCP once told a sender only where an uninterrupted stream ended. Selective acknowledgment added a second language: a compact map of the later bytes that had already arrived. That extra evidence changed loss recovery without changing who controlled the congestion window or when…
History
The Header That Waited Behind Its Data
A variable-length header could stand between an arriving packet and a useful boundary in memory. In the early 1980s, BSD systems tried moving that obstacle: put the data first and its higher-level headers afterwards, then restore the ordinary arrangement at the receiver. Trailer…
History
The Handshake That Had to Remember Its Previous Handshake: TLS Renegotiation
A TLS connection could be encrypted from end to end and still tell the server the wrong story about who had sent its first bytes. The renegotiation flaw of 2009 exposed a missing form of evidence: a new handshake needed to prove not only its own keys, but also which earlier…
IETF
The quarter-second bargain behind Happy Eyeballs
Happy Eyeballs turned dual-stack connection setup into a managed race. Its success lies in making path failure less visible to users; its cost is that the same success can make broken paths less urgent to repair.
Global Regional ISP Trends
RPKI’s Recovery Path Is Becoming a Routing Control Surface
A ROA is not useful merely because it exists. The operational result also depends on how repositories and validators move from delta to snapshot to fallback—and how long they trust a previously valid view when those paths fail.
History
The Address That Expired to Protect Its User: IPv6 Temporary Addresses
IPv6 privacy extensions did not make an address secret. They changed which address a host would prefer for its next conversation, how long that preference lasted, and when the identifier finally had to leave the interface.
History
Eight Bytes the Endpoints Could Not Negotiate Away
A PPPoE session could open successfully without carrying the packet size that justified opening it. The extension that addressed this problem separated permission, negotiation and a size-sensitive fallback. Its historical importance lay in a broadband migration: when the session…
History
The Forwarding Evidence an IP Error Left Out
The router removed the labels before it prepared the error. What remained could identify the original IP conversation while omitting the state that had governed its passage through the network. Adding that state to ICMP made a report more useful. It did not make the report a…
Europe and Middle East Cloud Services Trends
The Zero-Egress Invoice Is Not the Cost of Leaving Scaleway
A cloud bill can show nothing for moving the bytes and still conceal most of the work required to leave. The useful question is not whether egress is free, but whether the organisation can reproduce the service, prove the transition and close the old estate without losing…