RE: [Rfid] Re: XML vs. Text vs. Binary
"Howard Kapustein" <hkapustein@manh.com> Fri, 22 July 2005 13:47 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvxsQ-00016Q-LK; Fri, 22 Jul 2005 09:47:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvxsO-00015N-Oa for rfid@megatron.ietf.org; Fri, 22 Jul 2005 09:47:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15684 for <rfid@ietf.org>; Fri, 22 Jul 2005 09:47:42 -0400 (EDT)
Received: from nat2.manh.com ([65.166.51.6] helo=manh.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvyMd-0006Ak-4n for rfid@ietf.org; Fri, 22 Jul 2005 10:19:00 -0400
Received: from ([10.100.101.63]) by relay3.manh.com with ESMTP id 4029073.7179869; Fri, 22 Jul 2005 09:46:35 -0400
Received: from ma-atl96.us.manh.com ([10.100.101.96]) by ma-atl63 with trend_isnt_name_B; Fri, 22 Jul 2005 09:46:34 -0400
Received: from ma-atl57.us.manh.com ([10.100.101.57]) by ma-atl96.us.manh.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 22 Jul 2005 09:46:34 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Rfid] Re: XML vs. Text vs. Binary
Date: Fri, 22 Jul 2005 09:46:34 -0400
Message-ID: <02254DCB1D0B2340B8D1D54E770CAE76DAEBF6@ma-atl57.us.manh.com>
Thread-Topic: [Rfid] Re: XML vs. Text vs. Binary
Thread-Index: AcWOswuJe8YhvV9jQHqMfS2AXZxPtAAEE0ZA
From: Howard Kapustein <hkapustein@manh.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Scott Barvick <sbarvick@revasystems.com>
X-OriginalArrivalTime: 22 Jul 2005 13:46:34.0507 (UTC) FILETIME=[C63535B0:01C58EC3]
X-esp: ESP<4>=RBL:<0> RDNS:<0> SHA:<4> UHA:<0> SLS:<0> BAYES:<0> SPF:<0> CAN-SPAM Compliance Dictionary (TRU7a):<0> NigeriaScam Dictionary (TRU7a):<0> Obscenities Dictionary (TRU7a):<0> Spam Dictionary (TRU7a):<0> Porn Dictionary (TRU7a):<0> Embed HTML Dictionary (TRU7a):<0> URL Dictionary (TRU7a):<0> HTML Dictionary (TRU7a):<0>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: quoted-printable
Cc: rfid@ietf.org
X-BeenThere: rfid@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Control and Access of Infrastructure for RFID Operations Discussion List <rfid.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rfid>, <mailto:rfid-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rfid>
List-Post: <mailto:rfid@lists.ietf.org>
List-Help: <mailto:rfid-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rfid>, <mailto:rfid-request@lists.ietf.org?subject=subscribe>
Sender: rfid-bounces@lists.ietf.org
Errors-To: rfid-bounces@lists.ietf.org
>therefore the cost of XML is negligible? Cost has several dimensions, not just cpu. For instance, memory utilization can also be a significant factor. I have no idea how XML vs. TLS stack up on that front. But we should be clear when we're discussing such things we clearly understand what we're referring to, and not lumping disparate things together under one jambalaya umbrella. - Howard -----Original Message----- From: rfid-bounces@lists.ietf.org [mailto:rfid-bounces@lists.ietf.org] On Behalf Of Stephane Bortzmeyer Sent: Friday, July 22, 2005 7:43 AM To: Scott Barvick Cc: rfid@ietf.org Subject: [Rfid] Re: XML vs. Text vs. Binary On Fri, Jul 22, 2005 at 06:56:14AM -0400, Scott Barvick <sbarvick@revasystems.com> wrote a message of 121 lines which said: > the protocol processing is layered on top of standard security > mechanisms as discussed in Section 4.2 of the draft. Section 4.2 is nice but it just says that TLS MUST be present, not that it MUST be used, no? > Therefore, the implementation can safely access fields in payload as > efficiently as possible. It seems to me quite contradictory to say (David Husak's message) "We will use fixed-length encoding because it is faster" and "security is not an issue, since we use TLS". Surely, TLS processing is much more costly than XML processing and therefore the cost of XML is negligible? _______________________________________________ Rfid mailing list Rfid@lists.ietf.org https://www1.ietf.org/mailman/listinfo/rfid _______________________________________________ Rfid mailing list Rfid@lists.ietf.org https://www1.ietf.org/mailman/listinfo/rfid
- [Rfid] XML vs. Text vs. Binary Margaret Wasserman
- RE: [Rfid] XML vs. Text vs. Binary Frederico, Gustavo
- RE: [Rfid] XML vs. Text vs. Binary Rob.Buck
- RE: [Rfid] XML vs. Text vs. Binary David Husak
- RE: [Rfid] XML vs. Text vs. Binary Margaret Wasserman
- Re: [Rfid] XML vs. Text vs. Binary Marshall Rose
- [Rfid] Re: XML vs. Text vs. Binary Stephane Bortzmeyer
- RE: [Rfid] Re: XML vs. Text vs. Binary Scott Barvick
- Re: [Rfid] Re: XML vs. Text vs. Binary Juergen Schoenwaelder
- [Rfid] Re: XML vs. Text vs. Binary Stephane Bortzmeyer
- [Rfid] Re: XML vs. Text vs. Binary Scott Barvick
- Re: [Rfid] Re: XML vs. Text vs. Binary Scott Barvick
- RE: [Rfid] Re: XML vs. Text vs. Binary Howard Kapustein
- Contradictions (Was: [Rfid] Re: XML vs. Text vs. … Margaret Wasserman
- RE: [Rfid] XML vs. Text vs. Binary Howard Kapustein
- RE: [Rfid] Re: XML vs. Text vs. Binary Howard Kapustein
- Re: [Rfid] XML vs. Text vs. Binary Margaret Wasserman
- RE: [Rfid] XML vs. Text vs. Binary Howard Kapustein
- Re: [Rfid] XML vs. Text vs. Binary Marshall Rose
- Re: [Rfid] XML vs. Text vs. Binary Margaret Wasserman
- RE: [Rfid] XML vs. Text vs. Binary Rob.Buck
- RE: [Rfid] XML vs. Text vs. Binary Bud Biswas
- Re: [Rfid] XML vs. Text vs. Binary Arjun Roychowdhury
- RE: [Rfid] XML vs. Text vs. Binary Scott Barvick
- RE: [Rfid] XML vs. Text vs. Binary Howard Kapustein
- RE: [Rfid] XML vs. Text vs. Binary Scott Barvick
- RE: [Rfid] XML vs. Text vs. Binary Howard Kapustein
- RE: [Rfid] XML vs. Text vs. Binary Rob.Buck
- RE: [Rfid] XML vs. Text vs. Binary Suresh Bhaskaran