Re: [Coma] New Maillist for the discussion on the Management of Constrained Networks and Devices

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Tue, 05 June 2012 12:05 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 2305921F8528 for <coma@ietfa.amsl.com>; Tue, 5 Jun 2012 05:05:10 -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=[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 f+SyVgSAmCfS for <coma@ietfa.amsl.com>; Tue, 5 Jun 2012 05:05:09 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 148A121F85EE for <coma@ietf.org>; Tue, 5 Jun 2012 05:05:09 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id DF2B820BE7; Tue, 5 Jun 2012 14:05:07 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 4tUPji-_wXWm; Tue, 5 Jun 2012 14:05:07 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 18B5820B6C; Tue, 5 Jun 2012 14:05:07 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 1DFF11FAF873; Tue, 5 Jun 2012 14:05:05 +0200 (CEST)
Date: Tue, 5 Jun 2012 14:05:05 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Message-ID: <20120605120503.GA87941@elstar.local>
Mail-Followup-To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, ext Antonio Jara <jara@um.es>, Zach Shelby <zach@sensinode.com>, Benoit Claise <bclaise@cisco.com>, Ron Bonica <rbonica@juniper.net>, coma@ietf.org
References: <80A0822C5E9A4440A5117C2F4CD36A6403D56943@DEMUEXC006.nsn-intra.net> <4FC8CFEB.6040902@cisco.com> <341929CE-3341-41EC-A472-1213B6F8C320@sensinode.com> <CAOQrqOVgtLhqqkHCbjuCaNeQzozt8DMCU2Xvg=QRZTOXpYM1PA@mail.gmail.com> <80A0822C5E9A4440A5117C2F4CD36A6403D9AB54@DEMUEXC006.nsn-intra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6403D9AB54@DEMUEXC006.nsn-intra.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Benoit Claise <bclaise@cisco.com>, Ron Bonica <rbonica@juniper.net>, ext Antonio Jara <jara@um.es>, Zach Shelby <zach@sensinode.com>, coma@ietf.org
Subject: Re: [Coma] New Maillist for the discussion on the Management of Constrained Networks and Devices
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: Tue, 05 Jun 2012 12:05:10 -0000

On Tue, Jun 05, 2012 at 01:58:24PM +0200, Ersue, Mehmet (NSN - DE/Munich) wrote:
> Hi Antonio,
> 
> there is no final ToC or text available right now.
> All is open to your comment and suggestions.
> 
> I can imagine a ToC could possibly contain following:
> 
>    1. Introduction 
>      1.1.  Overview
>      1.2.  Basic scenarios in discussion
>      1.4.  Constrained Device Classes 
>    2. Terminology 
>    3. Problem Statement 
>    4. Requirements per Device Class 
>    5. Security Considerations 
>    6. Acknowledgments 
>    7. References 

I think device classes are one dimension but there are others. Lets
think also about "application scenarios or classes" (there might be
better terms): there will be applications and corresponding devices
where there simply is no explicit management ever (the device either
works or it is thrown away). Other scenarios may involve the need to
integrate constrained devices into a system also comprising more
traditionally managed devices. Other scenarios may be fully
application driven and any necessary management functions must become
part of that application.

/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/>