Protocol-Independent Multicast: Difference between revisions

Revision as of 15:49, 6 January 2022

Latest revision as of 22:04, 18 July 2025

(13 intermediate revisions by 9 users not shown)

Line 5:

There are four variants of PIM:

* '''PIM Sparse Mode''' (PIM-SM) explicitly builds unidirectional shared trees rooted at a ''rendezvous point'' (RP) per group, and optionally creates shortest-path trees per source. PIM-SM generally scales fairly well for wide-area usage.<ref>{{cite web |url=https://technet.microsoft.com/en-us/library/bb742462.aspx |title=PIM-SM Multicast Routing Protocol |date=9 December 2009 |publisher=[[Microsoft]] |access-date=2014-03-26}}</ref>{{ref RFC|4601}}

* '''PIM Dense Mode''' (PIM-DM) uses [[dense multicast]] routing. It implicitly builds shortest-path trees by flooding [[multicast]] traffic ___domain wide, and then pruning back branches of the tree where no receivers are present. PIM-DM is straightforward to implement but generally has poor scaling properties. The first multicast routing protocol, [[DVMRP]] used dense-mode multicast routing.<ref>{{cite web |url=http://www.multicasttech.com/faq/ |title=Frequently Asked Questions (FAQ) File for Multicasting |publisher=Multicast Tech |archive-url=https://web.archive.org/web/20110614164202/http://www.multicasttech.com/faq/ |archive-date=2011-06-14}}</ref> See RFC 3973.

* '''Bidirectional PIM''' (Bidir-PIM) explicitly builds shared bi-directional trees. It never builds a shortest path tree, so may have longer end-to-end delays than PIM-SM, but scales well because it needs no source-specific state.<ref name="Cisco Multicast"/>{{rp|70–73}} See RFC 5015.

* '''PIM Source-Specific Multicast''' (PIM-SSM) builds trees that are rooted in just one source, offering a more secure and scalable model for a limited number of applications (mostly broadcasting of content). In SSM, an IP datagram is transmitted by a source S to an SSM destination address G, and receivers can receive this datagram by subscribing to channel (S,G). See informational RFC{{IETF RFC|3569}}.

PIM-SM is commonly used in [[IPTV]] systems for routing multicast streams between [[VLAN]]s, [[Subnetwork|Subnetssubnet]]s or local area networks.<ref>{{cite web |url=https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-Y.Sup16-201202-I!!PDF-E&type=items |title=Supplement on guidelines on deployment of IP multicast for IPTV content delivery |publisher=[[ITU-T]] |access-date=2014-03-23}}</ref>

==Versions==

Line 42:

* Whether they arrive encapsulated or natively, the RP forwards the source's de-capsulated data packets down the RP-centered distribution tree toward group members.

* If the data rate warrants it, routers with local receivers can join a source-specific, shortest path, distribution tree, and prune this source's packets off the shared RP-centered tree.

* Where a router's local receivers are only interested in packets from a specific source within a multicast group, the router may skip joining the RP centered shared tree and jump straight to joining the source-specific shortest path tree.

* For low data rate sources, neither the RP, nor last-hop routers need join a source-specific shortest path tree and data packets can be delivered via the shared RP-tree.

Line 51 ⟶ 52:

The basic assumption behind dense mode is that the multicast packet stream has receivers at most locations. Sparse mode assumes relatively fewer receivers. Dense mode is ideal for groups where many of the nodes will subscribe to receive the multicast packets, so that most of the [[router (computing)|router]]s must receive and forward these packets (groups of a high density).

This difference shows up in the initial behavior and mechanisms of the two protocols. Dense Mode uses a fairly simple approach to handle [[IP multicast]] routing. The source initially [[broadcastingBroadcasting (networksnetworking)|broadcast]]s to every [[router (computing)|router]] directly connected to it. These neighboring routers further forward the data to their neighbors. When a router does not wish to receive this group's data (if no other neighboring PIM routers are present and no host is interested in the group), it sends a Prune message to indicate its lack of interest. Upon receiving a Prune message, the router will modify its state so that it will not forward those packets out that [[Interface (computer science)|interface]]. If every interface on a router is pruned, the router will also be pruned.<ref name=CiscoPIM/>

In older Cisco IOS releases, PIM-DM would re-flood all the multicast traffic every 3 minutes. This is fine for low volume multicast, but not higher bandwidth multicast packet streams. More recent Cisco IOS versions support a new feature called PIM Dense Mode State Refresh, since 12.1(5)T. This feature uses a PIM state refresh messages to refresh the Prune state on outgoing interfaces. Another benefit is that topology changes are recognized more quickly. By default, the PIM state refresh messages are sent every 60 seconds.

Line 71 ⟶ 72:

* [http://www.ietf.org/rfc/rfc3569.txt An Overview of Source-Specific Multicast (SSM)]

* [https://web.archive.org/web/20090615025136/http://www.netcraftsmen.net/welcher/papers/multicast03.html Netcraftmen Explanation of PIM Sparse Mode]

* [http://docwiki.cisco.com/wiki/Internet_Protocol_Multicast cisco docwiki]{{dl}}

* [https://technet.microsoft.com/en-us/library/bb742462.aspx PIM-SM Multicast Routing Protocol]

* [https://web.archive.org/web/20111004054835/http://troglobit.com/pimd.shtml pimd is a lightweight stand-alone PIM-SM v2 multicast routing daemon.]