Source specific multicast range distribution for L2 multicast networks
draft-ramki-igmp-ssm-ranges-00

Document Type Expired Internet-Draft (individual)
Last updated 2020-01-09 (latest revision 2019-07-08)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ramki-igmp-ssm-ranges-00.txt

Abstract

In an IGMP snooping multicast network with version 3 (v3) enabled on the routers, when a v2 join/leave is received for a multicast group the router operates on V2 compatible mode. For SSM ranges a (*,G)v2 or v3 report should be ignored by the router/switch. The IGMP snooping switches may not have knowledge about the user configured SSM range in the network to correctly discard/ignore the v2 join/ leave. Accepting (*,G) v2 or v3 will cause SSM operations to fail. This draft discusses distribution of SSM ranges in the L2 multicast network so that L2 snooping switches can learn about the configured SSM ranges and discard any (*,G) v2/v3 reports for the said ranges.

Authors

Ramakrishnan Sundaram (ramaksun@cisco.com)
Stig Venaas (stig@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)