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

Benoit Claise <bclaise@cisco.com> Fri, 27 September 2013 08:32 UTC

Return-Path: <bclaise@cisco.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 7555611E8133; Fri, 27 Sep 2013 01:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.539
X-Spam-Level:
X-Spam-Status: No, score=-10.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 hOqIyCuJ49FL; Fri, 27 Sep 2013 01:32:37 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 73F7621F9F70; Fri, 27 Sep 2013 01:32:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1708; q=dns/txt; s=iport; t=1380270757; x=1381480357; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=Ru2V5DQGDKrWZSdSZaL6FQcn4fhHfGXXkE/lSLvUAG8=; b=HZKYfvvlLeNGssJrRquZ2c9cUvGnsF+gr641qF6UxGbUwQ3uEw9Nzznk 1yFd/HIH4pFWysvA/p69yV/mx7lKEsRfypyzM/dGkeautCStbkJy4n/eD p3VWINV0mvRlN7OUQczWAjkTI2ScnZJv8Au8A2ZQnLxgE2g4FEyswkQ9W k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAJtBRVKQ/khR/2dsb2JhbABYgwc4wRyBHBZ0giUBAQEEMgEFQBELGAkWDwkDAgECAUUGAQwIAQEXh2sMukePWIQeA5Qgg12BL4UDi0aBZoFAOg
X-IronPort-AV: E=Sophos;i="4.90,991,1371081600"; d="scan'208";a="160058923"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 27 Sep 2013 08:32:35 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r8R8WXBA024431; Fri, 27 Sep 2013 08:32:33 GMT
Message-ID: <524542A1.1090408@cisco.com>
Date: Fri, 27 Sep 2013 10:32:33 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "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> <20130926132817.GB25326@elstar.local>
In-Reply-To: <20130926132817.GB25326@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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
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: Fri, 27 Sep 2013 08:32:41 -0000

Jürgen,
> 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.
Interesting.
And not point to say "one more time...", I only focus on the charter 
text, which is the contract between the IESG and WG.
When I read it:

	Specifically, 6lo will work on:
	...
	2. Related MIB modules

How am I supposed to understand what you have in mind?
This specific entry has to improve.

Regards, Benoit
>
>> 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
>