Re: [6lowapp] Next rev of CoRE Charter

Carsten Bormann <cabo@tzi.org> Wed, 03 February 2010 06:58 UTC

Return-Path: <cabo@tzi.org>
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 3266F3A697D for <6lowapp@core3.amsl.com>; Tue, 2 Feb 2010 22:58:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 FFEQ+wtW-cSM for <6lowapp@core3.amsl.com>; Tue, 2 Feb 2010 22:58:00 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9:209:3dff:fe00:7136]) by core3.amsl.com (Postfix) with ESMTP id 20F3E3A68AC for <6lowapp@ietf.org>; Tue, 2 Feb 2010 22:57:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id o136wTJJ023402; Wed, 3 Feb 2010 07:58:29 +0100 (CET)
Received: from [192.168.217.101] (p5489D8AE.dip.t-dialin.net [84.137.216.174]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTP id 81651D452; Wed, 3 Feb 2010 07:58:27 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <DFC50C8B-D84B-43E6-9691-503CC840ED5B@cisco.com>
Date: Wed, 03 Feb 2010 07:58:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <75CED471-D0E5-46B0-AC6B-D67349007E9B@tzi.org>
References: <2A7B1CDC-5B99-47E8-9331-039D5997E1CC@cisco.com> <DFC50C8B-D84B-43E6-9691-503CC840ED5B@cisco.com>
To: 6lowapp@ietf.org
X-Mailer: Apple Mail (2.1077)
Subject: Re: [6lowapp] Next rev of CoRE Charter
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, 03 Feb 2010 06:58:01 -0000

> 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