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> Thu, 11 January 2018 12:58 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 180BB12EB2F; Thu, 11 Jan 2018 04:58:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 o8KjcxpvOU8M; Thu, 11 Jan 2018 04:58:41 -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 B79B612DA6A; Thu, 11 Jan 2018 04:58:40 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 88A896AC; Thu, 11 Jan 2018 13:58:39 +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 EnT3fYI9uD8Y; Thu, 11 Jan 2018 13:58:38 +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, 11 Jan 2018 13:58:39 +0100 (CET)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 688472013E; Thu, 11 Jan 2018 13:58:39 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id AqFjB8toDtRj; Thu, 11 Jan 2018 13:58:39 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id EE1B92013D; Thu, 11 Jan 2018 13:58:38 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id CE11D420C3BE; Thu, 11 Jan 2018 13:58:37 +0100 (CET)
Date: Thu, 11 Jan 2018 13:58:37 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "tom p." <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: <20180111125837.vc6jvjpcbqpmexd2@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: "tom p." <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> <20180110163653.fjfbmr3gbnue52pq@elstar.local> <038f01d38ad8$59860240$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <038f01d38ad8$59860240$4001a8c0@gateway.2wire.net>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/kfQZDzH-pxDQKGWoSIi727gmuEg>
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: Thu, 11 Jan 2018 12:58:51 -0000

On Thu, Jan 11, 2018 at 12:32:29PM -0000, tom p. wrote:
> ----- Original Message -----
> From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
> Sent: Wednesday, January 10, 2018 4:36 PM
> 
> > 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?
> 
> Juergen
> 
> Yes, I would find that clearer.  Perhaps even better
> 
> OLD
>      e.g., for a configured value and one for an
>     operationally used value.
> NEW
>      e.g., one for a configured value and one (another?)  for an
>      operationally used value.
> 
> I would say 'one' and 'another'  but 'one' and 'one' would be clear
> enough.
>

I now have 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., one for a configured value and another for an operationally used
  value.

OK?

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