RFC 4604:Using Internet Group Management Protocol ...
RFC-Ref

destination address


Click on the red underlined text to get to the source

... multicast traffic sent to an SSM destination address, it SHOULD return an error to the application, as specified in [MSFAPI] (MODIFICATION). On a non-SSM ...
... A Group Record for a source-specific destination address may (under normal operation) be any of the following types: ...
... A report may include both SSM destination addresses and non-source- specific, i.e., Any-Source Multicast (ASM ...
... specific, i.e., Any-Source Multicast (ASM) destination addresses, in the same message. ...
... MLDv2], imposing a restriction on its use for SSM destination addresses. The rationale is that EXCLUDE mode does not apply to SSM addresses ...
... or MLDv1 to report interest in all SSM destination addresses, unqualified by a source address. As a result, SSM ...
... MLDv2], even if the group queried is a source-specific destination address. The transmission of such a query likely indicates either that the sending router ...
... address, it must respond with a report if the group matches the source-specific destination address of any of its subscribed source- specific channels, as specified in [IGMPv3 ...


... routers with respect to the following types of SFGMP messages for source-specific destination addresses: - IGMPv3 ...
... group record of either of the following types if it refers to an SSM destination address: - MODE_IS_EXCLUDE Current-State ...


... router not accept non-source-specific reception requests for an SSM destination address. The rules of [IGMPv3] and [MLDv2 ...
... SSM service for that destination address, thus creating a potential for an attacker to deny SSM ...



Google
Web
RFC-Ref