Zone_Multicast_Address

Multicast address

Multicast address

Logical identifier addressing a specific group of devices on a network

For broader coverage of this topic, see Multicast.

A multicast address is a logical identifier for a group of hosts in a computer network that are available to process datagrams or frames intended to be multicast for a designated network service. Multicast addressing can be used in the link layer (layer 2 in the OSI model), such as Ethernet multicast, and at the internet layer (layer 3 for OSI) for Internet Protocol Version 4 (IPv4) or Version 6 (IPv6) multicast.

IPv4

IPv4 multicast addresses are defined by the most-significant bit pattern of 1110. This originates from the classful network design of the early Internet when this group of addresses was designated as Class D. The CIDR notation for this group is 224.0.0.0/4.[1] The group includes the addresses from 224.0.0.0 to 239.255.255.255. Address assignments from within this range are specified in RFC 5771, an Internet Engineering Task Force (IETF) Best Current Practice document (BCP 51).

The address range is divided into blocks each assigned a specific purpose or behavior.

More information IP multicast address range, Description ...
Local subnetwork
Addresses in the range of 224.0.0.0 to 224.0.0.255 are individually assigned by IANA and designated for multicasting on the local subnetwork only. For example, the Routing Information Protocol (RIPv2) uses 224.0.0.9, Open Shortest Path First (OSPF) uses 224.0.0.5 and 224.0.0.6, and Multicast DNS uses 224.0.0.251. Routers must not forward these messages outside the subnet from which they originate.
Internetwork control block
Addresses in the range 224.0.1.0 to 224.0.1.255 are individually assigned by IANA and designated as the internetwork control block. This block of addresses is used for traffic that must be routed through the public Internet, such as for applications of the Network Time Protocol using 224.0.1.1.
AD-HOC block
Addresses in three separate blocks are not individually assigned by IANA. These addresses are globally routed and are used for applications that don't fit either of the previously described purposes.[9]
Source-specific multicast
The 232.0.0.0/8 (IPv4) and ff3x::/32 (IPv6) blocks are reserved for use by source-specific multicast.
GLOP[10]
The 233.0.0.0/8 range was originally assigned by RFC 2770 as an experimental, public statically-assigned multicast address space for publishers and Internet service providers that wished to source content on the Internet. The allocation method is termed GLOP addressing and provides implementers a block of 255 addresses that is determined by their 16-bit autonomous system number (ASN) allocation. In a nutshell, the middle two octets of this block are formed from assigned ASNs, giving any operator assigned an ASN 256 globally unique multicast group addresses.[11] The method is not applicable to the newer 32-bit ASNs. RFC 3180, superseding RFC 2770, envisioned the use of the range for many-to-many multicast applications. Unfortunately, with only 256 multicast addresses available to each autonomous system, GLOP is not adequate for large-scale broadcasters.[citation needed]
Unicast-prefix-based
The 234.0.0.0/8 range is assigned by RFC 6034 as a range of global IPv4 multicast address space provided to each organization that has /24 or larger globally routed unicast address space allocated; one multicast address is reserved per /24 of unicast space. A resulting advantage over GLOP is that the unicast-prefix mechanism resembles the unicast-prefix capabilities of IPv6 as defined in RFC 3306.
Administratively scoped
The 239.0.0.0/8 range is assigned by RFC 2365 for private use within an organization. Per the RFC, packets destined to administratively scoped IPv4 multicast addresses do not cross administratively defined organizational boundaries, and administratively scoped IPv4 multicast addresses are locally assigned and do not have to be globally unique. The RFC also discusses structuring the 239.0.0.0/8 range to be loosely similar to the scoped IPv6 multicast address range described in RFC 1884.
Ethernet-specific
In support of link-local multicasts which do not use IGMP, any IPv4 multicast address that falls within the *.0.0.0/24 and *.128.0.0/24 ranges will be broadcast to all ports on many Ethernet switches, even if IGMP snooping is enabled, so addresses within these ranges should be avoided on Ethernet networks where the functionality of IGMP snooping is desired.[12][dubious – discuss]

Notable IPv4 multicast addresses

