Re: [netmod] [Netconf] LC on YANG Library (bis)

Alexander Clemm <alexander.clemm@huawei.com> Fri, 16 February 2018 01:27 UTC

Return-Path: <alexander.clemm@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 2725A126DED; Thu, 15 Feb 2018 17:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.231
X-Spam-Level:
X-Spam-Status: No, score=-4.231 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 u46YQ1xoOIWa; Thu, 15 Feb 2018 17:27:16 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 6F6F5126CD8; Thu, 15 Feb 2018 17:27:16 -0800 (PST)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 265867ADA3E; Fri, 16 Feb 2018 01:27:13 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.361.1; Fri, 16 Feb 2018 01:27:14 +0000
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.168]) by SJCEML702-CHM.china.huawei.com ([169.254.4.179]) with mapi id 14.03.0382.000; Thu, 15 Feb 2018 17:27:07 -0800
From: Alexander Clemm <alexander.clemm@huawei.com>
To: Kent Watsen <kwatsen@juniper.net>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: NETCONF WG <netconf@ietf.org>, NETMOD WG <netmod@ietf.org>
Thread-Topic: [Netconf] [netmod] LC on YANG Library (bis)
Thread-Index: AQHTpnTc9+x4PHWQskiS0bFD5BSAGaOmPJ8w
Date: Fri, 16 Feb 2018 01:27:06 +0000
Message-ID: <644DA50AFA8C314EA9BDDAC83BD38A2E0EAE915F@sjceml521-mbs.china.huawei.com>
References: <F10CE657-FC6B-491B-A8DF-0CFEE98B863C@gmail.com> <644DA50AFA8C314EA9BDDAC83BD38A2E0EAE81CB@sjceml521-mbs.china.huawei.com> <20180213194821.cwbwwmy7bqhvkfsd@elstar.local> <644DA50AFA8C314EA9BDDAC83BD38A2E0EAE8224@sjceml521-mbs.china.huawei.com> <C3087D63-0C35-4828-8A04-CD2505CCE821@juniper.net>
In-Reply-To: <C3087D63-0C35-4828-8A04-CD2505CCE821@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.209.216.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/7was73gYsrUk4ETKCQ4-Qito73E>
Subject: Re: [netmod] [Netconf] LC on YANG Library (bis)
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: Fri, 16 Feb 2018 01:27:19 -0000

Hi Kent,

yes, it wouldn't have to be in this document.  But I do think a solution for this is clearly needed, and YANG library (or augmentation to it) is the best way to put it.  

I wasn't planning to put out an I-D on this myself, but can put it on my to-do list (and will be happy to contribute if someone wants to take the lead).  

--- Alex

