Re: [coman] are we there yet?

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Tue, 12 March 2013 21:47 UTC

Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: coman@ietfa.amsl.com
Delivered-To: coman@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E80D611E8109 for <coman@ietfa.amsl.com>; Tue, 12 Mar 2013 14:47:13 -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=[AWL=0.000, 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 EmN-huPKZC1a for <coman@ietfa.amsl.com>; Tue, 12 Mar 2013 14:47:13 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 017AC11E80D5 for <coman@ietf.org>; Tue, 12 Mar 2013 14:47:10 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r2CLl6C5014327 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 12 Mar 2013 22:47:06 +0100
Received: from DEMUHTC001.nsn-intra.net ([10.159.42.32]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r2CLl3o3026682 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Mar 2013 22:47:03 +0100
Received: from DEMUHTC006.nsn-intra.net (10.159.42.37) by DEMUHTC001.nsn-intra.net (10.159.42.32) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 12 Mar 2013 22:47:02 +0100
Received: from DEMUMBX005.nsn-intra.net ([169.254.5.216]) by DEMUHTC006.nsn-intra.net ([10.159.42.37]) with mapi id 14.02.0328.009; Tue, 12 Mar 2013 22:47:02 +0100
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: ext Zach Shelby <zach@sensinode.com>
Thread-Topic: [coman] are we there yet?
Thread-Index: AQHOHzz9Qq1aaE2MQ02p71ZdhReX95iiVisAgABBnSU=
Date: Tue, 12 Mar 2013 21:47:01 +0000
Message-ID: <2D81839E-121C-49E6-ABC0-EE37558638D2@nsn.com>
References: <22677.1363008722@sandelman.ca> <E4DE949E6CE3E34993A2FF8AE79131F80655D7@DEMUMBX005.nsn-intra.net> <CAK=bVC8CuqxsPo+5ihHeJrfY6S5=jhpQz5oDf0L_qybg5r_B5Q@mail.gmail.com> <CANF4ybt0MmnQXR0ZQKSPJ8AjW-wF-hduyysmzVq9ebj2jsfsQw@mail.gmail.com> <34966E97BE8AD64EAE9D3D6E4DEE36F21EDDDD20@szxeml525-mbx.china.huawei.com> <20130312014021.GA64284@elstar.local> <34966E97BE8AD64EAE9D3D6E4DEE36F21EDDDF18@szxeml525-mbx.china.huawei.com> <BBD6E278-49FC-42FB-A342-E40086B6B364@sensinode.com> <8254.1363105006@sandelman.ca>, <DA0F7870-F728-4E4C-8A70-F681FE2CF408@sensinode.com>
In-Reply-To: <DA0F7870-F728-4E4C-8A70-F681FE2CF408@sensinode.com>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: 2937
X-purgate-ID: 151667::1363124827-000050C9-0D45C572/0-0/0-0
Cc: "coman@ietf.org" <coman@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: [coman] are we there yet?
X-BeenThere: coman@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Management of Constrained Networks and Devices <coman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/coman>, <mailto:coman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/coman>
List-Post: <mailto:coman@ietf.org>
List-Help: <mailto:coman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/coman>, <mailto:coman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 21:47:14 -0000

I am not sure I get the point.

Is it the proposal that we should use OMA LwM2M for the purpose of Coman, or is it meant that more than what OMA LwM2M specifies is not needed?

Ideally, we need to support all management dimensions on the one side: the management protocol, the information model and the necessary data models, and an appropriate modeling language.
On the other hand different management tasks need to be addressed, e.g. fault, performance and security management and not only configuration.

I think we need also understand that in the Coman draft, M2M is just one use case between many.

It would be indeed useful to elaborate, how far OMA LwM2M supports the network management requirements listed in the Coman draft, which cover both management of constrained devices and the management of networks with diverse topologies containing constrained and non-constrained devices.

Mehmet



Am 12.03.2013 um 14:52 schrieb "ext Zach Shelby" <zach@sensinode.com>:

> On Mar 12, 2013, at 12:16 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
>>>>>>> "Zach" == Zach Shelby <zach@sensinode.com> writes:
>> Zach> We are just completing a new OMA Lightweight M2M standard
>> Zach> which includes an efficient Object system for managing
>> Zach> constrained devices over CoAP. It has a highly optimised form
>> Zach> of Object format which is applicable for device management,
>> Zach> network management and also application data. If you are
>> Zach> interested, I will present more information about this new
>> Zach> standard at the CoRE meeting on Wednesday.  
>> 
>> Awesome!!!!
>> 
>> is that:
>>             CoRE Resource Directory
>>     draft-shelby-core-resource-directory-05
> 
> Lightweight M2M (LWM2M) is a system standard in the Open Mobile Alliance. It includes DTLS, CoAP, Block, Observe, SenML and Resource Directory and weaves them into a device-server interface along with an Object structure. It uses a subset of the Resource Directory functionality, so the Resource Directory spec in CoRE is a more general solution.
> 
> In the Wed CoRE meeting I will be presenting a few slides on this (starts at page 113 of http://tools.ietf.org/agenda/86/slides/slides-86-core-1.pdf). You can also access the entire specification at:
> 
> http://member.openmobilealliance.org/ftp/Public_documents/DM/LightweightM2M/Permanent_documents/OMA-TS-LightweightM2M-V1_0_0-20130301-D.zip  
> 
> Regards,
> Zach
> 
> -- 
> Zach Shelby, Chief Nerd, Sensinode Ltd.
> http://www.sensinode.com @SensinodeIoT
> Mobile: +358 40 7796297
> Twitter: @zach_shelby
> LinkedIn: http://fi.linkedin.com/in/zachshelby
> 6LoWPAN Book: http://6lowpan.net
> 
> 
> 
> 
> _______________________________________________
> coman mailing list
> coman@ietf.org
> https://www.ietf.org/mailman/listinfo/coman