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 Host Spoke PIM. The Network Mistook It for a Router.
A control plane fails before any packet is lost when it accepts the wrong class of speaker. RFC 5294 showed how a host-facing interface could hear a valid PIM Hello, Register, Assert, or election message and convert mere protocol fluency into routing responsibility. The decisive…
IETF
The Filter Edited One Message. It Did Not Create One Truth.
A compliance stamp appeared in the archived copy, disappeared from a delivery notice, and broke a signature check downstream. All three observations were compatible with RFC 5293. The failure was not that Sieve behaved inconsistently. It was that the institution called three…
IETF
The Premium Lane Could Not Replace the Road.
A network can sell priority, reserve capacity, or attach a price to congestion without answering the harder constitutional question: what remains usable by everyone who did not enter that arrangement? RFC 5290 treated simple best-effort traffic not as a primitive awaiting…
IETF
The Control Plane Was Alive. It Was the Wrong Witness.
Two indicators can describe the same TDM pseudowire and still disagree without either message being malformed. One arrives inside the emulated data stream; the other travels through the PWE3 control plane. RFC 5287 did not treat that duplication as automatic resilience. While the…
History
One Datagram Changed Its Route. The Other Socket Defaults Should Have Survived: RFC 3542
The most revealing API changes are sometimes changes in the blast radius of an exception. RFC 3542 let one IPv6 datagram depart from one socket default without making that packet an excuse to erase every other choice the application had already made.
IETF
The Label Stayed Specific. The Route Became an Aggregate.
The control plane still carried a label for one exact egress. The IP routing table no longer carried that egress at all; it carried only the larger prefix that contained it. RFC 5283 made that asymmetry useful. It did not make the aggregate a witness that every specific…
IETF
The Feature Was Enabled. The Topology Had No Alternate.
A router can be configured for fast reroute and still have nowhere safe to send one destination when a link fails. RFC 5286 makes that apparent contradiction precise: a loop-free alternate exists only when a candidate neighbour passes a strict, destination-specific distance test…
History
The Best Route Was Not a Stable Answer: RFC 3345
A router can choose the best path in its own table, advertise it, and still help create a loop that makes the next “best” choice different. RFC 3345 showed how that can happen when BGP’s scaling shortcuts reduce which exit paths each router sees.
IETF
The Tunnel Was Open. The Subscriber Had Not Been Authenticated.
The TLS Finished messages crossed cleanly. The server had proved its side of the tunnel, encryption was active, and keying material could be derived. In the ordinary one-way EAP-TTLS branch, the subscriber’s real identity had not even been sent yet. Treating that moment as “user…
History
The AD Bit Reported Validation Policy, Not a Signed Answer: RFC 3655
A DNS reply can contain a one-bit assurance from the resolver that checked it. In 2003, RFC 3655 narrowed what that bit meant—and made clear that trusting the bit depended on trusting the resolver and the path to it.
IETF
Replay Finished. The Missing Beginning Was Still Missing.
The server sent a green `replayComplete` marker. Every notification it could replay for that subscription had been sent. The requested history still began earlier than the oldest event the log retained. Both statements were true, and a dashboard that stored only “complete” turned…
IETF
The Packet Said 3. The Session Knew What 3 Meant.
A packet capture can preserve every RTP byte and still lose the dictionary needed to read its metadata. RFC 5285 made that separation deliberate: compact numbers travel on the wire, while negotiated context decides what those numbers name.
History
The Route Stopped Flapping. Its Penalty Had Not: RFC 2439
The Route Stopped Flapping. Its Penalty Had Not: RFC 2439 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…
IETF
The Handover Had Four Signals. The Dashboard Showed One Green Light.
A mobile system detected a neighboring link, decided to leave, received an order to switch, and finally established a new radio connection. Those are four events with different producers and meanings. RFC 5270 kept them separate. A dashboard that compresses them into “handover…
IETF
The Error Crossed the Network. Its Meaning Stayed Local.
RFC 5284 lets an RSVP error carry an organization-specific diagnosis through equipment that does not understand it. That continuity is useful precisely because the standard does not confuse transport with interpretation, action or repair.
History
Control Lost Its Association; Forwarding Still Needed a Rule: RFC 3654
A router can lose contact with the process that programs it without losing every ability to move packets. RFC 3654 treated that interval as an architectural choice: detect the break, decide what the forwarding element should do, and plan how control and state return.
IETF
MOBIKE Updated the Outer Address. The Home Agent Never Saw the Move.
One mobile node can move once and produce two very different control-plane stories. The VPN gateway records a new outer address. The internal Mobile IPv4 home agent sees the same tunnel inner address and therefore no movement at all. RFC 5266 makes both stories correct—and makes…
IETF
The Home Agent Called the Network Trusted. The Interface Could Change Next.
A valid answer can become unsafe without ever becoming false. RFC 5265 lets a mobile node classify one attachment as internal after a protected exchange with its internal home agent. The classification is useful precisely because the protocol refuses to let it float free of the…
IETF
The Certificate Path Was Preserved. Its Authority Was Not Universal.
A flawless archive can preserve the wrong conclusion with perfect fidelity. RFC 5276 shows how to keep certificate paths and revocation material verifiable across decades; it also shows why preservation, trust policy and application authority must remain separate decisions.
IETF
A Partial Publication Expired. Its Whole Published State Disappeared.
RFC 5264 saves bandwidth by letting a presence user agent publish changes instead of repeating a complete document. The efficiency boundary is easy to misread: the patches do not become separately expiring records. They are folded into one current publication, and the lifetime…