Re: [netmod] (no subject)
Martin Bjorklund <mbj@tail-f.com> Tue, 07 November 2017 12:09 UTC
Return-Path: <mbj@tail-f.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 30A0913FE36 for <netmod@ietfa.amsl.com>; Tue, 7 Nov 2017 04:09:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ztPyf3AYi8jo for <netmod@ietfa.amsl.com>; Tue, 7 Nov 2017 04:09:29 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 3045313FC44 for <netmod@ietf.org>; Tue, 7 Nov 2017 04:09:27 -0800 (PST)
Received: from localhost (unknown [173.38.220.60]) by mail.tail-f.com (Postfix) with ESMTPSA id 6378B1AE02BB; Tue, 7 Nov 2017 13:09:25 +0100 (CET)
Date: Tue, 07 Nov 2017 13:08:01 +0100
Message-Id: <20171107.130801.1219859225033022699.mbj@tail-f.com>
To: zhuzhiguo@huawei.com
Cc: netmod@ietf.org, liquan92@huawei.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <90D4AD4FAC4AD946A3593922318387CC9C2272D9@nkgeml513-mbs.china.huawei.com>
References: <90D4AD4FAC4AD946A3593922318387CC9C2272D9@nkgeml513-mbs.china.huawei.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/zh0DTxtZM2yKAodTX-U-9nF-Tpk>
Subject: Re: [netmod] (no subject)
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, 07 Nov 2017 12:09:30 -0000
Zhuzhiguo <zhuzhiguo@huawei.com> wrote:
> Hi,
>
> I have one question about how to implement YANG module that import
> other-module which is NOT be implemented?
>
> For example, module-A import module-B, but any nodes that depend on B
> are not-supported
>
> Module A {
> import module-B;
> }
>
> There are two way to mark module-B is not really in use:
>
> Option-1: refer conformance-type in RFC 7895 (ietf-yang-library), mark
> module-A as "implement", module-B is "import"
This is correct. But if A augments some node in B, you have to
implement B as well.
> This way seems work, but some teammates think it may not comply with
> RFC.
Why wouldn't it?
> And we also argue about what module-B should be presented in
> <hello>
>
> <capabilities>
> <capability>module-A</capability>
> <capability>module-B</capability> ===>should any "import" module MUST
> be sent by server to client also?
> <capabilities>
Assuming A and B are YANG 1.1 modules, they should NOT be listed in
<hello> - yang-library is used instead.
> Option-2: mark module-B as "implement" also, but mark all-nodes as
> deviated
> This way seems work also, but it will cause NETCONF-client and
> NETCONF-server load module that have NO node that can be accessed
There's no reason to do this.
/martin
- [netmod] (no subject) Zhuzhiguo
- Re: [netmod] (no subject) Martin Bjorklund
- [netmod] 答复: (no subject) Zhuzhiguo
- Re: [netmod] 答复: (no subject) Martin Bjorklund