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
The ACK That Could Not Say Which Packet Arrived: Karn's Retransmission Ambiguity Rule
The same sequence range crossed the network twice. The acknowledgment that returned proved the bytes had arrived, but not which transmission had earned the reply. Karn's rule turned that uncertainty into a discipline: delivery evidence could advance while the round-trip estimator…
Number Resource Society
A Ghostbusters Record Is Not an Incident Command Roster
An RPKI relying party can validate every byte of a Ghostbusters Record and still not know whether anyone is watching the listed channel when action is needed. The signed entity solves discovery of minimal CA-maintainer contact data; operational accountability begins where that…
Story
APNIC’s RDAP Registrant Role Identifies a Registration Party, Not Corporate Ownership
One word inside a nested APNIC record carries real evidentiary weight, but less than its everyday meaning may suggest. The RDAP role `registrant` identifies the entity recorded for a registration; it does not turn the response into a corporate-ownership register or a live map of…
Number Resource Society
A Trust Anchor Rollover Needs an Acceptance Ledger
An RPKI trust-anchor operator can publish a successor key without making every relying party ready to use it. The transition is a sequence of verified observations, not a launch date: a defensible record must show what was announced, what remained stable, which validators crossed…
History
The Packet That Waited for Its Predecessor: Nagle's Small-Segment Rule
A one-byte write did not need a universal delay timer. It needed a rule about whether the connection already had data in flight. Nagle's answer made acknowledgment state—not the wall clock—the gate for another short TCP segment.
Story
ARIN’s Alternate Whois Link Is a Substitute View, Not Independent Corroboration
One ARIN RDAP record points sideways to ARIN’s older Whois REST service. That link is useful, but it does not turn two views from the same registry into two independent witnesses.
Global Regional ISP Trends
PolBox.TV: three registered relationships, one observed neighbour
PolBox.TV: three registered relationships, one observed neighbour 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…
Number Resource Society
An RPKI Publication Point Needs a Commit-to-Visibility Ledger
An RPKI publication server can accept an authenticated update atomically while relying parties still hold an earlier repository view. That is not necessarily a contradiction or a failure. It is a boundary between different authorities, protocols and observation times. A useful…
Story
LACNIC’s RDAP Name Is a Registration Label, Not a Legal or Routing Identity
A field called `name` invites more confidence than it deserves. In LACNIC’s live RDAP record for `200.0.0.0/21`, the value is simply the address interval written as a label. It identifies a registration record; it does not settle who legally owns the addresses or who operates the…
History
The Probe That Could Not Declare an Idle Peer Dead: TCP Keep-Alives
An idle TCP connection can be quiet without being broken. Keep-alive probing was designed to ask whether the peer's transport state could still answer, while denying any single unanswered probe the authority to declare that state dead.
Europe and Middle East Regional ISP Trends
Plusine Systems: three public names, separate responsibilities
Plusine Systems appears in public evidence under a legal name, the Axians commercial brand and the registered autonomous-system name PLUSINE-AS. Those identities can be joined, but the join does not answer every operational question. For a buyer, the useful work is to map which…
Story
AFRINIC’s RDAP Handle Is a Registry Reference, Not a Global Network Identity
The string `196.216.2.0 - 196.216.3.255` looks like an address range because it is one. In AFRINIC’s current RDAP response, however, that same string also serves as the entity’s `handle`. Its meaning there is narrower than the network identity that downstream systems may be…
Number Resource Society
An ASN Transfer Needs a Routing-Identity Handover Ledger
An ASN Transfer Needs a Routing-Identity Handover Ledger 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 Number…
History
The Acknowledgment That Waited for a Second Segment: TCP Delayed ACKs
TCP does not always answer one received data segment with one immediate acknowledgment. The receiver may wait briefly, but that silence is governed by a second-segment threshold, a timer, and exceptions that preserve loss evidence.
IETF
QNAME Minimisation Is a Query-Sequence Contract, Not a Privacy Switch
A resolver may advertise QNAME minimisation while exposing very different names, costs and failure modes from one lookup to the next. The feature matters only when operators can reconstruct the bounded sequence produced by delegation knowledge, cache state and negative proofs.
IETF
An SRv6 Locator Lease Makes DHCPv6 Part of the Routing Control Plane
An SRv6 locator is the address-space foundation from which a segment endpoint creates SIDs. RFC 10038 allows that foundation to arrive as a DHCPv6 lease. The convenience is real, but so is the transfer of authority: pool selection, lease renewal, route installation and withdrawal…
Story
RIPE NCC’s RDAP Country Code Does Not Geolocate the Network
A two-letter country code looks ready for a map. In a RIPE NCC RDAP network entity, however, it is a registration field—not a set of coordinates and not live evidence of where routers, users, traffic or services are located.
North America Regional ISP Trends
Plus Analytics: what an invisible route can and cannot prove about a VPN
Plus Analytics presents privacy as a service outcome. Its public number-resource record presents a different entity: administrative control. The gap between them is where a buyer’s diligence should begin, not where a verdict about the service should end.
Story
APNIC’s RDAP objectClassName Defines a Schema Class, Not a Network Role
The label `ip network` appears near the top of an APNIC RDAP response. It is easy to read it as a description of what an organisation does. Its real purpose is narrower and more useful: it tells software which RDAP entity schema it is processing.
Number Resource Society
An IPv4 Transfer Pre-Approval Needs a Registration-and-Expiry Ledger
An IPv4 transfer pre-approval answers a narrow question: how much address space a recipient may qualify to receive during a defined period. It does not identify a source, complete a transfer or prove that the registry has changed.