Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84; site opus.UUCP
Path: utzoo!linus!decvax!genrad!panda!talcott!harvard!seismo!hao!nbires!opus!mccallum
From: mccallum@opus.UUCP (Doug McCallum)
Newsgroups: net.lan
Subject: Re: Need help with Ethernet
Message-ID: <1214@opus.UUCP>
Date: Thu, 23-May-85 23:32:11 EDT
Article-I.D.: opus.1214
Posted: Thu May 23 23:32:11 1985
Date-Received: Mon, 27-May-85 06:56:44 EDT
References: <185@geowhiz.UUCP> <2027@topaz.ARPA>
Distribution: net
Organization: NBI,Inc, Boulder CO
Lines: 17

> implement IEEE 802.3 in a way that maintains compatibility with machines
> that use the Ethernet definitions. I don't know whether any vendors have
> actually implemented IEEE 802.3, and if so whether they did the extra work
> needed to be compatible with Ethernet. So far we haven't run into any real
> implementations of IEEE 802.3. (As I said above, most of the people who

Don't confuse the IEEE 802.3 standard with the IEEE 802.2 standard. 802.3
specifies a "media access method" of CSMA/CD and describes what is basically
Ethernet Version 2.0 with the type field called a length field. It is 
possible to be IEEE 802.3 compatible without implementing the IEEE 802.2
"Logical Link Control" protocol.  The vendors claiming 802.3 compatibity
probably are.  Full IEEE 802 compliance is another matter.  Very few
802.2 implementations are available.

			Doug McCallum
			NBI, Inc.
			{ucbvax, allegra, ut-sally}!nbires!mccallum