Protocol-Independent Multicast: Difference between revisions

Revision as of 22:14, 19 October 2024

Revision as of 22:48, 1 November 2024

Line 6:

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 3569.