home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- Path: sparky!uunet!math.fu-berlin.de!fauern!fauna!eckert
- From: eckert@immd4.informatik.uni-erlangen.de (Toerless Eckert)
- Subject: Re: What are the Pros/Cons of Multi-protocol routing?
- References: <l9aeprINNsg0@noc.near.net>
- Message-ID: <BtFIno.6DD@immd4.informatik.uni-erlangen.de>
- Organization: CSD., University of Erlangen, Germany
- Distribution: usa
- Date: Sun, 23 Aug 1992 09:06:59 GMT
- Lines: 36
-
- From article <l9aeprINNsg0@noc.near.net>, by kwe@noc.near.net (Kent England):
- > In article <86673@netnews.upenn.edu> Anthony Olejnik writes:
- >
- > TCP/IP has more sophisticated routing protocols than many of the other
- > internet protocols you can run, and it and OSI are the only protocols
- > suitable for a public internet.
-
- RSCS has proven to live in the large too ;-))
- >
- > The disadvantage of a single protocol backbone is tunneling everything
- > else when routing is easier.
-
- So, what about public data networks (or VDNs) with X.25 or Frame Relay ?
- In a way this is tunneling too, only that you would not consider
- Frame Relay by itself an Internet network protocol, but X.25 could be.
-
- > But tunneling is sometimes necessary such as for getting AppleTalk across
- > the Internet, for source routed bridging across a complex WAN, or for
- > tunneling SDLC.
- >
- > Don't underestimate the complexity of supporting additional protocols
- > whether tunneled or routed. Make sure you have enough features and
- > filters to control them. But if they are important enough to your
- > situation, then by all means support them.
-
- Yes, one should really weight the need for the additional protocol against
- the trouble it will cause.
-
- An important point with multiple protocols is the step towards integrated
- routing protocols in my opinion.
-
- --
-
- Toerless.Eckert@informatik.uni-erlangen.de
- /C=de/A=dbp/P=uni-erlangen/OU=informatik/S=Eckert/G=Toerless/
- 2b or not 2b that is ff
-