Re: [Rfid] Re: XML vs. Text vs. Binary
Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Fri, 22 July 2005 11:34 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvvnA-000735-K5; Fri, 22 Jul 2005 07:34:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dvvn9-00072x-F9 for rfid@megatron.ietf.org; Fri, 22 Jul 2005 07:34:11 -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 HAA03763 for <rfid@ietf.org>; Fri, 22 Jul 2005 07:34:10 -0400 (EDT)
Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvwHM-0000u0-MN for rfid@ietf.org; Fri, 22 Jul 2005 08:05:26 -0400
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id A1B3A395A8; Fri, 22 Jul 2005 13:33:52 +0200 (CEST)
Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 03524-05; Fri, 22 Jul 2005 13:33:51 +0200 (CEST)
Received: from boskop.local (unknown [10.50.250.214]) by hermes.iu-bremen.de (Postfix) with ESMTP id 7E5C7390EE; Fri, 22 Jul 2005 13:33:51 +0200 (CEST)
Received: by boskop.local (Postfix, from userid 501) id 1F1DF392779; Fri, 22 Jul 2005 13:33:49 +0200 (CEST)
Date: Fri, 22 Jul 2005 13:33:49 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Scott Barvick <sbarvick@revasystems.com>
Subject: Re: [Rfid] Re: XML vs. Text vs. Binary
Message-ID: <20050722113349.GA21188@boskop.local>
References: <0E03681B885F3B4296B999E34435A16E37344E@ms08.mse3.exchange.ms>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <0E03681B885F3B4296B999E34435A16E37344E@ms08.mse3.exchange.ms>
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: rfid@ietf.org
X-BeenThere: rfid@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
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
On Fri, Jul 22, 2005 at 06:56:14AM -0400, Scott Barvick wrote: > Stephane, > > From the security perspective, the protocol processing is layered on > top of standard security mechanisms as discussed in Section 4.2 of > the draft. Therefore, the implementation can safely access fields > in payload as efficiently as possible. I will leave it to implementors to decide whether they want to be robust against broken implementations or not. However, I like to point out two things: a) As long as security processing is done in software, this will weight more than any encoding/decoding required, whether that is a binary format or not does not matter. b) Our SNMP experience is that encoding/decoding is not at all an issue when it comes to the amount of CPU cycles burned. Most of the time is spend accessing the instrumentation and in the security processing (if enabled). So if you want to optimize CPU usage, make sure you look at the whole system and spend the efforts where you can maximize the benefit. Human readability is a major enabling factor. In theory, all you need is a decent library to handle binary encodings well but in the real world it seems to help if people can do things without relying on such a library. Human readable encodings (and I include XML here) simply enable more people to get into the "game" and this is ultimately driving the success of a technology. /js -- Juergen Schoenwaelder International University Bremen <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ 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