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 09:36 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 0E7E5128A6E for <netmod@ietfa.amsl.com>; Tue, 6 Nov 2018 01:36:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level:
X-Spam-Status: No, score=-6.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 Mi0bhtBMwQfI for <netmod@ietfa.amsl.com>; Tue, 6 Nov 2018 01:36:16 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5E56129AB8 for <netmod@ietf.org>; Tue, 6 Nov 2018 01:36:15 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:67c:1232:144:1a4f:a84b:2bfd:c611]) by mail.nic.cz (Postfix) with ESMTPSA id E2F2562AC7 for <netmod@ietf.org>; Tue, 6 Nov 2018 10:36:12 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1541496973; bh=rcIYCzDGYsNWSumlx7AzduPsbqBeGik+ngX++sblYWk=; h=From:To:Date; b=IMKhq13uim/BRCFk1uFEEGFvQdD8179aK3HugtCGQyVyZdouK6jWkdmZvYbiaO2jy 8K4zr0G4XVSlw8R3Q403h4qKUoVBMj79L45ftHrFK/DkeG/2SUwIXTpW+9p9b1zlZt Y2psfNLmTzCwew0Ev9miWf3raHiutyjDPYk5SzHQ=
Message-ID: <58740c15bf3277e04329546476f60c1d12516594.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: netmod@ietf.org
Date: Tue, 06 Nov 2018 16:36:09 +0700
In-Reply-To: <20181106063648.jjf2scqzoack5l3z@anna.jacobs.jacobs-university.de>
References: <154147032474.4217.10743411700898817061.idtracker@ietfa.amsl.com> <07b9bcea-72e3-9986-7d42-303c4797f13a@ericsson.com> <2a796f78-41b7-376c-8f51-215d14cc4e2c@cisco.com> <87y3a6izap.fsf@nic.cz> <20181106063648.jjf2scqzoack5l3z@anna.jacobs.jacobs-university.de>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.2
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/nPeSSPMuSTzgO_ooEEi5dZs7ENA>
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:36:19 -0000

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