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’s prop-167 Status Needs Two Rows
APNIC did publish the hourly directory statistics its community asked to see. The live files make that success unusually easy to verify. They also make a second fact harder to ignore: `prop-167-v002` asked for another output, and the Executive Council gave it a different…
CASE FILE
The Path Kept Its ID. Its Instructions Changed.
The IESG has approved a compact identifier for segment lists carried in BGP SR Policy. The number can simplify telemetry and cross-system configuration, but it stays meaningful only inside its Candidate Path—and it can remain unchanged while the actual SID sequence changes.
History
The Filename the Sender Was Not Allowed to Choose
FTP’s `STOU` command made a remote server allocate a collision-free pathname and report it before transfer, turning one line of reply text into a narrow receipt for a naming decision—not proof that the upload finished, remained stored, or belonged to anyone.
Story
The Date Line in 4.10: When ARIN’s Interpretation Becomes Text
`ARIN-2025-8` would put `within the ARIN service area` into NRPM 4.10 as a codification of existing staff practice. Its timetable says `Immediate`, while its comments say staff has no intention to extend the restriction to allocations issued before implementation. The statements…
History
The List That Was Not Its Address: How List-Id Gave Mailing Lists a Stable Name
When a mailing list changed processors, the place used to submit a message could move while the community stayed put. List-Id turned that mismatch into a design rule: give the list one durable name, then keep routing, actions and authentication under separate authority.
Story
AFRINIC’s Bandwidth Upgrade Cannot Be Closed by Uptime Alone
A service can remain switched on, connected to the Internet and technically available while every useful interaction through it becomes slower. AFRINIC’s February capacity notice described that middle state. Its own service commitment shows why restoring performance requires a…
History
The Route the Relay Was Told to Forget: How SMTP Kept Source-Route Syntax After Removing Its Authority
An old SMTP recipient can still arrive carrying a list of relays before the mailbox. A modern server must understand the form, yet it need not follow the list. That apparent contradiction records a deliberate transition: compatibility preserved the grammar after normal control of…
CASE FILE
The Gateway Said “Post-Quantum Ready.” The Tunnel Still Used ECDSA.
The IESG approved a mechanism for post-quantum signature authentication in IKEv2 on 24 August 2026. The decision advances the standards path for ML-DSA and SLH-DSA, but a supported algorithm, an advertised method and an authenticated tunnel remain three different facts.
History
The New Address That Was Not a Rename: How SMTP Split Forwarding from Referral
Two mail servers can know exactly the same thing—that a mailbox has moved—and still owe the sender opposite answers. SMTP encoded the difference in `251` and `551`: one server accepted responsibility and forwarded; the other refused the old recipient and left the next attempt to…
Story
RIPE NCC’s Five-Year Restriction Now Turns on “Involved”
RIPE-791 attached a later application to two named roles around a former member: contact person and representative. RIPE-863 replaces those roles with a different test—whether a person provided fraudulent or misleading data or was `involved` in providing it. The five-year period…
CASE FILE
IANA Registered a DELEG Capability Key. Deployment Still Needs Proof.
IANA added a temporary `deleg` key to the DNS Resolver Information registry on 24 August 2026. The entry gives operators a common way to declare support for the emerging DELEG protocol; it does not turn an Internet-Draft into a standard or a declaration into running behavior.
CASE FILE
The serial matched. The zone did not
The transfer finished, the file parsed and the SOA serial was exactly the number operations expected. One glue record was nevertheless missing. DNS had long possessed ways to say that a copy was newer and that a transaction came from an approved peer; ZONEMD added a different…
History
Repairing the Instrument Did Not Replay the Performance
RTP MIDI gave a receiver enough history to correct a note that would not end, without promising to replay every note that had gone missing. Its recovery journal drew a useful boundary for the real-time Internet: the state of a performance could be repaired, but the time in which…
History
The Offset That Could Not Name the File: How FTP Restart Assumed an Unchanged Object
After a large transfer breaks, a saved number feels like proof of progress. FTP could use that number to avoid sending the beginning again. But the number named a position, not the file version occupying that position. Resume worked only because both endpoints supplied an…
Story
Six Minutes Are Published. LACNIC’s Summary Column Says Nothing
LACNIC’s 2026 Board page presents six meetings, six dates and six links to approved minutes. Beside them sit six empty `Summary of activities` cells. The records exist; the map into the records does not. That difference determines whether a reader can find a decision without…
CASE FILE
The First Endpoint Was Preferred. It Was Never Eligible.
An HTTPS record can put one endpoint first and still require a client to ignore it. SVCB makes DNS a publisher of bounded connection plans, not a substitute for compatibility, endpoint authentication or running evidence.
IETF
Job Snijders and the Checklist That Could Sign Bytes, Not Truth
A cryptographic signature can settle a narrow argument and still leave the important business question open. Job Snijders and his co-authors designed the RPKI Signed Checklist to prove that a resource-authorized key signed a list of exact file digests. Its usefulness begins with…
History
The Name the Message Had to Mint Itself: How Message-ID Worked Without a Registry
A relay can add a trace field and change a message’s bytes without changing the message. An author can revise one sentence and create a new message even while most bytes remain. `Message-ID` gave that distinction a durable name, then let replies and distributed news servers build…
History
A Return Label Was Not a Shared Instruction
A RADIUS proxy could carry another proxy's private state without knowing what it meant. The common agreement concerned preservation, relative order and return, not a universal interpretation of every value. That small distinction left room for independent implementations while…
Story
ARIN’s 75% Gate Depends on a Plan That Can Change
Sixty assigned prefix units are 75% of a plan containing 80 units. The same sixty are only 60% of a revised plan containing 100. No address has moved, yet the qualification result has. Draft Policy `ARIN-2026-2` makes that possible in principle because its proposed…