Re: [6lowapp] Next rev of CoRE Charter

Robert Cragie <robert.cragie@gridmerge.com> Wed, 03 February 2010 12:31 UTC

Return-Path: <robert.cragie@gridmerge.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 84FA43A6904 for <6lowapp@core3.amsl.com>; Wed, 3 Feb 2010 04:31:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 1R2kyCGz-uzb for <6lowapp@core3.amsl.com>; Wed, 3 Feb 2010 04:31:27 -0800 (PST)
Received: from mail78.extendcp.co.uk (mail78.extendcp.co.uk [79.170.40.78]) by core3.amsl.com (Postfix) with ESMTP id B00073A691E for <6lowapp@ietf.org>; Wed, 3 Feb 2010 04:31:26 -0800 (PST)
Received: from client-86-29-35-162.glfd.adsl.virginmedia.com ([86.29.35.162] helo=[192.168.1.68]) by mail78.extendcp.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.70) id 1NceOp-0005w4-Ka; Wed, 03 Feb 2010 12:32:06 +0000
Message-ID: <4B696CC3.2080609@gridmerge.com>
Date: Wed, 03 Feb 2010 12:32:03 +0000
From: Robert Cragie <robert.cragie@gridmerge.com>
Organization: Gridmerge Ltd.
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
References: <2A7B1CDC-5B99-47E8-9331-039D5997E1CC@cisco.com> <DFC50C8B-D84B-43E6-9691-503CC840ED5B@cisco.com> <75CED471-D0E5-46B0-AC6B-D67349007E9B@tzi.org>
In-Reply-To: <75CED471-D0E5-46B0-AC6B-D67349007E9B@tzi.org>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha1"; boundary="------------ms000609050605090204080804"
Cc: 6lowapp@ietf.org
Subject: Re: [6lowapp] Next rev of CoRE Charter
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: robert.cragie@gridmerge.com
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, 03 Feb 2010 12:31:28 -0000

+1. The taxonomy of terms is not entirely clear nor defined so trying to 
classify at this stage is difficult. If you are going to pick a general 
term, I think constrained nodes/network works well, as I see LLN as a 
specialisation of a constrained nodes/network.

Robert

Robert Cragie (Pacific Gas & Electric)

Gridmerge Ltd.
89 Greenfield Crescent,
Wakefield, WF4 4WA, UK
+44 (0) 1924 910888
http://www.gridmerge.com <http://www.gridmerge.com/>



Carsten Bormann wrote:
>> 1) I would suggest to first try to adopt a common "language" across Working
>> Groups. In ROLL, we use the term LLN to refer to Low power and Lossy Networks.
>> Using similar terminology could help.
>>     
>
> While LLN are one class of a constrained network, I believe the focus of CoRE should be a bit wider and narrower at the same time.  E.g., there may be little reason not to run CoAP on simple nodes connected by RS-485-style networks, even if we don't have a single standard way to map IP onto them right now.  On the other hand, some nodes on an LLN way be able to run HTTP with good results.
>
> In other words:  I'm all for harmonization of terms, except where that muddies the waters.  Let's keep the three terms 6LoWPAN (a specific LLN where we do expect to have some highly constrained nodes), LLN, and constrained nodes/networks separate for now.  Yes, they all fit together in the region where they overlap, but, no, they aren't the same.
>
> Gruesse, Carsten
>
> _______________________________________________
> 6lowapp mailing list
> 6lowapp@ietf.org
> https://www.ietf.org/mailman/listinfo/6lowapp
>
>