Re: [netmod] Comments on draft-ietf-netmod-schema-mount-09
"Yemin (Amy)" <amy.yemin@huawei.com> Fri, 30 March 2018 02:47 UTC
Return-Path: <amy.yemin@huawei.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 72CAA12E868 for <netmod@ietfa.amsl.com>; Thu, 29 Mar 2018 19:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.212
X-Spam-Level:
X-Spam-Status: No, score=-4.212 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 7xlnGatPLUVg for <netmod@ietfa.amsl.com>; Thu, 29 Mar 2018 19:47:52 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 D951A12E059 for <netmod@ietf.org>; Thu, 29 Mar 2018 19:47:51 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id A725F3994C793 for <netmod@ietf.org>; Fri, 30 Mar 2018 03:47:47 +0100 (IST)
Received: from DGGEMA403-HUB.china.huawei.com (10.3.20.44) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 30 Mar 2018 03:47:48 +0100
Received: from DGGEMA521-MBS.china.huawei.com ([169.254.5.3]) by DGGEMA403-HUB.china.huawei.com ([10.3.20.44]) with mapi id 14.03.0361.001; Fri, 30 Mar 2018 10:47:42 +0800
From: "Yemin (Amy)" <amy.yemin@huawei.com>
To: Robert Wilton <rwilton@cisco.com>, "otilibil@eurecom.fr" <otilibil@eurecom.fr>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Comments on draft-ietf-netmod-schema-mount-09
Thread-Index: AQHTxPQs2rTyFU6SUUilNgTzKCTcPKPjb8lQ///uQICAAzczkP//3C8AgAGlf9A=
Date: Fri, 30 Mar 2018 02:47:42 +0000
Message-ID: <9C5FD3EFA72E1740A3D41BADDE0B461FCEFE7536@dggema521-mbs.china.huawei.com>
References: <20180326131751.28bgdvrf8kokc4k4@webmail.eurecom.fr> <9C5FD3EFA72E1740A3D41BADDE0B461FCEFE66B2@dggema521-mbs.china.huawei.com> <c1f0a35e-2733-613d-97a4-7710799b2ed5@cisco.com> <9C5FD3EFA72E1740A3D41BADDE0B461FCEFE7250@dggema521-mbs.china.huawei.com> <b4b30638-6986-3cec-cab8-e67c1826df1d@cisco.com>
In-Reply-To: <b4b30638-6986-3cec-cab8-e67c1826df1d@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.169.30.234]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/o0kLrNP73OzNBrw6FNUUXzSNq6E>
Subject: Re: [netmod] Comments on draft-ietf-netmod-schema-mount-09
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: Fri, 30 Mar 2018 02:47:54 -0000
Hi, -----Original Message----- From: Robert Wilton [mailto:rwilton@cisco.com] Sent: Thursday, March 29, 2018 5:32 PM To: Yemin (Amy) <amy.yemin@huawei.com>; otilibil@eurecom.fr; netmod@ietf.org Subject: Re: [netmod] Comments on draft-ietf-netmod-schema-mount-09 Hi Amy, On 29/03/2018 08:09, Yemin (Amy) wrote: > Hi Rob, > > Thanks for clarification. > By using the deviation, I can remove the containers I don't need, and I could also remove some data nodes within the container, right? Yes. > > BTW, your reply provides a good guideline. Is it possible to include those text into the draft? I'll leave this to the authors to decide. A more realistic example may be helpful given that mine was slightly contrived. [Amy] A concrete example would be even better! Thanks, Rob > > BR, > Amy > -----Original Message----- > From: Robert Wilton [mailto:rwilton@cisco.com] > Sent: Tuesday, March 27, 2018 6:33 PM > To: Yemin (Amy) <amy.yemin@huawei.com>; otilibil@eurecom.fr; > netmod@ietf.org > Subject: Re: [netmod] Comments on draft-ietf-netmod-schema-mount-09 > > Hi Amy, > > > On 27/03/2018 04:47, Yemin (Amy) wrote: >> Hi all, >> >> I also have a question/comment regarding this draft, maybe if it's discussed already. >> >> If there a model A, which I would like to use just part of model A in another model B, what should I do? >> The draft states that "This document allows mounting of complete data models only. Other specifications may extend this model by defining additional mechanisms such as mounting sub-hierarchies of a module." >> It seems that the current schema mount doesn't support such usage. > That is correct. > >> >> >> Then I'm thinking that using deviation to create a new sub-module A', then mount the sub-module A' in model B. >> Will it be a possible way out? > If you have a module A, then you could create another module, A-deviations, that used deviation delete statements to remove parts of A's schema. > > Then a server could mount both modules A and A-deviations, hence excluding parts of module A at the mount point. > > However, this approach would not allow you to only mount a descendant subtree in A. E.g. You couldn't just directly mount the "interfaces/interface/statistics" container from RFC 8343, but you could mount the ietf-interfaces module and then deviate delete all nodes except for the interfaces/interface/statistics container. > > Thanks, > Rob > > >> BR, >> Amy >> -----Original Message----- >> From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of >> otilibil@eurecom.fr >> Sent: Monday, March 26, 2018 7:18 PM >> To: netmod@ietf.org >> Subject: [netmod] Comments on draft-ietf-netmod-schema-mount-09 >> >> Hi members, >> >> I comment on that draft: >> >> * Instead of "it is often necessary that an existing module (or a set >> of modules) is added to the data model starting at a non-root >> location", this would read better: "it is often necessary that an >> existing module (or a set of modules) be added to the data model at >> locations other than the root." (Section 1) >> >> * 'The "mount-point" statement MUST NOT be used in a YANG version 1 >> module' Why this documents keeps YANG 1 off from its scope? (Section >> 3.1) >> >> * 'Specifically, a server that doesn?t support the NMDA, MAY >> implement revision 2016-06-21 of "ietf-yang-library" [RFC7950] under >> a mount point' [RFC7895] defines "ietf-yang-library", not [RFC7950] >> (Section >> 6) >> >> * Why not "Tree Diagram" instead of "Data Model"? The wording has >> become a Best Practice (Section 8) >> >> * Idem, "This document...has the following diagram" captures better the Best Practice than "This document...has the following structure" >> (Section 8) >> >> * Same remark on restricting to YANG 1.1: "The ?mount-point? >> statement MUST NOT be used in a YANG version 1 module, neither >> explicitly nor via a ?uses? statement (description of the extension >> "mount-point") >> >> * Should this sentence refers only to [RFC6020]? "This document registers a YANG module in the YANG Module Names registry [RFC6020]" >> (Section 10) >> >> * The document cites /schema-mounts as "The schema defined by this >> state data provides detailed information about a server >> implementation may help an attacker identify the server capabilities >> and server implementations with known bugs" I think this section >> should warn also >> on: >> ** Section 2.1.2 and 4 of [RFC7895] (the list 'module' contains the leaf 'schema': from which anyone may retrieve a YANG module) >> ** Section 3 of [RFC6022] (it defines the RPC 'get-schema'; with which anyone may get a YANG module) >> ** and Section 5 of [RFC8341] (reminding administrators to set user rights accordingly, and giving their defaults values). >> >> Regards, >> Ariel >> >> [RFC6020] https://tools.ietf.org/html/rfc6020 >> [RFC7895] https://tools.ietf.org/html/rfc7895 >> [RFC7950] https://tools.ietf.org/html/rfc7950 >> [RFC8341] https://tools.ietf.org/html/rfc8341 >> >> >> --------------------------------------------------------------------- >> - >> --------- This message was sent using EURECOM Webmail: >> http://webmail.eurecom.fr >> >> _______________________________________________ >> 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 >> . >>
- [netmod] Comments on draft-ietf-netmod-schema-mou… otilibil
- Re: [netmod] Comments on draft-ietf-netmod-schema… Yemin (Amy)
- Re: [netmod] Comments on draft-ietf-netmod-schema… Robert Wilton
- Re: [netmod] Comments on draft-ietf-netmod-schema… Yemin (Amy)
- Re: [netmod] Comments on draft-ietf-netmod-schema… Robert Wilton
- Re: [netmod] Comments on draft-ietf-netmod-schema… Yemin (Amy)
- Re: [netmod] Comments on draft-ietf-netmod-schema… Martin Bjorklund
- Re: [netmod] Comments on draft-ietf-netmod-schema… otilibil