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.
IETF
The Last Call Is for the Question, Not the Filter
The IESG has opened a final comment period on how to describe the limits of inter-domain source address validation. The October 1 deadline concerns an Informational problem statement and requirements, not approval of a universal filtering protocol. The distinction matters at the…
History
One DHCP Packet, Four Different Claims: What RFC 2132 Did Not Identify
A client could put a vendor class, a binding key and a shopping list into the same DHCP message. RFC 2132 gave each a different job. Reading them as one trustworthy portrait of a machine mistakes a configuration exchange for proof of identity or operation.
History
The Command Stayed ASCII. The Reader Needed More Than Bytes: RFC 2130
A mail server's command and the explanation a person reads after it fails can travel in the same conversation. The 1996 IAB character-set workshop insisted they were not the same design problem. Its report, RFC 2130, treated international text as a chain of explicit choices, not…
History
The Circuit Answered. The Flow Was Not Ready Yet: RFC 2129
In Toshiba’s 1997 cut-through proposal, a router could hear that its neighbour recognized a virtual circuit and still have no permission to send a particular IP flow over it. RFC 2129 put those answers in two different exchanges—and made both answers expire.
History
One Call Became Many Interfaces. Several Channels Became One Call: RFC 2127
RFC 2127 made an ISDN connection legible by separating its physical access, signaling, bearer channels and upper protocol into distinct managed interfaces. That clarity came with a warning still useful today: a topology row, a call counter, a channel allocation and a service…
IETF
RFC 10040 Deprecates LCAF Type 5. Experimental Is Not a Migration Plan
RFC 10040 gives LISP a new Geo-Location encoding and marks the older Geo-Coordinates type deprecated. The publication is real, but it does not collapse document maturity, registry state, implementation support, interoperability, migration and responsible location-data use into…
History
RFC 2169: An HTTP Route Is Not a Resource Authority
In 1997, RFC 2169 made an intentionally modest proposal: use ordinary HTTP requests to ask a resolver about a URN. Its value was not that HTTP could settle identity. It was that a familiar transport could carry a narrowly defined question while leaving authority, access and…
History
Version 3 Stayed. The Service Changed: RFC 2126’s Compatibility Trap
An old peer could return a perfectly parseable Class 0 confirmation to a Class 2 request that offered no alternative. The TCP connection was open, the TPKT version was familiar, and the reply was still unacceptable. RFC 2126 made that difference explicit.
CASE FILE
RFC 9647 and the Missing Evidence Chain Between Babel State and Network Behaviour
A Babel route row can report that a path is selected while the operational proof behind that selection remains incomplete: the YANG datastore may show intent, the interface may appear enabled, the neighbour may exist, and the route may be marked feasible, yet the chain from…
History
Permission Came Before the Call: RFC 2125’s Two-Stage Bandwidth Decision
Two peers could agree that another line should be tried and still have no new bandwidth. RFC 2125 made that gap explicit: BAP first obtained a response to the proposed action, then a separate Call-Status message reported what happened when somebody actually placed the call.
History
The Verdict Left the FAS. The Switch Still Had to Make It Real
RFC 2124 put connection policy in an external service, but it never made the service’s answer identical to the connection that followed. Its message chain preserved a more useful truth: a decision, an execution and an accounting record are different events.
History
RFC 2123: A Flow Record Was a Rule-Set Projection, Not the Wire
NeTraMet did not preserve traffic as such. Before a packet could become a flow row, a downloaded rule set decided which protocol mattered, which attributes survived, which direction counted as source, and how much detail the meter could afford. RFC 2123 made that editorial…
History
The Link Opened a Session, Not an Object: RFC 2122’s VEMMI Boundary
A `vemmi` hyperlink looked like an address, but its destination was not a file waiting to be fetched. RFC 2122 used the Web as a dispatch surface for a different system: a local client would open a continuing multimedia session, negotiate service and identity, and later decide…
IETF
When a BGP-SPF Restart Restores Transit Eligibility
A BGP-SPF node can remain reachable for its own services while losing the one signal that kept it out of transit paths. RFC 9815 makes that distinction explicit: omitting Node SPF Status 2 does not declare failure, but it does remove the non-transit constraint. The operational…
History
The Root Was a Coordination Shortcut, Not a World Directory: RFC 2120
X.500 drew a clean Directory Information Tree, but its root carried an awkward human obligation. Every administrator of a first-level Directory System Agent was expected to coordinate with every other one through bilateral agreements or private arrangements outside the standard.…
History
The Reset Was in the Next Packet: RFC 2118’s MPPC Recovery
RFC 2118 gave Microsoft Point-to-Point Compression a continuous memory and a deliberately spare recovery signal. When packet loss broke that shared history, the receiver asked for a reset—but it was the sender’s next `FLUSHED` data packet, not a separate Reset-Ack, that…
History
The Join Had No Receipt. The Tree Survived by Refresh: RFC 2117
RFC 2117 did not build a sparse multicast tree as one transaction. A local membership indication created one record; a Join/Prune refreshed records hop by hop; a source initially reached a rendezvous point inside Register messages; a branch could later move to source-specific…
History
The Browser Remembered the Session. It Did Not Prove the Person: RFC 2109
In RFC 2109’s model shop, a server called a browser-held value `Customer="WILE_E_COYOTE"`. Later requests returned that value while separate cookies accumulated for a rocket launcher and a shipping method. The exchange made stateless HTTP remember a sequence. It did not make the…
History
The MIB Located the Address. The Repeater Still Had No MAC
A management station could ask which hub port had carried a source address, rank the busiest ports and reconstruct a shared-Ethernet topology. RFC 2108 made those answers comparable without pretending that the repeater itself understood a packet.
History
The Address Said Home. The Dial-Up Line Said Away: RFC 2107
RFC 2107 let a remote dial-in client borrow the routing appearance of home. The illusion depended on a Foreign Agent, a Home Agent, a shared secret, a Tunnel ID and state that had to be created and destroyed in the right order.