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
CAPWAP State Is Not Service Proof: RFC 5415
RFC 5415 gives wireless operators a structured CAPWAP control plane: an Access Controller manages Wireless Termination Points, establishes protected sessions, changes configuration and carries client data through defined modes. The useful leadership boundary is inside that…
Leaders
As Root-Zone Requests Grew, Kim Davies Rebuilt RZMS
By 2022, larger top-level-domain portfolios and more frequent DNSSEC key changes had outgrown the assumptions of the Root Zone Management System. Kim Davies described how an ICANN team rebuilt RZMS around configurable approvals, concurrent requests and technical checks that could…
IETF
WiCoP Is a Historic Control Record, Not a Deployment Baseline: RFC 5414
RFC 5414 describes WiCoP, a Wireless LAN Control Protocol for centrally managing and provisioning large WLANs. The RFC Editor marks it Historic and identifies RFC 5415 as the replacement. That status changes the question for a leadership team: a controller diagram or provisioning…
IETF
SLAPP Security Is a Historical Boundary, Not Deployment Proof
RFC 5413 records the Secure Light Access Point Protocol as submitted during the CAPWAP work. Its discovery, authentication and secure transport ideas are useful historical evidence, but the RFC Editor says the document was published solely for the historical record, was not…
IETF
LWAPP Is a Historic Record, Not a Deployment Baseline
RFC 5412 documents the Lightweight Access Point Protocol as it was submitted during the CAPWAP work. It is valuable archival evidence about an access controller and wireless termination point model, but the RFC Editor explicitly labels it Historic and says it should not be used…
IETF
A SIP Guide Is a Map, Not a Deployment Certificate.
RFC 5411 is useful precisely because SIP is too large to hold in one mental model. It groups the RFC series by topics, labels their status and points readers toward related work. But the document is an Informational snapshot, not a live inventory of what a carrier runs. A listed…
IETF
The Broadcast Extension Carried a Key Message. It Did Not Prove the Key Was Installed.
OMA BCAST needed MIKEY to carry more than one kind of control message: short-term keys, long-term keys, reporting data and parental-control information. RFC 5410 adds a General Extension payload for that transport. The payload proves that a particular message was encoded for a…
IETF
CMS Wrapped the Key. The Recipient Identity Still Had to Match.
RFC 5409 is not a general promise that “IBE works with email.” It defines the CMS conventions for encrypting a content-encryption key with Boneh-Franklin or Boneh-Boyen IBE, including recipient-identity encoding and algorithm identifiers. The envelope can be structurally valid…
IETF
The Identity Could Be a Public Key. It Still Was Not Permission.
An identity-based encryption design promises a neat operational shortcut: calculate a public key from the recipient's identity, encrypt immediately, and ask a trusted private-key generator for the matching secret only when the recipient needs it. RFC 5408 makes the shortcut…
Creators
A Phrase Traveled Without Its Author: Cory Doctorow and Interoperability’s Policy Boundary
When a Canadian parliamentary witness invoked Cory Doctorow’s phrase “adversarial interoperability,” she was speaking about a bill on copyright locks and software-enabled devices. The exchange carried an idea into a formal record, but it did not make Doctorow the witness, the…
IETF
The Channel Was Bound. The Operation Was Still a Separate Decision.
An SIP gateway showed a verified security context and a clean message check. The dashboard promoted that evidence into “authorised and complete.” RFC 5407 draws a harder line: SIP Version 2 can bind a SIP message to lower-channel information, but the binding does not become local…
IETF
The Channel Was Bound. The Operation Was Still a Separate Decision.
An IPsec gateway showed a verified security context and a clean message check. The dashboard promoted that evidence into “authorised and complete.” RFC 5406 draws a harder line: IPsec Version 2 can bind a IPsec message to lower-channel information, but the binding does not become…
IETF
The Channel Was Bound. The Operation Was Still a Separate Decision.
An RTP gateway showed a verified security context and a clean message check. The dashboard promoted that evidence into “authorised and complete.” RFC 5404 draws a harder line: G.719 RTP Version 2 can bind a G.719 frame block to lower-channel information, but the binding does not…
IETF
The Channel Was Bound. The Operation Was Still a Separate Decision.
An RPC gateway showed a verified security context and a clean message check. The dashboard promoted that evidence into “authorised and complete.” RFC 5403 draws a harder line: RPCSEC_GSS Version 2 can bind a GSS context to lower-channel information, but the binding does not…
IETF
The Receipt Matched. The Order Was Not Yet Accepted.
The trading gateway returned a signed receipt with the expected Message Integrity Check. A dashboard promoted that narrow success into “order accepted.” RFC 5402 shows why the promotion is unsafe: compression changes which bytes sit inside the signature and MIC boundary, while…
IETF
The Page Looked Final. The File Was Not: RFC 5385
An executive opens a document, checks that every heading, page break and reference looks right, and approves what appears on screen. RFC 5385 shows why that moment is useful but incomplete: the visible page was an authoring view, while compliant output still depended on styles, a…
IETF
No Complaints Is Not a Multicast Delivery Receipt
A software publisher sent one release to thousands of receivers. The transfer curve flattened, the repair channel went quiet, and the control room marked the campaign complete. That last step turned a useful transport observation into a claim the protocol had never made: in a…
IETF
The Lowest Address Won. That Did Not Make It Right: RFC 5384
Two downstream routers ask for incompatible treatment of the same multicast tree. The upstream router cannot preserve both requests, so RFC 5384 gives it a deterministic answer: use the attribute supplied by the adjacency with the numerically smallest IP address. The network can…
Creators
Susan Kare and the File Behind the Icon
MoMA’s collection includes Susan Kare’s 1982 Macintosh icon sketchbook; a later account of the archive she brought to museums describes more than 300 floppy disks of born-digital work. The paper page and the disk are not two copies of one thing. Together, they show why a digital…
IETF
The Server Found Your Principal. It Still Had Not Authorized the Work
The login succeeded. A WebDAV request returned a URL that represented the current user. The client followed it, painted the account green and attempted a write. The write was denied. Nothing in that sequence contradicted RFC 5397. The standard solved a narrower problem: how a…