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

Ladislav Lhotka <lhotka@nic.cz> Tue, 06 March 2018 15:46 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 BF655124E15 for <netconf@ietfa.amsl.com>; Tue, 6 Mar 2018 07:46:08 -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] 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 ey67gsUGLTVz for <netconf@ietfa.amsl.com>; Tue, 6 Mar 2018 07:46:05 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id B3E8212E8CD for <netconf@ietf.org>; Tue, 6 Mar 2018 07:46:00 -0800 (PST)
Received: by trail.lhotka.name (Postfix, from userid 109) id 710C11820412; Tue, 6 Mar 2018 16:45:38 +0100 (CET)
Received: from localhost (unknown [89.24.57.191]) by trail.lhotka.name (Postfix) with ESMTPSA id 1A8AD182040D; Tue, 6 Mar 2018 16:45:37 +0100 (CET)
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
In-Reply-To: <20180305161745.jvv2q3bswsf2t5ju@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> <1520266329.7198.60.camel@nic.cz> <20180305161745.jvv2q3bswsf2t5ju@elstar.local>
Date: Tue, 06 Mar 2018 16:45:57 +0100
Message-ID: <874llt2one.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/cYjIiXphZzj6OQ_zy8jm7q1pQHc>
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: Tue, 06 Mar 2018 15:46:09 -0000

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> writes:

> On Mon, Mar 05, 2018 at 05:12:09PM +0100, Ladislav Lhotka wrote:
>> 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.
>>
>
> A server has to list _all_ deviation modules and I thought this takes
> care of things. The reason for having this list is that a client
> interested in say ietf-interfaces can directly find the modules that
> contain deviations affecting ietf-interfaces. Hence a client has to
> trust this list to be complete, i.e., the server has to report _all_
> deviation modules. If you still feel something is missing, perhaps it
> helps if you propose concrete text.

The server can include deviation modules in the YLbis "module" list. Now, the
question is whether this is enough, no matter what the "deviation"
leaf-lists say. It makes no sense to propose any text before we agree on
the answer to this question.

Note that one module can possibly include deviations for multiple target
modules. An implementor may then decide to apply deviations only to some
modules, and this can be effectively done through the "deviation"
leaf-lists.

Lada

>
> /js
>
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>

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