host
Click on the red underlined text to get to the source
... (IGMPv3) [IGMPv3] provides the ability for a host to selectively
request or filter traffic from individual sources within a multicast
group ...
... source-specific multicast is facilitated by small changes
to the SFGMP protocols on both hosts and routers. [SSM] defines
...
... IGMPv3 and MLDv2. In
doing so, this document defines modifications to the host and router
portions of IGMPv3 ...
...
This section defines the notion of an "SSM-aware" host and then goes
on to describe the API requirements ...
... host. It is important to note that SSM
can be used by any host that supports source filtering APIs and whose
...
... SSM work better on an
SSM-aware host, but they are not strict prerequisites for the use of
SSM.
...
... SSM] has a more thorough discussion of this topic.) A
host that knows the SSM address range and is capable of applying SSM ...
... host IP module of an SSM-aware host receives a non-source-
specific request to receive multicast traffic sent to an SSM ...
... specified in [MSFAPI] (MODIFICATION). On a non-SSM-aware host, an
application that uses the wrong API (e.g., "join ...
... SFGMP protocol module on an
SSM-aware host, including two modifications to the protocols as
described in [IGMPv3,MLDv2 ...
... clarifications of protocol operations. In doing so, it documents the
behavior of an SSM-aware host with respect to sending and receiving
the following GMP ...
... SFGMP support needed for SSM, and an error is logged when
the host enters compatibility mode for an SSM address ...
... channel (S,G) will not be delivered to a receiving host that has
requested to receive channel (S,G).
...
... [IGMPv3] and [MLDv2] specify that a host MAY allow an older-version
report to suppress its own IGMPv3 ...
... MLDv2 Membership Record. An
SSM-aware host, however, MUST NOT allow its report to be suppressed
in this situation (MODIFICATION). Suppressing reports in this
scenario would provide an avenue for an attacker ...
... the same message.
Additionally, a CHANGE_TO_INCLUDE_MODE record may be sent by a host
in some cases, for instance, when the SSM address range ...
... MLDv1) mode of operation on that interface.
If this occurs, the host will stop reporting source-specific
subscriptions on that interface and will start ...
... instance, if they have inconsistent manual configurations).
A host SHOULD log an error if it receives an IGMPv1, IGMPv2, or MLDv1 ...
... SSM address range(s) as the receiving host. A host SHOULD log
an error in this case (MODIFICATION).
...
... address range(s) as the receiving host. A host SHOULD log
an error in this case (MODIFICATION).
...
... query an SSM channel that a host has requested to leave via a
BLOCK_OLD_SOURCES record. A host must respond to a Group ...
... channel that a host has requested to leave via a
BLOCK_OLD_SOURCES record. A host must respond to a Group-and-
Source-Specific Query ...
... traffic from a
particular (S,G) pair to determine if there are any remaining
directly-attached hosts with interest in that (S,G) pair. Group-
and-Source-Specific Queries ...
... range could be sent by a non-SSM-aware host. A router SHOULD ignore
all such reports and specifically SHOULD NOT use them to establish IP
forwarding ...
... MLDv1 Done message may be sent by a non-SSM-aware
host. A router SHOULD ignore all such messages in the source-
specific address range ...
... router were to revert in this
situation, it would prevent an IGMPv3-capable host from receiving SSM
...