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
Stefan Savage and the measurement of cybercrime as a system
Stefan Savage’s research repeatedly replaced stories about attacks with measurements of traffic, supply chains, incentives and failure paths. From denial-of-service and worms to spam, payment networks, cloud infrastructure and connected vehicles, the recurring method is to…
Story
APNIC REx: When a Date Becomes a Matching Key
Three historical address records changed their dates without changing their ranges. The case shows why reconstructing a resource's past also requires understanding the past of the fields used to identify it.
CASE FILE
The Token Arrived Before the Call. Verification Still Had to Wait: RFC 9888
The signed identity token reached the destination service first. The telephone call was still crossing a path that could not carry that token with it. RFC 9888 makes this split useful for legacy networks, but it also leaves an operational obligation: two arrivals on two channels…
History
The Version Number Survived. The Security Framework Did Not: RFC 1441
In one of SNMP's durable historical jokes, the integer `1` in a message wrapper can mean community-based SNMP version 2. The arithmetic is harmless. The assumption it invites is not. A version field tells a receiver how to process a message; it does not, by itself, reveal which…
History
The Alarm Survived. Its Route to the Other Manager Had Expired: RFC 1451
The monitoring station was still sampling. The threshold still meant what its operator had configured. The event definition was still present. Yet the row that told the station how to notify another manager could count itself down to destruction. RFC 1451 made operational…
Creators
Albert Greenberg: The Network as a Distributed Computer
Across AT&T, Microsoft Azure and Uber, Albert Greenberg has worked on a recurring problem: how to make a vast network behave as one coherent system when topology, traffic, control software, hardware and failure patterns change at different speeds. His influence is best understood…
History
The Username Looked Like a Person. The Namespace Only Promised a Slot: RFC 1439
In 1993, a tidy rule for turning names into email accounts met a problem that no directory card could hide: two people could produce the same string, and a successful delivery could still reach the wrong human. RFC 1439 treated the collision not as clerical untidiness but as a…
CASE FILE
The Secure Channel Failed. The Client Was Not Allowed to Fall Back: RFC 9887
RFC 9887 turns a secure-transport upgrade into a rule about authority: when the protected TACACS+ path fails, reachability of the older path does not authorize the client to use it.
History
The File Arrived. The Recipient Had Not Accepted It: RFC 1440
In 1993, an experimental Internet protocol tried to deliver a file the way a network might deliver a parcel: the sender pushed it without logging into the destination, the receiving host put it aside, and the named recipient decided what to do later. That convenience depended on…
Global Institutional
Batfish and the promise of checking a network before change
Batfish turns multi-vendor configurations into a common routing and forwarding model so operators can test reachability, policy and selected failures before production changes. Its value still depends on snapshot completeness, parser coverage, explicit intent and post-deployment…
Story
RIPEstat’s Empty IP Lookup and the Route Beside It
A user’s two differently worded requests produced different views of a route. A successful retest leaves a narrower question than an outage: what did an empty answer actually establish?
History
The WAN Session Was Up. The End Stations Still Had Two Links: RFC 1434
In an early-1990s network, a terminal could believe it was talking to a distant peer while every acknowledgement it saw came from a router in the same room. RFC 1434 made that split deliberate: keep fragile local link timing local, build another circuit between switches, and…
CASE FILE
The Tag Resolved. The Aircraft Was Not Located: RFC 9886
The reverse-DNS answer arrived in milliseconds: a public key, a registration certificate and a static Remote ID record. The airspace display was still empty. RFC 9886 explains why both screens can be correct — it makes an aircraft-related identifier resolvable without turning…
Global Institutional
Batfish and the promise of testing a network before it changes
Batfish turns multi-vendor configurations into a model of routing and forwarding so operators can ask whether reachability, policy and failure behaviour survive a proposed change before touching production. Its answers can be exhaustive inside the model, but their operational…
Leaders
Aaron Moreck and the Network-Service Decisions Behind NaaS and SD-WAN
Aaron Moreck’s public record sits at the operating edge of a regional technology company: network services, customer connectivity, managed firewalls and SD-WAN. The evidence supports a profile of a technical decision surface, not a claim that one director owns every customer…
History
The Codes Aligned. The Circuit Still Needed Permission: RFC 1394
A two-letter domain, a telex answerback and a telephone prefix could all point toward the same country and still leave a message nowhere to go. RFC 1394 made those correspondences useful by placing them in one table. It also marked the table's limits: values could be wrong…
Creators
Albert Greenberg and the network as a distributed computer
Across AT&T, Microsoft Azure and Uber, Albert Greenberg repeatedly addressed the same problem: how to make a large network behave as a coherent system while topology, traffic, control software, hardware and failures change at different speeds. His influence is clearest in control…
Story
The Refill Behind LACNIC’s Falling ASN Forecast
The Refill Behind LACNIC’s Falling ASN Forecast 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 intelligence…
IETF
Bernie Volz and the DHCPv6 Trigger That Did Not Yet Configure a Client
A server log can make the word “Reconfigure” look final: the server issued the message, so a client must now have new settings. RFC 9915, co-authored by Bernie Volz, is more exact. Reconfigure is a carefully authenticated trigger for a later exchange. It is not, by itself, a…
History
The Route Named a Next Hop. The Link Still Had to Agree: RFC 1433
Two machines could occupy the same data-network service and still be unable to exchange a frame. RFC 1433 began from that uncomfortable fact: routing could identify a shorter next hop, while address resolution and link filters retained the power to make the route usable—or turn…