Re: Transport requirements for DNS-like protocols

John C Klensin <klensin@jck.com> Fri, 28 June 2002 14:40 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00D047FNM2@eListX.com> (original mail from klensin@jck.com); Fri, 28 Jun 2002 10:40:35 -0400 (EDT)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00D017FNM0@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Fri, 28 Jun 2002 10:40:35 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00D017FMLZ@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Fri, 28 Jun 2002 10:40:34 -0400 (EDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GYF00ANW7FML1@eListX.com> for ietf-irnss@lists.elistx.com; Fri, 28 Jun 2002 10:40:34 -0400 (EDT)
Received: from [209.187.148.217] (helo=P2) by bs.jck.com with esmtp (Exim 3.35 #1) id 17Nwut-0003h4-00; Fri, 28 Jun 2002 14:40:07 +0000
Date: Fri, 28 Jun 2002 10:40:06 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: Transport requirements for DNS-like protocols
In-reply-to: <200206281425.g5SEPCBZ015708@nic-naa.net>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>, Rob Austein <sra@hactrn.net>
Cc: ietf-irnss@lists.elistx.com
Message-id: <80029929.1025260806@localhost>
MIME-version: 1.0
X-Mailer: Mulberry/3.0.0a3 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
References: <200206281425.g5SEPCBZ015708@nic-naa.net>
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>

--On Friday, 28 June, 2002 10:25 -0400 Eric Brunner-Williams in
Portland Maine <brunner@nic-naa.net> wrote:

>> It could be construed as off-topic for ...
> 
> I wouldn't say its off topic. Then again, there may be several
> topics that resemble "transport requirements".

Rob, Eric, Michael, and others,

To the extent to which I have a voice here, I don't want to
waste time on "on topic" versus "off topic" discussions.  As the
last few notes have again made clear (at least to me), we are
still at the stage of asking rather basic questions about the
nature of this approach.   They are questions I would have
preferred to have gotten to many months ago, but so it goes...
they are clearly important.  The question of client-side versus
server-side functions and what can reasonably be transported and
how are, it seems to be, to be absolutely critical.  And if some
of you/us believe that teasing out transport details is useful
to making those decisions, or even to getting to how to think
about those decisions, I think it is on-topic, and probably in
the critical path.

For whatever it is worth, one of the main reasons I haven't
tried to turn "dns-role" into a protocol specification is
because I haven't felt we have anything resembling an informed
consensus around these issues.  So I'm delighted that the
conversation has started.

    john