Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!ucbcad!ucbvax!ftp.UUCP!jbvb
From: jbvb@ftp.UUCP (James Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip
Subject: ARCnet
Message-ID: <8711061746.AA09873@spdcc.COM>
Date: Fri, 6-Nov-87 12:27:19 EST
Article-I.D.: spdcc.8711061746.AA09873
Posted: Fri Nov  6 12:27:19 1987
Date-Received: Wed, 11-Nov-87 19:41:30 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 18

Is there any standard for ARCnet encapsulation of IP?  Has anyone even done it?
Given things I have heard from ARCnet manufacturers, example hardware drivers
are available.

The process looks like:

1. Locate or develop a standard for IP encapsulation and address resolution.
I have been told that ARCnet has a 1-byte hardware address.  This would seem
to point at a convention like ProNET (map low byte of the hardware address to
the low byte of the IP address), instead of a permutation of ARP.

2. Obtain an example hardware driver and some hardware.  Starting with MIT's
P1300 driver, I would imagine that one could get on-line in a month or
less.  I would probably have already done this if I had time, or felt
sufficiently wizardly to promulgate an encapsulation scheme.

James B. VanBokkelen
FTP Software Inc.