This is the talk page for discussing improvements to the IEEE 802.1Q article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1Auto-archiving period: 365 days |
This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
|
Note that the 'Q' is supposed to be upper case; see the IEEE web site: http://www.ieee802.org/1/pages/802.1Q.html. Although lower case is commonly used, it is technically incorrect. --Rick Sidwell 06:33, 17 December 2005 (UTC)
The text related to figure two states: "...in such cases, an alternate TPID such as hex 9100, or even 9200 or 9300, sometimes may be used for the outer tag; however this is being deprecated by 802.1ad, which specifies 88a8 for service-provider outer tags."
Shouldn't the figure TPID field then be changed to 88a8 since that is what is being usedm not 9100? —Preceding unsigned comment added by 77.110.39.122 (talk) 09:50, 26 November 2008 (UTC)
There is an error in the diagrams. The overall frame length should be bounded by the standard sizes of 64bytes - 1518 bytes. This should be the case regardless of the number of VLAN tags added.
Thus, the diagrams should read n=42-1496 for the single tagged frames, and n=38-1492 for the double tagged frame. —Preceding unsigned comment added by Neilneil2000 (talk • contribs) 11:37, 17 August 2009 (UTC)
Some amendmens have been made that add an explanation of using tagged frames for extended addressing. The relevant changes are:
There is no basis in IEEE or other standards, vendor implementations or elsewhere. If you have references describing frames extended in such a way, please feel free to add the explanations back with those references. I have reverted those changes again. —Preceding unsigned comment added by Stefan Bethke (talk • contribs) 10:07, 25 July 2010 (UTC)
[...]but the current (IEEE Std 802.1D- 2004) standard does not use the terms trunk or native.[...] -> I'm not quite sure, but 802.1D is "Rapid Spanning Tree Protocol" so shouldn't we instead refer to 802.1Q here? 217.91.83.80 (talk) 12:35, 27 January 2011 (UTC)
The correct order of the header fields is DMAC, SMAC, Type, Dot1Q tag, and so on. This article's header image shows the Dot1Q tag preceding the Type field. But the Type field value of 0x8100 indicates that a Dot1Q tag is the following field in the header. The Dot1Q tag shouldn't precede the Type field. Note when the Type field is less than 1500 (decimal) is denotes the payload size of the frame in bytes and is known as the Length. When the Type field is over 1536 it denotes the Type of payload. Some examples are: IPv4 – 0x0800 IPv6 – 0x86dd ARP – 0x0806 802.1Q – 0x8100 45.30.36.245 (talk) 23:07, 26 April 2023 (UTC)