[1752] in North American Network Operators' Group
Re: Policy Statement on Address Space Allocations
daemon@ATHENA.MIT.EDU (Iljitsch van Beijnum)
Tue Jan 30 19:42:35 1996
From: iljitsch@daisy.bART.nl (Iljitsch van Beijnum)
To: amb@xara.net
Cc: Daniel.Karrenberg@ripe.net
In-Reply-To: <199601301049.KAA02133@diamond.xara.net>
(from "Alex.Bligh" <amb@xara.net>)
(at Tue, 30 Jan 1996 10:48:59 +0000)
Date: Wed, 31 Jan 96 01:32:44
People on this list of lists seem to be focussing on squeezing more
aggregation out of assignment and routing policy's.
But that won't work. The Internet isn't organized in a geographical way=
=20nor
in a very hierarchical way.
There are less than 2000 Autonomous Systems, but more than 30000 routes=
=2E
That means an average of 15 routes per AS. That's the real problem. And
we know how to fix it too: renumber.
But whatever happens, the routingtable will continue to grow. Get used =
to
it. At present I can still run full routing with only a Cisco 2514 so t=
he
problem is hardly as big as some people (Sprint...) like to tell themse=
lves
and the rest of us.
We pay those backbone people big money, so either they do their job and
quit complaining about their overloaded CPU's, tight memory and other s=
tuff
or they find themselves another line of work.
I'm getting sick and tired of reading how everybody will bend over back=
wards
to find a way to live with an utterly ridiculous policy of some dinosau=
r
company with a flawed network because they pay their lawyers more than =
their
engineers.
Maybe they could get away with that in the good old phonebusiness, but =
not
on the Internet.
Iljitsch
