NAVYJOBS.COM

The current problem with DNS is not load on root NSes
(however, even a blind person can see how exponential
growth at more-than Moore's law will get it to the
point where you simply won't be able to find a box
fast enough to run root NS). Those of us with longer
memories remember times when 16Mb on AGSes was "more
than enough for any foreseeable future". And, yes,
followinmg your analogy, 99.999% of routers do not have
to have more than 100 routes in them. Does it help
a dozen of dying backbone boxes much?

The current problem is increased name collisions. Which is,
to say, a fundamental one.

No matter how you jump you won't be able to decrease rate
of name collisions w/o increasing depth of the tree.
The only other remedy is to stop choosing natural
abbreviations and start doing as AOL does with customer
names. Which is, essentially, an inferior way to do
exactly what i proposed to do.

(And, BTW, there's life after 26 letters are done with;
you can set moving "line in the sand" on who gets shorter
names).

But -- the idea that first level domains are sexy got
to be stomped out before anything real can be done about
DNS.

New TLDs is merely moving the problem one level higher.
It definitely cannot fix anything.

--vadim

PS. No, i don't call to "rename Internet". I call to
  stop the insane practice of building the flat
  namespace.

From GAVRON@ACES.COM Mon Apr 22 17:45 PDT 1996

Return-Path: <GAVRON@ACES.COM>
Received: from postman.ncube.com by butler.ncube.com (5.0/SMI-SVR4)
  id AA16312; Mon, 22 Apr 1996 17:45:36 +0800
Received: from Hearts.ACES.COM by postman.ncube.com (4.1/SMI-4.1)
  id AA18743; Mon, 22 Apr 96 17:47:04 PDT
Received: from ACES.COM by ACES.COM (PMDF V4.3-10 #4107)
id <01I3RYXO7X0G000031@ACES.COM>; Mon, 22 Apr 1996 17:46:44 -0700 (MST)