Re: [netmod] Fwd: New Version Notification for draft-ietf-netmod-yang-instance-file-format-00.txt
Martin Bjorklund <mbj@tail-f.com> Tue, 06 November 2018 09:42 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 70FE1130E69 for <netmod@ietfa.amsl.com>; Tue, 6 Nov 2018 01:42:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 O55ymGu6IOjO for <netmod@ietfa.amsl.com>; Tue, 6 Nov 2018 01:41:59 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 982FE130E5C for <netmod@ietf.org>; Tue, 6 Nov 2018 01:41:59 -0800 (PST)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id 779CD1AE018C; Tue, 6 Nov 2018 10:41:58 +0100 (CET)
Date: Tue, 06 Nov 2018 10:41:57 +0100
Message-Id: <20181106.104157.239419955739949818.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <58740c15bf3277e04329546476f60c1d12516594.camel@nic.cz>
References: <87y3a6izap.fsf@nic.cz> <20181106063648.jjf2scqzoack5l3z@anna.jacobs.jacobs-university.de> <58740c15bf3277e04329546476f60c1d12516594.camel@nic.cz>
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/NCbYTASFWujNmSBiKZLeo9oxWX8>
Subject: Re: [netmod] Fwd: New Version Notification for draft-ietf-netmod-yang-instance-file-format-00.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 06 Nov 2018 09:42:03 -0000
Ladislav Lhotka <lhotka@nic.cz> wrote: > On Tue, 2018-11-06 at 07:36 +0100, Juergen Schoenwaelder wrote: > > I agree that > > > > leaf datastore { > > type ds:datastore-ref; > > description "The identity of the datastore for which > > the instance data is documented for config=true data nodes. > > The leaf MAY be absent in which case the running dtastore or > > if thats not writable, the candidate datastore is implied. > > > > For config=false data nodes always the operational > > data store is implied."; > > } > > > > is pretty confusing. It should be something like this: > > > > leaf datastore { > > type ds:datastore-ref; > > description "The identity of the datastore holding > > the instance data. If the instance data is not associated > > Or rather the datastore that the instance data was extracted from. I prefer "associated with". There are other uses cases than just holding data "extracted from", e.g., data that is supposed to "be inserted into" a datastore. "associated with" is less resrictive. > After that, > the data exists on its own and the originating datastore may later be holding > something else. > > > with a datastore, then this leaf MUST be absent."; > > RFC 2119 language would make sense if there is anything that could break if that > MUST isn't observed. But we even didn't know what the data is going to be used > for. > > I would treat the "datastore" item as a purely optional information I agree. /martin > that, if > present, was provided for some reason. If it is false, what can we do? > > > } > > > > I am against merging data from different datastores together, which > > the last sentence of the original text seems to imply. > > Both config true and config false data may come from <operational>, so it > doesn't necessarily mean any mixing of datastores. But then again, I think that > the datastore information isn't in most cases that interesting. > > Lada > > > > > /js > > > > On Tue, Nov 06, 2018 at 11:51:26AM +0700, Ladislav Lhotka wrote: > > > Joe Clarke <jclarke@cisco.com> writes: > > > > === > > > > > > > > Section 6 > > > > > > > > With your datastore leaf, if I pull this off of a running YANG server, > > > > serialize it and share it with my customer, why wouldn't I have the > > > > actual datastore from which I retrieved it? What I'm saying is that > > > > this element may be missing, but if it is, I don't think you can assume > > > > the source datastore for config=true nodes. > > > > > > > > > > The description of the "datastore" leaf doesn't make much sense to > > > me. It says that for configuration data the default is "running" or > > > "candidate" if "running" isn't writable. Why should it matter whether > > > "running" is writable? It looks like it is assumed that the config data will > > > eventually be fed into the indicated datastore, but I don't see any > > > reason for such an assumption. > > > > > > I can see that "datastore" can be occasionally useful as auxiliary > > > metadata but, in my view, this document addresses also instance data > > > that is not necessarily bound to any datastore. > > > > > > Lada > > > > > > -- > > > Ladislav Lhotka > > > Head, CZ.NIC Labs > > > PGP Key ID: 0xB8F92B08A9F76C67 > > > > > > _______________________________________________ > > > netmod mailing list > > > netmod@ietf.org > > > https://www.ietf.org/mailman/listinfo/netmod > -- > Ladislav Lhotka > Head, CZ.NIC Labs > PGP Key ID: 0xB8F92B08A9F76C67 > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod >
- [netmod] Fwd: New Version Notification for draft-… Balázs Lengyel
- Re: [netmod] Fwd: New Version Notification for dr… Joe Clarke
- Re: [netmod] Fwd: New Version Notification for dr… Ladislav Lhotka
- Re: [netmod] Fwd: New Version Notification for dr… Joe Clarke
- Re: [netmod] Fwd: New Version Notification for dr… Juergen Schoenwaelder
- Re: [netmod] Fwd: New Version Notification for dr… Joe Clarke
- Re: [netmod] Fwd: New Version Notification for dr… Juergen Schoenwaelder
- Re: [netmod] Fwd: New Version Notification for dr… Ladislav Lhotka
- Re: [netmod] Fwd: New Version Notification for dr… Martin Bjorklund
- Re: [netmod] Fwd: New Version Notification for dr… Ladislav Lhotka
- Re: [netmod] Fwd: New Version Notification for dr… Balázs Lengyel
- [netmod] Datastore leaf for yang instance data Balázs Lengyel
- Re: [netmod] Datastore leaf for yang instance data Juergen Schoenwaelder
- Re: [netmod] Datastore leaf for yang instance data Balázs Lengyel
- Re: [netmod] Datastore leaf for yang instance data Balázs Lengyel
- Re: [netmod] Datastore leaf for yang instance data Juergen Schoenwaelder
- Re: [netmod] Datastore leaf for yang instance data Juergen Schoenwaelder
- Re: [netmod] Datastore leaf for yang instance data Martin Bjorklund
- Re: [netmod] Fwd: New Version Notification for dr… Joe Clarke
- Re: [netmod] Fwd: New Version Notification for dr… Juergen Schoenwaelder
- Re: [netmod] Datastore leaf for yang instance data Robert Wilton
- Re: [netmod] Datastore leaf for yang instance data Juergen Schoenwaelder
- Re: [netmod] Datastore leaf for yang instance data Robert Wilton
- Re: [netmod] Datastore leaf for yang instance data Juergen Schoenwaelder
- Re: [netmod] Fwd: New Version Notification for dr… Qin Wu
- [netmod] yang-instance-file-format - do we need a… Balázs Lengyel
- [netmod] yang-instance-file-format - do we need a… Balázs Lengyel
- Re: [netmod] yang-instance-file-format - do we ne… Juergen Schoenwaelder
- Re: [netmod] yang-instance-file-format - do we ne… Balázs Lengyel
- Re: [netmod] Datastore leaf for yang instance data Balázs Lengyel
- Re: [netmod] yang-instance-file-format - do we ne… Qin Wu