Re: [netmod] *one* week 2nd WG Last Call: draft-ietf-netmod-revised-datastores-07
Ladislav Lhotka <lhotka@nic.cz> Thu, 21 December 2017 16:03 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 CE5D9126D74; Thu, 21 Dec 2017 08:03:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level:
X-Spam-Status: No, score=-7.009 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, 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 K6l5ab-q8uxs; Thu, 21 Dec 2017 08:03:23 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 55DB1126CD6; Thu, 21 Dec 2017 08:03:23 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:c492:ff:fef1:fb2d]) by mail.nic.cz (Postfix) with ESMTPSA id 98C9863EFA; Thu, 21 Dec 2017 17:03:21 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1513872201; bh=L13vZrfFG67Y+qzTtU59ejT5F/7OV8/eOEEQRV8eGN4=; h=From:To:Date; b=erVtnoUJ5Nl+6NahOoCtkPx0PASvxE1X1fNoxhhEZ9aS48sR9K0u8Vkdh9WbVhllE 2hFrgRcKKzVBIldfNzAqnMUnajYzaC5a0qxEPdXCABVZFfJ/zlU3mWKVKZra9N05cr 8xuGVS1/Crc3p4PZT+Xf5uS0aYUVVh9qaafZrKZs=
Message-ID: <1513872201.18003.1.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: andy@yumaworks.com, netmod-chairs@ietf.org, netmod@ietf.org
Date: Thu, 21 Dec 2017 17:03:21 +0100
In-Reply-To: <20171221.142505.234244118393393232.mbj@tail-f.com>
References: <CABCOCHSPxEG+eXx5arHhMbxNMxgdCRKoe25Rv3-qXJ0QmVRMZw@mail.gmail.com> <20171219.212514.769253397796153677.mbj@tail-f.com> <87d138kz4k.fsf@nic.cz> <20171221.142505.234244118393393232.mbj@tail-f.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.3
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/u-TqwRVfLYOVWZuc7K1-1cFwwaw>
Subject: Re: [netmod] *one* week 2nd WG Last Call: draft-ietf-netmod-revised-datastores-07
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: Thu, 21 Dec 2017 16:03:27 -0000
On Thu, 2017-12-21 at 14:25 +0100, Martin Bjorklund wrote: > Ladislav Lhotka <lhotka@nic.cz> wrote: > > Martin Bjorklund <mbj@tail-f.com> writes: > > > > > Hi Andy, > > > > > > Andy Bierman <andy@yumaworks.com> wrote: > > >> Hi, > > >> > > >> I have reviewed draft-07 and my previous comments about NMDA have been > > >> addressed. > > >> > > >> This might be the most important sentence in the draft: > > >> > > >> sec. 5.3 > > >> > > >> The datastore schema for <operational> MUST be a superset of the > > >> combined datastore schema used in all configuration datastores except > > >> that YANG nodes supported in a configuration datastore MAY be omitted > > >> from <operational> if a server is not able to accurately report them. > > >> > > >> The MUST implies that there is no need to design a YANG library that can > > >> support > > >> an implementation that violates this MUST (i.e., 1 schema tree for the > > >> super-set) > > >> > > >> The MAY is troublesome because it completely contradicts the conformance > > >> expressed > > >> in each YANG module supported by the server. Any data node without any > > >> if-feature-stmts is mandatory to implement. > > > > > > This is required for transition purposes; a server that wants to > > > implement <operational> should not have to implement all modules at > > > once (as applied config). > > > > > >> What about config=false subtrees within a config=true subtree? > > >> Can they be omitted from <operational> as well, or does the draft just > > >> intend to > > >> omit the operational value of config=true nodes? Should be specific. > > > > > > The text says "nodes supported in a configuration datastore MAY be > > > omitted from <operational>". So it is implicit that it only applies > > > to config true nodes (since config false cannot be supported in a > > > config ds). How about: > > > > > > OLD: > > > > > > The datastore schema for <operational> MUST be a superset of the > > > combined datastore schema used in all configuration datastores except > > > that YANG nodes supported in a configuration datastore MAY be omitted > > > from <operational> if a server is not able to accurately report them. > > > > > > NEW: > > > > > > The datastore schema for <operational> MUST be a superset of the > > > combined datastore schema used in all configuration datastores > > > except that YANG "config true" nodes supported in a configuration > > > > If this is about schema or data nodes, I suggest to state it > > explicitly: > > > > ... "config true" schema/data nodes ... > > Yes, the new text uses "configuration data nodes". > > > > datastore MAY be omitted from <operational> if a server is not > > > able to accurately report them. > > > > > > > > >> Perhaps this draft does not need the MAY half of the sentence at all. > > >> The YANG library can specify that it is for conformance-reporting, not > > >> conformance-defining. > > > > > > I think we should keep the MAY, since the YANG library has to be > > > designed to support this case. > > > > Shouldn't the server add corresponding deviations to the schema for > > <operational> in this case? > > We wanted to explicitly support the case that a server doesn't (yet) > implement a given module with config nodes in operational. But maybe But with the new schema of YANG library, say Alt B, such a server can simply omit this module from the schema of <operational>, right? Lada > we should design for the future and remove the MAY half of the > sentence, as suggested above, and let such servers use deviations in > this case. > > > /martin > > > > > > > > Lada > > > > > > > > > > > /martin > > > > > > > > > > > > > > >> > > >> > > >> > > >> > > >> Andy > > >> > > >> > > >> On Mon, Dec 4, 2017 at 6:35 AM, Lou Berger <lberger@labn.net> wrote: > > >> > > >> > All, > > >> > > > >> > This starts a second working group last call on > > >> > draft-ietf-netmod-revised-datastores. > > >> > > > >> > As this is a 2nd LC that is focused on changes since the last LC, it > > >> > closes in *one* week. The working group last call ends on December 11. > > >> > Please send your comments to the netmod mailing list. > > >> > > > >> > At this point, we're most interested in verifying that previous > comments > > >> > are addressed since the last call on the -04 rev of the draft was held. > > >> > > > >> > A summary of changes can be found at > > >> > https://mailarchive.ietf.org/arch/msg/netmod/DWtD12bGkBZabEygRfiwZfcnUU > 4 > > >> > > > >> > A diff can be found at > > >> > https://tools.ietf.org/rfcdiff?difftype=--hwdiff&url1=draft-ietf-netmod > - > > >> > revised-datastores-04.txt&url2=draft-ietf-netmod-revised-datastores- > 07.txt > > >> > > > >> > Comments along the of: I have reviewed this version of the document and > it > > >> > addresses my previous comments would be particularly helpful. > > >> > > > >> > Thank you, > > >> > Netmod Chairs > > >> > > > >> > _______________________________________________ > > >> > netmod mailing list > > >> > netmod@ietf.org > > >> > https://www.ietf.org/mailman/listinfo/netmod > > >> > > > > > > > _______________________________________________ > > > netmod mailing list > > > netmod@ietf.org > > > https://www.ietf.org/mailman/listinfo/netmod > > > > -- > > Ladislav Lhotka > > Head, CZ.NIC Labs > > PGP Key ID: 0xB8F92B08A9F76C67 > > -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67
- [netmod] *one* week 2nd WG Last Call: draft-ietf-… Lou Berger
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Andy Bierman
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Lou Berger
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Lou Berger
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Martin Bjorklund
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Martin Bjorklund
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Andy Bierman
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Juergen Schoenwaelder
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Robert Wilton
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Lou Berger
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Juergen Schoenwaelder
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Lou Berger
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Ladislav Lhotka
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Martin Bjorklund
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Ladislav Lhotka
- Re: [netmod] *one* week 2nd WG Last Call: draft-i… Martin Bjorklund