Re: [Coma] Constrained Device Classes 0, 1 and 2 and their need for Management

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 06 June 2012 09:22 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: coma@ietfa.amsl.com
Delivered-To: coma@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96DC721F8873 for <coma@ietfa.amsl.com>; Wed, 6 Jun 2012 02:22:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.249
X-Spam-Level:
X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z05nemZMsqhO for <coma@ietfa.amsl.com>; Wed, 6 Jun 2012 02:22:19 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE7421F8872 for <coma@ietf.org>; Wed, 6 Jun 2012 02:22:19 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 538FE20C14; Wed, 6 Jun 2012 11:22:18 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id s3gM7jxlEUSn; Wed, 6 Jun 2012 11:22:18 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id D086420AFE; Wed, 6 Jun 2012 11:22:17 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id BBC431FB07C4; Wed, 6 Jun 2012 11:22:17 +0200 (CEST)
Date: Wed, 6 Jun 2012 11:22:17 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Message-ID: <20120606092217.GA89893@elstar.local>
Mail-Followup-To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, coma@ietf.org
References: <80A0822C5E9A4440A5117C2F4CD36A6403DFB0D5@DEMUEXC006.nsn-intra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6403DFB0D5@DEMUEXC006.nsn-intra.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: coma@ietf.org
Subject: Re: [Coma] Constrained Device Classes 0, 1 and 2 and their need for Management
X-BeenThere: coma@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Management of Constrained Networks and Devices <coma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/coma>, <mailto:coma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/coma>
List-Post: <mailto:coma@ietf.org>
List-Help: <mailto:coma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/coma>, <mailto:coma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2012 09:22:20 -0000

On Wed, Jun 06, 2012 at 10:42:13AM +0200, Ersue, Mehmet (NSN - DE/Munich) wrote:
> Hi All,
> 
> following is an attempt to define the device classes in constrained
> networks a bit more in detail. The text below follows the definition of
> the three device classes provided by Carsten.
> 
> Class-0 (C0) devices are very constrained sensor-like motes. They will
> most likely not have the possibility to have a direct communications
> with the Internet in a secure manner. These class-0 devices will
> participate in Internet communications with the help of larger devices
> acting as proxy or gateways. 
> 
> Class-1 (C1) devices are assumed to have about 10 Kbytes of RAM and
> roughly 100 Kbytes of code space (e.g. Flash). For example, this could
> be an AVR Raven mote (http://www.atmel.com/tools/AVRRAVEN.aspx). Class-1
> devices can't easily talk to other Internet nodes with a full protocol
> stack using HTTP, TLS and related security protocols, and XML-based data
> representations. However, they have enough power to use a reduced or
> lightweight protocol stack (e.g. with CoAP and UDP) and participate in
> meaningful conversations without the help of a gateway node. So they can
> be integrated into the IoT network in one way or the other but need to
> spare with memory for the protocol and application usage.
> 
> Class-2 (C2) devices are embedded devices with around 50 Kbytes of RAM
> and maybe 250 Kbytes of code space and can support mostly the same
> protocol stack as used on notebooks or servers. However, even these
> devices can benefit from lightweight and energy-efficient protocols and
> producing less bandwidth on air. Furthermore, using less network
> resources would leave more resources available to applications. As such
> using the same protocol stack on Class 1 and 2 devices might be
> beneficial.
> 
> I assume we cannot do much for the management on C0 devices. They will
> be most likely preconfigured and if ever will be reconfigured seldomly
> with a very small data set.
> 
> For C1 devices it is indeed subject for discussion and to understand
> what type of applications they could run and which management mechanisms
> would be most suitable.
> Even though they have some more functionality available we need to
> assess C2 devices for the type of applications they will be running and
> the management they would need. To be able to derive the requirements we
> need to discuss the uses cases and how the devices are involved in the
> management scenario. The use cases where C1 or C2 devices build a
> cluster or are part of a hierarchy as well as the assumed degree of
> automation might be essentially important.
> 
> Comments are welcome.

This classification is very rough since devices differ in their
architecture. For example, some devices can run their software right
out of flash memory and hence their RAM is really only used for the
storage of variables and the stack. Other devices have to copy the
machine code from flash to RAM before they can execute it. Such
devices have relatively large amounts of RAM but most of it is used to
store machine code.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>