Topic
Network-resource Evidence
Within the Topic facet, Network-resource Evidence 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.
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…
History
Dina Katabi and the Feedback Field That Was Not a Bandwidth Grant
A packet leaves its sender asking to increase the flow by a certain amount. The first router accepts the request; the second writes a smaller number; the receiver sends that surviving value back. XCP turned congestion control into an explicit negotiation, but the number in its…
History
RFC 2150 and the Long Walk from a URL to Centre Stage
A cultural work could be scanned, uploaded and assigned a URL while remaining far from the institutions that determined how it would be described, funded, preserved, taught and heard. RFC 2150 captured both the Internet’s remarkable power to carry culture and the larger stack of…
IETF
The Clock Agreed. Did the Traffic? Auditing RFC 9722 Recovery
RFC 9722 gives recovering EVPN peers a common instant for rerunning Designated Forwarder election. That is a precise control-plane promise—not evidence that clocks, forwarding entries and customer packets all crossed the boundary together.
CASE FILE
One Color Crossed Three ASes. It Never Became an SLA: RFC 9723
A low-latency color can survive every BGP hop and still fail to buy low latency. RFC 9723 gives SRv6 operators a compact way to propagate intent through colored locator prefixes; it does not merge the intent dictionary, route installation, packet path and customer outcome into…
CASE FILE
An IXP Classifier Cleared 90% on Tested Exchanges. That Is Not a Global Map
A new model can distinguish route-server exchange from bilateral interconnection with better than 90% accuracy on the exchanges used for its transfer test. That is a promising result. The public record still needs to say which exchanges, relationships and errors sit behind the…
History
Stephen Casner and the Timestamp That Was Not a Clock
Two packets leave in sequence and carry the same timestamp. That looks like a broken clock only if the number is asked to describe transmission. In RTP, the two packets may simply be fragments of one video frame. Stephen Casner and his coauthors made that distinction part of the…
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
ARIN Approved a Revised Strategic Plan. Its Public PDF Still Says December 2025.
ARIN’s draft minutes record an August 2026 vote on a “new” or “revised” strategic plan. The plan linked from ARIN’s public planning page, however, identifies itself as the version adopted in December 2025. That mismatch does not prove the strategy changed. It does show that the…
History
Anja Feldmann and the Traffic Matrix No Single Link Could Reveal
A red link on a network map looks like an answer: this is where the load is. For Anja Feldmann and her collaborators, it was only the start of the question. The counter could not say which demands had converged there, which routing decisions had brought them together, or where…
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
APNIC's RDAP Use Is 20%. That Is Not an Adoption Rate.
APNIC's new survey puts RDAP at 20% among respondents asked about core registry services. The number is useful evidence about reported use; it is not a census of deployed systems, a traffic share or a verdict on whether RDAP can replace WHOIS.
History
Jerry Saltzer and the Link That Carried a Name but No Permission
A path can tell a computer where a file is without answering whether the person following it may read the file. Jerry Saltzer’s account of protection in Multics turned that separation into an operating rule—and exposed how much revocation, audit and institutional power can be…
CASE FILE
The Stream Was Created. The Broadcast Was Not: RFC 9725
A WHIP endpoint can return `201 Created` while the programme remains black. RFC 9725 makes low-latency contribution easier to start; it also makes it essential to distinguish the HTTP resource from the media path, the production chain and the audience result.
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
AFRINIC's RRDP Lists 32 Deltas. That Is Not a Recovery Window.
AFRINIC's live RPKI notification showed a neat chain of 32 incremental updates. The number is useful, but it does not tell a network operator how long a validator may be offline before recovery changes from a small replay to a full snapshot.
IETF
SAV Benchmark Draft Makes “Legitimate” a Reported Fact, Not an Assumption
A revised IETF benchmarking draft puts an easily overlooked governance burden inside a technical test report: anyone measuring source address validation must say which packets were legitimate, which were spoofed, and why. That requirement matters because an error rate is only as…
CASE FILE
RFC 9727 Put the APIs in a Catalog. It Did Not Put the Catalog in Charge
The most dangerous API inventory can be perfectly formatted. Its links validate, its cache is warm, and its obsolete interface is gone from the list. None of those facts says what is still listening on the network.
History
Lixia Zhang and the Data Packet That Did Not Need Its Original Server
The revealing moment in Named Data Networking is not when a packet reaches a machine. It is when an Interest is answered by a copy found somewhere else—and the receiver can still ask who signed the data, whether that key was entitled to sign this name, and whether a fresher…