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.
Europe and Middle East Regional ISP
ROYA’s AS210837: The Missing Step Between Network Identity and Operating Control
ROYA’s AS210837: The Missing Step Between Network Identity and Operating Control intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…
History
Hawaii Internet Exchange: What Public Routing Records Cannot Yet Prove
Hawaii Internet Exchange: What Public Routing Records Cannot Yet Prove 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.…
History
The Third Duplicate ACK Opened a Temporary Window: RFC 2001’s Recovery Ledger
RFC 2001 did not turn three repeated acknowledgments into certainty. It turned them into a bounded permission: retransmit one apparently missing segment, keep the ACK clock moving through a temporary window adjustment, then remove that extra allowance when new data is…
IETF
The Package Resolved. The Running Schema Was Still Unproven
Revision 09 of the YANG Packages draft gives a schema collection a name, a version and deterministic recursive rules. That is a major improvement over an informal folder of modules. It is also the point at which a clean resolution result can be mistaken for evidence that no…
IETF
Leslie Daigle and the URN Namespace That Needed a Steward, Not a Resolver
A persistent name is easy to mistake for a durable hyperlink. Leslie Daigle’s work on the rules for Uniform Resource Name namespaces made the harder bargain visible: the name survives only if an institution keeps assigning it consistently, never recycles it and preserves the…
Story
AFRINIC’s Green Status Page Leaves a Website Incident in “Recovering”
AFRINIC’s public status API says every system is go. The same API says a July website incident is still present, still recovering and has never ended. Both statements cannot serve as the final operational record without a rule that explains how they reconcile.
Story
AFRINIC's Arabic Policy Index Returns 404 While English Tracks Seven Live Proposals
A policy register can be authoritative in one language and still become unreliable evidence in another. On 11 September, AFRINIC's English current-proposals index answered normally; the official Arabic route did not answer with an older table, a move notice or an English…
IETF
The BIER Attribute Reached the Border. The Neighboring Domain Was Not Authorized: RFC 9793
RFC 9793 gives BGP a way to carry the identifiers and encapsulation inputs from which a BIER router can calculate forwarding state. It also draws a harder line than the attribute's transitive flag suggests: at an EBGP administrative boundary, carriage is denied by default, and a…
IETF
Three Names, One File, No Proof of What Loaded
An unversioned YANG module, a revision-dated copy and a semantic-version copy can be byte-for-byte identical. That is useful repository hygiene. It is not a load receipt, a compatibility verdict or permission to roll the schema into production.
Global Institutional
DFINFRA and AS210860: The Missing Link Between Registration and Operational Control
DFINFRA and AS210860: The Missing Link Between Registration and Operational Control intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…
IETF
Neal Cardwell and the Loss Detector That Trusted Time Over Duplicate ACKs
Three duplicate acknowledgments once served TCP as a rough witness to loss. They are not a clock, and they say little when a transfer ends before a third witness arrives. RFC 8985 replaces that counting habit with a temporal test: later-sent data must be known delivered, then…
Story
Rapport Tests Cache Survival. Its Missing-Manifest Warning Is Still Commented Out
LACNIC’s young RPKI test suite preserves the right routes when a manifest disappears; the quieter question is whether the person responsible for those routes is demonstrably told why they are now coming from cache.
Story
RIPE NCC's Archived May GM Page Is Showing October's Live Registration Table
The October 2026 General Meeting page carried a live country-by-country registration count. At the same instant, the archived page for May displayed precisely the same 37 rows and 231 votes, although May's final report records 3,421 registrations and 3,049 ballots cast. The…
History
The List Expired on 16 June: RFC 2000 and the Two Axes of Protocol Status
RFC 2000 was itself an Internet Standard, yet it carried a use-by date. That was not a paradox. The document was authoritative as a dated classification, not a permanent measurement of what the Internet had implemented.
Global Institutional
DFINFRA and AS210860: The Control Chain Is Defined, but Not Yet Proven
DFINFRA and AS210860: The Control Chain Is Defined, but Not Yet Proven 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.…
CASE FILE
The Underlay Group Was Requested. The Receivers Were Not Proved: RFC 9798
One multicast-valued Receiver RLOC reaches a root ITR. It looks like a destination and may cause real forwarding state, but it answers neither “which ETRs asked?” nor “who received data?” RFC 9798 makes the division of labour precise enough to build a better receipt: preserve the…
Europe and Middle East Regional ISP Trends
Poyraz Hosting’s AS210574: What the Public Record Still Cannot Establish
Poyraz Hosting’s AS210574: What the Public Record Still Cannot Establish 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…
Leaders
What AFRINIC’s Registry Records Can—and Cannot—Attribute to Maina Mukhangu Noah
A public registry listing connects Maina Mukhangu Noah to ORG-BITL1-AFRINIC, but the available record does not establish that he held institutional authority inside AFRINIC. The distinction matters because a contact field can guide operational communication without identifying…
History
The UDP Table Knew the Port, Not the Conversation: RFC 2013
RFC 2013 gave a network manager two kinds of sight: four odometers for an entire UDP engine and a list of local doors where applications were listening. It could say that a door existed and that traffic totals moved. It could not say who stood outside, which process answered, or…
History
A CHAP Success Proved One Comparison, Not the Connection: RFC 1994
The decisive packet in CHAP was called Success. Its name sounded broader than its evidence: one authenticator had compared one response with one locally calculated value for one challenge. RFC 1994 made that comparison useful by binding it to time and direction—and left every…