Re: [netmod] Schema Mount Point Instance Yang Library Clarification

Rohit R Ranade <rohitrranade@huawei.com> Wed, 24 April 2019 08:52 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 E264812022E for <netmod@ietfa.amsl.com>; Wed, 24 Apr 2019 01:52:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 OJhCrs190whZ for <netmod@ietfa.amsl.com>; Wed, 24 Apr 2019 01:52:12 -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 97483120242 for <netmod@ietf.org>; Wed, 24 Apr 2019 01:52:12 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7FCE5C9891A2F1790A47; Wed, 24 Apr 2019 09:52:10 +0100 (IST)
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 24 Apr 2019 09:52:10 +0100
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 24 Apr 2019 09:52:10 +0100
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Wed, 24 Apr 2019 09:52:09 +0100
Received: from DGGEML530-MBS.china.huawei.com ([169.254.8.66]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0439.000; Wed, 24 Apr 2019 16:52:02 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: Ladislav Lhotka <lhotka@nic.cz>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Schema Mount Point Instance Yang Library Clarification
Thread-Index: AdT6VAX+3aUFgfdXRcC65yVox3OeTP//q0sA//9eTvA=
Date: Wed, 24 Apr 2019 08:52:02 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6BD49EF6@dggeml530-mbs.china.huawei.com>
References: <991B70D8B4112A4699D5C00DDBBF878A6BD49B90@dggeml530-mbs.china.huawei.com> <87pnpbq3p5.fsf@nic.cz>
In-Reply-To: <87pnpbq3p5.fsf@nic.cz>
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: 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/PU9C5ahNJz-8vSfa5Fi7I7KVRLw>
Subject: Re: [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 08:52:15 -0000

Hi Lada,

Thank you for your response. Please find inline.

-----Original Message-----
From: Ladislav Lhotka [mailto:lhotka@nic.cz] 
Sent: 24 April 2019 12:40
To: Rohit R Ranade <rohitrranade@huawei.com>om>; netmod@ietf.org
Subject: Re: [netmod] Schema Mount Point Instance Yang Library Clarification

Hi Rohit,

Rohit R Ranade <rohitrranade@huawei.com> writes:

> 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".

Yes, I think this is correct: the ietf-ospf module imports the ietf-interfaces module, so the latter has to be specified in the YANG library of the mounted schema with "import" conformance.

>
> 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 is wrong, parent-reference adds nothing to the schema, only to the accessible tree for XPath evaluations.
[Rohit R Ranade] So this needs to be corrected by an errata ?

Lada

> 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
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67