Re: [6lowapp] [6lowpan] hardware trends, new vs. existing protocols [Re: 4861 usage in LLNs]

Shidan <shidan@gmail.com> Tue, 10 November 2009 22:59 UTC

Return-Path: <shidan@gmail.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 03F4C3A6931; Tue, 10 Nov 2009 14:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.406
X-Spam-Level:
X-Spam-Status: No, score=-2.406 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 bxZkJg2JgKHV; Tue, 10 Nov 2009 14:59:46 -0800 (PST)
Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com [209.85.219.207]) by core3.amsl.com (Postfix) with ESMTP id 094303A6BBB; Tue, 10 Nov 2009 14:59:45 -0800 (PST)
Received: by ewy3 with SMTP id 3so599667ewy.37 for <multiple recipients>; Tue, 10 Nov 2009 15:00:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=UDXf/A/wyw8YRVtZzP7ioqOtq+/n4lWAozfz3IcOPpw=; b=MTSoWaUie3HZ2BMM/7CVXGHfbUkmgZ2u46pS4lLlsDMCT+yLOHr11z6IzIXnHW2ecz VfbBwOanCr7i60QR/4Zqz7H+tqaBuvNqUhcBskYyvsoNZoW3p0Hc1IGaUslhVGbdEG7k o8ZVkMtp49hh7LsauCKlRwoc7AdzbRM7lSU9k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=o+I/7gRXgW36spwLpGAuLlUc1aDiIwvGWVzu9QYGo7cR9cDLMeZGCa3nuZ8Im6kjOA w7tAAeZay2RSW+iSy/T0sndoxvnpd3tQWrQBefXABGb6YOWs+39QMfrnMzhKUELHVrud hBqR27x7/O9X/cBcnPN6mrIh+3b8v1R+Qvdqw=
MIME-Version: 1.0
Received: by 10.216.88.14 with SMTP id z14mr233359wee.25.1257894009397; Tue, 10 Nov 2009 15:00:09 -0800 (PST)
In-Reply-To: <87639il2fh.fsf@kelsey-ws.hq.ember.com>
References: <87y6mfwbfk.fsf@kelsey-ws.hq.ember.com> <1257809361.11184.123.camel@dellx1> <BCFFD6A3-8B4F-49CF-A657-DE34485134E1@tzi.org> <4AF8C20C.3070905@eecs.berkeley.edu> <9256B623-E13C-4EB3-9DE9-F850F2E828AC@tzi.org> <6B8DDEBE-5550-4795-81E0-DC137114EF83@archrock.com> <4AF8D5A0.1020600@eecs.berkeley.edu> <05C6A38D732F1144A8C4016BA4416BFE0242D3B1@SPO-EXVS-02.itron.com> <4AF90433.30204@eecs.berkeley.edu> <87639il2fh.fsf@kelsey-ws.hq.ember.com>
Date: Tue, 10 Nov 2009 18:00:09 -0500
Message-ID: <429b380e0911101500p3564d253g9dabe7aa1b002ac2@mail.gmail.com>
From: Shidan <shidan@gmail.com>
To: Richard Kelsey <richard.kelsey@ember.com>
Content-Type: multipart/alternative; boundary="0016e6d7e9259862e404780c45b9"
Cc: Michael.Stuber@itron.com, 6lowpan@ietf.org, 6lowapp@ietf.org
Subject: Re: [6lowapp] [6lowpan] hardware trends, new vs. existing protocols [Re: 4861 usage in LLNs]
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: Tue, 10 Nov 2009 22:59:48 -0000

Specially with respect to energy management, I don't think anyone is
suggesting IP doesn't fit the bill today. Rather, to the contrary, many
including myself, find it less clear if it's really necessary to redefine
everything proposed to meet today's use cases. I'm not saying it's not, but
just that it needs more careful analysis.

What Kris is saying on the state of current technology and where it is
headed, unlike some of the opposing arguments I've witnessed in this group,
is very clear and understandable to me. I think what would alleviate
everyones concerns, are equally clear arguments based on numbers, facts and
use cases as to why we need an overhaul of everything.

---
Shidan Gouran

On Tue, Nov 10, 2009 at 12:22 PM, Richard Kelsey
<richard.kelsey@ember.com>wrote:

>   Date: Mon, 09 Nov 2009 22:12:03 -0800
>   From: Kris Pister <pister@eecs.berkeley.edu>
>
>    > Abandoning the installed base just goes to reinforce the idea
>    > that IP isn't an appropriate technology for things.
>
>   Michael - I think that we have the same goal, but I disagree with that
>   statement.  I think that re-writing every protocol from discovery
>   through transport to applications, from scratch, is what reinforces the
>   idea that IP isn't an appropriate technology for things.
>
>   I realize that there are pressures from an installed base, but at this
>   point it's a tiny fraction of the overall potential.  If we let the 1%
>   installed base dictate the path for the next 99%, we should do our best
>   to ensure that it's the right path.
>
> Taking these two paragraphs together, you seem to be saying
> that IP is an appropriate technology for tomorrow's things,
> but not necessarily for today's.  While the hardware will
> obviously improve over time, we still need to pick some
> target platform.  The current 6lowpan charter gives 32K of
> flash as an example and mentions 802.15.4 repeatedly.  Are
> you suggesting that we recharter?
>
> The increasing capabilities of the hardware does give us the
> reassuring prospect that the longer we take the solve the
> problems the easier it will be to so.
>
>                                -Richard Kelsey
> _______________________________________________
> 6lowapp mailing list
> 6lowapp@ietf.org
> https://www.ietf.org/mailman/listinfo/6lowapp
>