Re: Where we stand and where we are going

Leslie Daigle <leslie@thinkingcat.com> Wed, 26 June 2002 19:29 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYB00904VGMJD@eListX.com> (original mail from leslie@thinkingcat.com) ; Wed, 26 Jun 2002 15:29:10 -0400 (EDT)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYB00901VGLJ9@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Wed, 26 Jun 2002 15:29:09 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYB00901VGLJ7@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Wed, 26 Jun 2002 15:29:09 -0400 (EDT)
Received: from zark.ecotroph.net (64.83.37.226.dsl226-static-nova.cavtel.net [64.83.37.226]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GYB0008VVGKM1@eListX.com> for ietf-irnss@lists.elistx.com; Wed, 26 Jun 2002 15:29:08 -0400 (EDT)
Received: from thinkingcat.com ([::ffff:216.168.231.197]) (AUTH: LOGIN leslie, TLS: TLSv1/SSLv3,128bits,RC4-MD5) by zark.ecotroph.net with esmtp; Wed, 26 Jun 2002 15:28:54 -0400
Date: Wed, 26 Jun 2002 15:27:39 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
Subject: Re: Where we stand and where we are going
To: John C Klensin <klensin@jck.com>
Cc: Michael Mealling <michael@neonym.net>, ietf-irnss@lists.elistx.com
Message-id: <3D1A15AB.2CD6E4CC@thinkingcat.com>
MIME-version: 1.0
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.17-lld11 i686)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en
References: <20020626094112.R24592@bailey.dscga.com> <1448782.1025092039@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>

Howdy,

John C Klensin wrote:
>  And I
> think, in that context, that, unless the capabilities and
> flexibilities of XML are needed, that we should assume that this
> is infrastructure. Hence, those capabilities and flexibilities
> should be assumed to be overhead, fluff, and opportunities for
> profiles that kill interoperability.

Actually, I'm not ready to agree with this (not saying I won't
get there -- saying I'm not there yet).  XML in toto is overkill,
but we're not talking about that; we're trying to define a
constrained service and leverage XML as an expression for it.

> I can't speak for consensus, but my preference in all of this is
> to follow N. Wirth to the greatest degree possible, i.e., the
> goal should be "as simple as possible, but no simplier".