[Rfid] Re: XML vs. Text vs. Binary

Scott Barvick <sbarvick@revasystems.com> Fri, 22 July 2005 11:50 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dvw2X-00070b-I9; Fri, 22 Jul 2005 07:50:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dvw2V-000705-Sb for rfid@megatron.ietf.org; Fri, 22 Jul 2005 07:50:03 -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 HAA05170 for <rfid@ietf.org>; Fri, 22 Jul 2005 07:50:02 -0400 (EDT)
Received: from mse3fe2.mse3.exchange.ms ([69.25.50.167]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvwWj-0001eR-DK for rfid@ietf.org; Fri, 22 Jul 2005 08:21:18 -0400
Received: from [192.168.1.45] ([157.130.221.86]) by mse3fe2.mse3.exchange.ms with Microsoft SMTPSVC(6.0.3790.211); Fri, 22 Jul 2005 07:49:56 -0400
From: Scott Barvick <sbarvick@revasystems.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
In-Reply-To: <20050722114239.GA23843@nic.fr>
References: <0E03681B885F3B4296B999E34435A16E37344E@ms08.mse3.exchange.ms> <20050722114239.GA23843@nic.fr>
Content-Type: text/plain
Message-Id: <1122032992.26431.2.camel@saco.revasystems.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2)
Date: Fri, 22 Jul 2005 07:49:52 -0400
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Jul 2005 11:49:56.0258 (UTC) FILETIME=[7AED2820:01C58EB3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: rfid@ietf.org
Subject: [Rfid] Re: XML vs. Text vs. Binary
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

You are correct to note that TLS is not required to be used.  However,
if you are concerned about security, which was the basis for your first
question, then you can use it.   There are environments where the
security concerns that you raise are not an issue.  For those and the
base case, I argue for efficient, mimimal requirements on the
implementations.

Scott

On Fri, 2005-07-22 at 07:42, Stephane Bortzmeyer wrote:
> 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