Topic
Multicast Routing
Within the Topic facet, Multicast Routing 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 Root Writes the Shortcut: RFC 9914 Projects Routing State into RPL
A leaf-to-leaf packet may climb a stretched RPL DODAG path through the Root even when a shorter directional path exists. RFC 9914 lets the Root project a PCE-computed shortcut as routing state into selected nodes—improving path choice, but also making freshness, precedence…
Leaders
Seyed Pouria Mousavizadeh Tehrani and the State Hidden Before IPv6’s First Reply
A first IPv6 exchange can expose network state that steady-state reachability leaves invisible.
Global Regional ISP Trends
An EVPN Designated Forwarder Election Is Not a Lossless Failover Proof
The control plane can agree on a new EVPN Designated Forwarder while one service remains unable to carry traffic. Election, attachment health, forwarding installation and packet continuity are related states—not interchangeable proof.
Global Regional ISP Trends
An IGMP Membership Report Is Not a Multicast Delivery Receipt
A receiver can ask for a multicast group and still see no usable stream. The membership report proves local interest; delivery depends on a separate chain of routing, forwarding and application evidence.
IETF
Dino Farinacci and the Requirement That Did Not Allocate a Multicast Address
A requirements document can make a future system easier to judge. It cannot make that system exist. That distinction is the useful way to read RFC 10019, an IETF document co-authored by Dino Farinacci with Nate Karstens and Mike McBride.
IETF
Hooman Bidgoli and the Leaf Set That Was Not a Delivered Multicast Service
The control plane can produce an orderly list of intended receivers while the data plane is still divided across controller state, replication segments, service context and receivers that have not seen a packet. RFC 10018 makes the list useful. It does not make the list a…
IETF
Mike McBride and the Multicast Registry That Prevented One Kind of Collision
Two IPv6 multicast allocation methods had been told to draw identifiers from the same box. RFC 10028 divided the box before a future host protocol and an old server protocol could make the same choice—and left operators with the harder job of proving that their networks had…
IETF
Joining the group is no longer enough: SSM makes the receiver name the sender
Source-Specific Multicast turns a multicast join into a choice: the receiver must identify both the group it wants and the source it is willing to hear.