Re: [Coma] If all you had was an LED ...

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Wed, 13 June 2012 21:22 UTC

Return-Path: <mehmet.ersue@nsn.com>
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 9921B21F846F for <coma@ietfa.amsl.com>; Wed, 13 Jun 2012 14:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 nI1ewAMZ0Yir for <coma@ietfa.amsl.com>; Wed, 13 Jun 2012 14:22:48 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC7421F8472 for <coma@ietf.org>; Wed, 13 Jun 2012 14:22:43 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q5DIKZ8N020453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 13 Jun 2012 20:20:35 +0200
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q5DIKZmf032507; Wed, 13 Jun 2012 20:20:35 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 13 Jun 2012 20:20:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Wed, 13 Jun 2012 20:20:34 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6403E538DF@DEMUEXC006.nsn-intra.net>
In-Reply-To: <20120608072625.GA5539@blackbox>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Coma] If all you had was an LED ...
Thread-Index: Ac1FSAVFmVbEbmXqTNSlufwv/LknwwAI77fQ
References: <2806342D-A112-4727-A584-4295E141B3E0@iii.ca> <20120608072625.GA5539@blackbox>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Johannes Gilger" <gilger@umic.rwth-aachen.de>, "Cullen Jennings" <fluffy@iii.ca>
X-OriginalArrivalTime: 13 Jun 2012 18:20:35.0060 (UTC) FILETIME=[39B10340:01CD4991]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1130
X-purgate-ID: 151667::1339611635-0000425E-0C5D4A20/0-0/0-0
Cc: coma@ietf.org
Subject: Re: [Coma] If all you had was an LED ...
X-BeenThere: coma@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 13 Jun 2012 21:22:50 -0000

Hi Cullen, Johannes,

> > Lots of existing stuff blinks them in various ways to indicate different states of the
> > network (no carrier, connected but no IP, etc). Would it make sense to have some
> > standardized recommendation about this?

Based on the manifold sensor devices and the needed interoperability for data exchange, it would be useful to have a common interpretation for the different states (standard model?) relevant to the management of these devices. 

> This also brings me to the question of how much this list
> will touch into management of security, i.e. bootstrapping of security
> associations, setting of access control rights, etc.

I think the management of security should be in our focus. Though what management of security covers is open for discussion.

Cheers,
Mehmet