Re: [Coma] (no subject)

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Sat, 30 June 2012 13:29 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 22DA121F866D for <coma@ietfa.amsl.com>; Sat, 30 Jun 2012 06:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.524
X-Spam-Level:
X-Spam-Status: No, score=-106.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 zyYhMHg+3slZ for <coma@ietfa.amsl.com>; Sat, 30 Jun 2012 06:29:45 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id DB1AE21F851E for <coma@ietf.org>; Sat, 30 Jun 2012 06:29:44 -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 q5UDTaBC023832 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 30 Jun 2012 15:29:36 +0200
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q5UDTVfV019386; Sat, 30 Jun 2012 15:29:33 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Sat, 30 Jun 2012 15:28:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 30 Jun 2012 15:28:59 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6403F7F8B6@DEMUEXC006.nsn-intra.net>
In-Reply-To: <004701cd55f8$aae33600$00a9a200$@cn>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Coma] (no subject)
Thread-Index: Ac1VQVaY6w8eFDCmSRGWO8JpmJw/nAAlj4TgAAg7WCAADpUgkA==
References: <00b101cd5508$22e90bd0$68bb2370$@cn> <20120628151851.GD56180@elstar.local> <80A0822C5E9A4440A5117C2F4CD36A6403F7F5E4@DEMUEXC006.nsn-intra.net> <004701cd55f8$aae33600$00a9a200$@cn>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Yan Wang" <ywang@cnnic.cn>
X-OriginalArrivalTime: 30 Jun 2012 13:28:59.0399 (UTC) FILETIME=[4E7CC170:01CD56C4]
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: 4624
X-purgate-ID: 151667::1341062976-00003CDD-8DC0541E/0-0/0-0
Cc: coma@ietf.org
Subject: Re: [Coma] (no subject)
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: Sat, 30 Jun 2012 13:29:46 -0000

Hi Yan,

> Maybe we should propose several use cases of different kinds of
networks. 
> It is good to make clear about their common requirements and
individual requirements.

I would appreciate it if you could provide the type of constraint
networks/devices and the use cases you have in mind as input for
discussion.

Our aim is to look at the use cases and requirements independently of
existing protocols. We might highlight gaps in existing technologies but
selecting the right protocol is an individual decision. 

Cheers, 
Mehmet 

> -----Original Message-----
> From: ext Yan Wang [mailto:ywang@cnnic.cn]
> Sent: Friday, June 29, 2012 3:11 PM
> To: Ersue, Mehmet (NSN - DE/Munich); 'Juergen Schoenwaelder'
> Cc: coma@ietf.org
> Subject: RE: [Coma] (no subject)
> 
> Dear Mehmet and Juergen,
> Thank you for your replies. Service management is really more suitable
to
> put in the use case.
> There are many kinds of constraint networks and devices, as well as
many
> kinds of existing protocols for network management. I am still not
quite
> clear about the management requirements. Maybe we should propose
several use
> cases of different kinds of networks. It is good to make clear about
their
> common requirements and individual requirements.
> 
> 
> Best wishes,
> Yan
> 
> > -----Original Message-----
> > From: coma-bounces@ietf.org [mailto:coma-bounces@ietf.org] On Behalf
Of
> > Ersue, Mehmet (NSN - DE/Munich)
> > Sent: Friday, June 29, 2012 5:15 PM
> > To: Juergen Schoenwaelder; Yan Wang
> > Cc: coma@ietf.org
> > Subject: Re: [Coma] (no subject)
> >
> > Hi Yan,
> >
> > service management is a huge topic area and I assume we cannot cover
it
> > exhaustively. IMO service management should be discussed as part of
the
> use
> > cases. Based on this we need to understand the requirements on the
> > management of networks with constrained devices.
> >
> > Cheers,
> > Mehmet
> >
> >
> > > -----Original Message-----
> > > From: coma-bounces@ietf.org [mailto:coma-bounces@ietf.org] On
Behalf
> > Of ext
> > > Juergen Schoenwaelder
> > > Sent: Thursday, June 28, 2012 5:19 PM
> > > To: Yan Wang
> > > Cc: coma@ietf.org
> > > Subject: Re: [Coma] (no subject)
> > >
> > > On Thu, Jun 28, 2012 at 04:29:29PM +0800, Yan Wang wrote:
> > >
> > > > By the way,
> > > >
http://tools.ietf.org/html/draft-ietf-lwig-guidance-00#section-4.5
> > mentioned
> > > > development of a light-weight SNMP agent for resource
constrained
> > devices
> > > > running the 6LoWPAN/RPL protocol stack.
> > >
> > > We have implemented an SNMP stack on Contiki and we have published
> > > details about it. I think I only very partially agree with what is
> > > written in this section 4.5. There is also an old expired I-D that
> > > might be relevant: <draft-hamid-6lowpan-snmp-optimizations-03.txt>
> > >
> > > > What the relationship between coma and core, coma and lwig?
> > >
> > > My understanding is that CORE is specifying CoAP. CoAP may be used
for
> > > management but CORE is not chartered to specifically look at this
> > > question. LWIG is looking at coming up with general guidelines for
> > > light-weight implementations of IP protocols and hence might
include
> > > guidelines for implementing SNMP. COMA probably can take a broader
> > > look at what is needed and in particular what the requirements
driving
> > > things are. There is also discussion on the netconf WG list
related to
> > > constrained devices, but it is as of now not chartered work.
> > >
> > > I assume COMA is an attempt to provide a common place to discuss
the
> > > management requirements and aspects of constrained networks and
> > > devices instead of having discussions in several places.
> > >
> > > Of course, as Bert Wijnen kept saying, adding a protocol with the
best
> > > intentions to replace other protocols just leads at the end to one
> > > more protocol. If that applies to discussion lists as well, then
we
> > > just have one more. ;-)
> > >
> > > /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/>
> > > _______________________________________________
> > > Coma mailing list
> > > Coma@ietf.org
> > > https://www.ietf.org/mailman/listinfo/coma
> > _______________________________________________
> > Coma mailing list
> > Coma@ietf.org
> > https://www.ietf.org/mailman/listinfo/coma