Content Type
Analysis
Within the Content Type facet, Analysis intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
Creators
David S. Miller and the public process behind Linux networking
A networking patch can start as a few lines of code and end up affecting servers, routers, phones, cloud hosts and appliances around the world. David S. Miller has spent decades close to the point where those changes become shared Linux infrastructure, first through the SPARC…
History
The Reply Was an Observation, Not Authority: RFC 2151 and the Limits of Diagnostic Tools
RFC 2151 put an Internet laboratory on an ordinary user's desk. Its commands made names, round trips, intermediate routers and remote services visible, but the very clarity of their output invited a category error: a tool could report what answered without acquiring authority to…
Story
RIPEstat Explains 12859:4000 With 12859:4xxx. The Wildcard Is Evidence
RIPEstat’s Looking Glass can place a useful sentence beside an opaque BGP community. In one frozen response, however, the observed value `12859:4000` received the description “customer routes” from the broader expression `12859:4xxx`. The explanation may be right. The missing…
Story
AFRINIC’s Uganda Anycast Node Is Two Services, Not One
AFRINIC’s Uganda Anycast Node Is Two Services, Not One 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. The Story…
Story
Rapport’s Forbidden-AKI Test Starts at Barry, Not at the Validator
A conformance test cannot prove that a validator rejected a forbidden certificate field until it proves that the field reached the certificate. A September correction to one LACNIC Rapport fixture makes that dependency unusually visible. The change replaces a scalar value that…
Story
APNIC Says prop-170 Reached Consensus. APNIC-127 Still Does Not Say “Nibble”
On 14 September, two official APNIC pages described prop-170 as having reached consensus at APNIC 62. A third official page still labelled it “For Discussion at APNIC 62 OPM”. The operative policy supplied a more important answer: APNIC-127 still contained the old IPv6 allocation…
Story
RIPE WHOIS Gives Invalid API Keys an Audit Identity
A failed credential usually looks like absence: no user, no permission, no successful update. In the current RIPE WHOIS source, however, the failure path can carry one durable-looking fact into its audit representation—the API key ID supplied as the Basic-auth username—even when…
Story
AFRINIC’s Hash Tool Is Also a Password-Receiving Surface
AFRINIC’s public generator returns a BCRYPT value, but its current form first asks a browser to send a field called `plaintextpassword`; the missing operational entity is a receipt for who can see that source value before the hash exists.
Story
LACNIC’s Migration Script Reuses a Volume at a Different Path
A persistent Docker volume can survive the container that populated it. LACNIC’s historical migration launcher leaves a narrower question unanswered: does the next application still look where that volume is attached?
Global Institutional
SNIA writes common storage rules without the power to enforce them
Since 1997, SNIA has tried to make storage systems from different vendors easier to compare, manage and trust. Its specifications reach from management software and cloud data to media erasure, energy use and hardware form factors, yet every useful rule still depends on companies…
Story
ARIN’s DS Payload Guide Calls Digest Type 3 MD5. IANA Says GOST
A public provisioning reference gives one DNSSEC code two incompatible identities. The correction is narrower than an API failure, but more consequential than a spelling change: the number determines the digest, and fixing its label would not make the retired algorithm suitable…
Creators
Jiří Pírko and the Linux interfaces exposing switch hardware
A physical switch can forward packets at extraordinary speed while revealing little about the tables, limits and failures inside it. Jiří Pírko's work on switchdev and devlink helped give Linux a common language for that hidden machinery, bringing forwarding state and device-wide…
Story
ISIF Now Starts With a Concept Note. The Foundation Performs the First Review
A shorter opening application can widen access to Internet-development grants. It does not make the entire selection sequence an independent committee decision—and the 2026 rules do not claim that it does.
Story
Sagan Can Mark a Traceroute Successful Without a Reply From the Destination
One Python flag tests a non-error reply at the end of the supplied trace. Another tests the destination address. Keeping those answers separate is the difference between reading a measurement and awarding it a meaning it has not earned.
Story
AFRINIC’s Duplicate nserver Row Is Gone. Redundancy Is Not a Row Count
A February discussion exposed two identical nameserver entries that produced only one DNS referral. The named example is now corrected. What remains useful is the distinction between an avoidable input mistake, an answering server and infrastructure that can survive a failure.
Story
Two Minutes Can Become Many in LACNIC’s Permission Cache
A public PAI client can restart the age of a cached permission entry after a malformed authorization reply without obtaining a new permission decision. Its small resilience mechanism exposes a larger question: which clock should govern an application when the authority it…
Story
Starla Uses RIPE Atlas Version Numbers. They Do Not Name Its Executable.
A Rust implementation can speak the probe’s language without becoming the same measuring instrument. Starla makes the distinction visible in source: its own package version, its compatibility numbers and its registration identity answer different questions.
Global Institutional
Akvorado turns sampled flows into a network’s working memory
Akvorado gives network operators a self-hosted way to retain, enrich and examine flow records across long periods. Its usefulness comes from making the path from router export to operational decision visible; its central limit is that every graph still inherits the sampling…
Creators
Russ White and the discipline of containing network complexity
Russ White and the discipline of containing network complexity 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. The…
Story
ARIN’s 2026 Revenue Bridge Does Not Reconcile
Three adjacent budget columns invite a reader to perform one ordinary calculation. In ARIN’s published 2026 revenue total, that calculation produces a different destination. The problem is not evidence of missing money. It is the missing public explanation of how one financial…