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
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…
CASE FILE
WTPF-26 Adopted Five Opinions. Each Final Text Matches Its Last Public Draft
Five documents left WTPF-26 with new numbers, new dates and the word `DRAFT` removed. Their authority state had changed: the Forum had adopted them. Their substantive English text had not. A pairwise comparison of the last public temporary documents with the five final Opinions…
Global Regional ISP Trends
A Damped BGP Prefix Is Not a Diagnosed Fault
Route Flap Damping can make a noisy prefix disappear from an operator’s update stream. That silence is a local control action shaped by penalties and timers—not proof that the circuit, router, policy or origin behind the instability has been found and repaired.
IETF
A QUIC Key-Phase Change Proves New Keys Worked, Not Why They Changed
A successful transition to the next packet-protection keys confirms protocol progress on one connection; it does not explain the policy, incident or deployment that caused the change.
Story
RIPE Database Now Composes Unicode. The Text Chain Needs a Normalisation Receipt
One visible name can arrive as two different code-point sequences. RIPE Database release 1.123 deliberately makes those sequences converge before the value passes through its remaining UTF-8 controls. That is good interoperability. It is also the moment when an evidentiary chain…
History
The One-Second Bet: How TCP Shortened Its Initial Retransmission Timer
Before TCP has measured a path, its first loss recovery rests on a guess. In 2011, the IETF cut that recommended guess from three seconds to one—and required the RTO to return to three seconds before data transmission if a shorter timer expired while the sender awaited…
Europe and Middle East Regional ISP Trends
Proftelecom-Service: the cash-flow test behind local network reliability
Proftelecom-Service sells a simple promise—local internet access—across Labytnangi, Kharp and Obskaya. Behind that retail price sits a less visible operating system of upstream capacity, access equipment, field repair, customer support and billing flexibility. Public records show…
Leaders
Prasanna Premachandra and the School Network That Turned Mobility Into Learning Time
A dropped wireless connection between classrooms looks like a small technical fault. Multiplied across a school day, it becomes lost teaching time, unequal access and a recurring demand on support staff. Prasanna Premachandra’s public record offers a tightly bounded case of how…
Story
RIPE RPSL aut-num Policies Declare Intended Routing, Not Observed BGP Behaviour
An import or export line in a RIPE Database aut-num entity is valuable evidence of a registered policy statement. It is not a measurement of what routers are doing now.
History
The Standard That Required Two Answers: TCP-AO's Cryptographic Baseline
Algorithm agility sounds like freedom of choice. For TCP-AO, RFC 5926 exposed the harder half of that promise: two endpoints could each support sound cryptography and still fail to authenticate a single segment unless they shared one precise MAC-and-key-derivation pair.
Global Regional ISP Trends
A Completed Route Refresh Is Not a Policy Reconciliation
Route Refresh lets a network replay BGP reachability without resetting the session. The exchange can finish perfectly while the operational question remains open: did the intended policy revision reach the right routers, act in the right direction and produce the expected…
IETF
A QUIC Stateless Reset Proves a Token Match, Not Why State Was Lost
A client can recognize that its peer no longer has usable QUIC connection state without learning which machine, deployment or routing decision made that state disappear.
Europe and Middle East Regional ISP Trends
Professional Programming Company: when a registry-linked address block is not proof of delivery
Professional Programming Company Ltd. markets connectivity, cloud and managed IT services in Saudi Arabia. RIPE links an ALLOCATED PA /22 entity to its organisation record, yet RIPEstat saw no public origin for that block on 5 September 2026. The gap is not an outage verdict. It…
History
The Translator That Changed the Authenticated Connection: TCP-AO and NAT
A middlebox can change a packet without changing its route. TCP-AO made the consequences depend on what changed: rewriting a TCP option could be accommodated by authenticating fewer fields, but rewriting an address or port changed the identity of the protected connection itself.
Story
LACNIC’s measurement commons turns regional latency into operating evidence
A latency chart is not a verdict on a country’s Internet. It becomes useful when operators can see the probes, time window and comparison behind it—and when the result leads to a question that can be tested again.
Story
AFRINIC Reported Unauthorised Routes from Reserved IPv4 Space. Full Withdrawal Was Not Yet Confirmed
AFRINIC described route announcements involving parts of 102.224.0.0/12 and several response actions; its notice did not close the record on full withdrawal.
IETF
The New IETF Steering Draft Says Drop. A Legacy Headend May Still Redirect
A failed steering instruction can now produce two opposite-looking outcomes. Revision 18 tells a supporting headend not to fall back to ordinary IP redirection when explicit Segment Routing intent is incomplete or unresolved; it must drop the matching traffic or use a declared…
History
The Reset That Could Not Be Trusted: TCP-AO After a Peer Reboot
TCP normally has a blunt way to tell a peer that an old connection no longer exists: send a reset. TCP-AO makes that answer harder to trust on purpose. When a protected peer reboots and forgets its connection state, the reset it can still send may be precisely the reset the…
Story
AFRINIC's Monitoring Button Is Deployed and Disabled
AFRINIC's deployment monitor contains the control announced in its August release, but not the address that would make the control usable. The public code handles that absence carefully: it leaves the button hidden. That is good failure behaviour. It is also evidence that a…
Story
LACNIC’s RPKI controls make route origin authority operable
LACNIC’s RPKI controls make route origin authority operable 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 Story…