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.
CASE FILE
AS210328 After Registration: The Missing Link Between Network Identity and Cloud Service
AS210328 After Registration: The Missing Link Between Network Identity and Cloud Service intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
History
The Packet That Could Not Be Decrypted: RFC 1969’s Cross-Packet Chain
A lost encrypted packet in RFC 1969 did more than remove its own contents. It also took away the input needed to decrypt the next packet—yet the ciphertext of that unreadable successor carried enough state to let the receiver continue after it. This peculiar two-packet shadow…
Global Regional ISP
What AS33169’s Public Routing Record Can—and Cannot—Show About Utherverse Network Operations
What AS33169’s Public Routing Record Can—and Cannot—Show About Utherverse Network Operations intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
IETF
The watts fell. The proof did not: RFC 9845 and the green-network control loop
A power graph can move down while the network’s carbon cost, workload allocation and service risk remain unknown. RFC 9845 makes visibility useful; it does not let one meter speak for the whole system.
Global Institutional
The ASN Is Not the Control Plane
The ASN Is Not the Control Plane intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The Global Institutional intelligence…
Number Resource Society
DFINFRA and AS210860: The Evidence Chain Still Stops at the Registry
A public-record investigation can identify where a network-control question begins. It cannot answer that question by treating a registry name as proof of ownership, authority or active service delivery.
Global Cloud Services
DATAMATIX and AS210973: From Network Visibility to a Testable Operating Business
DATAMATIX and AS210973: From Network Visibility to a Testable Operating Business intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…
History
The Turnaround Was the Budget: RFC 1986 and ETFTP’s Selective Evidence
On a half-duplex radio path, the expensive event was not merely losing a packet. It was surrendering the channel, synchronizing the other direction, and paying again before useful data could resume. RFC 1986 designed ETFTP around that bill.
History
The Uncompressed Packet That Changed the Dictionary: RFC 1967
An LZS-DCP packet can arrive with its data plainly uncompressed and still alter the shared state needed to decode the next compressed packet. RFC 1967 made that choice explicit, split state into numbered histories, and carried recovery signals inside later data packets. The…
Global Institutional
DFINFRA and AS210860: What Routing Evidence Can—and Cannot—Prove
DFINFRA and AS210860: What Routing Evidence Can—and Cannot—Prove intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
IETF
Donald E. Eastlake 3rd and the RBridge Nickname That Could Not Be a Permanent Identity
Two TRILL campuses join, and the same 16-bit nickname suddenly has two claimants. The number has not lied; the inventory that treated it as a permanent device identity has asked it to carry evidence it was never designed to hold.
Europe and Middle East Institutional
What Internetstiftelsen Controls—and What It Does Not
A sparse directory label points toward Sweden’s .se registry, but the evidence separates domain-name stewardship from the Internet’s IP-address and autonomous-system infrastructure.
Story
AFRINIC Calls Its NS2 Dashboard ‘Real-time.’ All Twelve Linked Measurements Are Stopped One-Offs
A page can refresh on demand without measuring the present. AFRINIC’s public NS2 dashboard illustrates the distinction: it advertises “Real-time Anycast Node Monitoring”, yet every RIPE Atlas measurement wired into the interface is a stopped one-off. The result is useful evidence…
Leaders
From Registry Association to Operational Authority: What AS211867 Records Can—and Cannot—Show
From Registry Association to Operational Authority: What AS211867 Records Can—and Cannot—Show intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
A Backup DNS Plan Is Not a Second Resolver
A 9 September APNIC Blog account turns a household outage into a precise infrastructure lesson: resilience begins only when an alternative service is running, reaches the clients that depend on it, survives a controlled failure and can be rolled back.
Story
RIPE NCC’s K-root Refresh Needs Three Acceptance Records, Not One Batch Status
Amsterdam can be refreshed while the three-site programme remains in progress. That is not a contradiction; it is a warning about the unit of evidence. RIPE NCC has named three K-root core sites whose seven-year-old routers and servers were due for replacement. The useful public…
IETF
The manifest followed the telemetry. The verdict did not
Revision 14 gives collected network data a companion record of its platform, schema and collection conditions. That makes a datapoint easier to read later; it does not make the datapoint complete, the clock trustworthy or the resulting decision correct.
History
The Packet Stayed Native, but the Dictionary Moved: RFC 1977's Hidden PPP State
A packet capture can show an ordinary PPP datagram while both endpoints quietly rewrite the codebook that will determine the meaning of the next compressed packet. RFC 1977 made that invisible transition a condition of interoperability.
IETF
Keith Moore and the Encoded Word That Changed the Display, Not the Sender
Two ASCII header lines can open into the same accented name on screen. That visual agreement is useful, but it is the end of a decoding process—not a receipt for who sent the message.
CASE FILE
The Cookie Returned. The Service Had Not: RFC 9853
RFC 9853 lets a DTLS endpoint test a peer address after a Connection ID recovers an existing security context from a datagram whose source has changed. The returned cookie can justify one binding decision at one moment. It cannot explain the change, promise a stable path, or…