Multicast address

Last updated

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.

Contents

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.

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

IP multicast address rangeDescriptionRoutable
224.0.0.0 to 224.0.0.255Local subnetwork [3] No
224.0.1.0 to 224.0.1.255Internetwork controlYes
224.0.2.0 to 224.0.255.255AD-HOC block 1 [4] Yes
224.1.0.0 to 224.1.255.255Reserved [2] : §3  [5]
224.2.0.0 to 224.2.255.255SDP/SAP block [6] Yes
224.3.0.0 to 224.4.255.255AD-HOC block 2 [7] Yes
225.0.0.0 to 231.255.255.255Reserved [2] : §3  [5]
232.0.0.0 to 232.255.255.255Source-specific multicast [3] Yes
233.0.0.0 to 233.251.255.255GLOP addressing [8] Yes
233.252.0.0 to 233.255.255.255AD-HOC block 3 [9] Yes
234.0.0.0 to 234.255.255.255[ citation needed ]Unicast-prefix-basedYes
235.0.0.0 to 238.255.255.255Reserved [2] : §3  [5]
239.0.0.0 to 239.255.255.255Administratively scoped [3] Yes
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. [2] : §6 
SDP/SAP block
Addresses in the reserved 224.2.0.0/16 range are not individually assigned by IANA. Fallen out of use [10] : §10  for security considerations, experimental Session Announcement Protocol [11] was the primary means of supplying addresses through Session Description Protocol, which now is mostly used in the establishment of private sessions.
Source-specific multicast
The 232.0.0.0/8 (IPv4) and ff3x::/32 (IPv6) blocks are reserved for use by source-specific multicast.
GLOP [12]
The 233.0.0.0/8 range was originally assigned as an experimental, public statically-assigned multicast address space for publishers and Internet service providers that wished to source content on the Internet. [13] 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. [14] The method is not applicable to the newer 32-bit ASNs. In September 2001, the IETF envisioned a broader use of the range for many-to-many multicast applications. [15] 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 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. [16] A resulting advantage over GLOP is that the unicast-prefix mechanism resembles the unicast-prefix capabilities of IPv6. [17]
Administratively scoped
The 239.0.0.0/8 range is assigned for private use within an organization. [18] 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 239.0.0.0/8 range may be structured to be loosely similar to the scoped IPv6 multicast address. [19]
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. [20] [ 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]

IP multicast addressDescriptionRoutable
224.0.0.0Base address (reserved)No
224.0.0.1The All Hosts multicast group addresses all hosts on the same network segment.No
224.0.0.2The All Routers multicast group addresses all routers on the same network segment.No
224.0.0.4This address is used in the Distance Vector Multicast Routing Protocol (DVMRP) to address multicast routers.No
224.0.0.5The Open Shortest Path First (OSPF) All OSPF Routers address is used to send Hello packets to all OSPF routers on a network segment.No
224.0.0.6The OSPF All Designated Routers (DR) address is used to send OSPF routing information to designated routers on a network segment.No
224.0.0.9The Routing Information Protocol (RIP) version 2 group address is used to send routing information to all RIP2-aware routers on a network segment.No
224.0.0.10The Enhanced Interior Gateway Routing Protocol (EIGRP) group address is used to send routing information to all EIGRP routers on a network segment.No
224.0.0.13 Protocol Independent Multicast (PIM) Version 2No
224.0.0.18 Virtual Router Redundancy Protocol (VRRP)No
224.0.0.19–21 IS-IS over IPNo
224.0.0.22 Internet Group Management Protocol (IGMP) version 3 [21] : §4.2.14 No
224.0.0.102 Hot Standby Router Protocol version 2 (HSRPv2) / Gateway Load Balancing Protocol (GLBP)No
224.0.0.107 Precision Time Protocol (PTP) version 2 peer delay measurement messagingNo
224.0.0.251 Multicast DNS (mDNS) addressNo
224.0.0.252 Link-local Multicast Name Resolution (LLMNR) addressNo
224.0.0.253 Teredo tunneling client discovery address [22] : §2.17 No
224.0.1.1 Network Time Protocol clients listen on this address for protocol messages when operating in multicast mode.Yes
224.0.1.22 Service Location Protocol version 1 generalYes
224.0.1.35 Service Location Protocol version 1 directory agentYes
224.0.1.39The Cisco multicast router AUTO-RP-ANNOUNCE address is used by RP mapping agents to listen for candidate announcements.Yes
224.0.1.40The Cisco multicast router AUTO-RP-DISCOVERY address is the destination address for messages from the RP mapping agent to discover candidates.Yes
224.0.1.41 H.323 Gatekeeper discovery addressYes
224.0.1.129–132 Precision Time Protocol (PTP) version 1 messages (Sync, Announce, etc.) except peer delay measurementYes
224.0.1.129 Precision Time Protocol (PTP) version 2 messages (Sync, Announce, etc.) except peer delay measurementYes
224.0.23.12 KNXnet/IP discovery [23] Yes
239.255.255.250 Simple Service Discovery Protocol addressYes
239.255.255.253 Service Location Protocol version 2 addressYes

