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

Henning Schulzrinne <hgs@cs.columbia.edu> Mon, 09 November 2009 02:32 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 BFC003A68EE for <6lowapp@core3.amsl.com>; Sun, 8 Nov 2009 18:32:30 -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 LsXzdpccE969 for <6lowapp@core3.amsl.com>; Sun, 8 Nov 2009 18:32:29 -0800 (PST)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by core3.amsl.com (Postfix) with ESMTP id 9FABF3A68DB for <6lowapp@ietf.org>; Sun, 8 Nov 2009 18:32:29 -0800 (PST)
Received: from new-host.home (pool-71-187-38-54.nwrknj.fios.verizon.net [71.187.38.54]) (user=hgs10 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id nA92WpUN012173 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 8 Nov 2009 21:32:52 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <4AF77C65.3050309@cisco.com>
Date: Sun, 8 Nov 2009 21:32:51 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <517197C5-5B51-4A0F-9E18-6DC876EB971C@cs.columbia.edu>
References: <547D55FF-B03C-458E-A51C-3223D5F005F4@tzi.org> <4AF77C65.3050309@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1076)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.65 on 128.59.29.8
Cc: 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: Mon, 09 Nov 2009 02:32:30 -0000

I find this conflation of Smart Energy/HAN and LowApp confusing. Most  
of the in-home networks are not exactly "challenged". Even ZigBee has  
250 kb/s (or 20 kb/s in the lowest-bandwidth mode), i.e., equivalent  
to early DSL or 1990's modems.

Henning

On Nov 8, 2009, at 9:20 PM, Benoit Claise wrote:

> Carsten,
>
> Thanks for the new charter proposal.
>
> - "This WG is concentrating on requirements from energy (e.g. Smart  
> Energy 2.0) and building management applications."
> Is the goal to describe these requirements in the "objectives and  
> architecture" document?
> If not, where can we understand those requirements from?
> The following were mentioned on the list:
>
> There are a lot of use cases to start with.  Here is a starter set:
> 1)  OpenHAN:
>
> http://www.utilityami.org/docs/UtilityAMI%20HAN%20SRS%20-%20v1.04%20-%200808
>
> 19-1.pdf
> 2)  SmartGridipedia:
>
> http://www.smartgridipedia.org/index.php/Category:Use_Cases
> , both the
> Intelligrid and Southern California Edison use cases are good
> 3)  ZigBee/HomePlug Market Requirements and Use Cases (which we are  
> using
> for our Smart Energy V2 work):
>
> http://www.homeplug.org/products/ZBHP_SE_MRD_090624.pdf
> Any other ones?
>
> "The framework will also specify specify a way to support interface  
> profiles, ..."
> Can you expand on "interface profile".
>
>
> "A document with operation and management advice about running a  
> network using these applications."
> Is advice the right word? It seems like one or two advices are  
> sufficient to manage the network ;-)
>
>
> Regards, Benoit.
>> I have put a new version of the WG charter proposal on the wiki  
>> page at
>> http://6lowapp.net
>> =
>> http://trac.tools.ietf.org/area/app/trac/wiki/6LowApp
>> (charter text is at the end of the page).
>>
>> Obviously, I could not pick up every comment that was on the list  
>> (they were partially going in conflicting directions), but please  
>> do comment on the new version.
>>
>> Gruesse, Carsten
>>
>> _______________________________________________
>> 6lowapp mailing list
>> 6lowapp@ietf.org
>> https://www.ietf.org/mailman/listinfo/6lowapp
>
> _______________________________________________
> 6lowapp mailing list
> 6lowapp@ietf.org
> https://www.ietf.org/mailman/listinfo/6lowapp