Re: [netmod] [Netconf] Alternative YANG library structure for 7895bis

Vladimir Vassilev <vladimir@transpacket.com> Wed, 15 November 2017 13:44 UTC

Return-Path: <vladimir@transpacket.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 03C7D124B17 for <netmod@ietfa.amsl.com>; Wed, 15 Nov 2017 05:44:10 -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 EAkjlfXP9bwa for <netmod@ietfa.amsl.com>; Wed, 15 Nov 2017 05:44:07 -0800 (PST)
Received: from mail.transpacket.com (s91205186171.blix.com [91.205.186.171]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3354C1243F3 for <netmod@ietf.org>; Wed, 15 Nov 2017 05:44:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.transpacket.com (Postfix) with ESMTP id 7105214064CC; Wed, 15 Nov 2017 14:44:05 +0100 (CET)
Received: from mail.transpacket.com ([127.0.0.1]) by localhost (mail.transpacket.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id JLLzmvYxtMVP; Wed, 15 Nov 2017 14:44:05 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by mail.transpacket.com (Postfix) with ESMTP id 45AD3140697A; Wed, 15 Nov 2017 14:44:05 +0100 (CET)
Received: from mail.transpacket.com ([127.0.0.1]) by localhost (mail.transpacket.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id jQms0GryyNsW; Wed, 15 Nov 2017 14:44:05 +0100 (CET)
Received: from [192.168.209.122] (s1853520235.blix.com [185.35.202.35]) by mail.transpacket.com (Postfix) with ESMTPSA id 132BE1406977; Wed, 15 Nov 2017 14:44:05 +0100 (CET)
To: Martin Bjorklund <mbj@tail-f.com>, "netmod@ietf.org" <netmod@ietf.org>
References: <cdc778b5-76f3-f0b2-71e3-1df5da49a2e3@transpacket.com> <47e8298b-20bb-fdbb-4181-9609a489a312@cisco.com> <3706518a-af15-1427-2660-f357824132f9@transpacket.com> <20171115.132011.1461354023659143851.mbj@tail-f.com>
From: Vladimir Vassilev <vladimir@transpacket.com>
Message-ID: <6e7804f1-82b2-3d93-1044-c98a9550f736@transpacket.com>
Date: Wed, 15 Nov 2017 14:44:04 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <20171115.132011.1461354023659143851.mbj@tail-f.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: nb
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/fxFUdGxUhWuoRZdXL_kmt-u8368>
Subject: Re: [netmod] [Netconf] Alternative YANG library structure for 7895bis
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 15 Nov 2017 13:44:10 -0000


On 11/15/2017 01:20 PM, Martin Bjorklund wrote:
> Vladimir Vassilev <vladimir@transpacket.com> wrote:
>
> [...]
>
>> It is clear that datastores with non-identical models can not be
>> supported with yang-library:1.0. However for the many usecases that do
>> not require the complexity of having different datastore models
>> (variation of the set of modules and the relevant deviations e.g. more
>> complex datastore centric conformance model) one can implement NMDA
>> with yang-library:1.0.
>>
>> My initial proposal was a change to draft-ietf-netconf-nmda-netconf-01
>> sec. 2.4. 'YANG Library Capability' to allow that usecase:
>>
>> OLD:
>> Support for NMDA requires the server to implement at least revision
>> 201X-XX-XX of the "ietf-yang-library"
>> ...
>> NEW:
>> Support for NMDA with datastores with non-identical models requires
>> the server to implement at least revision 201X-XX-XX of the
>> "ietf-yang-library"
> But that would imply that we keep two versions of ietf-yang-library
> around, and "current".
>
> Also note that the new proposed version is very similar in structure
> to the old yang library.  And if the server implements "identicial
> models", then the "not-implemented-in" will be empty, and so the
> contents of yang-library 1.1 is more or less the same as yang-library
> 1.0.
I aggree with what you say. My point is that the upgrade to 
yang-library:1.1 can come later then the upgrade to NMDA ietf-interfaces 
<get-data> etc. I will implement yang-library:1.1 as soon as I find a 
single usecase that justifies the work needed. At the moment I only have 
motivation to implement <get-data> and migrate to the NMDA modules and 
the only issue with that plan is the text in 
draft-ietf-netconf-nmda-netconf-01 sec. 2.4. 'YANG Library Capability'.

Following my gut feeling I would rather wait to see if yang-library:1.2 
is not coming up before I am done with the process of migrating to NMDA 
with identical datastore models. A reasonable concern taking into 
account yang-library:1.0 is about to be obsoleted so soon after the 
publication of rfc7895 because of a feature (introduction of 
datastore-centric conformance model) that has no value for me at the 
moment unlike the feature (unification of configuration and state trees) 
introduced with NMDA.

That said there might be a counter argument that the confusion of 
allowing NMDA implementations with both yang-library:1.0 and 
yang-library:1.1 is worse then forcing all NMDA applications to 
implement only yang-library:1.1. If this is so that should be stated 
clearly.

Vladimir

> /martin