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.
CASE FILE
The Error Returned as a New Question: DNS Report-Channel and the Authority of Feedback
An authoritative server can announce where it wants to hear about failures it cannot see. It cannot make a resolver diagnose, report or believe anything. DNS Error Reporting turns one local validation failure into a second DNS query, then leaves transport, caching and human…
IETF
Susan Hares and the Two Clocks of BGP Convergence
A router can finish explaining a new route before it finishes carrying packets over it. RFC 4098 names the first event in the control plane; RFC 7747 measures the second from outside the forwarding plane. Susan Hares co-authored both documents. Read together, they turn the word…
History
The Newest LSA Had to Disappear Before the Oldest Could Return: How OSPF Reset Sequence Time
OSPF gave every new instance of a link-state advertisement a larger number. The rule was simple until the largest number had already been used. A direct wrap would make the next truth look older than the last one, so OSPF turned rollover into a public ceremony: withdraw the old…
Story
At ARIN, Resource-Level Tech Authority Stops Before the ROA
ARIN's records can give a Technical Point of Contact authority over one network resource while routing-security actions remain organized around the containing organization. A newly confirmed suggestion asks ARIN to bridge that gap. The hard part is not adding another permission…
CASE FILE
The Signature Verified. The Command Was Still Unauthorized: HTTP Message Signatures and the Authority of Covered Components
RFC 9421 can prove that selected parts of an HTTP message survived in a defined semantic form. It cannot decide whether the signer was entitled to issue the command, whether an omitted field changed its meaning, or whether a valid request has already been used.
CASE FILE
The Packet Hid Its Exact Length. The Pattern Still Spoke: EDNS Padding and the Limits of DNS Privacy
An encrypted DNS message can conceal its names and answers while leaving a surprisingly useful silhouette. EDNS Padding changes that silhouette by adding bytes. The difficult question is not whether the packet became larger, but whether client, server, transport and path made…
History
The Report One Listener Could Send for a Crowd: Why IGMPv3 Ended Host Suppression
When a multicast router asked who was listening, the first widely deployed IGMP did not want every host to answer. Each listener waited for a random interval; the first report stood for the group, and the rest went silent. That economy was sound while the only decision was…
Story
One Source IP Accounted for 38.76% of APNIC's WHOIS Queries in an Hour
One Source IP Accounted for 38.76% of APNIC's WHOIS Queries in an Hour 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.…
Number Resource Society
Who can change the Dunnes RIPE record—and what that power does not prove
The authority behind a public internet-resource record is neither unlimited nor merely clerical. In the Dunnes case, protected RIPE Database entities are governed through maintainer authentication, `mnt-by` references and controlled member procedures. Those mechanisms can…
History
The Route That Came Back as Unreachable: How RIP Used Poisoned Reverse
A router learned a path from its neighbour, then deliberately told that same neighbour the path was unreachable. RIP called this poisoned reverse. The apparent contradiction bought fast escape from one kind of loop, while exposing how little any router could know about the…
CASE FILE
The Record Bound the Options. The Client Still Chose the Connection: DNS SVCB, HTTPS and Service Authority
A domain owner can authenticate a list of preferred endpoints, protocols and connection parameters before the first application exchange. That does not make the first preference a command, turn a routing target into the origin, or prove which path a real client can securely…
History
The Row That Existed Before It Could Be Used: How SNMP Separated Creation from Service
A network manager could write every visible cell in a configuration table and still not know whether the device had accepted a usable configuration. SNMP's answer was not to pretend that creation and operation were one event. `RowStatus` gave a conceptual row a lifecycle in which…
CASE FILE
The Counter Hit Its Ceiling. The Filename Opened a New Epoch: RPKI Manifests and Recovery Authority
A correctly signed RPKI manifest can become unusable because a relying party remembers an impossible predecessor. RFC 9981 gives the issuer a narrow way out: change the manifest filename, start a new comparison epoch and preserve every other freshness, location and integrity…
CASE FILE
The Feed Was Valid. The Answer Was Local: DNS Response Policy Zones and the Authority to Rewrite Resolution
An authenticated threat feed can tell a resolver what a publisher recommends. It cannot decide which users lose a name, whether the answer should disappear or be replaced, or who owns the damage when a correct transfer produces the wrong operational result.
IETF
Enke Chen and the Best Path That Kept Its Seat
A BGP router can change its forwarding choice even when the challenger is no better by policy, path length, origin, MED, session type or interior cost. RFC 5004 asks a narrower question: if the only remaining reason to move is the remote speaker's lower BGP Identifier, why move…
Story
AFRINIC's Validator Counted One Fewer Duplicate. The Final Set Stayed at 30,847
Two consecutive validation records moved in an oddly disciplined way. AFRINIC's public Routinator first counted 39,059 valid input VRPs and 8,212 duplicates, then 39,058 inputs and 8,211 duplicates. The final set offered to routers remained 30,847. That unchanged number is not…
History
The Reply That Could Not Edit the Request: How PPP Negotiated a Link
Two machines could share a point-to-point wire and still disagree about the link they were using. PPP did not resolve that disagreement by choosing a master. Each endpoint proposed the changes it wanted, and the other endpoint could accept the proposal exactly, suggest different…
History
The Byte That Had to Repeat Itself to Remain Data: How Telnet Made Room for Commands
Telnet put a terminal's characters and the protocol's own instructions into one TCP stream. That economy created a question every parser had to answer: when the value 255 arrived, was it data or the beginning of control? Telnet's answer was that a literal 255 could cross only by…
CASE FILE
The Digest Matched. The Zone Was Still Wrong: ZONEMD and the Limits of Cryptographic Integrity
A whole-zone checksum can expose truncation, corruption and substitution. It can also authenticate a mistake with perfect precision. The decision for infrastructure leaders is not whether to trust cryptography, but how narrowly to interpret what it has proved.
History
The Lease Could Outlive One Server, but Not Its Deadline: How DHCP Moved from Renewal to Rebinding
A DHCP client does not lose its address merely because one server falls silent. It first asks the server that granted the lease, later widens the request to other authorised servers, and keeps using the address only while the existing deadline still permits it. DHCP made…