Re: [netmod] I-D Action: draft-ietf-netmod-entity-02.txt
Martin Bjorklund <mbj@tail-f.com> Mon, 23 January 2017 10:58 UTC
Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0D361295DD for <netmod@ietfa.amsl.com>; Mon, 23 Jan 2017 02:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.1
X-Spam-Level:
X-Spam-Status: No, score=-5.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2stigm65bPnn for <netmod@ietfa.amsl.com>; Mon, 23 Jan 2017 02:58:44 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 851121295DC for <netmod@ietf.org>; Mon, 23 Jan 2017 02:58:44 -0800 (PST)
Received: from localhost (unknown [173.38.220.36]) by mail.tail-f.com (Postfix) with ESMTPSA id 71FAD1AE0285; Mon, 23 Jan 2017 11:58:43 +0100 (CET)
Date: Mon, 23 Jan 2017 11:58:41 +0100
Message-Id: <20170123.115841.723508035325803360.mbj@tail-f.com>
To: j.schoenwaelder@jacobs-university.de
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20170123094232.GC29022@elstar.local>
References: <148516226715.29498.6381011685248407321.idtracker@ietfa.amsl.com> <20170123094232.GC29022@elstar.local>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/t799QgGdJx_HZr311hdBbb2XklQ>
Cc: netmod@ietf.org
Subject: Re: [netmod] I-D Action: draft-ietf-netmod-entity-02.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2017 10:58:45 -0000
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote: > Hi, > > I wonder when we use 'state' and when 'status' - is there a subtle > distinction or should be just consistently use lets say 'state', i.e., > changed to alalarm-status to alarm-state and standby-status to > standby-state? The reason in this case is that we just used the MIB names. This said, I agree that "standby-state" and "alarm-state" are better. BTW, RFC 4268, which defines the original objects, says: The terms "state" and "status" are used interchangeably in this memo. > I also wonder about the mapping of the MIB object names to YANG leaf > names: > > +-------------------------------------+-----------------------------+ > | YANG data node in /hardware- | ENTITY-SENSOR-MIB object | > | state/component/sensor-data | | > +-------------------------------------+-----------------------------+ > | data-type | entPhySensorType | > | data-scale | entPhySensorScale | > | precision | entPhySensorPrecision | > | value | entPhySensorValue | > | oper-status | entPhySensorOperStatus | > | sensor-units-display | entPhySensorUnitsDisplay | > | value-timestamp | entPhySensorValueTimeStamp | > | value-update-rate | entPhySensorValueUpdateRate | > +-------------------------------------+-----------------------------+ > > Is the 'data-' prefix needed? If so, why is the a prefix not used for > 'precision' (scale and precision really go hand in hand). Unclear. I think I'm the one to blame for this inconsistency, and it goes back to the very first commit, but I can't remeber why. > Why is it > 'sensor-units-display' and not just 'units-display'? One option could > be: > > value-type > value-scale > value-precision > value > oper-status > units-display > value-timestamp > value-update-rate Yes this is better. > RFC 3433 points out that entPhySensorType and entPhySensorScale and > entPhySensorPrecision SHOULD NOT change during operation. What about > the YANG objects? I actually do not know what the SHOULD buys a client > since you can't rely on it. To be robust, you have to fetch an n-tuple > anyway and be prepared that a sensor may have changed its properties. > Should there be explicit text providing guidance that it is better to > fetch the whole n-tuple? This is certainly the simplest solution. Any comments? > Or alternatively, if supporting caching of > values is a goal, we may need to provide a > 'sensor-data/properties-last-changed' object that allows to make > caching of value properties robust. /martin
- [netmod] I-D Action: draft-ietf-netmod-entity-02.… internet-drafts
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Martin Bjorklund
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Juergen Schoenwaelder
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Martin Bjorklund
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Bogaert, Bart (Nokia - BE)
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Martin Bjorklund
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Bogaert, Bart (Nokia - BE)
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Juergen Schoenwaelder
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Bogaert, Bart (Nokia - BE)
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Bogaert, Bart (Nokia - BE)
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Martin Bjorklund
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Bogaert, Bart (Nokia - BE)
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Martin Bjorklund
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Bogaert, Bart (Nokia - BE)
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Martin Bjorklund
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Kent Watsen
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Martin Bjorklund
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Bogaert, Bart (Nokia - BE)
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Juergen Schoenwaelder
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Bogaert, Bart (Nokia - BE)
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Martin Bjorklund
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Bogaert, Bart (Nokia - BE)
- Re: [netmod] I-D Action: draft-ietf-netmod-entity… Martin Bjorklund