[Manet-dt] Re: PacketBB

"Charles E. Perkins" <charles.perkins@nokia.com> Wed, 28 March 2007 15:33 UTC

Return-path: <manet-dt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWa97-0006M0-7w; Wed, 28 Mar 2007 11:33:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWa96-0006L3-IQ; Wed, 28 Mar 2007 11:33:08 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWa95-0001gj-01; Wed, 28 Mar 2007 11:33:08 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l2SFWoaD017098; Wed, 28 Mar 2007 18:33:03 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Mar 2007 18:33:02 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Mar 2007 10:32:59 -0500
Received: from [10.162.85.153] ([10.162.85.153]) by daebe101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Mar 2007 10:32:59 -0500
Message-ID: <460A8AA7.8090006@nokia.com>
Date: Wed, 28 Mar 2007 08:32:55 -0700
From: "Charles E. Perkins" <charles.perkins@nokia.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: ext Ian Chakeres <ian.chakeres@gmail.com>
References: <019c01c76d85$0e6904f0$165cfa84@SEXTANT> <4607DBF4.8060608@nokia.com> <963155AB-4ECA-4082-96CE-1A003636C9E3@gmail.com>
In-Reply-To: <963155AB-4ECA-4082-96CE-1A003636C9E3@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Mar 2007 15:33:00.0143 (UTC) FILETIME=[5DFA6FF0:01C7714E]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070328183303-3E69CBB0-40C479C9/0-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: manet <manet@ietf.org>, manet-dt@ietf.org
Subject: [Manet-dt] Re: PacketBB
X-BeenThere: manet-dt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MANET Design Team <manet-dt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/manet-dt>
List-Post: <mailto:manet-dt@ietf.org>
List-Help: <mailto:manet-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=subscribe>
Errors-To: manet-dt-bounces@ietf.org

Hello Ian,

ext Ian Chakeres wrote:
> Charlie, I encouraged you (and others) to review PacketBB and to 
> suggest improvements. If you feel PacketBB is too heavyweight please 
> make specific suggestions to the authors and this list.
I will try to do this by next week.  In order to do so, I will have
to exhibit another packet format for comparison.  This will, of
course, involve certain assumptions that can then provide a lot
of room for discussion and championing alternative assumptions.
But perhaps at least it will provide a baseline for comparison.
>
> I personally disagree about the expensive cost of PacketBB and the 
> cost of using a TLV structure. Can you please provide some specific 
> examples where the cost is large? Or where we might save lots of 
> bits/bytes for NHDP, DYMO, or OLSRv2? In my analysis PacketBB almost 
> always results in fewer bits/bytes than a non-compacting format.
My goal would be to save some substantial packet size in the average
case.  If I can't show how to do it, then I'll happily go along with
the existing PacketBB structure, since it has been threshed out for
long enough otherwise.

Regards,
Charlie P.

>
> Ian Chakeres
>
> On Mar 26, 2007, at 8:13 PM, Charles E. Perkins wrote:
>
>>
>> Hello folks,
>>
>> Once again, I urge that we place as much consideration as
>> possible on reducing message size to the maximum extent.
>> I have myself been reluctant to spend a lot of time on reviewing
>> the document because I worry that my comments will not be
>> taken as constructive.  Ian has expressed his concern that I
>> am too late to make any suggestions for substantial change.
>>
>> I believe that the TLV structure is very expensive in terms
>> of byte overhead.  I also think that parseability is far less
>> important than message size, although both are important.
>> I would rate the relative importance as 90% vs. 10% for
>> the parseability/size tradeoff.
>>
>> Similar considerations may apply to NHDP.
>>
>> It is pretty clear that the trend has been to be more
>> "IETF"-like in the message design, at the expense of
>> message size.  In my opinion, this is inappropriate if we
>> want our work to be applicable for sensors or 6lowpan
>> or other low-power devices.  When one byte of airtime
>> consumes as much energy as millions of processor cycles,
>> it makes sense to favor additional processing to reduce
>> message size.  IETF protocols typically favor human
>> readability of the protocol document at the expense
>> of message size, and for many applications this is wholly
>> inappropriate.
>>
>> I would be very interested to hear opinions from other
>> members of the working group about this.
>>
>> Regards,
>> Charlie P.

_______________________________________________
Manet-dt mailing list
Manet-dt@ietf.org
https://www1.ietf.org/mailman/listinfo/manet-dt