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
Rerouting Wasn’t Session Recovery: RFC 3234
When a router failed, the familiar remedy was to find another path. In February 2002, RFC 3234 asked what happened when the failed device did more than route. A middlebox could hold state that the session needed, so restoring reachability did not restore the conversation.
IETF
The Final Filter Was Correct. The Update Still Leaked a Route.
Revision 03 of an IETF GROW draft turns BGP security from a static configuration question into a transaction question. A router may begin and end with the intended policy while briefly enforcing something else between commands.
IETF
The Tool Knew the SID. It Still Did Not Own the Actuator.
CORECONF-M2M proposes a compact route from YANG models and SID identifiers to MCP tools that an AI agent can call. The route can remove bespoke serialization without removing the harder boundary: who may act, what the device accepted and whether the physical world actually…
History
The Country Prefix Found the Resolver. It Did Not Prove the Archive Kept the Object: RFC 3188
The prefix `fi` could tell a client where Finland's branch of the NBN world began. It could not make a harvested Web page survive, authenticate the service answering today, or prove that the returned file was the original. RFC 3188 made a federation of local library numbers…
History
The ISBN Named an Edition. It Could Resolve to Many Copies—or the Wrong Book: RFC 3187
A persistent name was supposed to survive changing locations. RFC 3187 made the bargain concrete and awkward: one ISBN URN might lead to many URLs, no digital entity at all, or two bibliographic records because a publisher had reused a number by mistake. Persistence belonged to…
IETF
The Agent Went Silent. The Trust Score Punished What the Verifier Could Not See.
The proposed Network Behavioral Trust Protocol turns missing heartbeats and co-silence into score decay, SUSPECT and QUARANTINED states. That may be useful operationally, but an absence first describes a verifier's observation surface—not an agent's character.
History
RFC 1180 Explained TCP/IP, Then Sent Readers Back to the Standards
In January 1991, T.J. Socolofsky and C.J. Kale offered network professionals a practical way to follow an IP datagram from one host, through a router, to another. They also drew a bright line: the memo explained TCP/IP; it did not define it.
History
The Customer Saw a Private Wire. The Operator Held the Hidden Address Pair: RFC 3186
At one edge, customer equipment emitted an ordinary PPP frame. At the other, customer equipment received one. Between them, switches replaced the frame’s first octets, forwarded it through a shared MAPOS fabric, restored the original values and withheld the machinery from view.…
IETF
The Key Changed. The Instance Stayed the Same Because Someone Kept the Ledger.
OAuth attestation can prove that a client instance holds a current key. A new profile tries to preserve that instance's identity when the key changes. The continuity does not live in the identifier string: it lives in an attester's enrollment records, lifecycle rules and custody…
IETF
The Chain Proved a Clock Was Wrong. It Did Not Name the Culprit.
Roughtime can seal an inconsistency into portable evidence without pretending that cryptography has already decided whom to distrust.
History
The Firewall Was Allowed to Say No. It Wasn't Supposed to Break the Conversation: RFC 2979
In October 2000, an Informational RFC drew a line that packet filters often blurred: a site could refuse traffic for security reasons, but a firewall should not accidentally make legitimate, standards-compliant communication fail. That distinction assigned the repair bill to the…
IETF
The ICV Was Valid. The Path Record Could Still Be False.
IOAM can carry a cumulative integrity chain across the network and let a Validator confirm that protected fields were not modified. That is valuable evidence. It is not the same as proving that every expected record arrived, every participating node told the truth, or the…
History
The Name Entered RSVP. Authority Still Had to Decide What It Meant: RFC 3182
In 2001, an RSVP request could carry a user name, an application name, a Kerberos ticket or a certificate toward the router deciding whether a flow deserved scarce resources. That sounds like identity becoming authority. RFC 3182 documented something more conditional. The name…
History
A Secure Peer Link Could Still Carry an Untrusted MASC Claim: RFC 2909
MASC divided multicast address space into temporary, nested claims. Its 2000 security section identified a harder boundary: protecting the next peer did not make every relayed update trustworthy.
IETF
The Controller Reported Both Directions Done. The Network Had Not Proved Hitless
Fine-grain optical transport can change a low-rate service’s bandwidth without a planned interruption. Yet the green completion event at the multi-domain coordinator is only one controller’s conclusion. It is not a receipt for every direction, domain, protection path, tributary…
History
The New Flow Won Admission. Its Defending Priority Still Had to Survive the Next Arrival: RFC 3181
A flow could arrive late and still displace an earlier reservation. RFC 3181 made that reversal deliberate, but it did not give one number permanent authority. The new flow competed with a preemption priority; after admission, another value became its defence against the next…
History
One AS, 256 Multicast Addresses—and a Four-Byte Limit
GLOP made a static multicast block calculable from an existing network number: useful when groups had to stay put, but only as flexible as the two-byte AS field it borrowed.
History
The Runtime Replied 231. The Script Still Owed a Termination Receipt: RFC 3179
A control system can answer correctly before the work is done. RFC 3179 made that temporal gap explicit: one reply said a management script had reached a runtime state, other messages carried intermediate output or errors, and a later reply marked termination. None of them alone…
IETF
MOQT's New Filter Type Puts Relay Compatibility on the Wire
The latest Media over QUIC Transport draft makes a small but consequential change to a request's shape. A location filter now identifies its form explicitly, rather than asking a receiver to infer it from the number of encoded bytes. For relays and clients built against different…
History
The IPv6 /48 Was a Starting Point, Not a Size for Every Site
The story of the IPv6 /48 is not that the IETF discovered it was too large. It is that a tidy architectural recommendation became awkward when different kinds of real networks had to live inside the same prefix table.