| |
PA2AGA > TCPDIG 26.07.96 23:16l 125 Lines 4888 Bytes #-10939 (0) @ EU
BID : TCP_96_155B
Read: GUEST
Subj: TCP-Group Digest 96/155B
Path: DB0AAB<DB0PV<DB0MAK<DB0SON<DB0SIF<DB0AIS<DB0NDK<DB0ACH<DB0ACC<PI8DRS<
PI8DAZ<PI8GCB<PI8WFL<PI8VNW
Sent: 960726/1753Z @:PI8VNW.#ZH2.NLD.EU #:36604 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA14277 ; Fri, 26 Jul 96 17:39:15 UTC
Received: from pa2aga-1 by pa2aga (NET/Mac 2.3.60/7.1) with SMTP
id AA00001649 ; Fri, 26 Jul 96 19:32:09 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.60/7.5.3) with SMTP
id AA00007605 ; Fri, 26 Jul 96 19:21:59 MET
Date: Fri, 26 Jul 96 19:17:36 MET
Message-Id: <tcp_96_155B>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 96/155B
X-BBS-Msg-Type: B
The Internet has a similar problem. They keep buying bigger routers.
TSRN> First of all the problem as I am seeing it. In the 3 months
TSRN> that I have had gw.n1kio running I have seen many new GWs
TSRN> come on line and encap.txt grow. As encap.txt grows it is
TSRN> eating more and more of my memory in this dos based system.
TSRN> No I don't want to hear 'switch to linux/unix/os/2'. I like
TSRN> running in dos and many of us don't want to switch.
First of all, the memory limitations of DOS have always been a big problem.
Other than changing operating systems, your only real option is to move to a
DOS extender such as comes with the djgpp package. Even that, however, is not
much of a solution, since the minimum machine would be a 386SX, the same as
for
Linux or OS/2. There would be a memory advantage in that Linux and OS/2 both
require a minimum of 4 MB, but that is an absurd concern with RAM selling for
only about US$4 per megabyte.
TSRN> I am wondering why we havn't started regional 'routers' so
TSRN> that we don't have to carry the full encap.txt. I just get
TSRN> the feeling that is would be better if we had a major
TSRN> 'router' that we would default to, and that router would
TSRN> then route out of our 'local' region.
In my opinion, this would be an extremely bad idea. AXIP is already a kludge
from the point of view of routers, capable of introducing substantial
inefficiency that has to be managed away by hand. In effect, your proposal
would not only introduce such gross inefficiency, but would make it harder to
know that it had happened. You could eventually impose a netrom-style routing
debacle onto the Amprnet using techiques like this.
TSRN> Yes I know it would take some work to set up something like
TSRN> this. But as the ammount of new gateways grows, sooner or
TSRN> latter, most of us will have to start droping routing off of
TSRN> our systems. I can see encap.txt growing to over 50 K in the
TSRN> next 2 years.
If you are incapable of storing a global routing table at your level of
indirection, you can't play anymore. I have always sympathized in these
debates with the end users who want to run NOS on an XT, but that is a
ridiculous constraint to impose on major routers and gateways.
TSRN> I have heard that this subject was brought up before and that
TSRN> it was droped. Well I think that we had better re-think about
TSRN> this before encap gets out of control.
I don't see how any reasonable person would think of a 50 KB encap file as
being "out of control." I can imagine, as a purely theoretical possibility, a
situation where a very large database of routing information would have to be
maintained in a distributed manner and cached locally, much as we do now with
DNS information. However, encap is several orders of magnitude away from
that.
TSRN> I can envision a 'regional' encap for say New England having
TSRN> all the local routing and a default routing for anything out of
TSRN> New England to one major switch that would carry the full
TSRN> encap.txt.
The choice is between eating a slight bit more memory at each gateway or
eating
real network resources by routing each IP frame with less than optimum
efficiency and making it do extra hops.
TSRN> I would hope that this problem would get some discussion.
I would be quite surprised if you get any support on this.
-- Mike, N1BEE
------------------------------
Date: Thu, 25 Jul 1996 14:37:22 -0700 (PDT)
From: Phil Karn <karn@qualcomm.com>
Subject: Regional routing
>Other than changing operating systems, your only real option is to move to a
>DOS extender such as comes with the djgpp package. Even that, however, is
not
I've had NOS running fairly stably under DJGPP for some months now. If I
release it, will anybody pay attention? :-)
Phil
------------------------------
Date: Fri, 26 Jul 1996 10:25:06 +0700 (GMT+0700)
From: Eko Sutjipto <eko@stts.ac.id>
Subject: unsubscribe
unsubscribe eko@elang.stts.ac.id
------------------------------
End of TCP-Group Digest V96 #155
******************************
You can send your message for this bulletin
to: tcp-group@pa2aga on .AMPR.ORG-net
or: tcpaga@pi8vnw.#zh2.nld.eu on BBS-net
------
NOT TO: pa2aga@pa2aga or pa2aga@pi8vnw.#zh2.nld.eu PLEASE!!
It will get posted automatically within a few days
Read previous mail | Read next mail
| |
