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.
Story
LACNIC’s BGP Case Counts 368 Route Peers. The Vendor Could Not Produce a Definitive Installation List.
LACNIC’s latest routing-security case is unusually rich in network evidence and unusually poor in application evidence. The route, certificate and attack window can be reconstructed in detail; the vendor still cannot say which installations accepted the malicious update. That gap…
CASE FILE
The Server Accepted the Message. The User Still Could Not Find It.
RFC 9755 gives IMAP a precise UTF-8 handshake, but a capability banner and a successful APPEND are only the first receipts in a much longer chain from stored octets to usable mail.
History
Karen Sollins and the Delayed ACK That Made Every Packet Appear Twice
TFTP could deliver a file correctly and still damage the network carrying it. In the failure later called the Sorcerer’s Apprentice syndrome, one delayed acknowledgement could start a feedback loop in which every remaining data block and acknowledgement travelled twice. Karen…
History
Eight Bytes Drew a Recovery Boundary: RFC 2029 and CellB After Packet Loss
RFC 2029 gave every CellB packet its own spatial address: the first 4×4 cell’s coordinates and the image dimensions. That small repeated header let a receiver resume at a known place after loss, but it did not replace the missing cells or prove that the resulting frame was…
IETF
One MAC Address, Four Spellings: A YANG Draft Redraws the Duplicate Boundary
The proposed rule is easy to miss because nothing on screen has to change. A value can keep the colon, hyphen and letter case that arrived over the wire, while a second, invisible form decides whether another configuration entry is a duplicate.
Story
RIPE Atlas Firmware 5130 Added an OpenWrt Hardware Architecture. The Rollout Needs More Than a Version Number
Firmware 5130 gives RIPE Atlas a new `openwrt-hwprobe` architecture for next-generation firmware on existing hardware probes. That is a concrete engineering change, not merely a roadmap line. Yet the number 5130 can identify a release without proving which source, toolchain…
CASE FILE
The Receipt Behind the Cipher: What RFC 9771 Makes AEAD Buyers Prove
An authenticated-encryption label can be correct and still leave the decisive deployment question unanswered. RFC 9771 gives operators the vocabulary to distinguish a mathematical property, an implementation convenience, and an interface with different security rules. The next…
IETF
The Requirements Were Written. The Solution Was Not Proven
Revision 14 gives YANG versioning work a disciplined list of obligations: evolve modules without detonating dependency graphs, disclose compatibility, protect old clients, clarify retired nodes and explain migration. Its value is the questions it preserves. A requirements…
History
One Class A Subnet Could Defeat the Default: RFC 2036’s Compatibility Test
Opening unused Class A space in 1996 was not just a registry decision. It changed what every provider, customer domain and peer had to mean by a route: once a small component of an old classful parent appeared, inherited assumptions could send the rest of that parent away from an…
IETF
Two YANG Versions Can Coexist While the Effective Schema Still Diverges
An upgrade can look calm precisely when its most consequential uncertainty has moved downstream: `draft-ietf-netmod-yang2-00` lets an older importer and a YANG 2.0 dependency remain together, but that accommodation proves far less than a shared client view of the network.
IETF
Two Published Copies Can Match Before Any Device Changes
Revision 03 of a NETMOD working-group draft proposes a careful handoff for normative YANG modules: keep them visibly provisional through IESG approval, finish the bytes under RFC Editor control, validate again, and only then let the RFC and IANA copies appear together. That…
IETF
A Standards Action Can Authorize a Field. It Cannot Certify the Firewall: RFC 9778
RFC 9778 gives new IGMP values a high-visibility approval path. It also exposes a harder operational truth: a legitimate Type, Code, or extension flag can still be unknown to the security device deciding whether the packet is declined, inspected, or forwarded.
IETF
Four Buckets Did Not Make a Standard
Revision 00 of YANG Next Agreement turns a crowded GitHub issue pool into four decision lanes. That is useful scope control. It is not, however, a vote, a language specification or evidence that any tool or network can safely run what the lanes contain.
History
The Catalogue Was Verified. The Training Material Could Still Be Gone: RFC 2007
In 1996, a volunteer directory tried to keep Internet training reusable by recording three different clocks: when a resource changed, when its catalogue entry changed, and when someone last checked it. RFC 2007 shows why those dates were useful—and why none was a promise about…
Story
AIRRS Sends “amp;profile”. RIPEstat’s Real AFRINIC Profile Returns 500
A regional statistics portal can look complete while the choice that is supposed to make it regional never reaches the service under the expected name. AIRRS currently demonstrates that uncomfortable distinction: seven tabs can arrive, yet the evidence says they came through…
IETF
The Rule Chose the Sub-Interface. The Wire Still Owed Proof
A six-step precedence order can make VLAN classification deterministic without making forwarding observable. Revision 18 closes one ambiguity at the configuration boundary; operators still need counters, captures and path evidence to close the operational claim.
History
The MIB Saw the Binding. It Did Not See the Journey: RFC 2006
RFC 2006 gave operators a disciplined view of Mobile IP’s moving parts. Its tables, counters and alert could expose what a management agent believed had happened, while leaving delivery, identity, authority and continuity outside the frame.
History
The Interface That Had to Train Before Its MTU Changed: RFC 2020
In one of the more exact management designs of 1996, an operator could ask an IEEE 802.12 interface to change its framing, promiscuous mode or control role—but the request did not become an operational fact until the link trained and the current-state entities reported the…
IETF
The Server Said “Immutable.” That Was Only the First Receipt
Revision 14 gives a client a machine-readable explanation for configuration the server will not let it override. The annotation is useful precisely because its authority is narrow: it describes one node instance, not an eternal property of the device or proof of the service it…
Global Institutional
ISC’s Authority Is Fragmented Across the Internet’s Control Surfaces
ISC’s Authority Is Fragmented Across the Internet’s Control Surfaces intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow.…