1 - 2 - 3 - 4 - 6 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - R - S - T - U - V - W
multicast address
Click on the red underlined text to get to the source
... belonging to different nodes). A packet sent to a
multicast address is delivered to all interfaces
identified by that address ...
... addresses in IPv6, their function being
superseded by multicast addresses.
In this document, fields in addresses ...
... 2001:DB8:0:0:8:800:200C:417A a unicast address
FF01:0:0:0:0:0:0:101 a multicast address
0:0:0:0:0:0:0:1 the loopback address ...
... 2001:DB8::8:800:200C:417A a unicast address
FF01::101 a multicast address
::1 the loopback address ...
... Multicast Addresses ...
... interface may belong to any
number of multicast groups. Multicast addresses have the following
format:
...
...
T = 0 indicates a permanently-assigned ("well-known") multicast
address, assigned by the Internet Assigned Numbers Authority
(IANA ...
...
T = 1 indicates a non-permanently-assigned ("transient" or
"dynamically" assigned) multicast address.
The P flag's definition and usage can be found in [RFC3306 ...
... RFC3306].
The "meaning" of a permanently-assigned multicast address is
independent of the scope value. For example, if the "NTP servers
...
... NTP servers
group" is assigned a permanent multicast address with a group ID of
101 (hex), then
...
... Internet.
Non-permanently-assigned multicast addresses are meaningful only
within a given scope. For example, a group identified by the non-
...
... group identified by the non-
permanent, site-local multicast address FF15:0:0:0:0:0:0:101 at one
site bears no relationship to a group using the same address ...
... ID.
Multicast addresses must not be used as source addresses in IPv6
packets or appear in any Routing header ...
... multicast packets beyond of the scope
indicated by the scop field in the destination multicast address.
Nodes ...
...
Nodes must not originate a packet to a multicast address whose scop
field contains the reserved value 0; if such a packet is received, it
must be silently dropped. Nodes ...
... must be silently dropped. Nodes should not originate a packet to a
multicast address whose scop field contains the reserved value F; if
such a packet is sent or received, it must be treated the same as
packets destined to a global (scop E) multicast address ...
... multicast address whose scop field contains the reserved value F; if
such a packet is sent or received, it must be treated the same as
packets destined to a global (scop E) multicast address.
...
... Pre-Defined Multicast Addresses ...
...
The following well-known multicast addresses are pre-defined. The
group IDs defined in this section are defined for explicit scope
...
... equal to 0, is not allowed.
Reserved Multicast Addresses: FF00:0:0:0:0:0:0:0
FF01:0:0:0:0:0:0:0
FF02:0:0:0:0:0:0:0
...
... FF0F:0:0:0:0:0:0:0
The above multicast addresses are reserved and shall never be
assigned to any multicast group.
...
... unicast and anycast addresses. A Solicited-Node multicast
address is formed by taking the low-order 24 bits of an address
...
...
For example, the Solicited-Node multicast address corresponding to
the IPv6 address 4037::01:800:200E:8C6C is FF02::1:FF0E:8C6C. IPv6
addresses ...
... interface)
the associated Solicited-Node multicast addresses for all unicast and
anycast addresses ...
...
o The All-Routers multicast addresses defined in Section 2.7.1.
...
... IPv6 transition mechanisms.
o Added the "R" and "P" flags to Section 2.7 on multicast addresses,
and pointers to the documents that define them.
...