IPv6

Multicast addresses in IPv6 use the prefix ff00::/8. [19]

General multicast address format
bits844112
fieldprefixflg sc group ID

For all multicast addresses, the prefix field holds the binary value 11111111.

Currently, three of the four flag bits in the flg field are defined; [19] the most-significant flag bit is reserved for future use.

Multicast address flags [24]
bitflagMeaning when 0Meaning when 1
8reservedreservedreserved
9R (Rendezvous) [25] Rendezvous point not embeddedRendezvous point embedded
10P (Prefix) [17] Without prefix informationAddress based on network prefix
11T (Transient) [19] Well-known multicast addressDynamically assigned multicast address

The four-bit scope field (sc) is used to indicate where the address is valid and unique.

In addition, the scope field is used to identify special multicast addresses, like solicited node.

Solicited-node multicast address format
bits84479924
fieldprefixflgsczeroesonesunicast address

The sc(ope) field holds the binary value 0010 (link-local). Solicited-node multicast addresses are computed as a function of a node's unicast or anycast addresses. A solicited-node multicast address is created by copying the last 24 bits of a unicast or anycast address to the last 24 bits of the multicast address.

Unicast-prefix-based multicast address format [25] [17]
bits8444486432
fieldprefixflgscresriidplennetwork prefixgroup ID

Link-scoped multicast addresses use a comparable format. [26]

Based on the value of the flag bits, IPv6 multicast addresses can be Unicast-Prefix-based Multicast Addresses, [17] Source-Specific Multicast Addresses, [17] or Embedded RP IPv6 Multicast Addresses. [25] 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.

Multicast address scope
IPv6 address [note 1] IPv4 equivalent [18] : §8 Scope [27] Purpose
ffx0::/16, ffxf::/16Reserved
ffx1::/16Interface-localPackets with this destination address may not be sent over any network link, but must remain within the current node; this is the multicast equivalent of the unicast loopback address.
ffx2::/16224.0.0.0/24Link-localPackets with this destination address may not be routed anywhere.
ffx3::/16239.255.0.0/16Realm-Local scope [27] Local multicast particular to a network technology
ffx4::/16Admin-localThe smallest scope that must be administratively configured.
ffx5::/16Site-localRestricted to the local physical network.
ffx8::/16239.192.0.0/14Organization-localRestricted to networks used by the organization administering the local network. (For example, these addresses might be used over VPNs; when packets for this group are routed over the public internet (where these addresses are not valid), they would have to be encapsulated in some other protocol.)
ffxe::/16224.0.1.0-238.255.255.255Global scopeEligible to be routed over the public internet.

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. [28] 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. [29] 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. [30]

AddressDescription
ff02::1All nodes on the local network segment
ff02::2All routers on the local network segment
ff02::5 OSPFv3 All SPF routers
ff02::6OSPFv3 All DR routers
ff02::8 IS-IS for IPv6 routers
ff02::9 RIP routers
ff02::a EIGRP routers
ff02::d PIM routers
ff02::12 Virtual Router Redundancy Protocol (VRRP) version 3
ff02::16 MLDv2 reports [31]
ff02::1:2All DHCPv6 servers and relay agents on the local network segment [32]
ff02::1:3All LLMNR hosts on the local network segment [33]
ff05::1:3All DHCPv6 servers on the local network site [32]
ff0x::c Simple Service Discovery Protocol
ff0x::fb Multicast DNS
ff0x::101 Network Time Protocol
ff0x::108 Network Information Service
ff0x::181 Precision Time Protocol (PTP) version 2 messages (Sync, Announce, etc.) except peer delay measurement
ff02::6b Precision Time Protocol (PTP) version 2 peer delay measurement messages
ff0x::114Used for experiments

