Content deleted Content added
CyberOne25 (talk | contribs) m CyberOne25 moved page Protocol Independent Multicast to Protocol-Independent Multicast Tags: Mobile edit Mobile web edit Advanced mobile edit |
Citation bot (talk | contribs) Added date. | Use this bot. Report bugs. | Suggested by BorgQueen | Linked from User:AlexNewArtBot/GoodSearchResult | #UCB_webform_linked 198/1170 |
||
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.
| |||