Re: [netmod] 答复: (no subject)

Martin Bjorklund <mbj@tail-f.com> Tue, 07 November 2017 13:25 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 D968E13FB74 for <netmod@ietfa.amsl.com>; Tue, 7 Nov 2017 05:25:01 -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 imX17REYe1UC for <netmod@ietfa.amsl.com>; Tue, 7 Nov 2017 05:25:00 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB5713FAF3 for <netmod@ietf.org>; Tue, 7 Nov 2017 05:25:00 -0800 (PST)
Received: from localhost (unknown [173.38.220.60]) by mail.tail-f.com (Postfix) with ESMTPSA id 3ABCA1AE02BB; Tue, 7 Nov 2017 14:24:59 +0100 (CET)
Date: Tue, 07 Nov 2017 14:23:35 +0100
Message-Id: <20171107.142335.998654658313885657.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: <90D4AD4FAC4AD946A3593922318387CC9C227381@nkgeml513-mbs.china.huawei.com>
References: <90D4AD4FAC4AD946A3593922318387CC9C2272D9@nkgeml513-mbs.china.huawei.com> <20171107.130801.1219859225033022699.mbj@tail-f.com> <90D4AD4FAC4AD946A3593922318387CC9C227381@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="utf-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/14J4orwm4gzfRihj2UZhZqtT6w4>
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 13:25:02 -0000

Zhuzhiguo <zhuzhiguo@huawei.com> wrote:
> Hi Martin,
> Thank you for your reply.
> 
> If module-A and modul-B are 1.0 modules, are they should be presented
> in <hello>?

Yes, but note that if B is present in <hello>, a client will think
that all nodes in B are implemented.  This is why yang-library has the
'conformance' leaf.


/martin

> -----邮件原件-----
> 发件人: Martin Bjorklund [mailto:mbj@tail-f.com] 
> 发送时间: 2017年11月7日 20:08
> 收件人: Zhuzhiguo <zhuzhiguo@huawei.com>
> 抄送: netmod@ietf.org; Liquan (Liquan, NOS CSD) <liquan92@huawei.com>
> 主题: Re: [netmod] (no subject)
> 
> 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.
> -----////all these augments are deviated
> 
> > This way seems work, but some teammates think it may not comply with 
> > RFC.
> 
> Why wouldn't it?
> ------////client can get module-B, but can't do any operation on module-B
> 
> > 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