Ethernet

Ethernet frames with a value of 1 in the least-significant bit of the first octet [note 2] 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. [34]

Some well known Ethernet multicast addresses [35]
BlockEthernet multicast address Ethertype Usage

01-80-C2 [36]
IEEE (802 group)

01-80-C2-00-00-00

Local LAN Segment, stopping at STP-capable switches
SNAP (length) Spanning Tree Protocol (for bridges) IEEE 802.1D
0x88CC Link Layer Discovery Protocol (additional)
01-80-C2-00-00-010x8808 Ethernet flow control (pause frame) IEEE 802.3x
01-80-C2-00-00-020x8809"Slow protocols" including Ethernet OAM Protocol (IEEE 802.3ah) and Link Aggregation Control Protocol (LACP)

01-80-C2-00-00-03

Local LAN Segment until next multi-port ("non-TPMR") switch
0x888EPort authentication (IEEE 802.1X EAPOL)
0x88CCLink Layer Discovery Protocol (additional)
01-80-C2-00-00-08SNAP (length)Spanning Tree Protocol (for provider bridges) IEEE 802.1ad
01-80-C2-00-00-0D0x88F5Multiple VLAN Registration Protocol (for provider bridges) IEEE 802.1ad
01-80-C2-00-00-0ELocal LAN Link, never crosses another device
0x88CC Link Layer Discovery Protocol (primary)
0x88F7 Precision Time Protocol (PTP) version 2 over Ethernet (802.1AS)
01-80-C2-00-00-210x88F5 GARP VLAN Registration Protocol (also known as IEEE 802.1Q GVRP)

Multiple VLAN Registration Protocol (MVRP)

01-80-C2-00-00-30 through
01-80-C2-00-00-3F		0x8902Ethernet CFM Protocol IEEE 802.1ag

01-1B-19
IEEE (TC9)

01-1B-19-00-00-000x88F7 Precision Time Protocol (PTP) version 2 over Ethernet (native layer-2)
for electing the Grandmaster clock and advanced applications, otherwise 01-80-C2-00-00-0E

01-00-5E [37]
ICANN/IANA

01-00-5E-00-00-00 through
01-00-5E-7F-FF-FF		0x0800IPv4 Multicast: [38] Insert the low 23 bits of the multicast IPv4 address into the Ethernet address [39] : §2.1.1 

33-33-xx
locally administered

33-33-00-00-00-00 through
33-33-FF-FF-FF-FF		0x86DDIPv6 multicast: [40] The low 32 bits an Ethernet address for IPv6 multicast traffic are the low 32 bits of the multicast IPv6 address used. [39] : §2.3.1  For example, IPv6 multicast traffic using the address ff02::d uses the MAC address 33-33-00-00-00-0D, and traffic to ff05::1:3 goes to the MAC address 33-33-00-01-00-03.

01-0C-CD
IEC

01-0C-CD-01-00-00 through
01-0C-CD-01-01-FF		0x88B8 IEC 61850-8-1 GOOSE Type 1/1A
01-0C-CD-02-00-00 through
01-0C-CD-02-01-FF		0x88B9GSSE (IEC 61850 8-1)
01-0C-CD-04-00-00 through
01-0C-CD-04-01-FF		0x88BAMulticast sampled values (IEC 61850 8-1)

01-00-0C
Cisco Systems

01-00-0C-CC-CC-CCSNAP (length) Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), Unidirectional Link Detection (UDLD)
01-00-0C-CC-CC-CDSNAP (length)Cisco Shared Spanning Tree Protocol Address[ citation needed ]

802.11

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

See also

Notes

  1. ↑ x is a place holder indicating that the value of the flags field is unimportant in the current discussion.
  2. ↑ 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.

Related Research Articles

