Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7895bis-05.txt
Martin Bjorklund <mbj@tail-f.com> Mon, 19 March 2018 18:01 UTC
Return-Path: <mbj@tail-f.com>
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 8579412E049 for <netconf@ietfa.amsl.com>; Mon, 19 Mar 2018 11:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 PIItQrcvQmCP for <netconf@ietfa.amsl.com>; Mon, 19 Mar 2018 11:01:30 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id EAE3E12D890 for <netconf@ietf.org>; Mon, 19 Mar 2018 11:01:29 -0700 (PDT)
Received: from localhost (dhcp-915e.meeting.ietf.org [31.133.145.94]) by mail.tail-f.com (Postfix) with ESMTPSA id 9FE661AE049B; Mon, 19 Mar 2018 19:01:28 +0100 (CET)
Date: Mon, 19 Mar 2018 17:54:59 +0000
Message-Id: <20180319.175459.2231651052021179303.mbj@tail-f.com>
To: j.schoenwaelder@jacobs-university.de
Cc: lhotka@nic.cz, rwilton@cisco.com, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20180305160104.2fn7v2cdrdl6f54f@elstar.local>
References: <d18163c2-be3f-3807-aa47-fdc9a1d17b40@cisco.com> <1520265051.7198.56.camel@nic.cz> <20180305160104.2fn7v2cdrdl6f54f@elstar.local>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/nfTy0eRaNzNLXkzV1uznj8HRpdw>
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, 19 Mar 2018 18:01:34 -0000
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> 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. But require-instance defaults to "true", so it is not needed. > > 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 Ok, this makese sense. /martin > > /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/> >
- [Netconf] I-D Action: draft-ietf-netconf-rfc7895b… internet-drafts
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Martin Bjorklund
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Mahesh Jethanandani
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Ladislav Lhotka
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Robert Wilton
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Ladislav Lhotka
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Juergen Schoenwaelder
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Ladislav Lhotka
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Juergen Schoenwaelder
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Ladislav Lhotka
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Juergen Schoenwaelder
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Martin Bjorklund
- Re: [Netconf] I-D Action: draft-ietf-netconf-rfc7… Ladislav Lhotka