EtherType is a two-octet field in an Ethernet frame. It is used to indicate which protocol is encapsulated in the payload of the frame and is used at the receiving end by the data link layer to determine how the payload is processed. The same field is also used to indicate the size of some Ethernet frames.
In modern implementations of Ethernet, the field within the Ethernet frame used to describe the EtherType can also be used to represent the size of the payload of the Ethernet Frame. Historically, depending on the type of Ethernet framing that was in use on an Ethernet segment, both interpretations were simultaneously valid, leading to potential ambiguity. Ethernet II framing considered these octets to represent EtherType while the original IEEE 802.3 framing considered these octets to represent the size of the payload in bytes.
In order to allow Ethernet II and IEEE 802.3 framing to be used on the same Ethernet segment, a unifying standard, IEEE 802.3x-1997, was introduced that required that EtherType values be greater than or equal to 1536. That value was chosen because the maximum length (MTU) of the data field of an Ethernet 802.3 frame is 1500 bytes. Thus, values of 1500 and below for this field indicate that the field is used as the size of the payload of the Ethernet frame while values of 1536 and above indicate that the field is used to represent an EtherType. The interpretation of values 1501–1535, inclusive, is undefined.
The end of a frame is signaled by loss of carrier or by a special symbol or sequence in the line coding scheme for a particular Ethernet physical layer, so the length of the frame does not always need to be encoded as a value in the Ethernet frame. However, as the minimum payload of an Ethernet frame is 46 bytes, a protocol which uses EtherType must include its own length field if that is necessary for the recipient of the frame to determine the length of short packets (if allowed) for that protocol.
802.1Q VLAN tagging uses an 0x8100 EtherType value. The payload following includes a 16-bit tag control identifier (TCI) followed by an Ethernet frame beginning with a second (original) EtherType field for consumption by end stations. IEEE 802.1ad extends this tagging with further nested EtherType and TCI pairs.
The size of the payload of non-standard jumbo frames, typically ~9000 Bytes long, falls within the range used by EtherType, and cannot be used for indicating the length of such a frame. The proposition to resolve this conflict was to substitute the special EtherType value 0x8870 when a length would otherwise be used. However, the proposition (its use case was bigger packets for IS-IS) was not accepted and it is defunct. The chair of IEEE 802.3 at the time, Geoff Thompson, responded to the draft outlining IEEE 802.3's official position and the reasons behind the position. The draft authors also responded to the chair's letter, but no subsequent answer from the IEEE 802.3 has been recorded.
With the advent of the IEEE 802 suite of standards, a Subnetwork Access Protocol (SNAP) header combined with an IEEE 802.2 LLC header is used to transmit the EtherType of a payload for IEEE 802 networks other than Ethernet, as well as for non-IEEE networks that use the IEEE 802.2 LLC header, such as FDDI. However, for Ethernet, Ethernet II framing is still used.
EtherTypes are assigned by the IEEE Registration Authority. Not all well-known uses of EtherTypes are recorded in the IEEE list of EtherType values. For example, EtherType 0x0800 (used by IPv4) does not appear in the IEEE list. The Internet Assigned Numbers Authority has a separate list of some EtherType registrations, compiled from several sources, including the IEEE Registration Authority's list and some other lists; that list includes 0800.
|0x0800||Internet Protocol version 4 (IPv4)|
|0x0806||Address Resolution Protocol (ARP)|
|0x22F0||Audio Video Transport Protocol (AVTP)|
|0x22F3||IETF TRILL Protocol|
|0x22EA||Stream Reservation Protocol|
|0x6002||DEC MOP RC|
|0x6003||DECnet Phase IV, DNA Routing|
|0x8035||Reverse Address Resolution Protocol (RARP)|
|0x80F3||AppleTalk Address Resolution Protocol (AARP)|
|0x8100||VLAN-tagged frame (IEEE 802.1Q) and Shortest Path Bridging IEEE 802.1aq with NNI compatibility|
|0x8102||Simple Loop Prevention Protocol (SLPP)|
|0x8103||Virtual Link Aggregation Control Protocol (VLACP)|
|0x86DD||Internet Protocol Version 6 (IPv6)|
|0x8808||Ethernet flow control|
|0x8809||Ethernet Slow Protocols such as the Link Aggregation Control Protocol (LACP)|
|0x8863||PPPoE Discovery Stage|
|0x8864||PPPoE Session Stage|
|0x887B||HomePlug 1.0 MME|
|0x888E||EAP over LAN (IEEE 802.1X)|
|0x889A||HyperSCSI (SCSI over Ethernet)|
|0x88A2||ATA over Ethernet|
|0x88A8||Service VLAN tag identifier (S-Tag) on Q-in-Q tunnel.|
|0x88AB||Ethernet Powerlink|
|0x88B8||GOOSE (Generic Object Oriented Substation event)|
|0x88B9||GSE (Generic Substation Events) Management Services|
|0x88BA||SV (Sampled Value Transmission)|
|0x88BF||MikroTik RoMON (unofficial)|
|0x88CC||Link Layer Discovery Protocol (LLDP)|
|0x88DC||WSMP, WAVE Short Message Protocol|
|0x88E3||Media Redundancy Protocol (IEC62439-2)|
|0x88E5||MAC security (IEEE 802.1AE)|
|0x88E7||Provider Backbone Bridges (PBB) (IEEE 802.1ah)|
|0x88F7||Precision Time Protocol over IEEE 802.3 Ethernet|
|0x88FB||Parallel Redundancy Protocol (PRP)|
|0x8902||IEEE 802.1ag Connectivity Fault Management (CFM) Protocol / ITU-T Recommendation Y.1731 (OAM)|
|0x8906||Fibre Channel over Ethernet (FCoE)|
|0x8914||FCoE Initialization Protocol|
|0x8915||RDMA over Converged Ethernet (RoCE)|
|0x891D||TTEthernet Protocol Control Frame (TTE)|
|0x892F||High-availability Seamless Redundancy (HSR)|
|0x9000||Ethernet Configuration Testing Protocol|
|0x9100||VLAN-tagged (IEEE 802.1Q) frame with double tagging|
|0xF1C1||Redundancy Tag (IEEE 802.1CB Frame Replication and Elimination for Reliability)|