Xref: utzoo comp.protocols.tcp-ip:13841 comp.sys.dec:4569
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!mvb.saic.com!dayton.saic.com!fac2
From: fac2@dayton.saic.com (Earle Ake)
Newsgroups: comp.protocols.tcp-ip,comp.sys.dec
Subject: Re: DECnet encapsulation in TCP-IP
Message-ID: <1990Nov20.133921.1332@dayton.saic.com>
Date: 20 Nov 90 17:39:21 GMT
References: <90313.134117JHL1@psuvm.psu.edu> <15782@cbmvax.commodore.com> <897@fred.UUCP>
Organization: Science Applications Intl. Corp., Dayton, Ohio
Lines: 28

In article <897@fred.UUCP>, rbraun@polygen.uucp (Richard Braun) writes:
> 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.

	I think what he means is sending DECnet packages inside of TCP/IP
packets.  I am using IP over DECnet right now.  My TCP/IP packets are
enclosed in DECnet packets, sent over our company DECnet and received by
a machine that 'unwraps' them and then sends them off to the Internet.

-- 
_____________________________________________________________________________
             ____ ____    ___
Earle Ake   /___ /___/ / /     Science Applications International Corporation
           ____//   / / /__                 Dayton, Ohio
-----------------------------------------------------------------------------
Internet: fac2@dayton.saic.com             uucp: dayvb!fac2