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 Receiver That Chose What Came First
Before SMTP, a mail receiver could answer `MRSQ ?` with `215 T Text first, please`. It was asking for the complete message before it learned a single recipient. Another receiver could prefer to collect every address and accept one shared body afterward. This was more than syntax.…
CASE FILE
The Zone Went Dark. The Resolver Made the Outage Louder
When authoritative DNS stops answering, the first failure belongs to the zone. The next thousand queries may belong to the resolver. RFC 9520 draws a narrow but consequential line between the two: silence is not proof that a name does not exist, yet a resolver that has exhausted…
Story
AFRINIC Extended Its Bylaws Consultation. Its Only Named Form Went Down Four Days Before the Deadline
A deadline is a promise about access, not merely a date printed on a page. AFRINIC gave contributors until 17 May to use a designated constitutional-comment form; on 13 May it announced that the form host was unavailable, leaving the public record without the timestamps and…
CASE FILE
The Block Was Explained. The Policy Was Still a Claim.
The night shift sees an authenticated DNS response that says a name was blocked, identifies a policy category and offers a support route. The explanation is orderly, machine-readable and intact. It still does not reveal whether the upstream classification was right, who had…
History
The Byte the Sender Did Not Send: How FTP MODE C Reconstructed Filler from TYPE
A decoder reads a run count and reaches the next item without finding a value to repeat. Nothing has been lost. In FTP's compressed mode, that absence was a complete instruction: the missing byte had already been chosen elsewhere, by the representation type negotiated on the…
History
The Byte That Had to Appear Twice: How FTP Put Record Boundaries Inside a Stream
Two identical all-ones bytes could cross an FTP data connection side by side and emerge as one byte of file data. Change only the second byte to a small control value and the first became an escape announcing the end of a record, a file, or both. Early FTP solved a problem that a…
CASE FILE
The Proof Verified. The Fork Was Still Private.
Every response on Alice’s device verifies. Every later tree head extends the one before it. Across town, Bob sees the same tidy sequence—except his latest head commits to a different key for Alice. The log has not broken either local proof chain. It has separated the witnesses.
Story
RIPE-861 Recommends Off-List Nominations. The Candidate List Needs a Receipt
RIPE's new guide gives a quiet volunteer a private way to approach a continuing working-group chair. That can widen participation. It also moves the first step outside the public archive, making the later conversion from interest to a complete candidate list the part that needs…
CASE FILE
The Handshake Succeeded. The DNS Question Was Already Exposed
RFC 9539 lets a recursive resolver encrypt its next hop to an authoritative server without waiting for the server to advertise a new policy or present a verifiable identity. That modest bargain can hide many DNS questions from passive observers. It also creates an unusually…
History
The Missing Page That Was Not Zero: How FTP STRU P Carried Holes Across Hosts
An FTP transfer could move from one indexed page to a later one without sending anything for the position between them. That gap was not a dropped packet and it was not a page full of zeros. In FTP's page structure, absence itself belonged to the file map—and preserving it…
Europe and Middle East Regional ISP Trends
BSH's single-operator model makes dependency evidence part of the SLA
BSH offers distributed organisations a commercially simple proposition: aggregate communications services into one contract and give the customer one point of responsibility. That can reduce the cost of coordinating a fault. It does not, by itself, show whether the underlying…
History
The Instruction That Had to Survive the Split
One IPv4 datagram entered a router with two options. Loose Source and Record Route, type 131, had its high bit set. Record Route, type 7, did not. When the router cut the datagram into three fragments, the zero-offset fragment kept both options; the other two kept only the…
CASE FILE
The Certificate Was Fresh. The Number Authority Had Its Own Clock.
A verifier receives a PASSporT with an intact signature, a valid certificate path and a certificate that will expire in hours. Between issuance and the call, however, control of the calling number has changed. The credential can be fresh in the precise X.509 sense while the fact…
History
The Rename That Had Not Happened Yet: How FTP Put a File Between RNFR and RNTO
FTP could answer a rename request with a positive code while leaving the file exactly where it was. The first command, `RNFR`, named the source and produced an intermediate state; only the immediately following `RNTO` supplied the destination and could complete the action. The…
CASE FILE
The TLS Session Resumed. The DNS Subscription Did Not
DNS Push can make a changing RRset look continuously current by stopping the client’s TTL clock and replacing polling with a server’s promise to send changes. That promise belongs to one accepted subscription on one live DSO session. A resumed TLS channel is cheaper to rebuild…
Story
LACNIC and the economics of legitimacy after scandal
A balance-sheet test for how a regional Internet registry could restore trust after a verified governance failure without risking continuity.
Story
ARIN’s RDAP Parent Handle Describes Registration Hierarchy, Not Network Transit
Two handles in one ARIN RDAP response can reconstruct how an address block sits inside the registry, but they cannot reveal who carries its traffic. The distinction is small in syntax and consequential in analysis.
History
The Byte the Wire Refused to Define
The server accepted `TYPE L 36`. The next nine octets on the data connection carried not nine file units but two. FTP had standardized the carrier at eight bits while leaving the sender free to declare a 36-bit logical byte and the receiver free to choose an invertible local…
History
The Login That Survived a Filesystem Switch: How FTP SMNT Separated Identity from Namespace
An FTP user could authenticate once, set transfer parameters, then ask the server to exchange the file-system structure beneath the session. The command was called `SMNT`, for Structure Mount. Its sparse specification preserved a surprisingly modern distinction: a principal may…
Story
LACNIC's FORT Can Validate ASPA. Its Router Feed Defaults to Version 0
LACNIC announced a validator that can carry ASPA data towards routers. The release also keeps that route behind a configuration value whose default is zero. That is not a contradiction or a defect. It is the difference between shipping a capability and establishing that the…