Re: [netmod] definition of "fully expanded YANG"

"Rob Wilton (rwilton)" <rwilton@cisco.com> Fri, 19 July 2019 10:36 UTC

Return-Path: <rwilton@cisco.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 43BC01200B1 for <netmod@ietfa.amsl.com>; Fri, 19 Jul 2019 03:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 header.b=lKYMexwN; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ImWqdBEo
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 koIAtkA8r4fC for <netmod@ietfa.amsl.com>; Fri, 19 Jul 2019 03:36:04 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A6A9120020 for <netmod@ietf.org>; Fri, 19 Jul 2019 03:36:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13878; q=dns/txt; s=iport; t=1563532564; x=1564742164; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=NlknU2FQpO2FDkQa6x8VubLS+hlMDWEo1+dD2mCGMX0=; b=lKYMexwNt3Ih95P9t7i1uH9BfG7IIa/i5UaG3XbfQlo1C+Ui3YlIiCyx Er4WmMO9WZjLFhUMHZL4I9PSeKo0kVtEHs/D+xjq6ptg2NFfVSTtAhEjx BS5S9J6QcMIsh/ZANUNi04htDy4hl30z+WyQMGHYY09AvllfF3EYhhIpf 8=;
IronPort-PHdr: =?us-ascii?q?9a23=3AW3FZ9RNhQOW83zxKlTUl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEu60/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETB?= =?us-ascii?q?oZkYMTlg0kDtSCDBjhM//ucys8NM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BzAABZnDFd/4UNJK1lHAEBAQQBAQc?= =?us-ascii?q?EAQGBVAYBAQsBgRQvUANtVSAECyoKhBODRwONe0yCD5J7hFWBLhSBEANUCQE?= =?us-ascii?q?BAQwBASUIAgEBhEACF4I1IzUIDgEDAQEEAQECAQVthTwMhUoBAQEBAxIRChM?= =?us-ascii?q?BATgPAgEIEQQBASsCAgIwHQgBAQQBEggTB4MBgR1NAx0BAgygIwKBOIhgcYE?= =?us-ascii?q?ygnkBAQWBRkGCehiCEwMGgTQBi14XgUA/gRFGgkw+gmEBAQMBgSoBEgEhK4J?= =?us-ascii?q?eMoImjAoZMIIlhH6WcQkCghmGWI1PmAqNNYdIkAgCBAIEBQIOAQEFgVICNGd?= =?us-ascii?q?xcBU7gmyCQYNxhRSFP3KBKYt4gSIBgSABAQ?=
X-IronPort-AV: E=Sophos;i="5.64,282,1559520000"; d="scan'208,217";a="298868837"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Jul 2019 10:36:02 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x6JAa2Bn006515 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 19 Jul 2019 10:36:02 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 19 Jul 2019 05:36:02 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 19 Jul 2019 05:36:01 -0500
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 19 Jul 2019 05:36:01 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DTIKXIb97wuh9GznW28t+/A0TvHYf8oKjv+rPGhvasITI18Vv8yqIdLKhsRSJPLEM+uL+Ag2biBlWW+sZCZnJI9zBEa5XQ+K71PFMq8cO8s5ddcTmBXoDDyviQCLZD+oBKyPIOPqOHlUrTkAgNEAvBBU6CInuECH9TSxfXdyDfws7idwLWyvCR/hecXXwPd52+kIufHnkZOUKw4ZpH17sA7Nat4lPbiVGgzPIzdVuZqZn5Flaxx1+Wo6Ma/0ai94nHjDVjMiUOrui3KE4qgUzthL6PX4R9BoZ6cIlMO/uR3M7DVVmTlEQwUNJsNmsxGLoqtEDTkBFUu2yJX1mN5+3Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NlknU2FQpO2FDkQa6x8VubLS+hlMDWEo1+dD2mCGMX0=; b=k8ETzBuEHvsV4WWGQIEqUgtBLUx2hhOpneAnCtfJG1PWRYPmU5Rh4K3QHDG9+V5B3ReCQiev6Lm5tk4LplXkXmIEH9IYI73K2M2TG/iPWVyAebyPCjjx2y7/rLEvoGqu1btrrCkwTvpGvrHJlxK0x3T0Mo9fW37BPtXZQjBPdffZZUxGpXC9i/P4T5fR/pu5Oi0pLKUl+EfXkIeNzxgIPaSTZ5TgJKr025qs2CjCPMCY86tCdETcejiomopSJLIZbx4XUycFMFr+MVNm6XybtkKv5fPeLnA6vgHIBIN6KggbUfk3q9j76xWXsqlils+ieHLf7Xzzkviu5aYEtQxpzw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=cisco.com;dmarc=pass action=none header.from=cisco.com;dkim=pass header.d=cisco.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NlknU2FQpO2FDkQa6x8VubLS+hlMDWEo1+dD2mCGMX0=; b=ImWqdBEoIjDeM/qCAJFiH1/NjjgbZ70EejS/+X0yST8R5oSgfPpdPmIJ+R255sKyD9jB6sJCUnjNPnSug6cLjPZIE/6l0D5y+plSWNQWS6YfuQoO8sED5nDWo7y3Gl/K6Txlp8CECP4ujUdgiW/kx0IqG2yU7HYj6aeSKIA8yWI=
Received: from BYAPR11MB2631.namprd11.prod.outlook.com (52.135.227.28) by BYAPR11MB3670.namprd11.prod.outlook.com (20.178.237.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.14; Fri, 19 Jul 2019 10:36:00 +0000
Received: from BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::91da:1669:aaf0:d428]) by BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::91da:1669:aaf0:d428%4]) with mapi id 15.20.2094.013; Fri, 19 Jul 2019 10:36:00 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Michael Rehder <Michael.Rehder@Amdocs.com>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: definition of "fully expanded YANG"
Thread-Index: AdU8nuY0Bmt7E8Y5QVmOJ4Epr5b+lABfSjCw
Date: Fri, 19 Jul 2019 10:36:00 +0000
Message-ID: <BYAPR11MB2631AA0834EEEC1E8EA516D2B5CB0@BYAPR11MB2631.namprd11.prod.outlook.com>
References: <AM0PR06MB40833B02760A889E273D8278E7C90@AM0PR06MB4083.eurprd06.prod.outlook.com>
In-Reply-To: <AM0PR06MB40833B02760A889E273D8278E7C90@AM0PR06MB4083.eurprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [173.38.220.36]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7e82021b-150c-4883-b43a-08d70c34e43c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB3670;
x-ms-traffictypediagnostic: BYAPR11MB3670:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <BYAPR11MB367079DED49410E1DBCC5E3EB5CB0@BYAPR11MB3670.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01039C93E4
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(366004)(376002)(396003)(346002)(136003)(189003)(199004)(966005)(478600001)(14454004)(7696005)(76176011)(9326002)(229853002)(66946007)(66476007)(66556008)(64756008)(99286004)(476003)(5660300002)(25786009)(76116006)(14444005)(256004)(2501003)(7736002)(102836004)(33656002)(186003)(74316002)(66446008)(81166006)(26005)(81156014)(8936002)(446003)(66066001)(486006)(11346002)(53546011)(6506007)(52536014)(9686003)(110136005)(86362001)(6436002)(790700001)(6116002)(606006)(8676002)(316002)(3846002)(54896002)(68736007)(53936002)(2906002)(55016002)(6246003)(236005)(71200400001)(71190400001)(6306002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3670; H:BYAPR11MB2631.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: udBDZ7t++3RTnxj4IGj1/DSlTzjQUxhWplS1uFDeu5TRyIXuuz3p0FW1XY48TSQ5GTOYX+kjNSCx1mQMCRtjrc2XqfZ20LPJmc73OAPLZcjBNPfvvUZ8dlsZCEsvXTU0OiZDhvc5licmj7ePQS73+X8sIHhH9+QhWAXHTMmx7Lu5QbIlefXUWLr2rw2m7OWvqBDSkmVF92YV36L4kG53KKbKrGmKEbQPfVCbPOamcqRsBlZYR6RNdkF6y3KVxa6dMCCJebpdXOTDU0If8pwZkI9X97pRVsgdIlmQUcUq2FwTHhGP4jOS0xNjz/g/UeFkzs91Es0KcepWjyIbFBIFE5bRrtHoujasYVJgp9GV9GwZM2J3VQGXOG8lGcy4TwlSywrywfdCmk6uRM2ej3tKOLDOXaFORPzeQJi7hi9Bp/A=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB2631AA0834EEEC1E8EA516D2B5CB0BYAPR11MB2631namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7e82021b-150c-4883-b43a-08d70c34e43c
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2019 10:36:00.1271 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rwilton@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3670
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.22, xch-rcd-012.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/OCru3pygI4l9xs9pPrKOuT1TgEE>
Subject: Re: [netmod] definition of "fully expanded YANG"
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: Fri, 19 Jul 2019 10:36:06 -0000

Hi Michael,

I don’t know about “fully expanded YANG”, but some of the work by the YANG versioning design team might be of interest to you:

draft-verdt-netmod-yang-solutions-01<https://datatracker.ietf.org/doc/draft-verdt-netmod-yang-solutions/> gives an overview of the solution space.
draft-rwilton-netmod-yang-packages-01<https://datatracker.ietf.org/doc/draft-rwilton-netmod-yang-packages/> defines versioned packages (although it needs some updating to accommodate the changes that happened to draft-verdt-netmod-yang-module-versioning-00<https://datatracker.ietf.org/doc/draft-verdt-netmod-yang-module-versioning/>)/>).  A YANG package, if all dependencies are resolved, can be used to define a complete YANG schema (i.e. with module import/include dependencies resolved).  From a definition POV, this might be the “fully expanded YANG” that you are looking for.
However, as others are pointed out, it is effectively tooling that takes a list of YANG modules (perhaps from YANG library, or a YANG package, or other source) and internally constructs a complete schema with dependencies resolved, deviations applied, features handled appropriately.
Thanks,
Rob


From: netmod <netmod-bounces@ietf.org> On Behalf Of Michael Rehder
Sent: 17 July 2019 14:03
To: netmod@ietf.org
Subject: [netmod] definition of "fully expanded YANG"

Has there ever been discussion about defining “fully expanded YANG”, that is a YANG module with all internal and external imports resolved?
This has several uses:
- Base for workable DIFF between versions so one can see all impacts of changes
   I see this as a pretty important part of semantic version management – if you can’t see the net result of changes in a properly modular YANG package, how can you be sure of the version meaning?
- Base for translation/processing of the schema
  There are all sorts other materials one can generate from a YANG (or a fully expanded YIN). If not expanded then this processing is very difficult.

Thanks
Mike
This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service