osmocom
/
wireshark
14
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Update a comment to reflect reality as of 1997. 

"IEEE 802.3" has, since IEEE 802.3y-1997, supported a type/length field,
not just a length field (i.e., they acknowledged reality), so it's no
as if there are "802.3" as opposed to "D/I/X" or "Ethernet II" frames.

Change-Id: Ie7f61e48cb2a343a7c83e0747a6eee46964fc335
Reviewed-on: https://code.wireshark.org/review/9858
Reviewed-by: Guy Harris <guy@alum.mit.edu>
This commit is contained in:
Guy Harris 2015-08-03 14:14:50 -07:00
parent ae05f77630
commit 2964c281ab
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
epan/dissectors/packet-ieee8023.c
View File

@ -1,5 +1,12 @@
/* packet-ieee8023.c
* Routine for dissecting 802.3 (as opposed to D/I/X Ethernet) packets.
* Routine for dissecting Ethernet packets with a length field (as opposed
* to a type field).
*
* The name "ieee8023" is historical, dating back to when IEEE Std 802.3
* had only a length field and expected all packets to have an 802.2
* header following the MAC header. Since IEEE 802.3y-1997, 802.3
* supports either a type field or a length field, so it's no longer
* correct to refer to "802.3" vs. "D/I/X" or vs. "Ethernet II" frames.
*
* Wireshark - Network traffic analyzer
* By Gerald Combs <gerald@wireshark.org>