Re: [netmod] Last Call: <draft-ietf-netmod-revised-datastores-09.txt> (Network Management Datastore Architecture) to Proposed Standard two

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 10 January 2018 16:37 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 A3F4612D778; Wed, 10 Jan 2018 08:37:00 -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 3Sf_JYyCzzlo; Wed, 10 Jan 2018 08:36:58 -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 C835F129C6B; Wed, 10 Jan 2018 08:36:57 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 8E115EFF; Wed, 10 Jan 2018 17:36:56 +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 eyCj5kwoH2F5; Wed, 10 Jan 2018 17:36:55 +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; Wed, 10 Jan 2018 17:36:56 +0100 (CET)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6CD2F2013D; Wed, 10 Jan 2018 17:36:56 +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 fpFR60_Iclsv; Wed, 10 Jan 2018 17:36:55 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 5E2DD2013C; Wed, 10 Jan 2018 17:36:55 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 2360C420A198; Wed, 10 Jan 2018 17:36:53 +0100 (CET)
Date: Wed, 10 Jan 2018 17:36:53 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: daedulus@btconnect.com
Cc: ietf@ietf.org, netmod-chairs@ietf.org, bclaise@cisco.com, draft-ietf-netmod-revised-datastores@ietf.org, netmod@ietf.org
Message-ID: <20180110163653.fjfbmr3gbnue52pq@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: daedulus@btconnect.com, ietf@ietf.org, netmod-chairs@ietf.org, bclaise@cisco.com, draft-ietf-netmod-revised-datastores@ietf.org, netmod@ietf.org
References: <151388421473.12936.719186167168412861.idtracker@ietfa.amsl.com> <012c01d3896d$68c41d80$4001a8c0@gateway.2wire.net> <20180109.210824.760424986407969599.mbj@tail-f.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180109.210824.760424986407969599.mbj@tail-f.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/7nr0pV_8fCrpREkzD48eJYvkmRE>
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-revised-datastores-09.txt> (Network Management Datastore Architecture) to Proposed Standard two
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: Wed, 10 Jan 2018 16:37:01 -0000

On Tue, Jan 09, 2018 at 09:08:24PM +0100, Martin Bjorklund wrote:
> Hi Tom,
> 
> "tom p." <daedulus@btconnect.com> wrote:
> > Much of this I-D is about the idea that network management data objects
> > can often take two different values.  The I-D always refers to this as
> > being two values but is that a limit that this architecture imposes; or
> > can it be more?
> 
> The I-D talks about two instantiations in the Objectives section, when
> the original "config vs oper values" problem is explained, and how
> NMDA solves the problem.
> 
> But the archtecture allows for any number of instantiations; it all
> depends on which datastores a particular server implements.  For
> example, a config node might have one value in <candidate>, a
> different in <running> and yet a different value in <startup>.  This
> is not new to this document.
>

Right. Lets see there "two" is used:

- 1st paragraph in 2. Objectives: I think the text is clear since it
  talks about a concrete example of a configured value and an
  operationally used value.

- 2nd paragraph in 2. Objectives: This text talks about two separate
  branches in the old models, this should be fine.

- 4th paragraph in 2. Objectives: I think this is potentially
  causing the confusion. It says:

    With the revised architectural model of datastores defined in this
    document, the data objects are defined only once in the YANG schema
    but independent instantiations can appear in two different
    datastores, one for configured values and one for operational state
    values.

  Perhaps a better wording would be this:

    With the revised architectural model of datastores defined in this
    document, the data objects are defined only once in the YANG
    schema but independent instantiations can appear in different
    datastores, e.g., for a configured value and one for an
    operationally used value.

  This e.g. then kind of continues the example the section started
  with. Would this change have avoided the question?

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