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 Report the Sender Could Not Trust: Why TCP SACK Remained Advice
A TCP sender may keep a byte range in memory even after the receiver has explicitly reported it. That apparent distrust is the safeguard at the centre of selective acknowledgment: a precise observation can guide recovery without becoming a final receipt or a command.
History
The Acknowledgment That Learned to Point: How TCP SACK Made Loss Visible
TCP's original acknowledgment could certify an unbroken prefix of a byte stream, but it could not describe the islands waiting beyond the first gap. Selective acknowledgment added a small map of those islands while leaving the sender—not the receiver—in charge of repair.
History
The Router That Pointed Sideways: How ICMP Redirect Stayed Local
ICMP Redirect let a gateway reveal a better local next hop without becoming a routing authority. Its power ended at the host that had just used it.
History
The Number That Became Newer After Zero: How DNS Ordered Versions Without a Clock
At the edge of a 32-bit counter, DNS asks operators to accept an apparent impossibility: zero may be newer than 4,294,967,295. That rule let independent name servers agree on version order without sharing a clock, but only inside a deliberately bounded window.
History
The Zone That Knocked: How DNS NOTIFY and IXFR Cut Staleness
DNS once made every secondary wait before learning its authority was stale. In 1996, NOTIFY delivered the knock and IXFR carried only the edit.
History
The Address That Asked the Wire: How ARP Made Local Reachability Revisable
Routing can choose the next IP address without knowing how to put a frame on the local cable. ARP filled that last gap with a public question, a private answer, and a memory designed to be corrected.
History
The Connection That Had to Prove It Was New: Why TCP Needed a Three-Way Handshake
A packet can arrive at the right address, carry a plausible number and still belong to a conversation that has already died. TCP's familiar opening exchange was designed around that ambiguity: before accepting a new connection, both endpoints must show that they have seen each…
History
The Packet That Had to Learn Its Size: How Path MTU Discovery Moved Fragmentation to the Edge
A packet may cross a path whose narrowest link is invisible to its sender. The Internet spent four decades changing who should discover that limit, who should report it and who should decide what size to send next.
History
Two Kinds of Nothing: How DNS Learned to Separate NXDOMAIN from NODATA
An empty DNS answer can conceal two opposite realities: the requested name may be absent altogether, or it may be alive and carrying every record except the one requested. The Internet had to make that difference portable, cacheable and temporary before saving queries could stop…
History
The Error That Learned to Expire: How DNS Cached What Did Not Exist
The expensive DNS question is not always the one with a large answer. It may be the miss that thousands of resolvers repeat because nothing can be stored. Negative caching gave absence a scope, evidence and an expiry time—then forced operators to accept that a newly created name…
History
The Core That Had to Stop Being the Core: EGP and the Invention of Autonomous Systems
The early Internet did not decentralize by pretending that every network agreed. It learned to survive disagreement. The Exterior Gateway Protocol drew a boundary around what one routing administration could keep private and what it had to tell its neighbours. That boundary made…
History
The Clock Built from Disagreement: How NTP Made Internet Time Without Trusting One Server
In 1989, an Internet-wide experiment found clocks wrong by minutes, hours and, in a few cases, weeks. The problem was not a shortage of machines willing to state the time. It was deciding which statements deserved to move a local clock when packets, oscillators and operators…
History
The Map Made from Expired Packets: How Traceroute Turned Failure into Internet Evidence
In December 1988, Van Jacobson was not trying to draw the Internet. He was trying to find out where his packets had gone. The tool he assembled at Lawrence Berkeley Laboratory made the network answer indirectly: send a packet designed to expire, listen for the complaint, then let…
History
When One Router Announced Everyone’s Network: AS7007 and the Failure of Unchecked Trust
When One Router Announced Everyone’s Network: AS7007 and the Failure of Unchecked Trust intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
Story
RIPE NCC Split ENUM's Future From 23 Troubled Delegations
A draft prepared for September's ITU-T Study Group 2 meeting makes a careful retreat from a system-wide question. RIPE NCC now says Public ENUM should continue while 17 non-operational and six partly faulty delegations are handled as individual registry cases. The change is less…
History
When the First Network Became Replaceable: ARPANET’s Retirement and the Internet That Continued
ARPANET did not take the Internet with it when it was retired in 1990. That was not because the pioneering network had become unimportant. It was because its most important function—making unlike networks communicate—had already escaped the machinery and institution that first…
Story
LACNIC's 80% ROA Draft Ties New Addresses to Old Route Records
LAC-2026-3 would make a request for additional IPv4 or IPv6 resources the moment when LACNIC checks the routing-security state of an organization's existing address inventory. The proposed 80% threshold is simple enough to print in one line. Applying it fairly will require…
History
The Window That Learned Restraint: How TCP Stopped Congestion Collapse Without a Traffic Authority
The Internet's answer to its first congestion crisis was not a controller above the network. It was a new discipline inside every sender: learn the path from acknowledgements and loss, increase carefully, and retreat before retransmissions turn shared capacity into useless…
Story
APNIC Put Contactability and Judgment on the Same Agenda
One proposal asks whether an abuse report can reach the operator able to act. Another asks whether the reported conduct counts as abuse. APNIC 62 will discuss both on 10 September, but the route for a contested decision is still missing.
Story
The missing disposition in LACNIC’s 2026 Review Committee vote
The vote count is public, the audit windows have closed and the result is labelled official. Yet the same LACNIC page that offered two distinct seats currently identifies only one elected candidate, leaving the immediate-vacancy seat without a public disposition.