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
Ermanno Pietrosemoli and the Sea Link Whose Peak Was Not a Promise
In a picture used to teach long-distance wireless planning, the equipment has been running for days but the link counter has been running for minutes. Both numbers can be true. Ermanno Pietrosemoli's work on a remarkable radio crossing between Sardinia and Tuscany makes that…
Story
ARIN’s 2026 Revenue Bridge Does Not Reconcile
Three adjacent budget columns invite a reader to perform one ordinary calculation. In ARIN’s published 2026 revenue total, that calculation produces a different destination. The problem is not evidence of missing money. It is the missing public explanation of how one financial…
Story
AFRINIC’s Daily Filenames Advance. The Dataset Still Says 10 September
Three consecutive archive names deliver the same 491,382 bytes, the same internal serial and the same period end date. That proves repeated public content, not a registry outage. The missing distinction is between a fresh no-change release and an older result served again.
Story
APNIC Will Put VRP History in REx. A Timeline Still Needs a Vantage Point
APNIC plans to show current and historical RPKI VRP information for an individual Internet number resource in REx. That could turn a specialist dataset into useful public memory. But a dated line is not self-explanatory: unless it names the observation, derivation and scope…
Story
RIPE NCC Is Running Four Security Programmes at Once. Their Handoffs Need a Public Map
RIPE NCC’s quarterly plan puts audit work, risk management, application security and monitoring on four adjacent lines, all marked “In progress”. That is useful disclosure, but not yet a view of how evidence moves between them. A small public handoff map would let members…
IETF
RPSL’s Registry Prefix Stops After One Hop; the Policy Does Not
A proposed RPSL attribute can tell a resolver which Internet Routing Registry holds the next set entity. It cannot, by itself, tell an operator which registries supplied every entity in the policy that was eventually compiled and deployed.
Story
RIPE NCC Can Audit IPv6 Resources. Its Policy Does Not Link the Procedure
The registry’s authority is not the disputed point. The problem is navigational: two IPv6 clauses tell LIRs what they must produce during an audit, while the document never takes the reader to the procedure that explains why an audit starts, how far it can reach and how an…
IETF
A Power-State Catalogue Does Not Put a Line Card to Sleep
A line card may advertise a low-power mode, a 185-watt planning difference and a two-second worst-case wake-up. None of those fields decides whether the card may leave service while it is carrying traffic. A newly revised individual Internet-Draft makes equipment capability…
IETF
Port 8738 Cannot Name the Multicast Application It Admits
A firewall rule can be syntactically exact and still be semantically empty. “Allow UDP destination port 8738” identifies the shared entrance proposed for multicast applications, but it does not identify which application is meant to walk through it. The current IETF draft makes…
History
John S. Quarterman and the Map That Had to Define the Internet
A dot on a map looks like a fact. John S. Quarterman’s work showed that, on a network without a central census, the fact begins much earlier: someone must decide which service, machine, name, route or person the dot is allowed to represent.
Story
ARIN Used 199 Cleared Blocks to Fulfill 307 Requests. The Split Map Is Missing
ARIN’s July distribution closes one scarcity question and opens an accounting one: the registry says 199 cleared IPv4 blocks fulfilled 307 waiting-list requests, but its public records do not show how the input prefixes were divided into the issued prefixes.
IETF
MPLS STAMP Has Two Local Configurations and No On-Wire Agreement
A measurement packet can cross a label-switched path, reach the right reflector and return with plausible timestamps while the complete agreement that gives those numbers meaning remains stored separately at two endpoints. The MPLS STAMP draft specifies the exchange carefully; it…
Story
IRINN’s 13 Webinar Bars Sum to 3,567. The Same Slide Says 5,000+
IRINN’s APNIC 62 update offers an unusually useful test of capacity-building evidence: thirteen visible webinar counts reconcile exactly to 3,567, while a footer on the same page reports more than 5,000. Both may describe real activity, but the public record does not say whether…
IETF
SMTPUTF8 Draft Makes Invisible Unicode a Mailbox Admission Test
Two email addresses can occupy the same pixels and still contain different protocol input. Revision 05 of an IETF draft now makes that discrepancy part of the admission decision: a code point that renders as nothing does not disappear from the address a system is asked to accept.
Story
AFRINIC’s Transfer Log Reaches 13 September. Its Last Event Is 18 June
AFRINIC’s cumulative transfer file carries a production time and coverage end from 13 September 2026, while its newest transfer event is dated 18 June. Both dates can be correct; the missing evidence is what advancing the first clock proves about the second.
IETF
MPLS-IOAM Turns Unknown Load Balancing into a 19-Bit Constraint
A sequence counter is supposed to distinguish packets, but in an MPLS label stack its changing bits can also become accidental steering input. Revision 14 of an IETF MPLS-IOAM draft now says what to do when nobody can establish how a node balances traffic: keep a specific 19-bit…
History
Hans-Werner Braun and the Numbers That Made a Backbone Governable
Hans-Werner Braun helped operate NSFNET at the moment when a research network was becoming national infrastructure. His most durable lesson is not a router model or a speed record. It is that a backbone becomes governable when its operators can show, in public and with honest…
History
RFC 2061: When a Mail Preview Needed a Cleanup Write
In December 1996, [RFC 2061](https://www.rfc-editor.org/rfc/rfc2061.html) offered IMAP4 clients ways to keep working with older servers. One fallback could retrieve a preview and then require a flag change: preserving access did not preserve every promise attached to it.
Story
ARIN's WhoWas Accepts an IPv6 Address. The History Still Needs a Capability Receipt
A request can be well formed, a report can have the right columns, and the archive behind both can still remain unproved. ARIN’s public record now makes all three propositions about IPv6 WhoWas look adjacent. What it does not provide is the small, dated receipt that would make…
IETF
A Cable Record Is Not Proof the Cable Is There
A repair crew arrives at a roadside cabinet with a clean inventory view: one optical cable, the expected number of fibres, two named endpoints and a location reference. The screen is internally consistent. The trench is real. Yet the label on the closure belongs to an earlier…