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 Address Inside the Packet Was Invalid. The Frame Header Supplied the Source: RFC 2390
Frame Relay could deliver the same virtual circuit under one number at the sender and another at the receiver. RFC 2390 made the consequence explicit: the hardware-address fields inside an arriving InARP message could not be trusted as carried. The receiving interface had to take…
Story
RIPE Withdrew Its IPv6 PI Rewrite. The Rule an Operator Uses Did Not Move
An organisation planning an IPv6 PI request has two RIPE records to read. One, the proposal page, still showed a draft in Review Phase when checked on 27 September. The other, a working-group chair's message dated three days earlier, said that draft had been withdrawn. Neither…
Story
RIPE’s Central Asia Path Comparison Needs a Sample Ledger
Three maps can show change only if the rows behind them stay countable. RIPE NCC’s CAPIF 5 report presents an encouraging direction for Central Asian Internet paths across 2022, 2024 and 2026. The next useful publication is not a more confident adjective. It is a compact receipt…
History
David Culler and the Command That Was Never Completion
On a TinyOS mote, the most honest thing a command could do was return before the work was finished. The radio might still be transmitting, the sensor might still be converting and the relevant hardware interrupt might not yet exist. David Culler and his collaborators built that…
History
Sylvia Ratnasamy and the Map That Was Never Geography
CAN drew a map in order to avoid keeping one central index. Its coordinates did not mark countries, cables or even nearby machines. They marked a temporary division of work: hash a key to a point, then ask whichever node currently holds the enclosing zone. Sylvia Ratnasamy and…
CASE FILE
The Samples Came Back Exactly. The Recording’s Identity Did Not: RFC 9639
RFC 9639 makes a precise promise: a FLAC decoder can reconstruct the integer PCM samples supplied to the encoder. That is a powerful preservation property. It is not proof that the source was authentic, the metadata was true, the channels meant what the labels claimed, or a…
History
The URL That Carried Its Own Cargo
RFC 2397 made a small but consequential move: it put the representation inside the address. The result was not merely a convenient encoding trick. It changed where retrieval ended, where interpretation began, and which component actually controlled the outcome.
Story
DFINFRA and AS210860: Running the Commercial Half of a Test BTW Defined but Never Executed
DFINFRA and AS210860: Running the Commercial Half of a Test BTW Defined but Never Executed intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
History
The Compressor Forgot on Purpose: RFC 2395 and the Datagram Boundary
A sliding window normally becomes useful by remembering what came before. RFC 2395 made LZS forget before every IP datagram. That apparent waste was the design: a packet arriving alone had to remain decodable after an earlier packet was lost, delayed or reordered. Reset, flush…
CASE FILE
The Address Was Reserved. The Network Still Had to Drop It: RFC 9637
RFC 9637 gives large IPv6 examples a block that belongs to documentation rather than to an operator. That reservation prevents one class of collision. It does not install a route filter, isolate a lab, update a bogon list or prove that a packet using the block was rejected.
History
Larry Peterson and the Global Slice That Never Owned a Node
PlanetLab gave a research service one name across machines it did not own. That was the power of the slice and also its limit. Larry Peterson and his collaborators made a distributed set of virtual machines behave like one experimental place, while the universities and…
Global Institutional Trends
AS210764: who can change the ISC-AGP1 record, and what the maintainer chain says about ISC stewardship
AS210764: who can change the ISC-AGP1 record, and what the maintainer chain says about ISC stewardship intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
History
The Pool Had Spare Servers. The Session Could Not Move: RFC 2391
A service address can look like a place while concealing a choice. In RFC 2391, that address stood in front of a pool. A Load Sharing Network Address Translator chose one server when a new session arrived, rewrote the packets and kept both directions passing through itself. The…
CASE FILE
The File Knew the Offset. It Did Not Know Tomorrow’s Law: RFC 9636
RFC 9636 standardizes the binary file that many systems use to turn an instant into local civil time. The format can carry transitions, offsets, daylight-saving state, abbreviations and leap-second records. It cannot certify that the chosen zone was right, the source release is…
IETF
The commit returned. The stale host may still be writing
RFC 9561 maps the pNFS SCSI layout onto NVMe identifiers, reservations and flush commands. The map is precise. The operational receipts that prove fencing, stable storage and the application's result remain separate.
History
Jon Crowcroft and the Internet That Became One Context Among Many
The cleanest network diagram has one middle and many edges. Plutarch drew a more difficult picture. In the 2003 architecture proposed by Jon Crowcroft, Steven Hand, Richard Mortier, Timothy Roscoe and Andrew Warfield, the globally routed Internet remained useful but ceased to be…
CASE FILE
The Probe Came Back Green. It May Have Taken Another Road: RFC 9634
RFC 9634 explains how existing IP OAM tools can monitor a DetNet flow, but the decisive work is not launching a probe. It is proving that the specially constructed test packet experienced the path, treatment and resources of the production flow it is supposed to represent.
History
The Server Listed Its Features. The Command Still Had to Succeed: RFC 2389
FTP had accumulated extensions faster than clients could safely discover them. Before 1998, a client might learn whether a server understood a new command by sending it and seeing what happened. RFC 2389 inserted a quieter exchange: ask for the feature inventory first, then…
Story
ARIN Funded an RPKI Dashboard Around a 99% Claim. The Recipe Must Travel With It
Four numbers arrived in ARIN’s grant record: 3.9 billion observations, 139 GB, 9% and more than 99%. The first two describe a warehouse. The last two judge behaviour. A weekly public dashboard can make that judgement useful, but only if the exact measurement recipe travels with…
IETF
The algorithm has a number. The resolver may still say no
RFC 9563 gives SM2 signatures and SM3 digests stable DNSSEC identifiers. That solves an addressing problem. It does not establish IETF consensus, cryptographic suitability, implementation support, an authenticated delegation or a successful DNS answer.