Primary Domain
Multicast Routing
Within the Primary Domain facet, Multicast Routing intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
IETF
PIM Light’s Missing Hello Leaves Two Redundancy Decisions Outside the Interface
RFC 9739 lets multicast state cross a boundary without first establishing a PIM neighbour. The useful simplification leaves the network responsible for choosing who forwards a Join, preventing duplicate streams and turning a detected failure into an actual withdrawal.
CASE FILE
Two Sources, One Election, No Continuity Verdict: RFC 9856
RFC 9856 gives an EVPN fabric disciplined ways to choose among redundant multicast sources. The useful discipline begins by refusing a tempting shortcut: the chosen path is not the received service.
CASE FILE
The Repair Path Was Ready. The Multicast Service Was Not Yet Proven: RFC 9860
RFC 9860 gives multicast operators a more capable way to build a standby tree from a TI-LFA repair list. It also draws a useful boundary: a route calculation can accelerate local recovery, but the service verdict still belongs to evidence collected after the calculation.