Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site topaz.RUTGERS.EDU
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!columbia!topaz!hedrick
From: hedrick@topaz.RUTGERS.EDU (Charles Hedrick)
Newsgroups: net.dcom,net.lan
Subject: Re: TCP/IP and XNS compatibility ?
Message-ID: <3965@topaz.RUTGERS.EDU>
Date: Wed, 9-Oct-85 11:06:37 EDT
Article-I.D.: topaz.3965
Posted: Wed Oct  9 11:06:37 1985
Date-Received: Sat, 12-Oct-85 15:39:08 EDT
References: <151@ecrcvax.UUCP>
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 15
Xref: watmath net.dcom:1369 net.lan:1071

We have Dandelions talking to other systems on the Ethernet, so there
does not seem to be a compatibility problem at the Ethernet level.  We
are using Interlisp on the Dandelions, and it supposts TCP/IP, PUP,
and XNS.  We use PUP with our 4.2 systems (using Stanford's PUP
implementation, which Xerox distributes) and TCP/IP with other
systems.  If you are using the XDE or office system instead of
Interlisp, I think your only choice is XNS.  In that case, talk to
Xerox about XNS for your VAX.  I don't recall the exact state of that,
but they may have it. Someone else will have to comment on whether 4.3
XNS will suffice to support your Dandelions.  It is common for
non-Xerox "XNS" implementations to include only the lower levels, and
not Courier and the file server protocols.  I don't know hether 4.3
has this problem or not.  If so, it may be less use that you would
hope.
In that case, talk to Xerox about XNS software for