Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!NEPTUNE!MEGGERS
From: meggers@NEPTUNE.NTS.UCI.EDU (mark eggers)
Newsgroups: bit.listserv.novell
Subject: What TCP/IP suuport is there going to be, anyhow?
Message-ID: <9002011243.aa24928@orion.oac.uci.edu>
Date: 1 Feb 90 20:29:08 GMT
Sender: Novell LAN Interest Group <NOVELL@SUVM>
Reply-To: Novell LAN Interest Group <NOVELL@SUVM>
Lines: 30
Approved: NETNEWS@PSUVM Gateway
Return-path: meggers@neptune.nts.uci.edu
X-cc:         Mark Eggers <meggers@uci.edu>

There has been a LOT of discussion on just what TCP/IP support there will be
in 386 3.1. I have yet to get any definitive answers. This disturbs me,
because at least two divisions in our university are depending upon their
interpretations of Novell's TCP/IP support to make the internetworking possible.

I have a list of wants and questions that I hope are specific enough to get
reasonable answers to (by reasonable, I mean something that I can design
networks from).

1.      From a PC, will I be able to access an IP host while simultaneously
        running IPX? I know about the packet driver - it's great - but
        some departments are reluctant to use it.

2.      If I have an intervening IP network, will a PC on one IPX network
        be able to access the services on the other IPX network? If so,
        what hardware/software would I need?

3.      There are rumors that the new Novell 'bridges' will ROUTE IP. Is
        this true (in the proper sense of routing as opposed to bridging)?
        If so, what routing protocol will be employed? Will the routing
        protocol interoperate with other vendors' routers?

And now, the $64,000 question:

        If the above are all possible, when??

Mark Eggers, Data Communications Analyst, University of California, Irvine

phone:  (714) 856-6845
email:  mark-eggers@uci.edu