address
Click on the red underlined text to get to the source
... SSM, and presents a number
of clarifications to their behavior when used with SSM addresses.
This document updates the IGMPv3 and MLDv2 ...
... router SHOULD have a configuration option to set
the SSM address range(s). If this configuration option exists, it
MUST default to the IANA-allocated SSM ...
... 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 ...
... delivery
of packets sent to an SSM address will not receive the requested
service, because an SSM ...
... IGMPv2, or MLDv1 report for an SSM address when it is
operating in "older-version compatibility ...
... host enters compatibility mode for an SSM address, as described
below. In this situation, it is likely that traffic sent to a
...
...
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 ...
... host
in some cases, for instance, when the SSM address range is changed
through configuration. A router should process such a record ...
... host SHOULD NOT send any of the following record types
for an SSM address.
- MODE_IS_EXCLUDE as part of a Current-State ...
... MLDv2], imposing a restriction on
its use for SSM destination addresses. The rationale is that EXCLUDE
mode does not apply to SSM addresses ...
... destination addresses. The rationale is that EXCLUDE
mode does not apply to SSM addresses, and an SSM-aware router will
...
... or MLDv1 to report interest in all SSM destination addresses,
unqualified by a source address. As a result, SSM ...
... SSM destination addresses,
unqualified by a source address. As a result, SSM semantics will no
...
... host and the router disagree about the SSM address range (for
instance, if they have inconsistent manual configurations).
...
... query for an SSM address (MODIFICATION).
In order to mitigate this problem, it must be administratively
...
... Leave and MLDv1 Done messages should not be sent for an SSM address,
unless the sending host has reverted to older-version ...
... Group Specific Query for an
address in any configured source-specific range, it should process
the query ...
... 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 ...
... compliant with this document or that it is not configured with the
same SSM address range(s) as the receiving host. A host ...
... Query for an
SSM address, it must respond with a report if the group matches the
source-specific destination address ...
... 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 ...
... MLDv2]. The use of an SSM
address does not modify the behavior of the SFGMPs in this regard.
...
... service model. A router that knows the SSM address range and
is capable of applying SSM semantics ...
... MAY have a configuration option to apply SSM semantics to addresses
other than the IANA-allocated range ...
... routers with respect to the
following types of SFGMP messages for source-specific destination
addresses:
- IGMPv3 ...
... SFGMP Reports are used to report source-specific subscriptions in the
SSM address range. A router SHOULD ignore a group record of either
...
... group record of either
of the following types if it refers to an SSM destination address:
- MODE_IS_EXCLUDE Current-State ...
... semantics from being applied to SSM addresses, and to avoid reverting
to older-version compatibility ...
... group-
specific queries for addresses in the source-specific range. This
specification does not explicitly prohibit such a message, although,
...
... and-Source-Specific Queries are used within the source-specific
address range when a router receives a BLOCK_OLD_SOURCES Record for
one or more source-specific groups ...
... An IGMPv1/v2 or MLDv1 report for an address in the source-specific
range could be sent by a non-SSM ...
... host. A router SHOULD ignore all such messages in the source-
specific address range and MAY log an error (MODIFICATION).
...
... 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 ...
... Authors' Addresses ...
... copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
...