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.
Story
The Refill Behind LACNIC’s Falling ASN Forecast
The Refill Behind LACNIC’s Falling ASN Forecast 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 Story intelligence…
IETF
Bernie Volz and the DHCPv6 Trigger That Did Not Yet Configure a Client
A server log can make the word “Reconfigure” look final: the server issued the message, so a client must now have new settings. RFC 9915, co-authored by Bernie Volz, is more exact. Reconfigure is a carefully authenticated trigger for a later exchange. It is not, by itself, a…
History
The Route Named a Next Hop. The Link Still Had to Agree: RFC 1433
Two machines could occupy the same data-network service and still be unable to exchange a frame. RFC 1433 began from that uncomfortable fact: routing could identify a shorter next hop, while address resolution and link filters retained the power to make the route usable—or turn…
IETF
CATS OAM Can Verify a Steering Policy. It Cannot Choose a Remedy.
The active CATS OAM draft is trying to close a real visibility gap. A service instance can remain reachable at the network layer while the application behind it is slow, exhausted or unavailable. A system that steers traffic only by network reachability may therefore send clients…
Creators
Albert Greenberg and the network as a distributed computer
Across AT&T, Microsoft Azure and Uber, Albert Greenberg has worked on a recurring problem: how to make a large network behave like one coherent system when topology, traffic, control software, hardware and failure all change at different speeds. His influence is best understood…
CASE FILE
The Capability Was Advertised. The Protocol Was Not Authorized: RFC 9885
A zero-length IS-IS capability can be visible on every change-board screen and still be limited public evidence to authorize one configuration command. RFC 9885 makes that limit explicit: the advertisement is management information, not a protocol trigger, while safe MP-TLV…
Leaders
Amit Thapa Chhetri and the Long Build Behind Nepal's Cable Internet
Subisu's origin was not a clean founder myth. The public record instead shows a team testing an idea against a regulatory system that was not yet ready for it, then carrying the operating work forward until the venture became an institution. Amit Thapa Chhetri's role is useful…
IETF
Wassim Haddad and the Prefix That Did Not Yet Authorize Forwarding
A mobile router can have a home-agent registration before it knows which mobile-network prefix it may use. RFC 6276, co-authored by Wassim Haddad, makes the next boundary explicit: only a valid DHCPv6 Prefix Delegation lease allows that prefix into the home agent's binding cache…
Story
Inside AFRINIC’s Reverse-DNS Cleanup
The registry’s public data distinguish delegation records, domain entities and resource holders. They also distinguish an error inventory from removal events. Those differences explain why a falling count can reflect worthwhile maintenance without measuring the restoration of…
History
The Interim Fix Bought Time. It Could Spend the Future: RFC 1380
The Internet of 1992 had more than one deadline. Router tables and Class B allocations were under immediate pressure; a larger address space and a richer Internet layer demanded slower architectural work. RFC 1380 refused to hide that mismatch inside one programme. It recommended…
History
The Network Found the Book. It Could Not Keep the Shelf Current: RFC 1432
In March 1993, a bibliography about the Internet carried an unusually revealing provenance: much of its detail had arrived through the Internet itself. The network could help a reader discover a book, yet RFC 1432 also preserved the reasons discovery could never certify the…
CASE FILE
The Path Label Reached the Egress. The Transit Route Stayed Unseen: RFC 9884
One green LSP Ping result can answer a narrow and valuable question: the egress processed a Path Segment Identifier in the control-plane context named by the probe. It cannot reveal the transit route that delivered it. RFC 9884 makes that boundary operationally useful—provided…
IETF
Thomas Graf and the MPLS Label Number That Did Not Identify Its Control Plane
An MPLS label can look like an answer: a compact number at the top of a stack, captured in an export record and ready to be counted. Thomas Graf’s RFC 9160 begins with the smaller, more useful proposition. The number alone does not reliably tell an observer which control-plane…
Story
ARIN Publishes IPv6 Requests Beside Delegations. The Cohorts Are Not Joined.
An IPv6 request can enter ARIN’s system, pass automatically or move into staff review, prompt a request for more information, receive approval, wait for fees and a signed agreement, and only then become an issuance. ARIN publishes useful numbers at the entrance and the exit of…
History
The Transport Opened a Connection. SNMP Still Owned the Retry: RFC 1283
A connection is an enticing piece of evidence. It has a beginning, a lifetime and an end. In 1991, RFC 1283 placed SNMP on an OSI connection-oriented transport and then warned implementers not to read too much into that new structure. The connection could carry one or more…
CASE FILE
The Request Was Signed. The Other Private Key Was Still Only Asserted: RFC 9883
A certificate request can carry a valid signature and still offer no technical proof that the requester holds the private key named by its new public key. RFC 9883 does this deliberately. It turns the gap into an explicit policy choice—and a revocation dependency that operators…
IETF
Tommy Pauly and the QUIC ACK That Did Not Reach the Application
A QUIC acknowledgement can close one precise transport question while leaving the question an application actually cares about open. RFC 9221, co-authored by Tommy Pauly, makes that seam unusually visible for DATAGRAM frames: the receiver's transport processed a frame, but the…
History
The Client Found the Person. The Score Still Belonged to One Directory: RFC 1431
A successful search can be the beginning of an evaluation rather than its conclusion. In February 1993, RFC 1431 asked what an X.500 directory client had actually accomplished when a person's entry appeared—and what the answer had cost inside one particular directory.
CASE FILE
RFC 9882 Put SHA-512 in the Field. It Did Not Always Use It
A CMS record can truthfully name SHA-512 while that algorithm contributes nothing to the signature being checked. RFC 9882 requires exactly that combination on one of its two ML-DSA paths. The apparent contradiction disappears only when an auditor follows the bytes rather than…
IETF
Gorry Fairhurst and the Circuit Breaker Trip That Did Not Name the Fault
A transport circuit breaker is useful precisely because it knows less than an incident report. RFC 8084, written by Gorry Fairhurst, defines a way to halt or sharply reduce traffic after a configured measurement has remained beyond its threshold. It does not turn that reaction…