Talk:Multicast address/Archive 1

Misleading lead?

The lead includes a rather misleading sentence: "Multicast addressing can be used in the Link Layer (OSI Layer 2), such as Ethernet multicast, as well as at the Internet Layer (OSI Layer 3) as IPv4 or IPv6 multicast." The problem is that OSI Layer 2 is not called "Link Layer" it is called "Data Link Layer". OSI Layer 3 is not called "Internet Layer", it is called "Network Layer". Link Layer and Internet Layer are not from the OSI model, but from the Internet Protocol Suite. Was this done on purpose? --Muhandes (talk) 17:34, 5 July 2010 (UTC)

This stuff is a common source of confusion. I doubt it was done on purpose. WP:SOFIXIT --Kvng (talk) 23:54, 5 July 2010 (UTC)

Done. I just thought there was something behind it. Oh, and I just had to use the pun "misleading lead". --Muhandes (talk) 00:15, 6 July 2010 (UTC)

STP is not encapsulated through EtherType

The EtherType 0x0802 is not correct in the Ethernet section. The protocol STP is encapsulated in MAC by using length and LLC, and not EtherType. The layer LLC is either classical (LSAP = 42-42), either with the SNAP format(AA-AA)and PID = 01-0B.

I propose to remove the column "Type Field". Regards, 27 February 2011, Michel Hostet. —Preceding unsigned comment added by 82.120.137.91 (talk) 22:21, 27 February 2011 (UTC)

ACK from me, the protocol field is confusing in those cases. I'd keep it for IP/IPv6 though, maybe just replace the wrong values with the word "LLC"? --Eqvinox (talk) 19:13, 28 June 2011 (UTC)

Administratively scoped IPv4 multicast addresses

I noticed that the article references RFC 2365, but there is no mention in the article about the administratively-scoped IPv4 multicast address block, 239.0.0.0 - 239.255.255.255.

Would there be any objections to adding a section that covers this?

Imfargo (talk) 21:48, 23 February 2012 (UTC)

Section added. Please review.

Imfargo (talk) 21:40, 25 February 2012 (UTC)

Looks good. Thanks. And welocme to Wikipedia! --Kvng (talk) 17:36, 4 March 2012 (UTC)

Link for "Frequently Asked Questions (FAQ) File for Multicasting" Is Broken

The references contain a link for the above FAQ, but the link redirects to the root web site (which is German?) and no FAQ can be found. — Preceding unsigned comment added by 206.16.226.196 (talk) 20:19, 17 October 2012 (UTC)

"Registration" of Multicast

How does one go about registering for a multicast address, to avoid collisions with other vendors?

Family Guy Guy (talk) 13:54, 8 October 2015 (UTC)

IP multicast addresses are administered by IANA. Ethernet multicasts are administered by IEEE. ~Kvng (talk) 14:34, 11 October 2015 (UTC)

Table on Multicast Address Scope

I suggest to title the first column 'Scope' and only list the 4 relevant bits. This would be more consistent with the table on the multicast address flags.

Tommiie (talk) 09:09, 27 June 2017 (UTC)

Include non IANA registered 'well known' addresses?

I was thinking of editing the multicast address table to include CARP in the description of 224.0.0.18. I would consider this to be a fairly well known and often encountered protocol.

I propose changing the description of the table to reflect that it contains IANA and non-IANA registered addresses. The text describing link to the IANA Internet Multicast Addresses page would be clarified to inform the reader they can view the IANA list of registered multicast addresses.

rex 21:49, 22 May 2006 (UTC)

I've never encountered CARP in a production network, but who am I? I'm in favor of adding CARP and other non-IANA registered addresses, i.e. notable but not necessarily registered with IANA - similar to the List of TCP and UDP port numbers. Tommiie (talk) 09:49, 28 June 2017 (UTC)

typo?

should

ffx0::/16 and ff0f::/16 are reserved.

be

ffx0::/16 and ffxf::/16 are reserved.

instead?

Yes, those 4 bits are flags for all multicast addresses. I have corrected. ~Kvng (talk) 20:13, 20 May 2021 (UTC)