Re: Transport requirements for DNS-like protocols

Patrik Fältström <paf@cisco.com> Fri, 28 June 2002 14:09 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00C045ZKJP@eListX.com> (original mail from paf@cisco.com); Fri, 28 Jun 2002 10:09:20 -0400 (EDT)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00C015ZJJN@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Fri, 28 Jun 2002 10:09:20 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYF00C015ZJJM@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Fri, 28 Jun 2002 10:09:19 -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 <0GYF00ADY5ZEL1@eListX.com> for ietf-irnss@lists.elistx.com; Fri, 28 Jun 2002 10:09:19 -0400 (EDT)
Received: from xbe-ams-303.cisco.com (xbe-ams-303.cisco.com [144.254.75.93]) by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g5SE85Vq012125; Fri, 28 Jun 2002 16:08:14 +0200 (MET DST)
Received: from xfe-ams-302.cisco.com ([144.254.75.89]) by xbe-ams-303.cisco.com with Microsoft SMTPSVC(5.0.2195.4453); Fri, 28 Jun 2002 16:08:49 +0200
Received: from [10.0.1.100] ([144.254.74.55]) by xfe-ams-302.cisco.com with Microsoft SMTPSVC(5.0.2195.4453); Fri, 28 Jun 2002 16:08:49 +0200
Date: Fri, 28 Jun 2002 15:40:24 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
Subject: Re: Transport requirements for DNS-like protocols
In-reply-to: <20020628084423.V24592@bailey.dscga.com>
To: Michael Mealling <michael@neonym.net>
Cc: Rob Austein <sra@hactrn.net>, ietf-irnss@lists.elistx.com
Message-id: <15751338.1025278824@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: <199812050411.UAA00462@daffy.ee.lbl.gov> <vern@ee.lbl.gov> <20020628034133.D50C518AC@thrintun.hactrn.net> <15430645.1025273478@localhost> <20020628084423.V24592@bailey.dscga.com>
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: 28 Jun 2002 14:08:49.0765 (UTC) FILETIME=[536D6950:01C21EAD]

--On 2002-06-28 08.44 -0400 Michael Mealling <michael@neonym.net> wrote:

> I think that's a valuable enough guideline to warrant putting it into at
> least the SLS document I'm working on...

Please...

Of course, any kind of fuzzy matching rule _can_ be expressed in a more
clever hashing function. But, someone have to invent that hash, and if they
have already, we will not have more implementations.

So, simple protocol, simple processing on server side. Clever clients.

That also create an opportunity for people to compete for smart client
things.

   paf