Re: [netmod] Last Call: <draft-ietf-netmod-entity-07.txt> (A YANG Data Model for Hardware Management) to Proposed Standard

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Thu, 04 January 2018 13:33 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 B6E5D12D832; Thu, 4 Jan 2018 05:33:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 146htIJUtzrg; Thu, 4 Jan 2018 05:33:09 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EFEF126CD6; Thu, 4 Jan 2018 05:33:09 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 4AF4A3D; Thu, 4 Jan 2018 14:33:08 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id Mixov6DwfW-M; Thu, 4 Jan 2018 14:33:07 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 4 Jan 2018 14:33:08 +0100 (CET)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 370A420136; Thu, 4 Jan 2018 14:33:08 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id W294e799sm9D; Thu, 4 Jan 2018 14:33:07 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8E00420134; Thu, 4 Jan 2018 14:33:07 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 748234203D9C; Thu, 4 Jan 2018 14:33:07 +0100 (CET)
Date: Thu, 4 Jan 2018 14:33:07 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "tom p." <daedulus@btconnect.com>
Cc: netmod@ietf.org, draft-ietf-netmod-entity@ietf.org
Message-ID: <20180104133307.mihhlwavxqdc3qok@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: "tom p." <daedulus@btconnect.com>, netmod@ietf.org, draft-ietf-netmod-entity@ietf.org
References: <151389497762.28118.16231694341929195271.idtracker@ietfa.amsl.com> <04bb01d38558$bf88b4a0$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <04bb01d38558$bf88b4a0$4001a8c0@gateway.2wire.net>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/jH33HlacIzphQe-7bTooYEDq7BY>
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-entity-07.txt> (A YANG Data Model for Hardware Management) to Proposed Standard
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 04 Jan 2018 13:33:12 -0000

On Thu, Jan 04, 2018 at 12:37:02PM -0000, tom p. wrote:
> This I-D illlustrates a problem that the netmod WG has been wrestling
> with for a decade or more and (IMHO) has yet fully to solve.  This I-D
> is in Last Call at the same time as netmod-revised-datastores, which
> proposes the most recent solution.
> 
> The problem is that an 'object' can take more than one value and the
> question is how to represent that.  Previously it was by having twin
> trees in the schema; now it is by having one common schema and multiple
> datastores, <running> for the user-supplied values, <operational> for
> those actually in use, the latter including values learnt from the
> hardware or protocols or some other means.
> 
> In this model the situation arises with 'serial-num' which may take a
> value from the hardware or may be written as part of configuration (the
> idea of configuring serial numbers may seem unusual but has been
> inherited from the Entity MIB [RFC6933] with the endorsement of the
> netmod WG).
> 
> So if there is an accessible hardware value and the user writes a value,
> who wins?  There is no way of specifying this, neither in YANG nor in
> 'revised-datastores'; in this case, the 'description' specifies that the
> value determined from the component should be used so a user can
> configure a value, see it in the <running> datastore but not in the
> <operational> datastore and cannot tell why, unless they are familiar
> with the minutiae of description clauses.

The origin attribute will at least tell you where the operationally
used value is originating from.

> In this case, the model is clear as to which value, configured or
> learnt, wins; here, it is learnt.  In other cases, it may be that
> configured wins or that may be something a user wants to influence as
> part of policy.
> 
> Is that still one schema or is it now two slightly different schemas
> based on the description clause coupled with the datastore that the
> schema is being applied to?
> 
> Is the description clause an adequate way of expressing policy?
> 
> In passing, routing protocols addressed this dilemma a long time ago,
> with concepts such as 'Admin Distance'.
> 
> (Whether or not this particular value should be configurable is a
> different and irrelevant discussion; the MIB WG decided it should be,
> the YANG WG likewise - and there are plenty of other objects which
> illustrate this dilemma, how to specify who wins).
> 
> Tom Petch
> 
> ----- Original Message -----
> From: "The IESG" <iesg-secretary@ietf.org>;
> Sent: Thursday, December 21, 2017 10:22 PM
> 
> > The IESG has received a request from the Network Modeling WG (netmod)
> to
> > consider the following document: - 'A YANG Data Model for Hardware
> Management'
> >   <draft-ietf-netmod-entity-07.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> final
> > comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2018-01-10. Exceptionally, comments may
> be
> > sent to iesg@ietf.org instead. In either case, please retain the
> beginning of
> > the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >    This document defines a YANG data model for the management of
> >    hardware on a single server.
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-netmod-entity/
> >
> > IESG discussion can be tracked via
> > https://datatracker.ietf.org/doc/draft-ietf-netmod-entity/ballot/
> >
> > No IPR declarations have been submitted directly on this I-D.
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

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