Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!sgi!vjs@rhyolite.wpd.sgi.com From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver) Newsgroups: comp.dcom.lans Subject: Re: Ethernet alternative needed Summary: RFC-1042 Message-ID: <43263@sgi.sgi.com> Date: 20 Oct 89 00:04:20 GMT References: <9478@zodiac.ADS.COM> <2406@umbc3.UMBC.EDU> <43037@sgi.sgi.com> <6207@b11.ingr.com> Sender: vjs@rhyolite.wpd.sgi.com Distribution: na Organization: Silicon Graphics, Inc., Mountain View, CA Lines: 29 In article <6207@b11.ingr.com>, goodloe@b11.ingr.com (Tony Goodloe) writes: > > Something that I should , don't -- Is only difference > between an Ethernet frame and an 802.3 frame the usage of the > type/length field. I see how this causes problems. Are there any other > differences that I don't know. I have a real 802.3 spec, but no > Ethernet "spec", if one exists. > > tony "ground me but once" goodloe The "only" difference is the type/length field. However, that difference implies an extra 8-byte LLC header before the good stuff in IP, ARP, and ICMP packets (except where it is/was 3-bytes), as well as code to respond to some LLC ethernet packets. There are also changes in the "hardware type code" of ARP packets and perhaps RFC-951/bootp packets. The groady details are in RFC-1042 and IEEE 802.2. Similar things for FDDI (where we have no option) are in the soon to be replaced and/or updated RFC-1103. Vernon Schryver Silicon Graphics vjs@sgi.com P.S. There may be a difference in stuff like dribble bits, but who cares enough about such to look it up?