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 Hierarchy Was in the Address. The Router Did Not Read It: RFC 2374
RFC 2374 divided an IPv6 address into a public hierarchy, a site hierarchy and an interface identifier. Then it stated the more important rule: routers would match prefixes on arbitrary bit boundaries without knowing that internal structure. The labels organised allocation.…
History
The Codec Had a Name. The Decoder Had Not Arrived: RFC 2361
In 1998, the Internet learned how to point at multimedia formats that had grown up somewhere else. RFC 2361 carried Microsoft's WAVE numbers and AVI FourCC values into MIME's vendor tree. The bridge solved an identification problem. It did not ship software, inspect the body…
CASE FILE
The Tao Was Retired. The Web Page Inherited the Change-Control Problem: RFC 9592
Two engineers can follow the same official IETF link six months apart and both truthfully say they read the newcomer guidance. They may not have read the same words. That is not an argument for freezing the page. It is the reason a living page needs a receipt.
IETF
Open Cloud Mesh announced the share. It did not prove the resource could be accessed
An OCM Share Creation Notification records a grant at the federation layer. The access token, Protocol Server decision, underlying resource operation and recipient result still need receipts of their own.
History
Srinivasan Keshav and the Two Packets That Made a Hidden Queue Observable
The queue was inside a router, beyond the sender's sight. Srinivasan Keshav's answer was not to ask the router for a declaration, but to create a tiny event whose deformation could travel back as evidence: send two packets together and examine the distance between their…
History
The Address Did Not Say Which Machine Would Answer: RFC 2373
IPv6 anycast reused an ordinary unicast-shaped address for an extraordinary promise: deliver this packet to one member of a configured set. RFC 2373 made the economy possible by leaving the winning machine out of the address. The route chose it.
CASE FILE
The LIST Command Returned OK. Some Mailbox Metadata Was Still Missing: RFC 9590
A green completion line is comforting because it is exact. It is dangerous when a larger claim is attached to it. RFC 9590 makes that boundary unusually visible: an extended IMAP LIST command may complete successfully even when the server could not return metadata for one of the…
History
The Counter Rose. The Cause Did Not: RFC 2358 and Fast Ethernet
When Ethernet became ten times faster, its management vocabulary had to change without pretending that every new number was a diagnosis. RFC 2358 preserved one Ethernet identity across speeds, added evidence for 100 Mb/s operation and drew a durable line between a measured…
IETF
RFC 9797: A Randomized MAC Address Can Reduce Linkability Without Becoming Device Identity
A support desk can see the same laptop twice: once under yesterday’s MAC address and once under today’s. That does not mean there are two devices, and seeing one address twice does not prove there is only one. RFC 9797 makes this mundane ambiguity a governance problem: privacy…
History
The Commit Line Was Not the Business Receipt: RFC 2371
In a distributed purchase, the machines can agree on COMMIT while the customer is still staring at a timed-out page. RFC 2371 drew that boundary with unusual precision. Its Transaction Internet Protocol coordinated transaction managers; it did not carry the order, define the…
IETF
The MOQT object number jumped. The media had not necessarily disappeared
Media over QUIC now gives relays three answers for a hole in a fetch: never existed, still unknown, or timed out. Operations teams should resist turning all three into one red “loss” counter.
CASE FILE
The Signature Verified. It Did Not Name the Approvers: RFC 9591
An auditor receives a valid Schnorr signature, the group public key and the exact message. The equation checks. The approval list is still missing. RFC 9591 makes that result possible by design: FROST compresses several signing shares into one ordinary-looking signature. The…
History
The Address Moved. The Key Did Not: RFC 2356
A laptop leaving a private network in 1998 acquired a new address and, to an ordinary firewall, appeared to become someone else. RFC 2356 proposed a more durable name: let the packet present a cryptographic key identifier that survived the move. That separation was powerful, but…
History
The Unsubscribe Button Was Not the Unsubscribe Receipt: RFC 2369
In 1998, a mailing-list command could arrive inside an ordinary message without looking like a command at all. RFC 2369 gave mail clients a small set of structured headers from which they could build a consistent interface. Its deeper achievement was also its limit: the header…
Story
RIPE NCC's Signed Checklist Is Waiting Behind Two Other Jobs
A standard can exist, a community can ask for a service, and a registry can still have no date for delivering it. RIPE NCC's September RPKI plan puts Resource Signed Checklists behind identity and assurance work, with an API as the possible first product. The distinction matters…
History
Jeffrey C. Mogul and the Busy Receiver That Delivered No Packets
The processor was not idle. It was obeying every new arrival with such urgency that the work already admitted could not finish. Jeffrey C. Mogul and K. K. Ramakrishnan called the failure receive livelock: a receiver visibly running at full speed while useful delivery falls to…
IETF
A Regionalized ROA can sign a place. It still cannot prove a hijack
An individual Internet-Draft would add geography to route-origin validation. The useful part is a new, explicit signal. The dangerous shortcut is to treat that signal as the event it is meant to detect.
IETF
RFC 9818: A Delegated Prefix Is Not Usable Capacity Until the Lease, Route and Filter Agree
A provider may hand an IPv6 CE router more address space than one LAN needs. RFC 9818 shows why that allocation is only the first claim in a longer chain: a downstream lease, a next-hop route, a matching filter decision and a lifetime bounded by the parent delegation must remain…
History
The Packet Diagram Was Correct. The Implementations Still Disagreed: RFC 2360
A protocol can assign every bit and still leave its most consequential decision unwritten. When a count is wrong, an option is unknown or memory runs out, does the receiver salvage the message, discard it, reset the session or preserve the old state? In 1998, RFC 2360 treated…
CASE FILE
The Capability List Said EdDSA. It Still Had Not Named the Curve: RFC 9864
An algorithm name can look like a complete answer while leaving the decisive parameter somewhere else. A service that advertises `EdDSA` has said less than many capability systems assume: it may support Ed25519, Ed448, or a locally constrained interpretation. RFC 9864 repairs…