Talk:Multicast address: Difference between revisions

Content deleted Content added

Inline

Revision as of 19:11, 28 June 2011

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
???	This article has not yet received a rating on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by Networking task force.

Links from this article which need disambiguation (check | fix): [[Layer 3]], [[OSI]]

For help fixing these links, see Wikipedia:WikiProject Disambiguation/Fixing a page.

Added by WildBot | Tags to be removed | FAQ | Report a problem

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

typo?

should

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

be

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

instead?

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)[reply]

Ethernet Multicast is IP Multicast too?

It is not completely clear if the Ethernet multicast addresses mentioned in the article are exclusively used in combination with IP Multicast protocols rather than any alternate multicast protocols.

If this is the case I would suggest this article to link directly to the protocol it applies to, as in:

In computer networking a multicast address is an identifier for a group of hosts that have joined a multicast group using the IP Multicast protocol.

--SymlynX 17:33, 26 November 2006 (UTC)[reply]

IP address format

In the article, it says, "It ranges from 224.0.0.0 to 239.255.255.255, or, equivalently, 224.0.0.0/4" - shouldn't this last part read "224/4"? Hex equivalents would be E0.00.00.00 to EF.FF.FF.FF. Maybe the article should mention and define the two different styles of writing the IP ranges? Cbdorsett 07:37, 25 January 2007 (UTC)[reply]

"224/4" is read as 0.0.0.224/24 if you strictly adhere to standards. What you can write is 224.0/24, but 224.0.0.0/4 is perfectly fine and the least confusing. --Eqvinox (talk) 19:11, 28 June 2011 (UTC)[reply]

L2 before L3

I would like to suggest that the Ethernet section at the bottom is moved to before the IPv4 and IPv6 section. This makes the order of the sections consistent with the layer order. —Preceding unsigned comment added by 77.110.39.122 (talk) 07:53, 12 December 2008 (UTC)[reply]

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)[reply]

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)[reply]

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)[reply]

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)[reply]

@@ Line 32: / Line 32: @@
 In the article, it says, "It ranges from 224.0.0.0 to 239.255.255.255, or, equivalently, 224.0.0.0/4" - shouldn't this last part read "224/4"? Hex equivalents would be E0.00.00.00 to EF.FF.FF.FF. Maybe the article should mention and define the two different styles of writing the IP ranges? [[User:Cbdorsett|Cbdorsett]] 07:37, 25 January 2007 (UTC)
+:"224/4" is read as 0.0.0.224/24 if you strictly adhere to standards. What you can write is 224.0/24, but 224.0.0.0/4 is perfectly fine and the least confusing. --[[User:Eqvinox|Eqvinox]] ([[User talk:Eqvinox|talk]]) 19:11, 28 June 2011 (UTC)
 == L2 before L3 ==