Re: Revisiting The DNS Notation Backwardsness Problem and Multiple Parallel Root Server Clusters

"Stephen Sprunk" <ssprunk@cisco.com> Thu, 08 August 2002 19:29 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24160; Thu, 8 Aug 2002 15:29:34 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id PAA09359 for ietf-outbound.10@loki.ietf.org; Thu, 8 Aug 2002 15:30:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id PAA09275 for <ietf-mainout@loki.ietf.org>; Thu, 8 Aug 2002 15:23:45 -0400 (EDT)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23980 for ietf-mainout@loki.ietf.org; Thu, 8 Aug 2002 15:22:30 -0400 (EDT)
X-Authentication-Warning: ietf.org: majordom set sender to owner-ietf@ietf.org using -f
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.54]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23974 for <ietf@ietf.org>; Thu, 8 Aug 2002 15:22:25 -0400 (EDT)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.151]) by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id g78JN96I009460; Thu, 8 Aug 2002 12:23:09 -0700 (PDT)
Received: from nisser.cisco.com (localhost [127.0.0.1]) by sj-msg-av-1.cisco.com (8.12.2/8.12.2) with ESMTP id g78JNGqr018977; Thu, 8 Aug 2002 12:23:17 -0700 (PDT)
Received: from ssprunkw2k (ssprunk-w2k.cisco.com [64.101.135.221]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id MAA22260; Thu, 8 Aug 2002 12:23:01 -0700 (PDT)
Message-ID: <020001c23f11$06b4c7a0$dd876540@amer.cisco.com>
From: Stephen Sprunk <ssprunk@cisco.com>
To: Mohsen BANAN <public@mohsen.banan.1.byname.net>
Cc: Internet Technical Community <ietf@ietf.org>, public@mohsen.banan.1.byname.net
References: <20020806134223.1611.qmail@submit8.mail.intra><075e01c23d85$d3316690$dd876540@amer.cisco.com> <20020808022050.6174.qmail@submit8.mail.intra>
Subject: Re: Revisiting The DNS Notation Backwardsness Problem and Multiple Parallel Root Server Clusters
Date: Thu, 08 Aug 2002 14:17:44 -0500
Organization: Cisco Systems, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Thus "Mohsen BANAN" <public@mohsen.banan.1.byname.net>
> I spent a fair amount of time in early 1999 and
> educated IETF cult's chiefs about
>
>     The DNS Notation Backwardsness Problem
> >
> The conclusion of that thread was that indeed
> we have a genuine architectural DNS Notation Backwardsness
> Problem. I included samples of acknowledgement of the
> problem in my previous message. Was hoping by now
> that would be enough.

There is no consensus in the email quotes you supply -- just you ranting about a
problem the rest of us have decided isn't worth solving.

It's possible that domain names would be more logical or useful if they were
written in the reverse order.  However, they're not, and it's about 20 years and
500M users too late to change one of the most basic premises of DNS.  Stability
is more valuable than aesthetics.

> As we consider raising the DNS name space roof we have an opportunity
> to deal with other aspects of the DNS notation.

Nobody is seriously considering "raising the roof".  Creating a new,
higher-level root will only cause pain and a quick repeat of the problems we
have today.

S