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 Router Gave the Workstation an Address. It Did Not Give It an Identity: RFC 2106
RFC 2106 solved a real scaling problem by placing many remote SNA and NetBIOS workstations behind one DRAP server. The bargain was precise: fewer backbone peers, more state and judgment concentrated at the boundary.
History
The Tag Moved the Packet. It Did Not Prove the Path: RFC 2105
A packet entered a switch carrying a short tag. The machine used that value as an exact index, selected an interface, replaced the tag and sent the packet onward. That was the elegant part of Cisco’s 1997 Tag Switching proposal. The harder truth sat elsewhere: routing protocols…
History
Two Hash Passes Made a Reusable MAC. The Tag Did Not Make a Trust Decision: RFC 2104
RFC 2104 gave protocol designers a compact way to turn existing iterative hash functions into a message authentication code: one keyed inner pass, one differently keyed outer pass, and an interface that could survive replacement of the hash beneath it. What endured was the…
History
The Locator Moved. Then the Network Moved: RFC 2103
Nimrod’s mobility paper began with an elegant separation: keep the endpoint’s identity stable and update the locator that says where it can be reached. Then it found the case that broke the elegance—a network could move while the endpoint’s locator stayed the same, leaving the…
IETF
When “Lease” Stops Meaning “Address Assigned”
An operator upgrades a DHCPv6 inventory schema and discovers that one familiar dashboard label—“lease”—now conceals two different origins of authority. In one record, the server selected or delegated the resource. In another, the device selected a SLAAC or static address and…
History
The Tree Was Not Standardized. The Forwarding State Was: RFC 2102
Nimrod declined to choose one multicast tree algorithm. Its narrower bargain was more durable: different methods could coexist if routers agreed on the shape and meaning of the state that actually replicated packets.
History
The Cell Skipped the Router’s Work. It Did Not Inherit the Route: RFC 2098
At a Cell Switch Router, one tiny lookup decided whether an arriving ATM cell stayed a cell or became an IP datagram again. A matching VPI/VCI entry sent it straight through the switch; a miss returned it to reassembly and IP forwarding. RFC 2098 built a fast path from that…
IETF
The Default Route Survived. The Leaf Did Not: RFC 9692’s Fallen-Leaf Test
A fat-tree can retain a perfectly valid default route while one plane has lost the path to a particular leaf. RFC 9692 repairs that mismatch with disaggregation, but the receipt of a control-plane exception is only the beginning of the evidence chain.
History
The Link Was Open. Each Name Still Needed Admission: RFC 2097
PPP could bring a remote machine to the edge of a NetBIOS Frames network, but RFC 2097 did not treat link-up as reachability. Before NBF traffic flowed, NBFCP let the remote side ask a peer to project particular sixteen-octet names, return a result for every name, identify its…
CASE FILE
The Score Starts Before the Stopwatch: RFC 9693 and Stateful NAT Evidence
A stateful NAT benchmark can report zero loss and still be incomparable with the run beside it. The missing variable may not be the offered rate. It may be the population of connections that existed before the measured traffic began—and whether the tester could send a valid…
IETF
The New Name Left of the Slash Was Registered. Nothing Else Was Proven
RFC 9694 turns a rare naming decision into an operating commitment. A new top-level media type can change how software groups unknown formats, chooses handlers and presents content to users. The registry entry is real, but it is only the first receipt in a much longer chain from…
History
The Counter Passed One Receiver’s Window. It Did Not Name the Sender: RFC 2085
RFC 2085 placed a 64-bit replay counter inside one HMAC-MD5 Authentication Header transform, but only when the Security Association selected it. A receiver could admit unseen packets within its own reordering window and reject a repeated value. That was useful freshness evidence…
History
The Fourth Letter Decided What the Editor Could Keep: RFC 2083
An editor can change every pixel in a PNG and still face a question that no preview answers: what should happen to a chunk it does not understand? RFC 2083 put part of that decision into the capitalization of four bytes. The last letter governed copying after edits, while the…
IETF
The Average Was Fast. The Frame Arrived Too Late for the Head That Moved
RFC 9699 describes why XR edge delivery is not a shorter-cloud problem. Offloading can spare a mobile device heat and battery drain, but it places tracking, world state, rendering and frame return inside one moving deadline. A good average hides the frame that returns after the…
IETF
XR's edge problem is the demand that averages conceal
RFC 9699 describes why extended reality might need nearby computing. The harder commercial question is who can prove that the late, crowded and thermally constrained moments remain usable.
Story
RIPE NCC Kept the Lameness Checks and Stopped the Emails
In 2009, RIPE NCC separated two activities that are often mistaken for one: it continued periodic checks of broken DNS delegations and ended the bulk email alerts generated from them. The decision is a useful historical operating case in what an infrastructure measurement can…
History
The PostScript Bytes Stayed Still. The Carrier Identity Changed: RFC 2160
RFC 2160 gave a gateway two X.400 containers for one PostScript octet stream: an older Extended Body Part and a recommended FTAM Body Part. Both could cross into MIME without content conversion. That narrow success preserved the payload, but it did not prove which container a…
History
The Directory Stored Two Links. It Could Not Tell You What Either Meant: RFC 2079
A directory entry could carry two impeccable-looking links: one labelled “official record,” another “current service.” RFC 2079 made both values easy to store and split into URI and label. It did not tell a client whether the links described two resources, two locations for one…
IETF
The Router Answered for the Exit. The Link Was Still Unproven
RFC 9703 lets MPLS Ping and Traceroute ask whether an EPE-SID reaches the peer association named by its Target FEC Stack. The reply can validate an egress role, and sometimes the observed incoming interface. It cannot make a skipped interface check, an unreconciled controller…
IETF
The Same Mail, Through Another Door: What JMAPACCESS Actually Promises
A mail client can discover a JMAP route without asking its user to start again. The difficult decision comes afterward: which parts of the old connection's knowledge remain usable through the new one?