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 Deadline That Was Not a Retransmission Timer: TCP User Timeout
TCP can decide to retransmit a segment and still decide, on a different clock, that the connection has waited too long. The first decision schedules another attempt. The second ends the connection. RFC 5482 made that persistence preference visible to a peer without turning it…
Story
LACNIC Whois owner-c Marks Administrative Authority, Not Network Operation
LACNIC Whois owner-c Marks Administrative Authority, Not Network Operation 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…
IETF
QUIC Handshake Confirmation Is Not Application Readiness
A green dashboard can hide an important distinction: HANDSHAKE_DONE marks a transport and cryptographic transition, not a completed application transaction. Confirmation retires Handshake keys, but it does not certify early-data acceptance, backend health, durable storage, or…
Europe and Middle East Institutional Trends
Center-invest: a routing object is not a resilience audit
A single public routing record can contain a strikingly complete resilience story: three upstreams, RPKI controls and regulatory framing. Center-invest Bank's record is useful precisely because it shows where a due-diligence checklist begins—and where proof still has to come from…
Global Regional ISP Trends
A BMP Feed Is Not a Forwarding-State Audit
BGP Monitoring Protocol telemetry can make routing decisions visible at useful depth. It still cannot, by itself, certify that a selected route became a working packet path.
History
The Offer That Was Not a Negotiation: How TCP MSS Bounded Each Direction
Each side of a TCP connection can place a four-byte option in its opening SYN. The number does not settle a shared packet size. It says how much TCP data the option's sender is prepared to receive in one segment—a directional boundary that the other endpoint must combine with…
Story
AFRINIC Whois notify Sends Change Notices, Not Operations Responsibility
AFRINIC Whois notify Sends Change Notices, Not Operations Responsibility 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…
IETF
QUIC Idle Timeout Is a Silence Limit, Not a Session Lifetime Promise
A thirty-minute `max_idle_timeout` can look like a promise that a session will remain usable for thirty minutes. It is narrower: a boundary for how long QUIC endpoint state tolerates qualifying protocol silence.
IETF
Which Marking Wins? RFC 9895 and DLEP's Ethernet Credit Boundary
One packet matches both its Diffserv field and its tagged IEEE 802.1Q fields. Under RFC 9895, Ethernet classification takes precedence, so the Ethernet result determines the credit window against which transmission is accounted.
Story
RIPE Database sponsoring-org Records Administrative Sponsorship, Not Network Operation
The word “sponsor” can sound like ownership, financing or operational command. In the RIPE Database, `sponsoring-org` has a narrower and more useful meaning: it identifies the organisation administratively responsible for sponsoring an independent Internet number resource under…
IETF
A TTL of 255 Proves Network Proximity, Not the Identity of a BGP Peer
A packet can carry the address of a configured BGP neighbor and still be an impostor. RFC 5082 gives the receiving router a cheap test before scarce control-plane resources are consumed: start protected traffic at TTL 255 and distrust packets that arrive from farther away than…
History
The Handshake That Had to Remember Its Previous Handshake: How RFC 5746 Bound TLS Renegotiation
A TLS handshake could authenticate its own conclusion while saying nothing cryptographic about the bytes that came before it on the same connection. RFC 5746 repaired that gap by requiring every renegotiation to carry evidence from the immediately previous handshake.
Europe and Middle East Regional ISP Trends
PS Processing: an unobserved registered block is not spare capacity
An address range can sit in a registry without appearing in the same public routing view as its neighbours. PS Processing’s records show why the gap belongs in a reconciliation ledger, not in a capacity forecast.
IETF
Advertise, Subset or Reset? RFC 9894 and DLEP's Diffserv Credit Boundary
A modem can advertise more DSCP-linked credit windows than a router can realize. The operator therefore has to select a supported subset or reset the session; silently pretending that the two capability shapes match is not a safe operating state.
Story
A Splice Is Not a Recovery. Venezuela’s Atlas Study Needs the Events in Order
On 22 July, Cirion said the two ends of a Venezuelan submarine cable had been fused and end-to-end tests had passed, while pre-immersion work still lay ahead. On 23 July, the operator called the country completely reconnected. A later account uses 24 July for confirmation of full…
Story
APNIC Whois mnt-lower Marks Maintainer Hierarchy, Not Routing Hierarchy
The word “lower” invites a network diagram: upstream, downstream, and packets moving between them. In APNIC Whois, `mnt-lower` describes something narrower. It identifies a maintainer in the registry’s update-authorisation structure. That is useful accountability evidence, but it…
IETF
When May the Router Send? RFC 9893 and DLEP's Credit-Window Control Loop
A packet may be ready at the router, but transmission is permitted only after the router finds the matching classifier and FID credit window, confirms enough credits, and counts the packet with its MAC overhead.
IETF
QUIC Flow-Control Credit Is Permission, Not Reserved Capacity
A large `MAX_DATA` value can look like a capacity certificate. In QUIC it is narrower: an absolute ceiling on stream offsets the peer may send.
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…