[netmod] Schema Mount Yang Library Update

Rohit R Ranade <rohitrranade@huawei.com> Fri, 28 December 2018 04:07 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 77AA2128B14 for <netmod@ietfa.amsl.com>; Thu, 27 Dec 2018 20:07:35 -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 KngNlOELcYh6 for <netmod@ietfa.amsl.com>; Thu, 27 Dec 2018 20:07:33 -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 AEFEE12870E for <netmod@ietf.org>; Thu, 27 Dec 2018 20:07:33 -0800 (PST)
Received: from lhreml707-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 4B0F5369BBA5C for <netmod@ietf.org>; Fri, 28 Dec 2018 04:07:29 +0000 (GMT)
Received: from DGGEML404-HUB.china.huawei.com ( by lhreml707-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 28 Dec 2018 04:07:30 +0000
Received: from DGGEML530-MBS.china.huawei.com ([]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0415.000; Fri, 28 Dec 2018 12:07:09 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: Schema Mount Yang Library Update
Thread-Index: AdSeYUFYxAmOUSMrRlSaqc+d9z9IXA==
Date: Fri, 28 Dec 2018 04:07:09 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6BCBB04A@dggeml530-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_991B70D8B4112A4699D5C00DDBBF878A6BCBB04Adggeml530mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/CtcxBFz7UV2L1HeIicie26tDKoI>
Subject: [netmod] Schema Mount Yang Library Update
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: Fri, 28 Dec 2018 04:07:36 -0000

Hi All,

For the shared-schema type, the draft mentions "all instances of the same mount point MUST have the same YANG library content identifier".

I think to achieve above condition, most vendors will plan to have only one YANG library instance for that mount-point.

If use multiple instances for Yang library, it is possible that the algorithm may generate a new content identifier for same data as per below statement in Yang library 1.1 draft:

"There is no requirement that the same information always results in the same "content-id" value."

If use single instance of Yang library, when a YANG library update happens, for which mount-point instance should a YANG library update notification be sent ?
What is the guideline for the implementers of this draft regarding this point?

With Regards,