[netmod] Schema Mount Terminology Clarification

Rohit R Ranade <rohitrranade@huawei.com> Wed, 12 December 2018 10:12 UTC

Return-Path: <rohitrranade@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 2B7E412777C for <netmod@ietfa.amsl.com>; Wed, 12 Dec 2018 02:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Wp8qqW-j_M0j for <netmod@ietfa.amsl.com>; Wed, 12 Dec 2018 02:12:47 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com []) (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 479AD12F18C for <netmod@ietf.org>; Wed, 12 Dec 2018 02:12:47 -0800 (PST)
Received: from lhreml705-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 387478179EFFC for <netmod@ietf.org>; Wed, 12 Dec 2018 10:12:41 +0000 (GMT)
Received: from DGGEML423-HUB.china.huawei.com ( by lhreml705-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 12 Dec 2018 10:12:42 +0000
Received: from DGGEML510-MBX.china.huawei.com ([]) by dggeml423-hub.china.huawei.com ([]) with mapi id 14.03.0415.000; Wed, 12 Dec 2018 18:12:29 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: Schema Mount Terminology Clarification
Thread-Index: AdSSAHJMd79djmViQCOmlgelvyOoWA==
Date: Wed, 12 Dec 2018 10:12:29 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6BCA7DE4@dggeml510-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_991B70D8B4112A4699D5C00DDBBF878A6BCA7DE4dggeml510mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/UUTX_PMeDBh-Zo8oE06QqQc_2Wo>
Subject: [netmod] Schema Mount Terminology Clarification
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Dec 2018 10:12:49 -0000


1.       The term "data model" is used many times in this document, but it is not defined in this document but defined in RFC 7950. I think it should be added under the "following terms are defined in [RFC7950]" part.

2.       The term "This document allows mounting of complete data models only" is used in Section 1. I think here "complete data model" should be replaced by "schema tree" as it is more precise?

a)         RFC 7950 , schema tree: The definition hierarchy specified within a module

b)   RFC7950, data model: A data model describes how data is represented and accessed

3.       The "data model" term is used many times Eg: "LNE's data model", "share the same data model", "NI data model", "mounting one data model consisting of any number of YANG modules"   etc, sometimes using the term "data model" as a collection of YANG modules and sometimes for a single Yang module. I feel, where-ever we refer to single Module, we need to use the term "schema tree" and when we refer to collection of YANG modules, we can refer to as Data Model.. Please provide your opinions.

With Regards,