IETF Logo Mail Archive

Re: [netmod] Fwd: New Version Notification for draft-ietf-netmod-yang-instance-file-format-00.txt

Ladislav Lhotka <lhotka@nic.cz> Tue, 06 November 2018 04:51 UTC

Return-Path: <lhotka@nic.cz>
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 3CAF812D4EA for <netmod@ietfa.amsl.com>; Mon, 5 Nov 2018 20:51:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 KZ3fuQXOORMi for <netmod@ietfa.amsl.com>; Mon, 5 Nov 2018 20:51:36 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 882521294D0 for <netmod@ietf.org>; Mon, 5 Nov 2018 20:51:36 -0800 (PST)
Received: by trail.lhotka.name (Postfix, from userid 109) id 11CF9182113D; Tue, 6 Nov 2018 05:59:24 +0100 (CET)
Received: from localhost (dhcp-9cfe.meeting.ietf.org [31.133.156.254]) by trail.lhotka.name (Postfix) with ESMTPSA id CB0751821139; Tue, 6 Nov 2018 05:59:21 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Joe Clarke <jclarke@cisco.com>, Balázs Lengyel <balazs.lengyel@ericsson.com>, "netmod@ietf.org" <netmod@ietf.org>
In-Reply-To: <2a796f78-41b7-376c-8f51-215d14cc4e2c@cisco.com>
References: <154147032474.4217.10743411700898817061.idtracker@ietfa.amsl.com> <07b9bcea-72e3-9986-7d42-303c4797f13a@ericsson.com> <2a796f78-41b7-376c-8f51-215d14cc4e2c@cisco.com>
Mail-Followup-To: Joe Clarke <jclarke@cisco.com>, Balázs Lengyel <balazs.lengyel@ericsson.com>, "netmod\@ietf.org" <netmod@ietf.org>
Date: Tue, 06 Nov 2018 11:51:26 +0700
Message-ID: <87y3a6izap.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/2OxHysdeW2uBfWz1BKSo3KmpNx4>
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 04:51:39 -0000

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

v2.23.0 | Report a Bug | By Email