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

Benoit Claise <> Fri, 01 June 2012 14:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CE2F021F8A9B for <>; Fri, 1 Jun 2012 07:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.513
X-Spam-Status: No, score=-10.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qvyFk5KnLzx4 for <>; Fri, 1 Jun 2012 07:21:35 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id ECD1621F8A99 for <>; Fri, 1 Jun 2012 07:21:33 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from ( []) by (8.13.8+Sun/8.13.8) with ESMTP id q51ELWhD017690; Fri, 1 Jun 2012 16:21:32 +0200 (CEST)
Received: from [] ( []) by (8.13.8+Sun/8.13.8) with ESMTP id q51ELVMa003567; Fri, 1 Jun 2012 16:21:31 +0200 (CEST)
Message-ID: <>
Date: Fri, 01 Jun 2012 16:21:31 +0200
From: Benoit Claise <>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Ersue, Mehmet (NSN - DE/Munich)" <>
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ron Bonica <>,
Subject: Re: [Coma] New Maillist for the discussion on the Management of Constrained Networks and Devices
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Management of Constrained Networks and Devices <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 01 Jun 2012 14:21:40 -0000

Dear all,

[reducing the mailing lists to coma only]

I believe it is time to think on what is needed for the management of 
constrained devices and how the OPS area could address the requirements.

What would be nice is a  "constrained devices management: problem 
statement" draft so that
1. the requirements are clearly written down
2. the OPS area could, if required, work on the protocol/data model 
language/data model modules/encoding mapping

1. we should NOT put the proposed solutions in that draft, i.e. "if you 
want to do X, then use Y". My fear is that the requirements will be 
tweaked if people don't like the protocol/data model language.
2. the feedback must come from the constrained device experts. OPS 
should not be building a solution for a problem that we, OPS, think that 
the constrained devices experts have.

Regards, Benoit.

> Hi All,
> as noted in the maillist announcement of IETF secretary "coma" maillist
> is for the discussion on the management of constrained networks and
> devices. The mailing list will discuss and identify the issues and
> requirements and objectives for the management of devices in such an
> environment with a special focus on and differentiation of device
> classes.
> The idea and trigger for the maillist creation came from a discussion in
> the OPS directorate during IETF #82. As
> draft-ietf-opsawg-management-stds-07 states IETF so far has not
> developed specific technologies for the management of constrained
> networks. OPS directorate members stated in IETF #82 that there is a
> need to understand the requirements and the necessary solutions for the
> management of such a constrained network and its devices. The assumption
> people had was that we need a comprehensive management approach to be
> able to address the diverse needs of different device classes.
> Although the OPS area was doing already standardization work for network
> management, the Core WG is one of the essential WGs at IETF interested
> in the management of constrained devices.
> Following are some of the questions which have been raised in the OPS
> directorate meeting, which are for sure subject to extend from Core WG
> pov.:
> *	Do we need a new development for IoT management (i.e.
> constrained devices) at all?
> -	If yes, what is really needed as standard and what is an
> overkill?
> *	What type of devices can we support?
> *	How are the classes 0-2 for constrained devices defined in
> detail?
> *	Is some simple configuration management already sufficient?
> -	Or do we need also a simple fault management and monitoring?
> *	What type of data model modules do we need to standardize?
> -	Just a few core models like ip-cfg, interface?
> -	or also other specific models for monitoring?
> *	Can we use available management standards and data models as a
> starting point and simplify them?
> *	Concerning the encoding (JSON, XML, or binary) we seem to be
> flexible with tools.
> -	Concerning a normative data modeling language, we need to choose
> a suitable language capable to prepare structured models.
> -	Is JSON sufficient for this purpose, or should YANG or any other
> modeling language be used?
> *	What is appropriate as message transport?
> -	CoAP over UDP with soft-transactions?
> -	Netconf-Light over TCP?
> Obviously the list of the questions above is not exhaustive.
> Carsten kindfully provided already in the Prague meeting the definition
> of device classes 0-2
> ( I think it would
> be useful to start a discussion first on the detailed definition of
> these device classes 0-2 in constrained networks and based on their
> capabilities which functionality they will be able to support. This can
> be then used as a guideline for further discussion on the requirements
> or objectives for management of such devices.
> As noted in the announcement the result of the coma discussion can lead
> to a taxonomy document and a problem statement highlighting the need for
> new work.
> Please send your opinions/comments to the coma maillist (
> To subscribe pls go to:
> Cheers,
> Mehmet
> BTW: Coma has been chosen as the maillist name following the definition
> below:
> Coma \Co"ma\, n. [L., hair, fr. Gr. ko`mh.]
>     1. (Astron.) The envelope of a comet; a nebulous covering,
>        which surrounds the nucleus or body of a comet.
>        [1913 Webster]