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

Alexander Clemm <> Tue, 13 February 2018 19:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 980CB12D893; Tue, 13 Feb 2018 11:38:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.229
X-Spam-Status: No, score=-4.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8bgyk4uxZmCy; Tue, 13 Feb 2018 11:38:39 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5129F1241F3; Tue, 13 Feb 2018 11:38:39 -0800 (PST)
Received: from (unknown []) by Forcepoint Email with ESMTP id E88002B5D5365; Tue, 13 Feb 2018 19:38:35 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 13 Feb 2018 19:38:37 +0000
Received: from ([]) by ([]) with mapi id 14.03.0382.000; Tue, 13 Feb 2018 11:38:31 -0800
From: Alexander Clemm <>
To: Mahesh Jethanandani <>, NETCONF WG <>
Thread-Topic: [Netconf] LC on YANG Library (bis)
Thread-Index: AQHTm47nGQKkuQuITEyr+4DYs4MJdKOiyLPw
Date: Tue, 13 Feb 2018 19:38:31 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_644DA50AFA8C314EA9BDDAC83BD38A2E0EAE81CBsjceml521mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netmod] [Netconf] LC on YANG Library (bis)
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 13 Feb 2018 19:38:41 -0000


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

--- Alex

From: Netconf [] On Behalf Of Mahesh Jethanandani
Sent: Thursday, February 01, 2018 11:00 AM
Subject: [Netconf] LC on YANG Library (bis)


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



Mahesh & Kent