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
RIPE NCC Has 110 Sanctions Investigations. Its Table Has No Clock.
RIPE NCC’s latest sanctions report makes the size of its screening work visible: the cumulative register reached 2,172 alerts, with 110 still under investigation on 2 July 2026. What the table cannot show is equally consequential. A reader can see where cases sit, but not how…
Story
APNIC Says prop-170 Reached Consensus. APNIC-127 Still Does Not Say “Nibble”
On 14 September, two official APNIC pages described prop-170 as having reached consensus at APNIC 62. A third official page still labelled it “For Discussion at APNIC 62 OPM”. The operative policy supplied a more important answer: APNIC-127 still contained the old IPv6 allocation…
Story
ARIN’s Jacksonville Workshop Has Two Start Times
Three days before the event, ARIN’s dated notice says 9:30 while its live outreach page says 10:00. One labelled schedule can make both times useful.
Story
RIPE WHOIS Gives Invalid API Keys an Audit Identity
A failed credential usually looks like absence: no user, no permission, no successful update. In the current RIPE WHOIS source, however, the failure path can carry one durable-looking fact into its audit representation—the API key ID supplied as the Basic-auth username—even when…
IETF
RFC 9730 and the Evidence Boundary Between Distributed Recovery and Centralized Control
RFC 9730 matters less because it settles an architectural contest than because it makes a mixed-control reality explicit: transport networks can combine distributed GMPLS behavior with centralized coordination, and the operational challenge is therefore to distinguish who…
History
Raj Jain and the One Bit That Needed Two Time Filters
DECbit is remembered as a one-bit congestion signal. The more consequential idea was the timing around it: routers and endpoints each had to decide what a stream of momentary observations meant before anyone changed the traffic load.
Story
AFRINIC’s Hash Tool Is Also a Password-Receiving Surface
AFRINIC’s public generator returns a BCRYPT value, but its current form first asks a browser to send a field called `plaintextpassword`; the missing operational entity is a receipt for who can see that source value before the hash exists.
Story
LACNIC’s Migration Script Reuses a Volume at a Different Path
A persistent Docker volume can survive the container that populated it. LACNIC’s historical migration launcher leaves a narrower question unanswered: does the next application still look where that volume is attached?
History
Scott Shenker and the decision before a flow begins
Ethane and NOX made enterprise networking answer a question that routing alone cannot settle: who may start this connection, and which path makes that permission real?
Story
ARIN’s DS Payload Guide Calls Digest Type 3 MD5. IANA Says GOST
A public provisioning reference gives one DNSSEC code two incompatible identities. The correction is narrower than an API failure, but more consequential than a spelling change: the number determines the digest, and fixing its label would not make the retired algorithm suitable…
Creators
Jiří Pírko and the Linux interfaces exposing switch hardware
A physical switch can forward packets at extraordinary speed while revealing little about the tables, limits and failures inside it. Jiří Pírko's work on switchdev and devlink helped give Linux a common language for that hidden machinery, bringing forwarding state and device-wide…
Story
ISIF Now Starts With a Concept Note. The Foundation Performs the First Review
A shorter opening application can widen access to Internet-development grants. It does not make the entire selection sequence an independent committee decision—and the 2026 rules do not claim that it does.
Story
Sagan Can Mark a Traceroute Successful Without a Reply From the Destination
One Python flag tests a non-error reply at the end of the supplied trace. Another tests the destination address. Keeping those answers separate is the difference between reading a measurement and awarding it a meaning it has not earned.
Story
AFRINIC’s Duplicate nserver Row Is Gone. Redundancy Is Not a Row Count
A February discussion exposed two identical nameserver entries that produced only one DNS referral. The named example is now corrected. What remains useful is the distinction between an avoidable input mistake, an answering server and infrastructure that can survive a failure.
History
RFC 2063: The missing minutes inside a recovered total
When a reader stops while its meter keeps running, accumulated traffic may remain recoverable. The missing collections still leave a hole in the history of when that traffic passed.
Story
Two Minutes Can Become Many in LACNIC’s Permission Cache
A public PAI client can restart the age of a cached permission entry after a malformed authorization reply without obtaining a new permission decision. Its small resilience mechanism exposes a larger question: which clock should govern an application when the authority it…
History
Urs Hölzle and the Fabric That Learned to Change in Pieces
An awkward failure in an early Google network helps explain a less visible infrastructure achievement: making a vast switching system serviceable without treating it as one indivisible machine.
Story
Starla Uses RIPE Atlas Version Numbers. They Do Not Name Its Executable.
A Rust implementation can speak the probe’s language without becoming the same measuring instrument. Starla makes the distinction visible in source: its own package version, its compatibility numbers and its registration identity answer different questions.
Creators
Russ White and the Discipline of Containing Network Complexity
From IPv4 /31 prefixes to today's work on BGP capability signals, Russ White has spent more than three decades at the places where protocols meet real-world operations. His public work defends an unglamorous but vital idea: a new abstraction does not destroy complexity. It must…
Creators
Russ White and the discipline of containing network complexity
Russ White and the discipline of containing network complexity 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…