> -----Original Message-----
> From: Kent Watsen [mailto:kwatsen@juniper.net]
> Sent: Thursday, February 15, 2018 7:51 AM
> To: Alexander Clemm <alexander.clemm@huawei.com>om>; Juergen
> Schoenwaelder <j.schoenwaelder@jacobs-university.de>
> Cc: NETCONF WG <netconf@ietf.org>rg>; NETMOD WG <netmod@ietf.org>
> Subject: Re: [Netconf] [netmod] LC on YANG Library (bis)
> 
> Alex,
> 
> What you want makes sense to me.  How about putting it into an I-D that
> augments the yang library bis?  It doesn't have to be in this document, right?
> 
> Kent
> 
> ===== original message =====
> 
> Well, we need a general solution for that.  YANG-push is just one use case.  There
> are other cases where there will be "metadata" (that does not pertain to instance
> data)  and capabilities that clients want to discover.  YANG library (in itself
> providing "metadata" about what a server supports and is capable of) is an
> excellent place to maintain this information.  It also provides the opportunity to
> be systemic about it, as opposed to requiring everyone to define their own little
> custom extensions.
> --- Alex
> 
> > -----Original Message-----
> > From: Juergen Schoenwaelder
> > [mailto:j.schoenwaelder@jacobs-university.de]
> > Sent: Tuesday, February 13, 2018 11:48 AM
> > To: Alexander Clemm <alexander.clemm@huawei.com>
> > Cc: Mahesh Jethanandani <mjethanandani@gmail.com>om>; NETCONF WG
> > <netconf@ietf.org>rg>; NETMOD WG <netmod@ietf.org>
> > Subject: Re: [netmod] [Netconf] LC on YANG Library (bis)
> >
> > Alexander,
> >
> > I disagree. This YANG Library is mandatory for all implementations;
> > what you talk about seems to concern only implementations that support
> > YANG push. Hence, this is an extension that should go in its own module.
> >
> > /js
> >
> > On Tue, Feb 13, 2018 at 07:38:31PM +0000, Alexander Clemm wrote:
> > > Hi,
> > >
> > > I have taken a look at this document.
> > >
> > > My main comment is that one aspect that is missing, that I believe
> > > should be
> > added, concerns the inclusion of certain metadata about the modules.
> > Specifically, in the context of YANG-Push we had a discussion about
> > being able to mark nodes that are notifiable on change.  This is just
> > one particular use case of a more general issue; in YANG-Push after
> > much debate the conclusion was for now to simply make implementors
> > aware of this issue and advise that a solution to this must be
> > provided, with the clear understanding that eventually a standard solution
> should be defined.
> > >
> > > Since the goal of YANG-Library is to allow clients to find out what
> > > is actually
> > supported on a given server, this is the right place to keep this
> > information.  One possible way to address this would be, for a given
> > module, to maintain a list of "meta-info", with a key "meta-tag", and
> > a list with references to the nodes to which the metadata applies.  In
> > the case of notifiable-on-change, you would have a list with one entry
> > "notifiable-on-change", and then the list with the node definitions to which this
> tag applies.
> > >
> > > Editorial nit:
> > > 2nd paragraph Introduction: informaton --> information
> > >
> > > Thanks
> > > --- Alex
> > >
> > > From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Mahesh
> > > Jethanandani
> > > Sent: Thursday, February 01, 2018 11:00 AM
> > > To: NETCONF WG <netconf@ietf.org>
> > > Cc: NETMOD WG <netmod@ietf.org>
> > > Subject: [Netconf] LC on YANG Library (bis)
> > >
> > > WG,
> > >
> > > The authors of rfc7895bis have indicated that they believe the
> > > document is
> > ready for LC[1].
> > >
> > > This starts a two week LC on the
> > > draft<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.iet
> > > f.org_html_draft-2Dietf-
> 2D&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-nd
> > >
> b3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=oAL
> b7L
> > >
> KrUkKDsJ06VIM3Anx_iD05BkmxjaM0TZF1heA&s=NaY8R9DBhInZQAxL35_KjFze
> YHfy
> > > TOVJLnMHAKGeKF0&e=
> > netconf-rfc7895bis-04>. The LC will end on February 15.
> > >
> > > Please send your comments on this thread. Reviews of the document,
> > > and
> > statement of support are particularly helpful to the authors. If you
> > have concerns about the document, please state those too.
> > >
> > > Authors please indicate if you are aware of any IPR on the document.
> > >
> > > Thanks.
> > >
> > > [1]
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_ma
> > > il-
> 2Darchive_web_netconf_current_msg13980.html&d=DwICAg&c=HAkYuh63rs
> > > uhr6Scbfh0UjBXeMK-
> ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGT
> > >
> vjISlaJdcZo&m=oALb7LKrUkKDsJ06VIM3Anx_iD05BkmxjaM0TZF1heA&s=Qm6
> U9CIp
> > > DHS0jqUnGGZl8X05qeA_VvMyyuOtwDHBf1M&e=
> > >
> > > Mahesh & Kent
> > >
> >
> > > _______________________________________________
> > > netmod mailing list
> > > netmod@ietf.org
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_ma
> > > ilman_listinfo_netmod&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-
> ndb3voD
> > >
> TXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=oALb7LKr
> UkK
> > > DsJ06VIM3Anx_iD05BkmxjaM0TZF1heA&s=GPdqlio_2laQl93jobGXgXOs-
> WpouxE1W
> > > 4MeGxvh558&e=
> >
> >
> > --
> > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> > Fax:   +49 421 200 3103
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.jacobs-
> 2Duniversity.de_&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-
> ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=o
> ALb7LKrUkKDsJ06VIM3Anx_iD05BkmxjaM0TZF1heA&s=z9V8kyto9EgyGp3JswA
> 2QbJBSQd3eczfciztcC1gNt4&e=>
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_netconf&d=DwICAg&c=HAkYuh63rsuhr6S
> cbfh0UjBXeMK-
> ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=o
> ALb7LKrUkKDsJ06VIM3Anx_iD05BkmxjaM0TZF1heA&s=j9edlpIGbuEeS7yMrV4i
> RWY7vvq0c2FqIemuHf17LLU&e=
>