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 First Packet Was Only a Candidate: How RTP Made Continuity Earn Trust
One packet can look perfectly respectable. Its version is right, its payload type is familiar, its length is plausible and its source number has not appeared before. RTP nevertheless refused to let that isolated packet define a stream. A receiver first had to see a relationship…
CASE FILE
The JSON Was Valid. The Trunk Still Needed an Owner: RFC 10006 and the Apply Boundary
A service provider can now describe a SIP trunk in a form an enterprise edge can discover, authenticate for and parse. The consequential question begins one step later: who is entitled to turn that description into running configuration?
Story
LACNIC’s TAL Page Shows Two URLs and Links to Two Others
LACNIC’s trust-anchor page presents two addresses as TAL downloads. A reader who clicks them reaches distinct, valid TAL files through legacy Innovaportal targets. A reader or script that copies the addresses printed on the page instead receives the same HTML application shell…
CASE FILE
The Boot Loader Identified Itself. The Relying Party Still Had to Decide
RFC 10013 gives a measured component a portable identity and sampled value inside an Entity Attestation Token. That evidence can be fresh, signed and correctly encoded while the final question — what this device may do — remains unanswered.
History
The Handle That Outlived the Path: How NFS Made Identity Opaque and Staleness Explicit
A pathname tells a client how to search a filesystem. It does not have to be the identity by which later operations reach the file. NFS built that separation into a small opaque value called a file handle, then spent successive protocol versions defining exactly how long the…
IETF
Paul Hoffman and the Root Copy That Could Answer Only Its Own Host
A recursive resolver can keep the entire DNS root zone close enough that a root query never leaves its machine. RFC 8806 permits that local execution path, then surrounds it with unusual restraints: the service cannot answer the next host, cannot invent a byte of root data…
Number Resource Society
A ROA Change Needs an Authorization-and-Withdrawal Ledger
A route can be Valid while the organization behind it has already forgotten who approved the authorization, what changed, or how to reverse it. ROA governance needs evidence that joins intent, publication, observation and withdrawal—not another screenshot of a green status.
History
The Counter That Fell While Traffic Kept Rising: How SNMP Marked a New Measurement Epoch
A link can carry traffic continuously while its byte counter suddenly becomes smaller. SNMP made that apparent contradiction manageable by separating normal numeric wrap, wider observation windows and an explicit marker for the moment a measurement history breaks.
CASE FILE
The Route Advertised 70. The Local Link Could Carry 50: RFC 10005 and Bandwidth Authority
One upstream says it has 70 units of capacity. The receiving router can reach that upstream only across a 50-unit local link, yet policy assigns it 70% of the traffic. The BGP UPDATE is valid, every session remains established, and congestion is still the expected result. RFC…
Story
RIPE NCC’s Two Voting Codes Need a Credential Map
RIPE NCC tells October’s voters to expect two codes in two emails. That is a useful instruction, but it is not yet an account of the control. The names “Code 1” and “Code 2” describe a user journey; they do not show what each credential proves, who can recreate it, or when a…
Story
ARIN’s 29 August Stats Pair Split Across Two 2023 Filenames
ARIN’s public statistics directory contained a small but unusually legible publishing error on 29 August. The current data and checksum were available under their correct 2026 names, yet current-period artifacts also appeared through two extra paths dated 2023—and those two paths…
Story
AFRINIC Is Shrinking Its Data-Centre Footprint. Recovery Now Crosses a Cloud Boundary
AFRINIC's 2025 infrastructure report describes a sensible modernisation: retire obsolete equipment, use a smaller physical estate, place backups off site and test restoration every quarter. The harder question begins after the backup succeeds. Can the registry show that an…
History
The Socket Closed Before the Command Finished: How FTP Kept Completion on the Control Connection
An FTP data socket can go quiet at the exact moment an operator most wants a verdict. The bytes have stopped, the connection has closed, and a file may even be visible on disk. Yet the protocol has not asked any of those observations to decide the command. FTP kept that decision…
CASE FILE
The DNS Said the Domain Was for Sale. It Did Not Have Authority to Close the Deal
RFC 10023 makes a registered domain’s availability visible in DNS. Its compact signal can open a negotiation while the domain remains in use; it cannot identify the rightful seller, bind a price or complete the transfer.
History
The Number That Changed While the Session Stayed: How SDP Separated Identity from Revision
A multimedia description can change its address, codec, direction and timing without becoming a different conversation. SDP made that continuity testable with two deliberately separate coordinates: one names the session lineage, the other names the description's revision.
IETF
Stuart Cheshire and the Half-TTL Rule for Silence
The strangest useful mDNS query is one that already contains answers. A host puts its cached records into the question so nearby responders can decide not to repeat them. RFC 6762 makes that silence conditional: the record must still carry at least half its proper TTL, and nobody…
History
The Hash That Stayed While the Keys Changed: How SSH Bound Authentication to One Session
An SSH connection can replace the cryptographic machinery protecting it without making every shell, file transfer or forwarded channel begin again. The protocol made that continuity explicit: the first key exchange left behind a hash that later keys could not rename.
History
The Number That Grew at Every Cache: How HTTP Age Estimated a Response Without Dating the Object
A browser can receive `Age: 120` for a document written years ago. The apparent contradiction disappears once the field is read narrowly: HTTP did not ask caches to date content. It asked each cache to carry forward, correct and extend an estimate about one stored response.
CASE FILE
The Zone Was Online. One Address Family Could Not Reach Its Authority: RFC 10001 and DNS Partition
The dashboard stayed green because its resolver quietly used IPv4. An IPv6-only resolver followed the same published delegation, reached a missing dependency and stopped. The name had not disappeared; its authority existed on one transport path and not the other. RFC 10001 turns…
CASE FILE
The Route Tree Remembered Every Target It Saw. It Did Not Authorize the Detour
SIP History-Info can show how a request moved from one target to another. That makes it valuable evidence. It does not make the resulting route complete, truthful, permitted or successful.