Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo)

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Thu, 26 September 2013 13:29 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 92AE921F9D52; Thu, 26 Sep 2013 06:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.161
X-Spam-Level:
X-Spam-Status: No, score=-103.161 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, 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 3U8tPFGn5sth; Thu, 26 Sep 2013 06:29:01 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 393DF21E804E; Thu, 26 Sep 2013 06:28:24 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4834020BC1; Thu, 26 Sep 2013 15:28:22 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id NZN7qDPKuVKD; Thu, 26 Sep 2013 15:28:22 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id D756420A1F; Thu, 26 Sep 2013 15:28:21 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 167BD288C993; Thu, 26 Sep 2013 15:28:17 +0200 (CEST)
Date: Thu, 26 Sep 2013 15:28:17 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Message-ID: <20130926132817.GB25326@elstar.local>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "coman@ietf.org" <coman@ietf.org>, The IESG <iesg@ietf.org>, 6lo WG <6lo@ietf.org>
References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52419C92.9040807@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "coman@ietf.org" <coman@ietf.org>, "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, The IESG <iesg@ietf.org>, 6lo WG <6lo@ietf.org>
Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo)
X-BeenThere: coman@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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: Thu, 26 Sep 2013 13:29:05 -0000

On Tue, Sep 24, 2013 at 04:07:15PM +0200, Benoit Claise wrote:
> >My understanding is that the charter refers to
> >
> >http://tools.ietf.org/html/draft-schoenw-6lowpan-mib-03
> >
> >and that it not aims at a general discussion about network management
> >of constrained devices. That is, it refers to concrete work instead of
> >abstract work.
> That's actually my point. Should we focus on developing a MIB
> module, taking for granting that SNMP is THE way to manage
> constrained nodes? Or should we ask ourselves: based on the
> collected management requirements, let's see what is more
> appropriate?

One more time: The goal here is to define the number and the semantics
of the counters that need to implemented in the 6LoWPAN layer in order
to enable basic monitoring and troubleshooting. The formalism we have
(as a standard) for that are MIB modules.

There are several ways to transport the data over various protocols
today and there may be even more in the future. This activity is about
getting agreement what exactly needs to be counted where in the
6LoWPAN processing.

> You know, like I2RS is currently doing, instead of jumping to
> NETCONF/YANG directly because it seemed like the solution.

If you believe this is needed here in order to define a bunch of
counters.

/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/>