[netmod] Schema Mount Point Instance Yang Library Clarification

Rohit R Ranade <rohitrranade@huawei.com> Wed, 24 April 2019 04:18 UTC

Return-Path: <rohitrranade@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 A81BB120133 for <netmod@ietfa.amsl.com>; Tue, 23 Apr 2019 21:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 ZzSQ0ysYaj6A for <netmod@ietfa.amsl.com>; Tue, 23 Apr 2019 21:18:22 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 81439120075 for <netmod@ietf.org>; Tue, 23 Apr 2019 21:18:22 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7D5A15C1A47826199735 for <netmod@ietf.org>; Wed, 24 Apr 2019 05:18:20 +0100 (IST)
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 24 Apr 2019 05:18:19 +0100
Received: from DGGEML530-MBS.china.huawei.com ([169.254.8.66]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0439.000; Wed, 24 Apr 2019 12:18:07 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: Schema Mount Point Instance Yang Library Clarification
Thread-Index: AdT6VAX+3aUFgfdXRcC65yVox3OeTA==
Date: Wed, 24 Apr 2019 04:18:07 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6BD49B90@dggeml530-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.150.121]
Content-Type: multipart/alternative; boundary="_000_991B70D8B4112A4699D5C00DDBBF878A6BD49B90dggeml530mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Bo2jolONe5LwnZDMk2UIg1EYfOg>
Subject: [netmod] Schema Mount Point Instance Yang Library 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, 24 Apr 2019 04:18:24 -0000

Hi All,

In https://tools.ietf.org/html/rfc8528#section-4, a below example is shown for parent references,

"
     +--rw interfaces
     |  +--rw interface* [name]
     |     ...
     +--rw network-instances
        +--rw network-instance* [name]
           +--rw name
           +--mp root
              +--rw routing
                 ...

"
Consider a simple case where the ietf-routing module and ietf-ospf module are mounted as part of network-instance of a L3vpn. Also consider that for ietf-ospf , it has some interface configuration as shown below.
This needs parent-references , since the interface configuration is in the parent data-tree of mount-point.

module: ietf-ospf
   augment /rt:routing/rt:control-plane-protocols/
            rt:control-plane-protocol:
     +--rw ospf
        +--rw areas
        |  +--rw area* [area-id]
        |     +--rw interfaces
        |        +--rw interface* [name]
        |           +--rw name     if:interface-ref

Since the YANG library "under" the mount-point-instance has to be complete, I was thinking that the YANG library under the mount-point will have the "ietf-interfaces" YANG module. Since the "ietf-interfaces" module under the network-instance mount-point may not make sense,  the "conformance-type" for it will be "import" instead of "implement".

Another statement though confuses me , where the argument of  "presence" statement of "shared-schema",
""The mounted schema together with the 'parent-reference'
                make up the schema for this mount point.";"  ==> Does this mean that YANG Library of the mount-point-instance should not have "ietf-interfaces" in this case ? This may make the client work complicated.


With Regards,
Rohit