The following table is a list of notable well-known IPv4 addresses that are reserved for IP multicasting and that are registered with the Internet Assigned Numbers Authority (IANA).[5]

More information IP multicast address, Description ...

IPv6

Multicast addresses in IPv6 use the prefix ff00::/8. The general format of the IPv6 multicast address is described by RFC 4291:

More information Bits, Field ...
More information Bit, Flag ...

Based on the value of the flag bits, IPv6 multicast addresses can be Unicast-Prefix-based Multicast Addresses, Source-Specific Multicast Addresses (both types introduced by RFC 3306, updated by RFC 7371), or Embedded RP IPv6 Multicast Addresses (introduced by RFC 3956, updated by RFC 7371). Each of these types of multicast addresses have their own format and follow specific rules.

Similar to a unicast address, the prefix of an IPv6 multicast address specifies its scope, however, the set of possible scopes for a multicast address is different. The 4-bit scope field (bits 12 to 15) is used to indicate where the address is valid and unique.

More information IPv6 address, IPv4 equivalent ...

The service is identified in the group ID field. For example, if ff02::101 refers to all Network Time Protocol (NTP) servers on the local network segment, then ff08::101 refers to all NTP servers in an organization's networks. The group ID field may be further divided for special multicast address types.

Notable IPv6 multicast addresses

The following table is a list notable IPv6 multicast addresses that are registered with IANA.[21] To be included in some of the below multicast groups a client must send a Multicast Listener Discovery (MLD), a component of ICMPv6 suite, to join that group.[22] For example, to listen to ff02::1:ff28:9c5a, a client must send a MLD report to the router, containing the multicast address, to indicate that it wants to listen to that group.[23]

More information Address, Description ...

Ethernet

Ethernet frames with a value of 1 in the least-significant bit of the first octet[note 3] of the destination MAC address are treated as multicast frames and are flooded to all points on the network. While frames with ones in all bits of the destination address (FF-FF-FF-FF-FF-FF) are sometimes referred to as broadcasts, Ethernet generally does not distinguish between multicast and broadcast frames. Modern Ethernet controllers filter received packets to reduce CPU load, by looking up the hash of a multicast destination address in a table, initialized by software, which controls whether a multicast packet is dropped or fully received.

The IEEE has allocated the address block 01-80-C2-00-00-00 to 01-80-C2-FF-FF-FF for group addresses for use by standard protocols. Of these, the MAC group addresses in the range of 01-80-C2-00-00-00 to 01-80-C2-00-00-0F are not forwarded by 802.1D-conformant MAC bridges.[27]

More information Block, Ethernet multicast address ...

802.11

802.11 wireless networks use the same MAC addresses for multicast as Ethernet.

See also

Notes

  1. [N 1]
    The recommended style for Request for Comments (RFC) documents is "MSB 0" bit numbering.
  2. [N 2]
    x is a place holder indicating that the value of the flags field is unimportant in the current discussion.
  3. [N 3]
    On Ethernet, the least-significant bit of an octet is the first to be transmitted. A multicast is indicated by the first transmitted bit of the destination address being 1.

