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 IPv6 Route Won SPF. The Next Hop Spoke Only IPv4.
One IS-IS graph can carry several network-layer stories. RFC 5308 gives IPv6 its own reachability, interface-address and protocol-support vocabulary, but it does not make an ordinary adjacency proof that every transit node can forward IPv6. A route may be perfectly intelligible…
IETF
The IGP Called It Point-to-Point. Ethernet Still Asked for a MAC Address.
RFC 5309 lets two routers operate a link-state protocol as though a LAN were a point-to-point circuit. That administrative simplification removes the designated-router and pseudonode model. It does not remove Ethernet, VLAN membership or next-hop resolution. A logical adjacency…
IETF
The Link Advertised Capacity. Nothing Had Been Reserved Yet.
A traffic-engineering database can look like an inventory: colors, addresses, metrics and eight rows of available bandwidth. RFC 5305 makes a more exact reading unavoidable. Some values are administrative, some may deliberately exceed the physical link, and the most volatile…
IETF
Every Router Accepted the Route. One Border Could Still Send It Back.
An inter-area prefix can arrive, pass every ordinary reachability check and improve a path inside a Level 1 area. None of those facts proves that the area can remember where the route came from. RFC 5302 makes the decisive compatibility question narrower and more demanding: every…
History
Fast, Smooth, Seamless: RFC 3753 Kept Three Handover Labels Apart
Before engineers could compare a mobile handover, they needed to say what kind of handover they meant. In June 2004, an IETF glossary separated five mostly independent control questions and distinguished latency, packet loss and application-visible continuity—without specifying a…
IETF
The Packet Carried a MAC. The Receiver Still Had to Enforce It.
Authentication is often treated as a property of the packet: the field is present, the digest looks right, the session is “secure.” RFC 5304 makes the harder fact visible. One router may emit HMAC-MD5 while deliberately not verifying inbound HMACs during transition; another may…
IETF
The Nonce Repeated. The Failure Did Not Become Permission.
Misuse resistance is a promise about the shape of a cryptographic failure, not a waiver for the control that failed. RFC 5297's SIV construction keeps authenticity when a nonce repeats and confines the privacy loss to an equality signal. That is valuable precisely because nonce…
IETF
Both Routers Heard Hello. That Still Did Not Prove the Path.
The dangerous word in a network status is often “up.” RFC 5303 gave point-to-point IS-IS a stronger way to earn that word: not merely “I heard you,” but “I know you heard me, and this reply belongs to this system and this circuit.” It also left a crucial boundary intact.…
IETF
The Finish Was Authentic. The Key Was Not Yet in Use.
The peer verified a protected EAP-Finish/Re-auth and derived the expected re-authentication MSK. The ER server had already accepted the sequence number. Yet the authenticator had not installed that rMSK, and the lower-layer security association had not begun. A valid finish…
History
A Search Result Was Not an Identity: RFC 3744’s Canonical Principal
WebDAV’s access-control design had to solve a problem that a display name could hide: one person or software agent might be reachable through several URLs, while an access-control entry needed an unambiguous principal reference. RFC 3744 paired limited human-oriented discovery…
IETF
The Keys Were Different. The Boundary Still Collapsed.
An access system rotated its EMSK, derived a fresh root and produced exactly the bytes its specification expected. The downstream service kept using an older cache entry because the key name, lifetime and replacement event had not travelled with the secret. Cryptographic…
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…