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

Ulrich Herberg <ulrich@herberg.name> Thu, 03 October 2013 21:05 UTC

Return-Path: <ulrich@herberg.name>
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 5410E1F0D37 for <coman@ietfa.amsl.com>; Thu, 3 Oct 2013 14:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 3UXHTwe5ikM8 for <coman@ietfa.amsl.com>; Thu, 3 Oct 2013 14:04:58 -0700 (PDT)
Received: from mail-ve0-x22b.google.com (mail-ve0-x22b.google.com [IPv6:2607:f8b0:400c:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 04AC321F8FE5 for <coman@ietf.org>; Thu, 3 Oct 2013 13:52:18 -0700 (PDT)
Received: by mail-ve0-f171.google.com with SMTP id pa12so2012863veb.2 for <coman@ietf.org>; Thu, 03 Oct 2013 13:52:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=T7/2SSr82Fn3A5B52bmeKi6YuyAWh93tjXgntsTdKCQ=; b=cpBhoOGdc/ElkBCQQ7Z1hPuaBWerkmmvrtDTzUKAu/BRHx5zMP23+4bIlR1XihIp68 wh1LDqnV1+OjAwpcefwPKUY/6EoBN2fLsu7zFPM9RBsn2BKoNGyZsjlS7JA1ZdSm6dQ0 Hg1gwUTREPiP69lNL6iWd7yNXd96GmpJGZg4M=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=T7/2SSr82Fn3A5B52bmeKi6YuyAWh93tjXgntsTdKCQ=; b=ikYZlRAsL3AKho7s0nDxiRj/djXDyX94yIW9nF7Bi4AmoXEGII2l81+CG62uhaBeha yTRo2xkNMIA0iy7pL1JQB0gp87o8mzzBqyLLFZ+ErN3LQdG4Tzf0W5QFN9uplqfA+Lzr XlpNyrifcnvh5vvoH0fu3DCckUL/McWS/cjhekaAEN/WvBZpmEsMl4nGrHpTt/039yu6 BoY1lQeM0RA/sSPGNLwYAyy3hLooCkp3kLy5XABlhZCMYZbHX0QExN3+9YNS2bNVssqo oLb0e+xKF8JSsILfWiz9K6jX+br/g7DgyWoaOQqBBlmkS/zK2PA0Xnvqn5soC+QOf482 xvpg==
X-Gm-Message-State: ALoCoQkET825IbFkiSWYhJaJ50Op0EmCaNchE4EVTSdsoHslIZ0R+LkHcm1CWvxI+2Ek2YuHJE2G
MIME-Version: 1.0
X-Received: by 10.58.152.193 with SMTP id va1mr9205968veb.10.1380833537908; Thu, 03 Oct 2013 13:52:17 -0700 (PDT)
Received: by 10.220.168.8 with HTTP; Thu, 3 Oct 2013 13:52:17 -0700 (PDT)
In-Reply-To: <F5B5FDF6-3F08-45F1-BD08-1C9C1F01DC41@tzi.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> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <BD90D6F5-B01E-40CD-880D-6E9A597581BE@bogus.com> <d3b936fbfff74f21b0fbefb2dfedf77e@DB3PR01MB011.eurprd01.prod.exchangelabs.com> <524D2BCB.8020008@cisco.com> <F5B5FDF6-3F08-45F1-BD08-1C9C1F01DC41@tzi.org>
Date: Thu, 03 Oct 2013 13:52:17 -0700
Message-ID: <CAK=bVC84rU0EoHzQGfnykpQzd9MOVLz-D2YYUyJtjJv_mpa0Rw@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Benoit Claise <bclaise@cisco.com>, "coman@ietf.org" <coman@ietf.org>, "Turner, Randy" <Randy.Turner@landisgyr.com>, "6lo@ietf.org" <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
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, 03 Oct 2013 21:05:06 -0000

Carsten,

On Thu, Oct 3, 2013 at 2:53 AM, Carsten Bormann <cabo@tzi.org> wrote:
> On Oct 3, 2013, at 10:33, Benoit Claise <bclaise@cisco.com> wrote:
>
>>  Information model for the counters in the 6LoWPAN layer for basic monitoring
>>  and troubleshooting, and a mapping to a data model (MIB module in this case)
>
> I still believe the parenthesis is a bit constraining (pun not intended), not the least because over time we will have more than one case.  (We also have at least one thing that actually is not a counter.)  More importantly, new IP-over-foos may need new counters, so limiting this to the 6LoWPAN layer means we'll need to recharter for a 6lobac MIB module etc.

I agree with you on this point. It appears to me that we narrow down
the charter to a very small part of work, and we would end up
rechartering very soon, for example if a "6lobac" module is proposed.
Also, the proposed wording only includes counters; what about
read-write objects such as flags to provision objects? Would we want
to exclude that?


>
> For the ~ 10 % of work of the WG that is concerned with defining those counters (and related bits of information), the WG will need to listen for input from the management experts.
>
> I think the decision that the current one will be a MIB module should be in the milestones, and the charter should say how we arrive at these decisions.

Yes.

Regarding Benoit's proposal of separating information and data module,
I am not sure whether this requires a separate deliverable; but as
Benoit said, this is not necessarily related, and could be a section
of, e.g., the 6lowpan MIB module. That could be part of the discussion
how to structure this once the WG is formed.

How about the following text:
- Information and data models (e.g., MIB modules) for these adaptation
layers for basic provisioning, monitoring and troubleshooting.

Best regards
Ulrich