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.
History
The Rename That Had Not Happened Yet: How FTP Put a File Between RNFR and RNTO
FTP could answer a rename request with a positive code while leaving the file exactly where it was. The first command, `RNFR`, named the source and produced an intermediate state; only the immediately following `RNTO` supplied the destination and could complete the action. The…
CASE FILE
The TLS Session Resumed. The DNS Subscription Did Not
DNS Push can make a changing RRset look continuously current by stopping the client’s TTL clock and replacing polling with a server’s promise to send changes. That promise belongs to one accepted subscription on one live DSO session. A resumed TLS channel is cheaper to rebuild…
Story
LACNIC and the economics of legitimacy after scandal
A balance-sheet test for how a regional Internet registry could restore trust after a verified governance failure without risking continuity.
Story
ARIN’s RDAP Parent Handle Describes Registration Hierarchy, Not Network Transit
Two handles in one ARIN RDAP response can reconstruct how an address block sits inside the registry, but they cannot reveal who carries its traffic. The distinction is small in syntax and consequential in analysis.
History
The Byte the Wire Refused to Define
The server accepted `TYPE L 36`. The next nine octets on the data connection carried not nine file units but two. FTP had standardized the carrier at eight bits while leaving the sender free to declare a 36-bit logical byte and the receiver free to choose an invertible local…
History
The Login That Survived a Filesystem Switch: How FTP SMNT Separated Identity from Namespace
An FTP user could authenticate once, set transfer parameters, then ask the server to exchange the file-system structure beneath the session. The command was called `SMNT`, for Structure Mount. Its sparse specification preserved a surprisingly modern distinction: a principal may…
Story
LACNIC's FORT Can Validate ASPA. Its Router Feed Defaults to Version 0
LACNIC announced a validator that can carry ASPA data towards routers. The release also keeps that route behind a configuration value whose default is zero. That is not a contradiction or a defect. It is the difference between shipping a capability and establishing that the…
Story
A Date Is Not a Review Window: AFRINIC’s Missing Assessment-to-Agenda Record
AFRINIC’s staff impact assessment for `AFPUB-2026-GEN-002-DRAFT01` is dated 23 June 2026. AFRINIC-37 met on 24 June, with the Policy Compliance Dashboard scheduled for 15:15–16:05 local meeting time. The minutes preserve the PDWG Chair’s concern that providing an assessment only…
CASE FILE
The Record Expired. The Resolver Kept It Alive
DNS Serve Stale can preserve service when authorities cannot answer. It can also keep a retired address or denial alive after the publisher's ordinary freshness claim has ended. The difference lies in who owns the exception and whether its evidence survives.
History
The Message That Tried to Arrive Before the Mailbox: How SMTP Abandoned Terminal Delivery
Early SMTP could ask for more than mail. One command demanded that the text appear on a user's live terminal, another treated the terminal and mailbox as alternatives, and a third attempted both. Those verbs made a fleeting human state—logged in and willing to be interrupted—part…
Story
AFRINIC’s RDAP CIDR Array Describes a Registered Range, Not a BGP Route
AFRINIC’s RDAP service can render a registered address interval in the same CIDR notation used by routing systems. The shared notation is useful for comparison, but the registry field does not establish that a route exists, identify its origin or prove that traffic can reach the…
Story
ARIN Calls Its Space Policy Joint. IETF Has Not Adopted the Address Model
ARIN-2026-1 says the proposal is joint with an IETF working group. The linked IETF record says the address model has no formal standing, and the working-group chairs found no clear consensus to adopt it as-is. Both statements can be faithfully recorded only if institutional…
CASE FILE
The SID Chose a Member Link. It Did Not Own the Bundle.
One peering interface was really three physical links. The ordinary Peer Adjacency SID sent traffic to the logical bundle and let its own balancing choose a member. The new member SID could instead place one flow on the lane that looked emptiest. That sharper instruction did not…
History
The Green Light That Was Not Yours: How NNTP Separated Group Policy from Posting Permission
A news server marks one group `y`, the old shorthand for posting permitted, and still refuses the person at the keyboard. Another group carries `n`, yet a specially privileged client may pass. NNTP did not contradict itself. It made the catalogue describe the group's ordinary…
History
The Correct Password That Still Needed an Account
The password had done its job. The FTP server did not reject it, yet it did not say the user was logged in. It returned `332` and waited for `ACCT`—a third piece of access-control information whose authority belonged neither to the user name nor to the secret that followed it.
History
The Address Seen from Outside: What STUN Could Discover but Not Guarantee
When a client behind a Network Address Translator (NAT) seeks to understand its reachable address from the perspective of an external server, it performs a specific exchange: sending a STUN Binding request. This request, originating from a known local address and port, traverses…
CASE FILE
The Certificate Named an Interface. It Did Not Prove the Device.
The commissioning test produced two honest identifiers. The certificate named the factory address of one Wi-Fi interface. The frame arriving at the access point used a private address chosen for that network. Rejecting the connection would punish a real device for using a privacy…
CASE FILE
Two Answers Said NOERROR. Only One Carried the New Zone
RFC 9660 can bind a DNS answer to the zone version that produced it. That makes a mismatch visible without pretending that one version token proves the zone is correct, the fleet has converged or users saw the same path.
Story
Where Member Notice Stops: RIPE-865 and the Burden of a Public Record
RIPE-865 preserves the general position that RIPE NCC members are informed when authorities seek their data or registry action, unless notice is expressly prohibited. Its eEvidence section creates a different notification state: confidentiality applies, and the RIPE NCC cannot…
Story
LACNIC and the economics of IANA recognition and franchise risk
IANA recognition is not a commercial franchise, yet it creates a similarly scarce institutional position: one regional registry becomes the globally accepted gateway between an upstream numbering system and a defined community.