blob: 2e8c966f1695bfda4402d3e3de447d79584c7ea4 [file] [log] [blame]
Everton Marques9830ce22014-08-19 12:16:11 -03001WHY SSM
2
3Benefis of PIM SSM over PIM SM
4------------------------------
5
6- SSM consumes minimum link bandwidth
7- SSM simplifies multicast address management (specially important for
8 inter-domain multicast)
Everton Marques7cb0d4a2014-08-19 13:44:37 -03009 - SSM (S,G) channels easily provide unique per-application addressing
10 - SSM does not require MSDP between PIM domains
Everton Marques9830ce22014-08-19 12:16:11 -030011- SSM does not suffer instabilities from traffic-driven SPT switchover
Everton Marques7cb0d4a2014-08-19 13:44:37 -030012- SSM is not suscetible to DoS attack from unwanted sources
Everton Marques9830ce22014-08-19 12:16:11 -030013- SSM does not use RP. Some RP issues:
14 - RP is possible point of failure
15 - RP demands redundancy management
16 - RP may require PIM dense mode support for RP election
17 - RP is possible performance bottleneck
18 - RP may demand lots of extra management
Everton Marques7cb0d4a2014-08-19 13:44:37 -030019- SSM can be deployed in an existing PIM SM network (only the last hop
20 routers need to support IGMPv3)
21- SSM is easier to deploy and maintain
Everton Marques9830ce22014-08-19 12:16:11 -030022
23PIM-SSM drawbacks
24-----------------
25
Everton Marques7cb0d4a2014-08-19 13:44:37 -030026- SSM requires IGMPv3 support on both receivers and last-hop routers
Everton Marques9830ce22014-08-19 12:16:11 -030027- SSM may be memory intensive when managing (S,G) states for
28 many-to-many multicast distribution
Everton Marques7cb0d4a2014-08-19 13:44:37 -030029- SSM will keep (S,G) state as long as there are subscriptions from
30 receivers, even if the source is not actually sending traffic
31
Everton Marques9830ce22014-08-19 12:16:11 -030032--EOF--