An Internet Protocol address is a numerical label such as 192.0.2.1 that is assigned to a device connected to a computer network that uses the Internet Protocol for communication. IP addresses serve two main functions: network interface identification, and location addressing.

<span class="mw-page-title-main">IPv4</span> Fourth version of the Internet Protocol

Internet Protocol version 4 (IPv4) is the first version of the Internet Protocol (IP) as a standalone specification. It is one of the core protocols of standards-based internetworking methods in the Internet and other packet-switched networks. IPv4 was the first version deployed for production on SATNET in 1982 and on the ARPANET in January 1983. It is still used to route most Internet traffic today, even with the ongoing deployment of Internet Protocol version 6 (IPv6), its successor.

<span class="mw-page-title-main">IPv6</span> Version 6 of the Internet Protocol

Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion, and was intended to replace IPv4. In December 1998, IPv6 became a Draft Standard for the IETF, which subsequently ratified it as an Internet Standard on 14 July 2017.

Classless Inter-Domain Routing is a method for allocating IP addresses for IP routing. The Internet Engineering Task Force introduced CIDR in 1993 to replace the previous classful network addressing architecture on the Internet. Its goal was to slow the growth of routing tables on routers across the Internet, and to help slow the rapid exhaustion of IPv4 addresses.

Open Shortest Path First (OSPF) is a routing protocol for Internet Protocol (IP) networks. It uses a link state routing (LSR) algorithm and falls into the group of interior gateway protocols (IGPs), operating within a single autonomous system (AS).

<span class="mw-page-title-main">Subnet</span> Logical subdivision of an IP network

A subnetwork, or subnet, is a logical subdivision of an IP network. The practice of dividing a network into two or more networks is called subnetting.

<span class="mw-page-title-main">Classful network</span> Early system for organizing the IPv4 address space

A classful network is an obsolete network addressing architecture used in the Internet from 1981 until the introduction of Classless Inter-Domain Routing (CIDR) in 1993. The method divides the IP address space for Internet Protocol version 4 (IPv4) into five address classes based on the leading four address bits. Classes A, B, and C provide unicast addresses for networks of three different network sizes. Class D is for multicast networking and the class E address range is reserved for future or experimental purposes.

A broadcast address is a network address used to transmit to all devices connected to a multiple-access communications network. A message sent to a broadcast address may be received by all network-attached hosts.

In Internet networking, a private network is a computer network that uses a private address space of IP addresses. These addresses are commonly used for local area networks (LANs) in residential, office, and enterprise environments. Both the IPv4 and the IPv6 specifications define private IP address ranges.

The Neighbor Discovery Protocol (NDP), or simply Neighbor Discovery (ND), is a protocol of the Internet protocol suite used with Internet Protocol Version 6 (IPv6). It operates at the internet layer of the Internet model, and is responsible for gathering various information required for network communication, including the configuration of local connections and the domain name servers and gateways.

In computer networking, the multicast DNS (mDNS) protocol resolves hostnames to IP addresses within small networks that do not include a local name server. It is a zero-configuration service, using essentially the same programming interfaces, packet formats and operating semantics as unicast Domain Name System (DNS). It was designed to work as either a stand-alone protocol or compatible with standard DNS servers. It uses IP multicast User Datagram Protocol (UDP) packets and is implemented by the Apple Bonjour and open-source Avahi software packages, included in most Linux distributions. Although the Windows 10 implementation was limited to discovering networked printers, subsequent releases resolved hostnames as well. mDNS can work in conjunction with DNS Service Discovery (DNS-SD), a companion zero-configuration networking technique specified separately in RFC 6763.

IP multicast is a method of sending Internet Protocol (IP) datagrams to a group of interested receivers in a single transmission. It is the IP-specific form of multicast and is used for streaming media and other network applications. It uses specially reserved multicast address blocks in IPv4 and IPv6.

In the Internet addressing architecture, the Internet Engineering Task Force (IETF) and the Internet Assigned Numbers Authority (IANA) have reserved various Internet Protocol (IP) addresses for special purposes.

Internet Control Message Protocol version 6 (ICMPv6) is the implementation of the Internet Control Message Protocol (ICMP) for Internet Protocol version 6 (IPv6). ICMPv6 is an integral part of IPv6 and performs error reporting and diagnostic functions.

