Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7895bis-05.txt

Ladislav Lhotka <lhotka@nic.cz> Mon, 05 March 2018 16:12 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78DA212D942 for <netconf@ietfa.amsl.com>; Mon, 5 Mar 2018 08:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level:
X-Spam-Status: No, score=-7.01 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, T_RP_MATCHES_RCVD=-0.01] 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 RzgvrSB0dwUr for <netconf@ietfa.amsl.com>; Mon, 5 Mar 2018 08:12:37 -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 AEA5012D9FF for <netconf@ietf.org>; Mon, 5 Mar 2018 08:12:10 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:1850:78ff:fe12:72ed]) by mail.nic.cz (Postfix) with ESMTPSA id 4D4CC627A2; Mon, 5 Mar 2018 17:12:09 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1520266329; bh=cymf1npK6BR/9GIFquZhUZK0trunot/Of+O+CSrzH3Q=; h=From:To:Date; b=EPzAGLqLq0dQUE/5odFIlmG5yL8JdRpee3K5ar3KySHdEyivAmAR4UgyAXLA5fPVf GVM8tQx+RKPPNBr5mmjqRx2Nq7d1q9OXqmmaAHW5G80L3qsV358rzvyjMPAxlI5IQF iJ+syT1D5rIt66+sUYyEiaXyUX7DWTN29H6Upt/c=
Message-ID: <1520266329.7198.60.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Cc: Robert Wilton <rwilton@cisco.com>, Martin Bjorklund <mbj@tail-f.com>, netconf@ietf.org
Date: Mon, 05 Mar 2018 17:12:09 +0100
In-Reply-To: <20180305160104.2fn7v2cdrdl6f54f@elstar.local>
References: <151974422911.28529.17468772806691724854@ietfa.amsl.com> <20180227.161434.1039409215522320595.mbj@tail-f.com> <87woyqmwdp.fsf@nic.cz> <d18163c2-be3f-3807-aa47-fdc9a1d17b40@cisco.com> <1520265051.7198.56.camel@nic.cz> <20180305160104.2fn7v2cdrdl6f54f@elstar.local>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.5
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/netconf/YqJBrv5K13jx4c3Wk4vq3SpaMdg>
Subject: Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7895bis-05.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 16:12:38 -0000

On Mon, 2018-03-05 at 17:01 +0100, Juergen Schoenwaelder wrote:
> On Mon, Mar 05, 2018 at 04:50:51PM +0100, Ladislav Lhotka wrote:
> > > 
> > > Note, that the deviation leaf-list is a leafref back to the module 
> > > list.  Hence, for the YANG instance data to be valid, any entries in the 
> > > deviation list must be included in the modules list.
> > 
> > Hmm, even this is actually not true - the type should have
> > 
> >   require-instance true;
> > 
> > right?
> 
> Yes, I think this should be there.
>  
> > If "module" and "deviation" are required to match, the document
> > should say so.
> 
> Note that section 3 says:
> 
>    o  deviation list: The name of each YANG module with deviation
>       statements affecting a given YANG module, in a given datastore
>       schema, MUST be identified.
> 
> I know, this is in the objectives section and not in the YANG
> definitions, perhaps we need to make this clear there as well.
> Perhaps just change
> 
> OLD
> 
>      "List of YANG deviation modules used by this server to modify
> 
> NEW
> 
>      "List of all YANG deviation modules used by this server to modify

But still it doesn't say how the deviation list is determined from YLbis data. A
server/client implementor may IMO choose any of the three options that I listed.

Lada

> 
> /js
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67