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 Timestamp Saved Before the Search: How NEWNEWS Chose Duplicates Over Missing Articles
A news reader asks a server what arrived since its last visit. The obvious bookkeeping move is to save the time when the answer comes back. It is also the dangerous one. An article can arrive while the server is searching: too late for the current result, yet earlier than the…
History
The Relay That Added Context by Cutting Off the Message
A nearly full syslog packet arrived without a recognizable timestamp. To make the record usable, the relay had to prepend its own local time and, if it could, the name by which it knew the sending device. The envelope did not grow with the explanation. At 1,024 bytes, the new…
CASE FILE
The files matched. The authority did not
An RPKI Signed Checklist can bind exact file bytes to a declared set of Internet Number Resources. That is a useful and unusually precise proof. It is also much narrower than the green result can appear: the entity does not identify a company, certify a document's truth, prove a…
IETF
Clarence Filsfils and the Segment List That Learned to Share an Address
An SRv6 path can be perfectly explicit and still carry waste: the same locator block repeated across instruction after instruction, plus zero padding that moves through the network without adding a decision. RFC 9800 removes that repetition. Its deeper achievement is to specify…
History
The Secure Channel That Had to Forget the Conversation: How NNTP STARTTLS Reset the Session
A news client has already inspected a server's capabilities, selected a newsgroup and positioned an article. Then it asks for TLS. The TCP connection stays open, but the protocol refuses to carry those earlier conclusions into the protected phase. The group selection disappears…
Story
ARIN’s 28 “Legitimate” Fraud Reports Were Not 28 Findings of Fraud
ARIN’s annual shorthand divided 223 policy-noncompliance reports into 195 outside its fraud process and 28 deemed legitimate. The arithmetic is exact. The meaning is not. ARIN’s own quarterly record shows that the 28 include corrected records, withdrawn routes, unconfirmed…
CASE FILE
The Counter Named the Discard. It Had Not Proven the Cause.
Two interfaces report the same standardized discard class during one service degradation. At the first, a deliberate access rule is doing precisely what its owner intended. At the second, an old rule is catching valid traffic after a routing change. The labels agree; the…
History
The Stream That Started Over Without Closing the Association
A counter could return to zero while its old data remained in the network. SCTP stream reconfiguration made that contradiction a controlled transition: the stream could acquire a new sequence epoch only after a named TSN boundary had accounted for the old one. The association and…
History
The Link That Stayed Up After Rejecting a Protocol
The refusal arrived over a link that had already succeeded. Its two endpoints could frame PPP packets and keep LCP open; they simply did not share support for everything one endpoint tried to place inside. Protocol-Reject turned that mismatch into a bounded instruction: name the…
History
The Article the Server Declined Before It Saw the Body: How IHAVE Separated an Offer from Acceptance
One news server offers three identifiers to a peer. The peer answers that it already has the first, cannot decide about the second just now, and wants the third. Only then does the third article cross the wire. Even that transfer does not settle the matter: after inspecting the…
CASE FILE
Two validators agreed on the version. They did not agree on the routes
Two RPKI validators can report the same RRDP session and newest serial while retaining different repository histories. The disagreement becomes visible only if they remember what hash an already-seen delta carried before. RFC 9697 turns that memory into an operational control…
History
The Address That Grew Old Before It Died
A control room can stop assigning new work to a console without pulling power from the job already running there. IPv6 gave an autoconfigured address the same kind of staged retirement. One clock ended its claim on future communication; another ended the address itself. The gap…
CASE FILE
The Packet Carried the Action. One Router Could Not Read Far Enough to Perform It.
A correctly formed MPLS packet enters a path with a hop-by-hop action in a post-stack header. The first router finds and performs it. A middle router sees the in-stack indication but cannot read the entire post-stack container, so it skips that processing and forwards the packet.…
Story
AFRINIC Can Count 4,498,432 Reserved Addresses. It Cannot Publicly Explain the Count
AFRINIC’s daily statistics can tell an exact story about stock and almost none about state change. On the 20260827 serial, 4,498,432 IPv4 addresses sat behind one word—`reserved`—even though AFRINIC publicly describes three quite different reasons for placing addresses there.
History
The Acknowledgment That Arrived Before the Answer
The phone can still be ringing when a network announcement begins. To a listener, the moments run together. To SIP, they are separate claims: a provisional message was received, media parameters may have been negotiated, early audio may be flowing, and the invitation still has no…
History
The List That Described an Entire Hierarchy but Could Not Force It to Match: How checkgroups Separated Reconciliation from Ownership
Two news servers can receive the same newer, authenticated list of every group in a hierarchy and still end with different catalogues. One removes an old local entry that the list omits. The other keeps it as an explicit exception. The list is complete, scoped and ordered; the…
History
The Mapping the Host Could Request but the Gateway Still Owned: PCP
A PCP request looks like agency at the edge: a host names the service it wants exposed and proposes a public port. The reply reveals the harder truth. The gateway decides which mapping exists, for how long, and under whose policy—and the host must keep earning that state through…
CASE FILE
The Header Asked the Proxy to Stream. It Did Not Prove the First Event Moved.
An origin opens a Server-Sent Events response, sets `Incremental: ?1` and emits its first event. One proxy understands the field and forwards every arrival. The next proxy has never heard of the field, so it waits for the complete response. The response is designed never to…
History
The Error That Could Explain Itself Without Changing the Answer
Two DNS replies can carry the same `SERVFAIL` result and demand opposite repairs. One may mean that no authoritative server could be reached. The other may mean that a validating resolver received data it was required to distrust. For decades, the wire result hid that difference.…
History
The Group That Existed in a Message but Not on Every Server: How newgroup Separated Namespace Declaration from Local Adoption
A Netnews control article could carry a proposed group name across the network, yet the name became usable only where a serving agent chose to adopt it. The gap between declaration and local state was not a flaw around the protocol. It was the authority boundary that made a…