Re: [6lowapp] Next version of charter proposal up on 6lowapp.net

Zach Shelby <zach@sensinode.com> Thu, 05 November 2009 21:05 UTC

Return-Path: <zach@sensinode.com>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 375793A67EC for <6lowapp@core3.amsl.com>; Thu, 5 Nov 2009 13:05:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhjpBftKi1+w for <6lowapp@core3.amsl.com>; Thu, 5 Nov 2009 13:05:04 -0800 (PST)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by core3.amsl.com (Postfix) with ESMTP id 103E83A67B0 for <6lowapp@ietf.org>; Thu, 5 Nov 2009 13:05:03 -0800 (PST)
Received: from [192.168.1.5] (line-5076.dyn.kponet.fi [85.29.66.39]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.4/8.13.4) with ESMTP id nA5L5JR7032741 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 5 Nov 2009 23:05:21 +0200
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=windows-1252; format=flowed; delsp=yes
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <20091105163552.GA10440@elstar.local>
Date: Thu, 5 Nov 2009 23:05:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6BD6C5F2-4101-4E54-B3BE-E3E55596D191@sensinode.com>
References: <547D55FF-B03C-458E-A51C-3223D5F005F4@tzi.org> <20091105163552.GA10440@elstar.local>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.1076)
Cc: "6lowapp@ietf.org" <6lowapp@ietf.org>
Subject: Re: [6lowapp] Next version of charter proposal up on 6lowapp.net
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2009 21:05:05 -0000

On Nov 5, 2009, at 18:35 , Juergen Schoenwaelder wrote:
> --
>
> I have not clue what this means:
>
>   [...] For these benchmark cases, the
>   payload will be based on interface profile specific XML documents
>   compressed with EXI.
>
> Which benchmark cases is this text referring to? And why suddenly fix
> a certain encoding?

I agree, it should be removed. The EXI was mentioned there as a  
benchmark for payload sizes (not to fix anything), but that doesn't  
make sense either. I think the overhead goal should be more explicit  
there instead of talking about benchmarks. Now it says "enabling a  
50-70 byte payload".... considering what? I assume a 50-70 payload  
after IEEE 802.15.4 + 6LoWPAN  + UDP + CoAP without LoWPAN  
fragmentation.... without security. Or should we just say CoAP should  
aim at a header overhead of less than 10 bytes for simple cases  
without security?

Zach

-- 
http://www.sensinode.com
http://zachshelby.org - My blog “On the Internet of Things”
Mobile: +358 40 7796297

Zach Shelby
Head of Research
Sensinode Ltd.
Kidekuja 2
88610 Vuokatti, FINLAND

This e-mail and all attached material are confidential and may contain  
legally privileged information. If you are not the intended recipient,  
please contact the sender and delete the e-mail from your system  
without producing, distributing or retaining copies thereof.