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 Has an ASN Endpoint and an Empty Changelog. They Do Not Prove the Same Release
APNIC Has an ASN Endpoint and an Empty Changelog. They Do Not Prove the Same Release intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
IETF
The old connection is the test
An accepted QUIC configuration and a healthy service can coexist without proving that the connection already carrying work adopted the change. Revision 08 of the QUIC YANG draft puts that missing proof inside the implementation: the operational question is what changed in the…
IETF
A Call-Home Datagram Is Not Device Authority
A managed router may need to reach an operator from behind an address translator or firewall. The newest NETCONF working-group draft adapts Call Home to QUIC by having the device send an empty UDP datagram and the management system connect back to its source. The mechanism is…
CASE FILE
The Log Filter Made Tomorrow’s Evidence Decision
RFC 9742 gives network operators a common language for configuring syslog. The harder question is whether that language preserves the particular evidence an incident will make valuable.
IETF
A Fast-Path Timestamp Is Not an Authenticated Measurement
A network can make a measurement faster by keeping a probe in silicon. That is an engineering gain, not a cryptographic transformation. The proposed Timestamp and Forward mode for segment-routing STAMP lets a reflector write a receive time in the data plane and send the packet…
Story
RIPE NCC Lets Operators Sign ASPAs Without Showing the Providers It Sees
RIPE NCC has made ASPA signing possible and tells operators to list every real upstream. Its public guide also says the Dashboard offers no BGP-derived hint about who those upstreams might be. The missing interface is not an automatic answer but an evidence receipt that helps a…
Story
RIPE’s NRTMv4 Source Gate Reads a Replica. Its Fallback Does Not Cover the Gate
A three-file code change gives RIPE NCC’s NRTMv4 service a sensible read path and leaves one unusually precise question behind: when a source is new, what proves the catalogue reached that path before the service begins treating it as authoritative?
IETF
An Unset FRR Flag Cannot Name the Local Policy That Won
A traffic-engineering head end asks every repair point to keep a backup path below a delay bound. The reservation comes back with one repair point’s new flag unset. Traffic may still have a backup there, computed under local policy, but the ingress cannot tell from that bit which…
CASE FILE
RFC 9744: the circuit identities a shared tunnel must retain
Fewer service labels can make a carrier network cheaper to operate. The saving becomes less convincing when the remote edge can no longer tell which customer circuit needs a different path.
Story
AFRINIC's 2026 Closure Data Spells Voluntary Two Ways
AFRINIC has done the useful thing by publishing reproducible statistics on closed memberships and returned number resources. But its current 2026 data place `VOLUNTARY` beside `VOLUNTART`, and the dashboard treats the two strings as different categories. That one-character split…
IETF
A Verified RDAP Contact Needs an Audience Boundary, Not a Universal Badge
A registrar can verify an email address once and face two different disclosure questions the next morning: what may an anonymous reader learn, and what may an authenticated investigator learn for a justified purpose? The verification event is the same. The authority to disclose…
CASE FILE
RFC 9746: the compatibility cost of choosing EVPN split horizon
A default-method entity can send an upgraded Ethernet segment back to its encapsulation baseline. The operational question is whether the network has kept the resources and evidence needed to make that return safely.
IETF
An Authenticated BGP Update Is Not an SD-WAN Tunnel Admission Record
When a protected control-plane session delivers a syntactically valid route, it is tempting to treat the event as one completed act of trust. In an SD-WAN, however, the update has only crossed the first of several institutional boundaries. The harder question is not whether BGP…
IETF
A Writable Port Map Needs an Override Receipt
The service orchestrator has found a promising attachment point. One reference tells it which physical port lies beneath the logical choice, and the next capacity query may decide whether the order proceeds. In the IETF’s new Last Call, that small reference is normally…
IETF
A BMP Percentile Is Local Until Its Sampling Method Travels With It
A router can report a P95 that is correctly encoded, correctly attributed and still unsafe to compare with the P95 from the next router. The missing link is not another decimal place. It is the method that selected the observations from which the percentile was made.
History
RFC 2056 and the Fork in a Z39.50 URL
In 1996, RFC 2056 gave two URL schemes to Z39.50 because one locator could conceal two very different kinds of work. One scheme entered a continuing, stateful inquiry; the other attempted a tightly bounded retrieval of a server-identified item. The distinction is a small piece of…
CASE FILE
RFC 9747: the neighbour returns a packet, not a health declaration
Unaffiliated BFD Echo removes the need for the far end to speak BFD. That useful simplification leaves the local operator owning both the test and the decision made from its result.
IETF
IPv6-Only Is a Scoped Forwarding Claim, Not an IPv4 Decommission Certificate
The phrase “IPv6-only” sounds like a clean finish line. In an operating network it can describe something much narrower: one link natively forwards IPv6 while IPv4 still reaches users through translation, another plane remains dual-stack, and a management path still depends on…
History
The Walk Could Not Be Repeated: RFC 2041’s Contract Between Trace and Experiment
A wireless failure observed along one route could be taken back to a laboratory, but only after researchers decided what the record meant and which effects a wired testbed could reproduce. RFC 2041 made those decisions unusually visible.
Story
A Correct RIR Record Did Not Fix One Geo-IP Error After Two Months
An APNIC 62 case study exposed a small but consequential accountability gap: the registry data could be right, several geolocation databases could agree, and one downstream service could still send a customer to the wrong country.