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 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.
IETF
The IPv6 Test Passed. The Update Channel Still Needed IPv4
The release dashboard was green. The main interface had loaded over IPv6, its API calls had completed, and the deployment was labelled ready. The first update exposed the missing cell: a helper still reached an IPv4-only repository. Revision 03 of an IETF application-testing…
IETF
The Log Had No Gaps. Its Last Pages Could Still Be Missing
A verifier receives receipts numbered zero through forty-two. Every signature checks, every running count agrees and no number is absent. The display says “complete.” That conclusion is one receipt too early: the holder may simply have withheld everything from forty-three onward.
IETF
The Counter Read Zero. The Evidence Window Had Been Cleared
The QoS policy was still attached to the interface. The incident dashboard showed no classified packets, no meter violations and no queue drops. That could have meant the link had been quiet. It could also have meant that somebody had reset the counters. Revision 16 of an IETF…
IETF
The Header Looked Like an Access Token. The Authority Model Had Changed
The new DPoP credential draft makes an audaciously economical move: put a reusable issuer-signed Credential where an access token normally goes, then reuse the proof machinery unchanged. The bytes fit. The hard question is whether the verifier remembers that the authority behind…
CASE FILE
SensorThings Gains an SSN Relationship Map, Not a Round-Trip Guarantee
W3C has added a seven-row navigation crosswalk to its sensor ontology draft. It makes a migration choice visible, while leaving the conversion and its evidence to the teams that operate it.
IETF
The Bundle Was Up. The Controller Still Could Not Pair Its Strands
A link-aggregation group can look like one healthy pipe while hiding several physical strands. A controller may know every local member at both ends and still be unable to say which port meets which across the gap. An IETF proposal adds the missing reciprocal labels—but also…
IETF
One String Came Back. The OAuth Grant Was Still Unfinished
The new out-of-band OAuth draft solves a real human-interface problem with unusual restraint: instead of asking a remote-terminal user to copy both `code` and `state`, it makes one string. The danger begins when that cleaner handoff is mistaken for a stronger grant.
IETF
The First Packet Opened the Return Path. It Did Not Authenticate the Caller
A network element sends a 1,200-byte empty knock. The management system throws away its contents, reads the apparent source address, and opens a new QUIC connection back. That reversal is the heart of a young IETF proposal—and a precise lesson in why a message that creates work…
IETF
The Boolean Was Signed. The Chain State Had Already Moved
Wallet State Attestation revision 01 turns an issuer’s reading of on-chain state into a portable signed answer. Its strongest contribution is also its warning: signature, state anchor, freshness, finality and authorization remain different proofs.
IETF
The Registry Closed. The Number Did Not Die
Standards institutions rarely get a clean shutdown switch. Their harder task is to stop allocating new meaning without pretending that old meaning vanished. A six-page Internet-Draft about legacy IANA registries exposes that problem with unusual precision: it proposes four…
History
Equal Cost Did Not Make the Paths Interchangeable: RFC 2991 and the Price of Stable Multipath
Two routes can tie in the routing table and still disagree about packet size, delay and what a probe can see. In 2000, RFC 2991 made the router’s choice among those paths a question of how much disruption a network was willing to accept.
IETF
The Key Update Was Sent. The New Epoch Was Not Yet Shared
CURRENT's unfinished MLS-TLS proposal puts a useful operational fact on the wire: one endpoint can move first, while the other still waits for authenticated proof of the same cryptographic state. “Rotated” is therefore not one event but a custody chain.
IETF
The Stack Got Smaller. The Configuration Became the Protocol
A proposed modular form of SCHC can turn a four-byte IPv6 prefix into a one-byte RuleID. The bargain only works because both endpoints already possess the meaning that no longer travels on the wire.
History
The Network Could Decline Without Saying No: RFC 2990 and the Missing QoS Feedback Loop
In November 2000, RFC 2990 described an awkward bargain at the centre of Internet quality of service. A network could remember each application's reservation and return a precise answer, but carrying that state through a high-speed core was expensive. Or it could aggregate…
IETF
The Session Was Accepted. The Decoder Still Needed Yesterday’s Frame
The third-edition RTP payload for JPEG XS keeps a familiar wire envelope while adding Temporal Differential Coding. That compatibility is useful, but it creates a precise leadership risk: a successful negotiation can attest to declared capability without attesting to the decoder…
History
The Checklist Graded Capabilities, Not Packets: RFC 2989
In November 2000, RFC 2989 assembled a formidable checklist for network-access AAA protocols. It asked whether a candidate could scale, fail over, protect entities, carry EAP, authorize, reconcile state and deliver accounting records. Then it inserted the sentence that kept the…
IETF
The Contact Converged. Its Merge Decision Had No Receipt
Two devices can finish with the same compact vCard after a synchronization engine decides that independently created telephone properties are really one value. The record may be valid, useful and fully interoperable. It still cannot say why the heuristic fired, whose edit…
History
The Tags Looked the Same. One Was a Limit, the Other a Preference: RFC 2987
In November 2000, RFC 2987 placed `charset` and `language` inside the same media-feature grammar. Both used registered tokens, equality comparison and optional quality weights. Yet the document refused the most convenient inference: identical syntax did not make the two claims…
IETF
The Handshake Got Smaller. The Missing Certificates Became Onboarding State
An IETF draft proposes taking bulky intermediate certificates out of post-quantum TLS-based EAP handshakes. The bytes do not disappear. They move to an earlier EST retrieval, a local cache and an administrator's decision that both sides are ready to proceed without them.