Source-specific multicast
Source-specific multicast (SSM) is a method of delivering multicast packets in which the only packets that are delivered to a receiver are those originating from a specific source address requested by the receiver. By so limiting the source, SSM reduces demands on the network and improves security.
SSM requires that the receiver specify the source address and explicitly excludes the use of the (*,G) join for all multicast groups in RFC 3376, which is possible only in IPv4's IGMPv3 and IPv6's MLDv2.
Any-source multicast (as counterexample)
[edit]Source-specific multicast is best understood in contrast to any-source multicast (ASM). In the ASM service model a receiver expresses interest in traffic to a multicast address. The multicast network must
- discover all multicast sources sending to that address, and
- route data from all sources to all interested receivers.
This behavior is particularly well suited to groupware applications where
- all participants in the group want to be aware of all other participants, and
- the list of participants is not known in advance.
The source discovery burden on the network can become significant when the number of sources is large.
Operation
[edit]In the SSM service model, in addition to the receiver expressing interest in traffic to a multicast address, the receiver expresses interest in receiving traffic from only one specific source sending to that multicast address. This relieves the network of discovering many multicast sources and reduces the amount of multicast routing information that the network must maintain.
SSM requires support in last-hop routers and in the receiver's operating system. SSM support is not required in other network components, including routers and even the sending host. Interest in multicast traffic from a specific source is conveyed from hosts to routers using IGMPv3 as specified in RFC 4607.
SSM destination addresses must be in the ranges 232.0.0.0/8 for IPv4. For IPv6 current allowed SSM destination addresses are specified by ff3x::/96, where the hexadecimal digit x represents the scope.[1] Note however that the allocation may be extended in the future so receivers and network equipment should treat any ff3x::/32 address as SSM.[2]
References
[edit]- ^ S. Deering, B. Haberman, T. Jinmei, E. Nordmark, B. Zill (March 2005). "RFC 4007: IPv6 Scoped Address Architecture". IETF. doi:10.17487/RFC4007.
{{cite journal}}: CS1 maint: multiple names: authors list (link) - ^ Hugh Holbrook, Brad Cain (August 2006). "RFC 4607: Source-Specific Multicast for IP". IETF. doi:10.17487/RFC4607. Retrieved May 25, 2013.
Further reading
[edit]- S. Bhattacharyya (July 2003). Bhattacharyya, S. (ed.). An Overview of Source-Specific Multicast (SSM). doi:10.17487/RFC3569. RFC 3569.