From: shields@tembel.org (Michael Shields)
To: cypherpunks@toad.com
Message Hash: 09aa7c0d3c999bf85967f6d1a689216a963f821f094e08432792c51cb979e948
Message ID: <47n7m0$i3k@yage.tembel.org>
Reply To: <9511070647.AA00471@sulphur.osf.org>
UTC Datetime: 1995-11-07 09:26:29 UTC
Raw Date: Tue, 7 Nov 1995 17:26:29 +0800
From: shields@tembel.org (Michael Shields)
Date: Tue, 7 Nov 1995 17:26:29 +0800
To: cypherpunks@toad.com
Subject: Re: censored? corrected [Steve Pizzo cited in The Spotlight]
In-Reply-To: <9511070647.AA00471@sulphur.osf.org>
Message-ID: <47n7m0$i3k@yage.tembel.org>
MIME-Version: 1.0
Content-Type: text/plain
In article <9511070647.AA00471@sulphur.osf.org>,
Rich Salz <rsalz@osf.org> wrote:
> >Originally DNS was just a handy user-friendly thing, but then
[...]
> Hunh?
>
> The Arpanet always used hostnames.
Sorry. But still, then intent was to be user-friendly (right?), and
a side effect was to make it possible to renumber without anyone noticing.
Renumbering didn't affect the health of the net until recently, with
CIDR, where blocks of IP addresses could be aggregated arbitrarily.
A provider might now get 10.11.12/22 (i.e., a 22-bit-long prefix), and
then assign customers 10.11.12/24, 10.11.13/23, &c., with only one entry
in the backbone routing tables. To make this work you have to renumber
when you change providers. Fortunately, we have DNS to provide a name
more stable than the IP address.
That's the connection between DNS and routing, and it's why using names
instead of numbers is Good.
--
Shields.
Return to November 1995
Return to “shields@tembel.org (Michael Shields)”