Xref: utzoo comp.protocols.tcp-ip:13828 comp.sys.dec:4557
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!bu.edu!polygen!rbraun
From: rbraun@polygen.uucp (Richard Braun)
Newsgroups: comp.protocols.tcp-ip,comp.sys.dec
Subject: Re: DECnet encapsulation in TCP-IP
Message-ID: <897@fred.UUCP>
Date: 19 Nov 90 20:01:53 GMT
References: <90313.134117JHL1@psuvm.psu.edu> <15782@cbmvax.commodore.com>
Reply-To: rbraun@fred.UUCP (Richard Braun)
Organization: Polygen Corporation, Waltham, MA
Lines: 27

grr@cbmvax.commodore.com (George Robbins) writes:
>In article <90313.134117JHL1@psuvm.psu.edu> JHL1@psuvm.psu.edu writes:
>> We're interested in encapsulating DECnet within a TCP-IP package.  We
>> are looking primarily for a software solution...
>
>I believe TGV multinet can handle this...

MultiNet is, IMHO, far and away the best TCP/IP package available for
VAX/VMS.  (This after reviewing products ranging from Process Software
to Fusion to Wollongong to...)  It's a Stanford-bred product written
in C with some TOPS-20'isms in it.

But I fail to understand the original question:  "encapsulating DECnet
within TCP/IP".  That just doesn't mean anything.  It could mean
buying a binary license to DECnet and one to TCP/IP and writing an
application which calls both.  Or it could mean buying a MultiNet
source license for $megabucks plus a TCI "CommUnity" DECnet source
license for $megabucks and integrating the two.  Or it could mean
going to DEC or Equinox or some other company and buying a LAT/TCP
terminal server to hook onto your Ethernet.  As you can see, you
can come up with solutions that cost anywhere from $3,000 to
$3,000,000.

What's the need, anyway?  And was it on VMS-only or does it have to be
platform-independent?

-rich