Xref: utzoo comp.protocols.tcp-ip:13832 comp.sys.dec:4558
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!cbmvax!grr
From: grr@cbmvax.commodore.com (George Robbins)
Newsgroups: comp.protocols.tcp-ip,comp.sys.dec
Subject: Re: DECnet encapsulation in TCP-IP
Message-ID: <15986@cbmvax.commodore.com>
Date: 20 Nov 90 18:06:56 GMT
References: <90313.134117JHL1@psuvm.psu.edu> <15782@cbmvax.commodore.com> <897@fred.UUCP>
Reply-To: grr@cbmvax.commodore.com (George Robbins)
Organization: Commodore, West Chester, PA
Lines: 26

In article <897@fred.UUCP> rbraun@fred.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...
> 
> But I fail to understand the original question:  "encapsulating DECnet
> within TCP/IP".  That just doesn't mean anything.  It could mean
> buying...

Usually enscapulation means that you have a network path that supports
only one protocol, such as a point-to-point DECnet link, over which you
would like to have packets for some other protocol such as TCP/IP pass
transparently.  This is pretty much the opposite of what a gateway does.

Wollengong, Multinet and probably countless others handle the case of
getting TCP through a VMS DECnet link, I assume that this person was
interested in doing the opposite, trying to get a transparent DECnet
link over an internet or other "TCP/IP" path.

-- 
George Robbins - now working for,     uucp:   {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing:   domain: grr@cbmvax.commodore.com
Commodore, Engineering Department     phone:  215-431-9349 (only by moonlite)