[netmod] YANG Packages

Robert Wilton <rwilton@cisco.com> Thu, 20 December 2018 17:44 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 7A7E6131165 for <netmod@ietfa.amsl.com>; Thu, 20 Dec 2018 09:44:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id h5P_TuWEXIZM for <netmod@ietfa.amsl.com>; Thu, 20 Dec 2018 09:44:40 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2382F13115E for <netmod@ietf.org>; Thu, 20 Dec 2018 09:44:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4724; q=dns/txt; s=iport; t=1545327880; x=1546537480; h=from:subject:to:message-id:date:mime-version; bh=B6HOq9kHRJdtZau4vPqP5p06dqbF6xgpJVvEYLOqFuA=; b=bpyFhGOpezBVscycvQRr0MKkOLNzpxbHbo+lSEIjVtNFS0VNdU/Dtj0K 4HXdkob5ATT9nnf+e6kxj6HFiAaUchLpJpFffIcDh8rWyYswY6Nx3pVXy URPQhwm8KZBKJ48LN+eOO+UaRcOQGOoFcNDKfm52eiBjkuMMcnOvZARI6 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CMAABo1Btc/xbLJq1lHAEBAQQBAQc?= =?us-ascii?q?EAQGBUwUBAQsBgQ2BXIEChCSIeIx8CJInhVuBew0jh1k2Bw0BAwEBAgEBAm0?= =?us-ascii?q?cAQuFZnU+Al8NCAEBF4MHAYIBD5hZjnSBLx+EIkA/hGEFjFaBQD+BOAyFfQI?= =?us-ascii?q?DAYFHgx6CVwKJd5dGCYcRik4GGIoJh1SJTYR7hEeGfoFNAy4ogS4zGggbFYM?= =?us-ascii?q?oixuFPz8DjxcBAQ?=
X-IronPort-AV: E=Sophos;i="5.56,378,1539648000"; d="scan'208,217";a="8942786"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Dec 2018 17:44:37 +0000
Received: from [] (dhcp-ensft1-uk-vla370-10-63-23-68.cisco.com []) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id wBKHibiY003228 for <netmod@ietf.org>; Thu, 20 Dec 2018 17:44:37 GMT
From: Robert Wilton <rwilton@cisco.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Message-ID: <38b2c418-d47d-0275-87b0-f5d004863dbe@cisco.com>
Date: Thu, 20 Dec 2018 17:44:37 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------EE2C0E20795031BAAA79A8DC"
Content-Language: en-US
X-Outbound-SMTP-Client:, dhcp-ensft1-uk-vla370-10-63-23-68.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/pgSClSaZ74VtEF4YW08MhfqB94o>
Subject: [netmod] YANG Packages
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: Thu, 20 Dec 2018 17:44:43 -0000


I've written up an ID for a potential solution for YANG packages using 
instance data:


    This document defines YANG packages, an organizational structure
    holding a set of related YANG modules, that can be used to simplify
    the conformance and sharing of YANG schema.  It describes how YANG
    instance data documents are used to define YANG packages, and how the
    YANG library information published by a server can be augmented with
    additional packaging related information.


Potentially this work may be of use as part of the YANG versioning 
design team work.  In addition, if the WG likes this approach of 
defining YANG packages, then it might also be useful to bind a schema to 
a YANG instance data document.

Some questions for members of the WG:

1) Do members of the WG agree that YANG packages is something that needs 
to be solved?

2) Is the approach in this draft of defining these as instance data 
documents a good starting point?

3) This approach augments YANG library-bis, reusing module-sets, but not 
replacing the way that modules are reported in YANG library-bis.  Is 
this the right approach?  This approach tries to allow module-sets to be 
reused for both schema and packages, but the YANG library-bis rules for 
combining module-sets (i.e. no conflicts) may make this harder to really 
reuse the module-sets for both purposes.

Of course, any other comments or feedback is welcome and appreciated.