Re: [Coma] (no subject)

"Yan Wang" <ywang@cnnic.cn> Fri, 29 June 2012 13:11 UTC

Return-Path: <ywang@cnnic.cn>
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 162E221F8759 for <coma@ietfa.amsl.com>; Fri, 29 Jun 2012 06:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599]
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 tX8q20PdhF9S for <coma@ietfa.amsl.com>; Fri, 29 Jun 2012 06:11:24 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id 6891F21F874C for <coma@ietf.org>; Fri, 29 Jun 2012 06:11:21 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: ywang@cnnic.cn
Received: from unknown127.0.0.1 (HELO cnnicpc) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 29 Jun 2012 21:11:11 +0800
From: "Yan Wang" <ywang@cnnic.cn>
To: "'Ersue, Mehmet \(NSN - DE/Munich\)'" <mehmet.ersue@nsn.com>, "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>
References: <00b101cd5508$22e90bd0$68bb2370$@cn> <20120628151851.GD56180@elstar.local> <80A0822C5E9A4440A5117C2F4CD36A6403F7F5E4@DEMUEXC006.nsn-intra.net>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6403F7F5E4@DEMUEXC006.nsn-intra.net>
Date: Fri, 29 Jun 2012 21:11:09 +0800
Message-ID: <004701cd55f8$aae33600$00a9a200$@cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1VQVaY6w8eFDCmSRGWO8JpmJw/nAAlj4TgAAg7WCA=
Content-Language: zh-cn
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: Fri, 29 Jun 2012 13:11:25 -0000

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