[35442] in North American Network Operators' Group
Re: Namespaces (was: new.net: yet another dns namespace overlay play)
daemon@ATHENA.MIT.EDU (bob bownes)
Thu Mar 8 21:04:26 2001
Message-ID: <3AA832DE.6793ED3E@web9.com>
Date: Thu, 08 Mar 2001 17:33:18 -0800
From: bob bownes <bownes@web9.com>
MIME-Version: 1.0
To: Scott Gifford <sgifford@tir.com>
Cc: Joshua Goodall <joshua@roughtrade.net>, nanog@merit.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
Interesting analogy...How many here are old enough to remember when (in
the US) the first two digits of the exchange meant something?
617-GArden8-xxxx was the houses in/around the garden section of town
long ago & far away...
But we've drifted well off operational topic.
Scott Gifford wrote:
>
> Joshua Goodall <joshua@roughtrade.net> writes:
>
> [ ... ]
>
> > A better method for addressing data would be based on source-brokered,
> > signed, distributed caches of keywords that can be search and, more
> > importantly, bookmarked in the context of each signer.
>
> I'm not sure I want something that elaborate to ftp a file from my
> laptop to my desktop. And I certainly don't want to have to remember
> IP addresses for both of them.
>
> I think DNS works pretty well. You just have to think of it like an
> 800 number --- 800 numbers are ambiguous (1-800-CONTACTS could provide
> information about how to contact people, information about aliens
> contacting the earth, or information about the old PBS show 3-2-1
> Contact!, but it in fact sells contact lenses), but they're still
> easier to remember than the digits.
>
> ------ScottG.