In computer networking, a link-local address is a network address that is valid only for communications on a local link, i.e. within a subnetwork that a host is connected to. Link-local addresses are most often unicast network addresses assigned automatically through a process known as stateless address autoconfiguration (SLAAC) or link-local address autoconfiguration, also known as automatic private IP addressing (APIPA) or auto-IP. Link-local addresses are not all unicast; e.g. IPv6 addresses beginning with ff02:, and IPv4 addresses beginning with 224.0.0. are multicast addresses that are link-local.

A unique local address (ULA) is an Internet Protocol version 6 (IPv6) address in the address range fc00::/7. These addresses are non-globally reachable. For this reason, ULAs are somewhat analogous to IPv4 private network addressing, but with significant differences. Unique local addresses may be used freely, without centralized registration, inside a single site or organization or spanning a limited number of sites or organizations.

<span class="mw-page-title-main">IPv6 address</span> Label to identify a network interface of a computer or other network node

An Internet Protocol version 6 address is a numeric label that is used to identify and locate a network interface of a computer or a network node participating in a computer network using IPv6. IP addresses are included in the packet header to indicate the source and the destination of each packet. The IP address of the destination is used to make decisions about routing IP packets to other networks.

An IPv6 packet is the smallest message entity exchanged using Internet Protocol version 6 (IPv6). Packets consist of control information for addressing and routing and a payload of user data. The control information in IPv6 packets is subdivided into a mandatory fixed header and optional extension headers. The payload of an IPv6 packet is typically a datagram or segment of the higher-level transport layer protocol, but may be data for an internet layer or link layer instead.

A solicited-node multicast address is an IPv6 multicast address used by the Neighbor Discovery Protocol to determine the link layer address associated with a given IPv6 address, which is also used to check if an address is already being used by the local-link or not, through a process called DAD. The solicited-node multicast addresses are generated from the host's IPv6 unicast or anycast address, and each interface must have a solicited-node multicast address associated with it.

