Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!mips!pacbell.com!tandem!netcom!jbreeden
From: jbreeden@netcom.UUCP (John Breeden)
Newsgroups: comp.sys.novell
Subject: Re: Encapulation of Novell IPX packets over TPC/IP networks?
Message-ID: <19477@netcom.UUCP>
Date: 28 Dec 90 02:06:22 GMT
References: <1044@rsp.UUCP> <11090002@acf3.NYU.EDU>
Organization: Netcom- The Bay Area's Public Access Unix System {408 241-9760 guest}
Lines: 24

In article <11090002@acf3.NYU.EDU> chapman@acf3.NYU.EDU (Gary Chapman) writes:
>Can you explain basically how this works?  Who encapsulates ipx/spx in ip
>and who un-encapsulates?  - Gary Chapman, NYU

Take the WHOLE Netware datagram and stick it in a tcp-ip datagram as data.

The package from Europe runs as a VAP on a server and acts just like Netware's 
"bridge" (why oh why does Novell call a router a "bridge", must be the same 
one who decided that Novell's brain dead 802.2 header quailifies as IEEE).
It's the VAP in the servers that incap/unincapsulate.

The advantage? Now you can use "real" routers like Cisco or Wellfleet, add
HDLC, SLIP and PPP links, router management via SNMP etc, and best of 
all - get rid of RIP.

BTW: Banyan does the same thing (encapsulation) with their "server to server
tcp-ip option".
-- 
 John Robert Breeden, 
 netcom!jbreeden@apple.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden
 -------------------------------------------------------------------
 "The nice thing about standards is that you have so many to choose 
  from. If you don't like any of them, you just wait for next year's 
  model."