Re: [manet] Re: [Manet-dt] Review Request

"SATOH, Hiroki (HitachiSDL)" <hiroki.satoh.yj@hitachi.com> Thu, 29 March 2007 01:24 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 1HWjMu-0002yz-Ok; Wed, 28 Mar 2007 21:24:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWjMt-0002yq-6r; Wed, 28 Mar 2007 21:23:59 -0400
Received: from mail4.hitachi.co.jp ([133.145.228.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWjMo-0002KL-Fn; Wed, 28 Mar 2007 21:23:59 -0400
Received: from mlsv5.hitachi.co.jp (unknown [133.144.234.166]) by mail4.hitachi.co.jp (Postfix) with ESMTP id 2118133CC4; Thu, 29 Mar 2007 10:23:53 +0900 (JST)
Received: from mfilter-s6.hitachi.co.jp by mlsv5.hitachi.co.jp (8.12.10/8.12.10) id l2T1Nu0j006035; Thu, 29 Mar 2007 10:23:56 +0900
Received: from vshuts2.hitachi.co.jp (unverified) by mfilter-s6.hitachi.co.jp (Content Technologies SMTPRS 4.3.17) with SMTP id <T7ea9a1cde90ac906b6e2c@mfilter-s6.hitachi.co.jp>; Thu, 29 Mar 2007 10:23:52 +0900
Received: from hsdlgw92.sdl.hitachi.co.jp ([133.144.7.20]) by vshuts2.hitachi.co.jp with SMTP id M2007032910235204852 ; Thu, 29 Mar 2007 10:23:52 +0900
Received: from vgate2.sdl.hitachi.co.jp by hsdlgw92.sdl.hitachi.co.jp (8.13.1/3.7W06092911) id l2T1Nqo3010447; Thu, 29 Mar 2007 10:23:52 +0900
Received: from sdl99w.sdl.hitachi.co.jp ([133.144.14.250]) by vgate2.sdl.hitachi.co.jp (SAVSMTP 3.1.1.32) with SMTP id M2007032910235106155 ; Thu, 29 Mar 2007 10:23:51 +0900
Received: from [127.0.0.1] (IDENT:U2FsdGVkX18sfUlT84E+2MDOB33qfjferp7PV9IbAsM@localhost.localdomain [127.0.0.1]) by sdl99w.sdl.hitachi.co.jp (8.13.1/3.7W04031011) with ESMTP id l2T1Njd3019449; Thu, 29 Mar 2007 10:23:46 +0900
In-Reply-To: <4607DBF4.8060608@nokia.com>
References: <019c01c76d85$0e6904f0$165cfa84@SEXTANT> <4607DBF4.8060608@nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <06E6CE31-1A9A-4DA8-81EE-6ACFC9951664@hitachi.com>
Content-Transfer-Encoding: 7bit
From: "SATOH, Hiroki (HitachiSDL)" <hiroki.satoh.yj@hitachi.com>
Subject: Re: [manet] Re: [Manet-dt] Review Request
Date: Thu, 29 Mar 2007 10:23:44 +0900
To: manet <manet@ietf.org>, manet-dt@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc:
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

I agree with the importance of reducing message size especially for  
sensor network. And it could be applicable if we change packet format  
with smart way.
But from industrial point of view,  I also worry about DELAY for the  
standardization. Almost all companies could not follow frequent draft  
update, because of a lot of cost. And MANET WG already advertised  
PacketBB almost Last Call for RFC in 67th and 68th IETF.

So I urge that first of all we move packetBB to RFC. After  
standardization, we start to discuss how improve packet format and  
update RFC in need.
In my opinion packet format applicability depends on the service or  
the application in real world. It may difficult to cover every  
situation by only one document. Because the new service or the new  
situation become available by technological invention day by day. I  
think the merit of Last Call much bigger than that of delayed  
standardization. The improvement update for real application from now  
on will be done after standardization, I think.

Again I strongly recommend accelerate EVERY standardization process.  
Because I hope the MANET technique will be available as soon as  
possible in real world from industrial standpoint, now only use for  
some experimental work or limited field.

Regards,
Hiroki

---------------------------------------------
SATOH, Hiroki
Hitachi, Ltd., Systems Development Laboratory
E-mail : hiroki.satoh.yj@hitachi.com
---------------------------------------------



On 2007/03/26, at 23:43, 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.
>
>
>
>
> ext Joe Macker wrote:
>> At the manet WG meeting we discussed a workplan prior to moving  
>> SMF to Last
>> Call for Experimental consideration. While some readability  
>> improvements may
>> be done the authors request that the WG provide comments as soon as
>> possible.  Positive and general comments are encouraged along with  
>> others.
>> If you an implementor and find something confusing we are  
>> interested in
>> hearing from you.
>> Please see the recent briefings on line from the last meeting to  
>> understand
>> the recent changes and upcoming plan.
>>
>> Thanks,
>> Joe
>>
>>
>>
>> _______________________________________________
>> Manet-dt mailing list
>> Manet-dt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/manet-dt
>>
>
>
> _______________________________________________
> Manet-dt mailing list
> Manet-dt@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet-dt
>


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