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.
Global Regional ISP Trends
A Graceful BGP Restart Can Lengthen a Blackhole
Graceful Restart is meant to keep traffic moving while a BGP process returns. Its safety depends on a fact the surviving session cannot prove by itself: whether the restarting router still has the forwarding state needed to carry packets. When a helper retains a route longer than…
Europe and Middle East Regional ISP Trends
PKP Ferrit’s registry footprint makes operator identity a due-diligence question
PKP Ferrit’s public records connect a company name, an Internet-number allocation and an observed route origin. They do not collapse those layers into proof that one organisation currently controls every operational or contractual part of the service.
IETF
The Second Address Became the Primary One: What RFC 9873 Changes in EPP Contact Data
RFC 9873 turns a contact update into a more explicit state transition: an EPP contact may carry one additional email address, and an optional `primary` attribute says which address is to be treated as primary. The protocol records that relationship; it does not certify the…
Story
APNIC’s RDAP Active Status Describes a Registry Object, Not Route Reachability
The word `active` looks like an operational verdict. In an APNIC RDAP response, however, it belongs to the registered entity—not to a live measurement of routes, packets or services.
Europe and Middle East Institutional Trends
Piter-IX turns regional peering reach into a resilience question
Piter-IX presents a broad exchange footprint across Russian cities. That reach can shorten interconnection paths and widen choice, but a map is not yet a resilience proof: buyers still need to know which facilities, transport routes and operating processes can fail together.
History
The Chain That Made a Public Key Believable: PEM Certificate Management
A public key does not identify its owner by itself. RFC 1422 addressed that gap for Privacy Enhanced Mail by specifying certificates, certification authorities, validation paths, and revocation information—the institutional machinery needed before a relying party could treat a…
NPNOG
After the RPKI Panel: Did npNOG’s 2020 Routing-Security Moment Survive the Screen?
The official page does not, by itself, prove that entities created ROAs, deployed validation or changed production routing policy afterwards.
Story
ARIN’s RDAP Notices Describe the Lookup Service, Not the Network’s Operating Policy
The warning labels attached to a registry lookup travel with the answer, but they do not belong to the network named inside it. ARIN’s top-level RDAP notices tell a reader how the lookup service may be used, where suspected inaccuracies can be reported and who claims copyright in…
IETF
The Prefix Arrived Before the Query: How RFC 9872 Changes NAT64 Discovery
An IPv6-only host that must reach IPv4 services needs to know which IPv6 prefix its network uses for address synthesis. RFC 9872 turns that knowledge into an access-network signal: learn PREF64 from Router Advertisements first, and use DNS discovery only when that signal is…
Global Regional ISP Trends
A Fast IPv4 Fallback Can Make Broken IPv6 Look Healthy
A dual-stack service can answer every ordinary check while its IPv6 path is unusable. The availability result is real, but the protocol-family conclusion is not: a client may have escaped through IPv4 before the dashboard noticed what failed.
Europe and Middle East Regional ISP Trends
Pishgaman Ofogh Barkhat’s route boundary makes locality a due-diligence question
A local registration record is useful evidence, but it is not a map of every controller who can affect a customer’s data path. Pishgaman Ofogh Barkhat LLC illustrates why buyers should separate those questions before turning “local” into a resilience claim.
Story
LACNIC’s RDAP Conformance List Identifies Response Specifications, Not Network Authority
An RDAP response can look like a compact certificate of power: it carries a registry name, a range, a handle, a hierarchy link and a row of terse technical tokens. But the tokens in `rdapConformance` answer a narrower question. They describe the specifications used to build the…
History
The Pointer That Was Never Out of Band: TCP Urgent Data
TCP urgent data is a small control surface with a long history. The URG flag makes a 16-bit urgent pointer meaningful, but RFC 793 described the boundary it marks in two contradictory ways. That ambiguity crossed from the specification into implementations and application APIs.
IETF
The Bitmap Says a UDP Option Appeared—not What It Did: RFC 9870
RFC 9870 gives IPFIX exporters a compact way to report which UDP Option kinds appeared in a Flow. Its bitmaps are useful precisely because their claim is narrow: they preserve observed presence, not a packet history, a receiver’s processing decision or an application outcome.
IETF
DNS TCP Fallback Is a Capacity Path, Not an Exception
A resolver can pass every small UDP health check and still fail the first answer that matters. When a response is truncated, correctness moves onto TCP; listener capacity, connection state and middlebox policy then become part of DNS availability.
Story
LACNIC’s IPv4 transfer market and the price of scarcity
IPv4 exhaustion does not end allocation politics. It changes the place where they happen: from the distribution of a free pool to the rules governing transfers of resources that are already held.
History
Six Bytes Became an Address Only After the Domain Was Known: RFC 1449
An archive can preserve every octet and still lose the fact. Imagine finding six bytes in an old SNMP configuration: four could be an IPv4 address and two could be a UDP port. That reading is valid only if another field says the value belongs to the UDP transport domain. Without…
Story
AFRINIC's IPv6 Monitor Shows What Its 54% Contains
A routing dashboard now distinguishes an advertised allocation prefix from routes to smaller pieces of it. Its South Africa data show why that distinction is useful—and why neither the combined total nor the narrower category is a service-quality score.
History
The Database Said One Address. The Reply Followed the Packet Back: RFC 1445
The address book and the live packet disagreed. For a new request, the 1993 SNMPv2 administrative model used the address recorded for the destination. For the reply, it ordered something else: use the transport domain and address from which this request actually arrived, even if…
History
The Clock Went Back. The Key Had to Change: RFC 1446
After a power failure, an SNMP agent wakes with yesterday’s shared secret and a clock that thinks yesterday has not happened yet. A captured request, previously too old to accept, can become “recent” again. Its digest never changed. The receiver’s boundary of acceptable time did.…