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

Henning Schulzrinne <hgs@cs.columbia.edu> Wed, 11 November 2009 10:12 UTC

Return-Path: <hgs@cs.columbia.edu>
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 91BD33A69FC; Wed, 11 Nov 2009 02:12:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 mhCl9axn0F2G; Wed, 11 Nov 2009 02:12:13 -0800 (PST)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by core3.amsl.com (Postfix) with ESMTP id 7840E3A68CB; Wed, 11 Nov 2009 02:12:13 -0800 (PST)
Received: from fokuswl198.fhi-fokus.de (fokuswl198.fhi-fokus.de [193.174.153.198]) (user=hgs10 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id nABACZqO000202 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 11 Nov 2009 05:12:36 -0500 (EST)
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> <4AF9BB54.7070006@eecs.berkeley.edu> <87eio62cu7.fsf@kelsey-ws.hq.ember.com>
In-Reply-To: <87eio62cu7.fsf@kelsey-ws.hq.ember.com>
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
Message-Id: <278C5C8B-928A-4B01-BA9B-9ADD1CD41CC7@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Date: Wed, 11 Nov 2009 05:12:33 -0500
To: Richard Kelsey <richard.kelsey@ember.com>
X-Mailer: Apple Mail (2.1076)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.65 on 128.59.29.8
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: Wed, 11 Nov 2009 10:12:15 -0000

The charter is presumably a draft, not a consensus. The numbers in the  
charter seem to lack rigorous justification, so I'm not comfortable  
with them as they stand. So, yes, I'm suggesting to either drop the  
numbers or make them more useful. In addition, memory size arguments  
are not terribly helpful unless each proposal will have a canonical  
implementation in the I-D. At least from my experience, people are  
very bad at estimating implementation complexity, except that one's  
own proposal by definition has lower complexity than any competing  
proposals.

Henning

On Nov 10, 2009, at 6:13 PM, Richard Kelsey wrote:

>   Date: Tue, 10 Nov 2009 11:13:24 -0800
>   From: Kris Pister <pister@eecs.berkeley.edu>
>
>   I think that today's things are being designed with
>   wonderful chips like your Ember EM351 and EM357 which
>   have 128kB and 192kB of flash and lots of RAM; like the
>   Jennic JN5148, the Freescale MC13224, the Dust DN2510.
>   They can run IP, they will run IP, and in many cases they
>   do run IP.
>
> Kris,
>
> Their wonderfulness aside, those chips are not what the
> 6lowpan charter describes.  Yes, I agree that rechartering
> for bigger platforms would make our job easier, and could
> reduce the number of new protocols needed.  I am not arguing
> for or against it, just asking you if you are proposing that
> we amend the charter.  If not, then we should use the specs
> that it has.
>                            -Richard Kelsey
> _______________________________________________
> 6lowapp mailing list
> 6lowapp@ietf.org
> https://www.ietf.org/mailman/listinfo/6lowapp
>