Re: Transport requirements for DNS-like protocols

Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net> Fri, 28 June 2002 14:38 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00D047CKL2@eListX.com> (original mail from brunner@nic-naa.net); Fri, 28 Jun 2002 10:38:44 -0400 (EDT)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00D017CJL0@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Fri, 28 Jun 2002 10:38:43 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00D017CJKZ@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Fri, 28 Jun 2002 10:38:43 -0400 (EDT)
Received: from nic-naa.net (216-220-241-233.midmaine.com [216.220.241.233]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GYF00ANH7CIL1@eListX.com> for ietf-irnss@lists.elistx.com; Fri, 28 Jun 2002 10:38:43 -0400 (EDT)
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1]) by nic-naa.net (8.12.4/8.11.6) with ESMTP id g5SEZtBZ015739; Fri, 28 Jun 2002 10:35:55 -0400 (EDT envelope-from brunner@nic-naa.net)
Date: Fri, 28 Jun 2002 10:35:55 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Subject: Re: Transport requirements for DNS-like protocols
In-reply-to: "Your message of Fri, 28 Jun 2002 10:17:04 EDT." <20020628101704.Y24592@bailey.dscga.com>
To: Michael Mealling <michael@neonym.net>
Cc: John C Klensin <klensin@jck.com>, Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= <paf@cisco.com>, Rob Austein <sra@hactrn.net>, ietf-irnss@lists.elistx.com, brunner@nic-naa.net
Message-id: <200206281435.g5SEZtBZ015739@nic-naa.net>
Content-type: TEXT/PLAIN
List-Owner: <mailto:ietf-irnss-help@lists.elistx.com>
List-Post: <mailto:ietf-irnss@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-irnss/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-irnss-request@lists.elistx.com?body=help>
List-Id: <ietf-irnss.lists.elistx.com>

> Very fundamental and very important, especially if you ever
> aspire to running something even a fraction of the size of
> ".com"....

Uh, the flatness of the namespace is an artifact of non-technical policy
making. It isn't something that anyone other than the direct beneficiaries
have an interest in. It brand management. We don't do that. Other bodies
do.

I don't care if .com can't be signed, searched, inverted, hashed, browned,
or stir-fried. Defect of implementation is an implementation issue.

Cheers,
Eric