References

  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. 1 2 3 4 5 M. Cotton; L. Vegoda; D. Meyer (March 2010). IANA Guidelines for IPv4 Multicast Address Assignments. IETF. doi: 10.17487/RFC5771 . ISSN   2070-1721. BCP 51. RFC 5771.Best Common Practice. Obsoletes RFC  3138 and 3171. Updates RFC  2780.
  3. 1 2 3 IP Multicast Routing Configuration Guide, Cisco , retrieved 2021-01-13
  4. ↑ AD-HOC Block 1
  5. 1 2 3 4 "IANA IP multicast addresses assignments". Internet Assigned Numbers Authority.
  6. ↑ SDP/SAP Block
  7. ↑ AD-HOC Block 2
  8. ↑ 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)
  9. ↑ AD-HOC Block 3
  10. ↑ Begen, A; Kyzivat, P; Perkins, C; Handley, M (January 2021). SDP: Session Description Protocol. Internet Engineering Task Force (IETF). doi: 10.17487/RFC8866 . ISSN   2070-1721. RFC 8866.Proposed Standard. Obsoletes RFC  4566.
  11. ↑ Handley, M; Perkins, C; Whelan, E (October 2000). Session Announcement Protocol. Network Working Group. doi: 10.17487/RFC2974 . RFC 2974.Experimental.
  12. ↑ 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.
  13. ↑ D. Meyer; P. Lothberg (February 2000). GLOP Addressing in 233/8. Network Working Group. doi: 10.17487/RFC2770 . RFC 2770.Obsolete. Obsoleted by RFC  3180.
  14. ↑ "Frequently Asked Questions (FAQ) File for Multicasting". Multicast Tech. Archived from the original on 2011-05-16.
  15. ↑ D. Meyer; P. Lothberg (September 2001). GLOP Addressing in 233/8. Network Working Group. doi: 10.17487/RFC3180 . BCP 53. RFC 3180.Best Common Practice. Obsoletes RFC  2770.
  16. ↑ M. Thaler (October 2010). Unicast-Prefix-Based IPv4 Multicast Addresses. Internet Engineering Task Force (IETF). doi: 10.17487/RFC6034 . ISSN   2070-1721. RFC 6034.Proposed Standard.
  17. 1 2 3 4 5 B. Haberman; D. Thaler (August 2002). Unicast-Prefix-based IPv6 Multicast Addresses. Network Working Group. doi: 10.17487/RFC3306 . RFC 3306.Proposed Standard. Updated by RFC  3956, 4489 and 7371.
  18. 1 2 D. Meyer (July 1998). Administratively Scoped IP Multicast. Network Working Group. doi: 10.17487/RFC2365 . BCP 23. RFC 2365.Best Common Practice.
  19. 1 2 3 4 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.
  20. ↑ "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.
  21. ↑ B. Cain; S. Deering; I. Kouvelas; B. Fenner; A. Thyagarajan (October 2002). Internet Group Management Protocol, Version 3. Network Working Group. doi: 10.17487/RFC3376 . RFC 3376.Proposed Standard. Updates RFC  2236. Updated by RFC  4604.
  22. ↑ C. Huitema (February 2006). Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs). Network Working Group. doi: 10.17487/RFC4380 . RFC 4380.Proposed Standard. Updated by RFC  5991 and 6081.
  23. ↑ "IPv4 Multicast Address Space Registry". www.iana.org. Retrieved 2024-06-30.
  24. ↑ Silvia Hagen (May 2006). IPv6 Essentials (Second ed.). O'Reilly. ISBN   978-0-596-10058-2.
  25. 1 2 3 P. Savola; B. Haberman (November 2004). Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address. Network Working Group. doi: 10.17487/RFC3956 . RFC 3956.Proposed Standard. Updated by RFC  7371. Updates RFC  3306.
  26. ↑ J-S. Park; M-K. Shin; H-J. Kim (April 2006). A Method for Generating Link-Scoped IPv6 Multicast Addresses. Network Working Group. doi: 10.17487/RFC4489 . RFC 4489.Proposed Standard. Updates RFC  3306.
  27. 1 2 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.
  28. ↑ "IPv6 Multicast Address Space Registry". Internet Assigned Numbers Authority.
  29. ↑ P. Savola (January 2008). Overview of the Internet Multicast Routing Architecture. Network Working Group. doi: 10.17487/RFC5110 . RFC 5110.Informational.
  30. ↑ S. Deering; W. Fenner; B. Haberman (October 1999). Multicast Listener Discovery (MLD) for IPv6. Network Working Group. doi: 10.17487/RFC2710 . RFC 2710.Proposed Standard. Updated by RFC  3590 and 3810.
  31. ↑ 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.
  32. 1 2 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.
  33. ↑ B. Aboba; D. Thaler; L. Esibov (January 2007). Link-Local Multicast Name Resolution (LLMNR). Network Working Group. doi: 10.17487/RFC4795 . RFC 4795.Informational.
  34. ↑ IEEE. "Standard Group MAC Address: A Tutorial Guide" (PDF). IEEE Standards Association. pp. 2–3. Archived from the original (PDF) on 2022-10-09.
  35. ↑ Patton, Michael A.; et al. "Multicast (including Broadcast) Addresses". cavebear.com. Karl Auerbach.
  36. ↑ "Standard Group MAC Address - Public Listing". IEEE-SA. Retrieved 30 November 2022.
  37. ↑ "IANA Multicast 48-bit MAC Addresses". IANA. Retrieved 31 January 2021.
  38. ↑ S. Deering (August 1989). Host Extensions for IP Multicasting. Network Working Group. doi: 10.17487/RFC1112 . STD 5. RFC 1112.Internet Standard 5. Obsoletes RFC  988 and 1054. Updated by RFC  2236.
  39. 1 2 D. Eastlake III; J. Abley (October 2013). IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters. Internet Engineering Task Force (IETF). doi: 10.17487/RFC7042 . ISSN   2070-1721. BCP 141. RFC 7042.Best Common Practice. Obsoletes RFC  5342. Updates RFC  2153.
  40. ↑ M. Crawford (December 1998). Transmission of IPv6 Packets over Ethernet Networks. Network Working Group. doi: 10.17487/RFC2464 . RFC 2464.Proposed Standard. Obsoletes RFC  1972.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.