References

  1. [1]
    MULTICAST_IP_ADDR. General Electric Digital Solutions. CIMPLICITY 10.0. In network prefix or Classless Inter-Domain Routing ( CIDR) notation, IP multicast addresses are summarized as 224.0.0.0/4.
  2. [2]
    IP Multicast Routing Configuration Guide, Cisco, retrieved 2021-01-13
  3. [3]
    AD-HOC Block 1
  4. [4]
    IANA Guidelines for IPv4 Multicast Address Assignments. sec. 3. doi:10.17487/RFC5771. RFC 5771.
  5. [5]
    "IANA IP multicast addresses assignments". Internet Assigned Numbers Authority.
  6. [6]
    AD-HOC Block 2
  7. [7]
    Fall, K.R. and Stevens, W.R. (2011). TCP/IP Illustrated. Vol. 1. Addison-Wesley. p. 55. ISBN 9780321336316.{{cite book}}: CS1 maint: multiple names: authors list (link)
  8. [8]
    AD-HOC Block 3
  9. [9]
    RFC 5771 Section 6.
  10. [10]
    Joseph, Vinod; Mugulu, Srinivas (2011). Deploying Next Generation Multicast-Enabled Applications - Label Switched Multicast for MPLS, VPN, VPLS, and Wholesale Ethernet. Morgan Kaufmann/Elsevier. p. 7. ISBN 978-0-12-384923-6. Lacking anything better to call it, one of the authors [of RFC2770], David Meyer, simply began refer to this as "GLOP" addressing and the name stuck.
  11. [11]
    "Frequently Asked Questions (FAQ) File for Multicasting". Multicast Tech. Archived from the original on 2011-05-16.
  12. [12]
    "Guidelines for Enterprise IP Multicast Address Allocation" (PDF). Cisco. p. 7. Retrieved 2023-01-14. most Layer 2 switches flood all multicast traffic that falls within the MAC address range of 0x0100.5E00.00xx [...] to all ports on the switch even if IGMP Snooping is enabled. [...] There are several multicast group ranges besides the 224.0.0.0/24 that will map to the 0x0100.5E00.00xx MAC address range and hence also will be flooded by most Layer 2 switches.
  13. [13]
    RFC 3376 Section 4.2.14
  14. [14]
    RFC 4380 item 2.17
  15. [15]
    Silvia Hagen (May 2006). IPv6 Essentials (Second ed.). O'Reilly. ISBN 978-0-596-10058-2.
  16. [16]
    RFC 3956
  17. [17]
    RFC 3306
  18. [18]
    R. Hinden; S. Deering (February 2006). IP Version 6 Addressing Architecture. Network Working Group. doi:10.17487/RFC4291. RFC 4291. Draft Standard. Obsoletes RFC 3513. Updated by RFC 5952, 6052, 7136, 7346, 7371 and 8064.
  19. [19]
    RFC 2365 section 8.
  20. [20]
    R. Droms (August 2014). IPv6 Multicast Address Scopes. Internet Engineering Task Force. doi:10.17487/RFC7346. ISSN 2070-1721. RFC 7346. Proposed Standard. Updates RFC 4007 and 4291.
  21. [21]
    "IPv6 Multicast Address Space Registry". Internet Assigned Numbers Authority.
  22. [22]
    RFC 5110
  23. [23]
    RFC 2710
  24. [24]
    R. Vida; L. Costa, eds. (June 2004). Multicast Listener Discovery Version 2 (MLDv2) for IPv6. Network Working Group. doi:10.17487/RFC3810. RFC 3810. Proposed Standard. Updates RFC 2710. Updated by RFC 4604.
  25. [25]
    T. Mrugalski; M. Siodelski; B. Volz; A. Yourtchenko; M. Richardson; S. Jiang; T. Lemon; T. Winters (November 2018). Dynamic Host Configuration Protocol for IPv6 (DHCPv6). IETF. doi:10.17487/RFC8415. ISSN 2070-1721. RFC 8415. Proposed Standard. Obsoletes RFC 3315, 3633, 3736, 4242, 7083, 7283 and 7550.
  26. [26]
    B. Aboba; D. Thaler; L. Esibov (January 2007). Link-Local Multicast Name Resolution (LLMNR). Network Working Group. doi:10.17487/RFC4795. RFC 4795. Informational.
  27. [27]
    IEEE. "Standard Group MAC Address: A Tutorial Guide" (PDF). IEEE Standards Association. pp. 2–3. Archived (PDF) from the original on 2022-10-09.
  28. [28]
    Patton, Michael A. et. al.. "Multicast (including Broadcast) Addresses". cavebear.com. Karl Auerbach. {{cite web}}: External link in |author= (help)
  29. [29]
    "Standard Group MAC Address - Public Listing". IEEE-SA. Retrieved 30 November 2022.
  30. [30]
    "IANA Multicast 48-bit MAC Addresses". IANA. Retrieved 31 January 2021.
  31. [31]
    RFC 7042 2.1.1
  32. [32]
    RFC 7042 2.3.1
Share this article:

This article uses material from the Wikipedia article Zone_Multicast_Address, and is written by contributors. Text is available under a CC BY-SA 4.0 International License; additional terms may apply. Images, videos and audio are available under their respective licenses.