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 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.
History
The Bit That Ended the Record: How ONC RPC Put Message Boundaries Back on TCP
A TCP reader can receive half a header, three complete calls or the tail of one reply. None of those read sizes says where an RPC message ends. ONC RPC solved the problem with four bytes: 31 bits counted one fragment, while the remaining bit closed one record after that…
CASE FILE
The Packet Came Back Complete. The Evidence Set Didn't: RFC 10029 and Authority Across DNS Types
A resolver asks once for an address, an IPv6 address and an HTTPS service binding. One successful packet returns. That packet can still leave one of the three questions unfinished. RFC 10029 makes the missing distinction operational: a shared envelope can reduce transactions, but…
Europe and Middle East Regional ISP Trends
Trifle's pioneer story needs a current operator-control map
Trifle's pioneer story needs a current operator-control map 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. The Europe…
CASE FILE
The Dialog Was Found. The Transfer Was Not Yet Earned: SIP Replaces and the Authority to Move a Conversation
A help-desk console can show “transfer accepted” while the target has refused the new call and the original caller is still hearing hold music. The messages may all be correct. The failure lies in treating a reference, a dialog match and a completed handoff as one event.
History
The Message That Arrived as Several Messages: How MIME Made Reassembly a Local Act
A large mail entity could cross the Internet as several ordinary messages, each accepted or delayed on its own, and still become one typed entity at the far end. MIME achieved that without pretending the wrappers were the entity: it supplied a narrow grouping grammar and left…
History
The Condition That Turned a Range into the Whole: How HTTP If-Range Kept Partial Bytes in One Version
A client had the first million bytes of a file and wanted the rest. The offset was easy to state; the dangerous question was whether “the rest” still belonged to the same version. HTTP answered with a condition that could turn a request for a fragment into delivery of the whole…
CASE FILE
The Call Refreshed. The Conversation Might Not Have: SIP Session Timers and the Authority to Declare a Session Alive
A voice platform can receive a perfect 200 response to a session refresh while the caller hears silence, the media path has failed and the billing clock keeps running. The signaling record is real. The mistake begins when that one reality is allowed to speak for all the others.
History
The Trail That Grew Backwards: How Usenet Path Stopped a Relay from Sending News Back
A news article arrived at one server carrying the name of the server that had just sent it. That small trace let the receiver avoid an absurd next move—offering the same article straight back—without mistaking a mutable journey record for a return address, a signature or the…
IETF
Ari Keränen and the Candidate Pair That Won Before Success Could Be Claimed
An ICE log can name the transport path a session selected with millisecond precision. It still cannot tell an operator whether anyone heard a word, whether an application admitted the session or whether permission to keep sending remained fresh. The useful record begins where the…
CASE FILE
The Registry Redrew the Range. The Old Allocator Kept Issuing IDs: RFC 10028 and Authority over IPv6 Multicast Coexistence
RFC 10028 gives dynamic IPv6 multicast allocation methods separate numeric territory. That is necessary coordination, but it does not reach into an old appliance, rewrite its pool or show that the intended stream reached a listener. The operational question begins where the new…
Story
AFRINIC's New ASN and /24 Share a Holder ID, Not a Transaction ID
AFRINIC's New ASN and /24 Share a Holder ID, Not a Transaction ID 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. The…
History
The Link That Never Left the Message: How MIME Content-ID Named Embedded Parts
An HTML message could point to a picture using something that looked like a URL, yet no browser had to leave the message to fetch it. MIME made that possible by giving each body part a label, letting another part spell the label as `cid:`, and leaving the receiving application to…
Story
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity 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.…