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.
History
The Module Kept Its Name. The Device Did Not Prove Its Version: RFC 1442
A monitoring console can display a MIB module's latest revision date with complete confidence and still know almost nothing about the code answering from a particular device. RFC 1442 gave SNMP information modules a stable identity and a disciplined memory of change. It also drew…
IETF
A DNS Cookie Supplies Return-Path Evidence, Not Client Identity
A valid DNS Server Cookie can show that a requester at a source address is returning a value issued in an earlier exchange. That is useful evidence against off-path forgery. It is not a login, a durable device identifier or permission to attach a person’s name to the query.
Story
ARIN’s Reverse-DNS Controls Follow the Parent Block
A customer’s address range does not tell an operator where the reverse-DNS handoff belongs. ARIN’s direct-allocation rules put the editing boundary higher in the tree than a downstream inventory may suggest.
History
The Same Application Crossed Two Versions. The Proxy Changed the Operation: RFC 1452
The application asked for a bulk retrieval. The old agent never saw one. Between them, a bilingual manager consulted a local database, selected SNMPv1, zeroed two fields and changed the PDU into a single next-step request. RFC 1452 called the result transparent to the…
Story
What Comes After ARIN’s Empty Whois Replies
ARIN resolved a problem with some Whois queries in August. For anyone whose tools retained a suspect result, the next task is different: checking the local copy without turning a failed observation into a registration verdict.
Creators
Stefan Savage and measuring cybercrime as a system
Stefan Savage’s research repeatedly replaced isolated attack stories with measurements of traffic, supply chains, incentives and failure paths. From DDoS and network worms to spam, payment networks, cloud infrastructure and connected vehicles, the method is consistent: identify…
CASE FILE
The Slice Identifier Reached the Transport Edge. The Guarantee Still Had to Be Built: RFC 9889
RFC 9889 turns 5G network slicing into a chain of accountable translations: the mobile domain can name a slice, but the transport domain must still classify traffic, allocate resources, install state and prove the resulting service.
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…