Re: [netmod] Comments on draft-ietf-netmod-schema-mount-09

"Yemin (Amy)" <amy.yemin@huawei.com> Tue, 27 March 2018 03:48 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 17D0B126E64 for <netmod@ietfa.amsl.com>; Mon, 26 Mar 2018 20:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 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, 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 CedP20WJTNLg for <netmod@ietfa.amsl.com>; Mon, 26 Mar 2018 20:48:02 -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 6B1D2124D6C for <netmod@ietf.org>; Mon, 26 Mar 2018 20:48:02 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id D04AE5B9DBAD9 for <netmod@ietf.org>; Tue, 27 Mar 2018 04:47:58 +0100 (IST)
Received: from DGGEMA423-HUB.china.huawei.com (10.1.198.156) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 27 Mar 2018 04:47:59 +0100
Received: from DGGEMA521-MBS.china.huawei.com ([169.254.5.3]) by dggema423-hub.china.huawei.com ([10.1.198.156]) with mapi id 14.03.0361.001; Tue, 27 Mar 2018 11:47:56 +0800
From: "Yemin (Amy)" <amy.yemin@huawei.com>
To: "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
Date: Tue, 27 Mar 2018 03:47:56 +0000
Message-ID: <9C5FD3EFA72E1740A3D41BADDE0B461FCEFE66B2@dggema521-mbs.china.huawei.com>
References: <20180326131751.28bgdvrf8kokc4k4@webmail.eurecom.fr>
In-Reply-To: <20180326131751.28bgdvrf8kokc4k4@webmail.eurecom.fr>
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/vNS--fLiQAd6nEMXamAYawyVU5A>
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: Tue, 27 Mar 2018 03:48:05 -0000

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. 

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?

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