Re: [6lowapp] HTTP and SIP

Adam Dunkels <adam@sics.se> Mon, 12 October 2009 11:19 UTC

Return-Path: <adam@sics.se>
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 5388C3A68D0 for <6lowapp@core3.amsl.com>; Mon, 12 Oct 2009 04:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.482
X-Spam-Level:
X-Spam-Status: No, score=-0.482 tagged_above=-999 required=5 tests=[AWL=0.278, BAYES_05=-1.11, HELO_EQ_SE=0.35]
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 7YqcpV-HGr2k for <6lowapp@core3.amsl.com>; Mon, 12 Oct 2009 04:19:46 -0700 (PDT)
Received: from letter.sics.se (letter.sics.se [193.10.64.6]) by core3.amsl.com (Postfix) with ESMTP id 89A7728C19C for <6lowapp@ietf.org>; Mon, 12 Oct 2009 04:19:46 -0700 (PDT)
Received: from [10.1.1.254] (unknown [10.1.1.254]) by letter.sics.se (Postfix) with ESMTP id 6E28340124; Mon, 12 Oct 2009 13:19:46 +0200 (CEST)
Message-ID: <4AD310CC.40808@sics.se>
Date: Mon, 12 Oct 2009 13:19:40 +0200
From: Adam Dunkels <adam@sics.se>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: d.sturek@att.net
References: <429b380e0910101030q25f1ad7fge7157c2e04b5d530@mail.gmail.com> <4AD105DC.3070407@sics.se> <001701ca4a0d$b6416610$22c43230$@sturek@att.net>
In-Reply-To: <001701ca4a0d$b6416610$22c43230$@sturek@att.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 6lowapp@ietf.org
Subject: Re: [6lowapp] HTTP and SIP
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: Mon, 12 Oct 2009 11:19:47 -0000

Don Sturek wrote:
> .5 seconds for one hop and 2 seconds for 4 hops are really not acceptable
> for many applications.
> 
> We should of course investigate using existing protocols.   However it does
> not seem likely that full HTTP and XML deployed over devices like IEEE
> 802.15.4 with very small packet sizes will scale very well  (certainly, for
> any application expecting to do home or building controls, those latencies
> don't work).  Ideally, we should find something that allows for full
> HTTP/etc. while enabling constrained devices to operate with a solution that
> can be expanded/compressed.

I agree with this, and that's also why I think the 6lowapp initiative is 
important.

As a sidenote, though: the 0.5 seconds and 2 seconds are not latencies, 
but completion time. Latency about 0.3s per hop in this case, which is 
due to the power-saving radio mechanism we use, which switches the radio 
off for 99% of the time, while waking up twice per second. So the 
HTTP/TCP does not incur the significant part of the latency in this case.

/adam
-- 
Adam Dunkels <adam@sics.se>se>, +46707731614
http://twitter.com/adunk | http://www.sics.se/~adam/