Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!sgi!rpw3@rigden.wpd.sgi.com
From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
Newsgroups: comp.dcom.lans
Subject: Re: 802.3 vs ethernet
Message-ID: <112424@sgi.sgi.com>
Date: 22 Jun 91 01:47:42 GMT
References: <1991Jun21.162957.24583@nas.nasa.gov>
Sender: guest@sgi.sgi.com
Reply-To: rpw3@sgi.com (Rob Warnock)
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 28

In article <1991Jun21.162957.24583@nas.nasa.gov> storm@nas.nasa.gov
(Steve Storm) writes:
+---------------
| I'll gice you one thing I have found that is amusing.  One of our
| machine types is SGI workstations.  Checking the docs reveals this
| information.  Yes, their chip set understands 802.3.  No, their software
| doesn't understand 802.3.  Where does this leave me?  (Waiting for the
| next release, that's where.)
+---------------

As far as I know, we have no plans for *ever* talking 802.3-style TCP, in
the next release or any other. The 802.2 SAP for TCP was deprecated at the
first TCP/IP Interoperability Conference, and anyone who is still using
it is out of step, not us. We use Ethernet encapuslation on Ethernets, and
RFC 1103 802.2/SNAP/"Ethernet" encapsulation on FDDI.

Obviously, if we were to offer an ISO protocol product at some point, it
would use 802.3 encapsulation for the ISO packets [with the appropriate 802.2
SAP(s)]. But TCP would continue to use Ethernet encapsulation.


-Rob

-----
Rob Warnock, MS-1L/515		rpw3@sgi.com		rpw3@pei.com
Silicon Graphics, Inc.		(415)335-1673		Protocol Engines, Inc.
2011 N. Shoreline Blvd.
Mountain View, CA  94039-7311