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.
Europe and Middle East Regional ISP Trends
Protelecom: two ASNs do not prove two failure domains
Two autonomous systems can make a network look diversified before anyone has shown that the underlying infrastructure is independent. Protelecom’s public records offer a compact example of why buyers should separate routing identities from tested resilience.
History
The Neighbor That Stayed in the Cache After It Became Unreachable: How RFC 7048 Separated Failover from Forgetting
IPv6 Neighbor Discovery once treated the last unanswered unicast probe as both a warning to seek another path and a reason to erase the path it already knew. RFC 7048 split those decisions: a neighbor could become officially unreachable without its final link-layer address being…
Story
ARIN Net Type Records Registration Path, Not a Current Customer Relationship
“Reallocated” and “reassigned” look like labels for a business relationship. In ARIN’s registry, they do something narrower: they describe how an address block entered a downstream registration chain and what the recipient intended to do with it. That history is useful, but it is…
IETF
Who Tells the Router Which Queue? RFC 9892 and DLEP's Traffic-Classification Boundary
A modem can supply a replaceable Traffic Classification Identifier (TID) set to a router. Flow Identifiers (FIDs) then group DSCP or VLAN/PCP matches; when both classifier families match, Ethernet VID/PCP wins. The important boundary is that RFC 9892 describes how classification…
IETF
A QUIC ACK Proves Packet Processing, Not Application Delivery
A packet entering an ACK range has crossed a strong transport boundary. It has not necessarily crossed the boundary into the receiving application.
Story
APNIC Built the RPKI Revocation Mechanism. Its Authority Is Still Catching Up
APNIC says the technical implementation of prop-166 is complete, but its public record still places the policy in implementation while updates to the Certification Practice Statement and RPKI Terms and Conditions remain outstanding. The gap matters because the proposal would…
History
The Address That Spoke Before It Was Proven Unique: How Optimistic DAD Bounded Early Use
A newly attached IPv6 host used to wait for a uniqueness test before speaking. RFC 4429 shortened that silence without pretending the test had already passed: the address could carry traffic, but not yet exercise the Neighbor Discovery powers of an uncontested owner.
Story
LACNIC WHOIS nslastaa Records the Last Successful Check, Not Current DNS Health
A date in a registry response can look like a present-tense assurance. LACNIC gives `nslastaa` a narrower meaning: it is the last date on which a correct reverse-DNS configuration was observed on a listed server. That historical success is useful evidence, but it is not a promise…
Europe and Middle East Regional ISP Trends
Pronet: why a 14-day route window beats a static footprint
Pronet: why a 14-day route window beats a static footprint 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 Europe…
IETF
A QUIC Version List Is Not a Server Capability Receipt
A Version Negotiation packet can explain why one connection attempt changed course. It cannot authenticate a server, certify a fleet inventory or prove which version a successful connection finally used.
History
The Clock Moved Only for Useful News: How TCP Tied Its Timer to New Acknowledgment
An acknowledgment can arrive without changing what a TCP sender knows. RFC 6298 made that distinction control the retransmission clock: progress receives a fresh interval, repetition does not.
Story
LACNIC’s IRR turns route filters into a derived registry view
A route filter can look like a policy decision even when several of its inputs were generated from other registry systems. LACNIC’s Internet Routing Registry makes that provenance part of the operating question.
Story
AFRINIC WHOIS source identifies a database namespace, not a record’s provenance
AFRINIC WHOIS source identifies a database namespace, not a record’s provenance 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…
Europe and Middle East Regional ISP Trends
Promsvyaz Engineering: what four more-specific routes reveal about control
A registered address block can look singular in a ledger while behaving as several operational units on the Internet. Promsvyaz Engineering’s records show why buyers should inspect the route beneath the aggregate before treating address count as one asset.
Story
LACNIC Geofeeds makes IP location a maintained claim, not a registry fact
An address holder’s legal domicile is not necessarily where its packets meet users. LACNIC Geofeeds creates a public path for member administrators to state where address blocks are actually used—and makes maintenance part of the claim.
History
The Old Mean Had to Move Last: How TCP Kept Its Timeout Variance Honest
A new round-trip measurement does two jobs inside TCP: it changes the expected delay and tests how wrong that expectation was. RFC 6298 fixed the order so the sample could not soften its own surprise before variance was recorded.
IETF
A Valid QUIC Retry Tag Does Not Authenticate the Server
The Retry integrity check binds a packet to an observed Initial, but identity, token acceptance and client-address validation remain separate facts.
Europe and Middle East Regional ISP Trends
Promservice: the cost of keeping address capacity commercially ready
Promservice Ltd. appears in RIPE records associated with sizeable IPv4 and IPv6 allocations. Yet a dated RIPEstat view did not see two exact aggregate prefixes announced. That contrast is not evidence of failure. It is a due-diligence prompt: registry association, route…
Story
APNIC Counted 9.7 Billion DNS Queries. It Still Cannot Name the Retry Layer
APNIC Labs changed only the answer and watched the traffic change with it. Silence brought 9.69 billion queries to an authoritative server; a positive answer brought far fewer per test. The ratio is startling and reproducible. The identity of the system that repeated the work is…
Story
APNIC prop-175 Moves the IPv6 Evidence Test to the First Request
APNIC prop-175 would let an eligible organisation justify an initial provider-independent IPv6 assignment larger than `/48` when the operational requirement is already documented. The proposal is still only on the Policy SIG mailing list. Its promise is less duplicated procedure…