<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MSDP on Council of Elrond</title><link>https://songkou.github.io/tags/msdp/</link><description>Recent content in MSDP on Council of Elrond</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 20 Nov 2023 12:00:00 +0800</lastBuildDate><atom:link href="https://songkou.github.io/tags/msdp/index.xml" rel="self" type="application/rss+xml"/><item><title>PIM Sparse Mode in Detail</title><link>https://songkou.github.io/posts/pim-sparse-mode-detailed/</link><pubDate>Mon, 20 Nov 2023 12:00:00 +0800</pubDate><guid>https://songkou.github.io/posts/pim-sparse-mode-detailed/</guid><description>&lt;p&gt;A step-by-step walk through the PIM Sparse Mode (PIM-SM) control plane — from a receiver&amp;rsquo;s IGMP report through shared-tree construction, source registration, the native source tree, and the optional shortest-path-tree switchover — then how to make the Rendezvous Point redundant with Anycast RP. For the Designated Router versus Assert election and multicast-ECMP behavior, see the companion post &lt;a href="https://songkou.github.io/posts/pim-dr-assert-multicast-ecmp/"&gt;PIM DR, Assert, and Multicast ECMP&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="1-overview"&gt;1. Overview&lt;/h2&gt;
&lt;p&gt;Protocol Independent Multicast Sparse Mode (PIM-SM) builds multicast distribution trees only where receivers explicitly request traffic. It is intended for networks where multicast receivers are sparsely distributed.&lt;/p&gt;</description></item></channel></rss>