RE: Transport requirements for DNS-like protocols

Patrik Fältström <paf@cisco.com> Mon, 01 July 2002 12:22 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYK00904L282E@eListX.com> (original mail from paf@cisco.com); Mon, 01 Jul 2002 08:22:56 -0400 (EDT)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYK00901L272C@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Mon, 01 Jul 2002 08:22:56 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYK00901L272B@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Mon, 01 Jul 2002 08:22:55 -0400 (EDT)
Received: from ams-msg-core-1.cisco.com (ams-msg-core-1.cisco.com [144.254.74.60]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GYK002EHL26YC@eListX.com> for ietf-irnss@lists.elistx.com; Mon, 01 Jul 2002 08:22:55 -0400 (EDT)
Received: from xbe-lon-303.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g61CLbin028389; Mon, 01 Jul 2002 14:21:53 +0200 (MET DST)
Received: from xfe-ams-301.cisco.com ([144.254.75.88]) by xbe-lon-303.cisco.com with Microsoft SMTPSVC(5.0.2195.4453); Mon, 01 Jul 2002 13:22:22 +0100
Received: from dhcp-64-103-48-81.cisco.com ([144.254.74.55]) by xfe-ams-301.cisco.com with Microsoft SMTPSVC(5.0.2195.4453); Mon, 01 Jul 2002 14:21:57 +0200
Date: Mon, 01 Jul 2002 14:05:11 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
Subject: RE: Transport requirements for DNS-like protocols
In-reply-to: <49106200.1025509669@localhost>
To: John C Klensin <klensin@jck.com>, Nicolas Popp <nico@realnames.com>, 'Michael Mealling' <michael@neonym.net>
Cc: Rob Austein <sra@hactrn.net>, ietf-irnss@lists.elistx.com
Message-id: <27510013.1025532311@localhost>
MIME-version: 1.0
X-Mailer: Mulberry/2.2.0 (Mac OS X)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
References: <17823168.1025345475@localhost> <2626548.1025471624@KLENSIN-TP> <27312065.1025513558@localhost> <49106200.1025509669@localhost>
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>
X-OriginalArrivalTime: 01 Jul 2002 12:21:57.0905 (UTC) FILETIME=[E4E67810:01C220F9]

--On 2002-07-01 07.47 -0400 John C Klensin <klensin@jck.com> wrote:

> And, in this particular
> case, I think we are likely to need a more complex search than
> something that yields easily to client-side canonicalization and
> lookup, but I see almost no advantage to getting involved with
> per-client (or per-user) server state.

I agree completely!

   paf