North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: MEDIA: ICANN rejects .xxx domain

  • From: Todd Vierling
  • Date: Fri May 12 18:14:01 2006
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=p3PkfktqlIb8R2Ytoj95EQbY8Oewd48r4qWx8vJasQaRsnNowvRiUqUxz7tvWoO7siWNPNABwoufBRVq9TNCdYYoTs3b3Hmv51WB8qUKdBE3wPoAxKxQQKRHg6viRxHj5/doxtDNYgSnQSiOrAucbsu4VDoYJB1q+OwwP+Fw59w=

On 5/12/06, Barry Shein <[email protected]> wrote:
On May 12, 2006 at 14:51 [email protected] (Todd Vierling) wrote:
 > The complexity added by TLDs has one extremely critical good side
 > effect:  distribution of load by explicitly avoiding a flat entity
 > namespace.  The DNS has a hierarchical namespace for a reason, and
 > arguments to the contrary will convince on the order of sqrt(-1)
 > people.

As if you couldn't just hash on whatever the last component is and
pick a server on that basis? Query(server[Sum(bytes) mod Nservers])?

There are probably good answers to people's suggestions for change but
working backwards from "that's the way we've always done it"
If you bothered to read the 1983 RFCs I mentioned, and others related
to machine naming, you'd realize that the DNS of today is not, in
fact, "the way we've always done it."

The namespace *was* flat, once.  That didn't scale, and not just
because of technical limitations -- the fact that there are only so
many useful combinations of 26 letters in a relatively short name had
some weight in there too.  So hierarchical naming was standardized
(some forms of nonstandard hierarchy existed before then), and it's
unlikely we're going back anytime in the foreseeable future.

Changing *how* the names are structured into a different hierarchy of
organization, I could believe.  Changing the fact that they are
structured back to being unstructured... the ship has already sailed.

-- Todd Vierling <[email protected]> <[email protected]> <[email protected]>