Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!ftp.UUCP!jbvb
From: jbvb@ftp.UUCP.UUCP
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Arcnet and TCP/IP
Message-ID: <8710300632.AA19039@spdcc.COM>
Date: Fri, 30-Oct-87 00:53:35 EST
Article-I.D.: spdcc.8710300632.AA19039
Posted: Fri Oct 30 00:53:35 1987
Date-Received: Sat, 31-Oct-87 17:47:12 EST
References: <8710292103.AA03815@orchid.uucp>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 11

As of this moment, I don't know of any standard encapsulation for IP on ARCnet.
That would need thought and discussion, along with parallel issues like "to
ARP or not to ARP", "802.2, 802.2, wherefore art thou 802.2" and "trailer,
trailer, who's got the trailer".  Then, it should go in an RFC.

I think you might find Standard Microsystems? (somewhere on Long Island,
a big manufacturer of ARCnet hardware), receptive to your efforts.  You
might also cast about on the mailing lists for anyone who has already done
an encapsulation scheme, to save some design work, and gain compatibility.

jbvb