IETF Logo Mail Archive

Re: [Netmod-ver-dt] Resolving package conflicts

"Joe Clarke (jclarke)" <jclarke@cisco.com> Wed, 11 September 2019 17:55 UTC

Return-Path: <jclarke@cisco.com>
X-Original-To: netmod-ver-dt@ietfa.amsl.com
Delivered-To: netmod-ver-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 946F01202A0 for <netmod-ver-dt@ietfa.amsl.com>; Wed, 11 Sep 2019 10:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, 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 header.b=QjVTLS1i; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=EECx+Lai
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 FMO8tNZNiB0o for <netmod-ver-dt@ietfa.amsl.com>; Wed, 11 Sep 2019 10:55:26 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68F59120115 for <netmod-ver-dt@ietf.org>; Wed, 11 Sep 2019 10:55:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19549; q=dns/txt; s=iport; t=1568224526; x=1569434126; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=H0BvEdEP1Ti13M8v7+23PsyxWnfVz0Oyo6sXI/qjpD8=; b=QjVTLS1iDQBHPNB4T6WlG8ieN/pBwevDJppNd9nvIvsnT2y4xgAOii6p KH32zSNUidvmX43a6bdW5G194t/obyxhWzL3yiiVLI7iMCDQUK9MmJyXf PovOeeN4xnSxQXvM19BBcBzhMwsUmT+z62aW34Gy+bnJm+aicSf18TYMj 8=;
IronPort-PHdr: 9a23:1E7+7BEoORwLse/qiuaw/p1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1A3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+efzhayUgH8lqX15+9Hb9Ok9QS47z
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A3AAAeNHld/4ENJK1lGwEBAQEDAQEBBwMBAQGBVQQBAQELAYEVL1ADbVYgBAsWFAqEF4NHA4pnlXCEXIEugSQDVAkBAQEMAQEYAQoKAgEBg3pFAheCPiM2Bw4CAwkBAQQBAQECAQYEbYUuDIVLAgEDAQEQER0BASwLAQ8CAQg/AwICAiULFBEBAQQOBSKDAAGBHU0DHQECDJ9yAoE4iGFzgTKCfQEBBYJHgkIYghYDBoE0AYt3GIFAP4E4H4JMPoJhAQGCDoJeMoImj0CFIZdqCoIhjA8GiGIbmQqmbQIEAgQFAg4BAQWBWQsmgVhwFTsqAYJBgkKDcoUUhT9zgSmNXAGBIgEB
X-IronPort-AV: E=Sophos;i="5.64,494,1559520000"; d="scan'208,217";a="632431017"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Sep 2019 17:55:25 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x8BHtPZj022688 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <netmod-ver-dt@ietf.org>; Wed, 11 Sep 2019 17:55:25 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 11 Sep 2019 12:55:24 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 11 Sep 2019 13:55:23 -0400
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 11 Sep 2019 13:55:23 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fjnz9Pa4jt9C0KedrD91OEb4TNBozz7NLjovn9R4gD6a1VF0rXI8u4UgKifPbiXgL9o8rz/qVH2q9IxZQjUVtptE0Vjgj7X1Jx85sNI3w33RYhfVNZQVI9iOLmOc/ohCI2XGja/nEwKQKOTIdBmgVxlHcXMkRRp4C/TNEV07G757iI+10F4wHu7DvqByPsPLijcklcN8KI9N5fbCdrM2Z0RsipCLJODKz5ZrWDvLBtNo9rz0u7mKGNn3lOuZCayLq+/Oaazyj9Na50Lr0jJHAwGGV4xYkgVPIYagC4JlRARMQsFNNehfFNsj46AQciiuu+kmWF/aKwjGleXcMjX/GA==
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=H0BvEdEP1Ti13M8v7+23PsyxWnfVz0Oyo6sXI/qjpD8=; b=F3S+XWVHSk1dBdxsMKv0Q/dun2FGWgrGMsdKZoU95mzqLa4VVQMyDKKlfElX8+VH18Dn1/rMH+XmPVehTMZb5b06r3MDXABAkkWzAB/4yJXbiTuKgmVGW6VRhc6J1HnC4iyYAcBuEmPTkZUUzgSD38GNs5iHFyOVLE9BdyiXbYK1/T4DfIgD7nbEmiGijSzy4VTlmhVU0j8qZEjxCJGACbrHTOwW6oaQmqcZXLBHeVsg3crUmewCNNLZqkuG9EGSTYDNELZ5NHiJpYkOu2YFjJen1mDNQ68/1t6Kx3zhDuGS92yWaQIxmWHRRTmscTly20Lqd6syuyid0nLUV3LhPQ==
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=H0BvEdEP1Ti13M8v7+23PsyxWnfVz0Oyo6sXI/qjpD8=; b=EECx+LaitVepD9BSUAQ2Aay4x48K90WH+Plld0gO1OQ1OEZ3F8rszI51nVDkJeIZ+9K+gbTq5dANvLrJ0hLu3AfFZf1ciBziGw1GCMNXsgKb4MnJi0sKbwH4GeIQjSm48MrR0vtudtToXiCqLzpsLp80YAx6SG6uzrU6W23nkx0=
Received: from DM6PR11MB3418.namprd11.prod.outlook.com (20.177.219.223) by DM6PR11MB3644.namprd11.prod.outlook.com (20.178.230.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.14; Wed, 11 Sep 2019 17:55:22 +0000
Received: from DM6PR11MB3418.namprd11.prod.outlook.com ([fe80::ddcd:cbad:9978:4c68]) by DM6PR11MB3418.namprd11.prod.outlook.com ([fe80::ddcd:cbad:9978:4c68%5]) with mapi id 15.20.2241.018; Wed, 11 Sep 2019 17:55:22 +0000
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
CC: "netmod-ver-dt@ietf.org" <netmod-ver-dt@ietf.org>
Thread-Topic: [Netmod-ver-dt] Resolving package conflicts
Thread-Index: AdVohPwpEQpYeopUSXOua5yScTazvwARRgaA
Date: Wed, 11 Sep 2019 17:55:22 +0000
Message-ID: <3BC3F203-5C69-43AB-94B4-B56874A7135C@cisco.com>
References: <MN2PR11MB4366FB929D5867AA78244608B5B10@MN2PR11MB4366.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB4366FB929D5867AA78244608B5B10@MN2PR11MB4366.namprd11.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=jclarke@cisco.com;
x-originating-ip: [70.231.19.155]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7407d979-5adb-4336-60bf-08d736e13767
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM6PR11MB3644;
x-ms-traffictypediagnostic: DM6PR11MB3644:
x-ms-exchange-purlcount: 1
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <DM6PR11MB36449A22C059BC82B38B12C0B8B10@DM6PR11MB3644.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0157DEB61B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(366004)(396003)(39860400002)(346002)(189003)(199004)(51444003)(6506007)(6306002)(14454004)(81156014)(446003)(76176011)(36756003)(6862004)(6246003)(86362001)(66066001)(236005)(54896002)(6512007)(606006)(316002)(37006003)(53936002)(71200400001)(11346002)(71190400001)(2906002)(476003)(486006)(2616005)(99286004)(26005)(186003)(256004)(53546011)(3846002)(6116002)(8936002)(66556008)(7736002)(6486002)(966005)(33656002)(102836004)(81166006)(478600001)(91956017)(76116006)(229853002)(5660300002)(6436002)(6636002)(8676002)(66946007)(25786009)(4326008)(64756008)(66446008)(66476007); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB3644; H:DM6PR11MB3418.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: zinXL4b0RTb+sB7NH6YtAAbLD1KT2WRX+ULMz7B/0bvDa3630RSxkwKMLyNTFTx8IjQBNMCIpyneuza7Rn1IzUzkHn490M1XOXC3jmcdlnQCER8p8GGiRcxAXidndrpADyDOvjhQ6Ph5xnxEoW/DRs6ioVAuQXDaB+VfCWwqv6/Zv00FxuD2pc1co9q789z+HWdHXsNeaID0dkT9xguL23I18QdPGJnJ1AQUy9xWCABphBtFLO8irs24TvrOoZlx9tLqp5S8uG63Ex/LqSaXZaEvOPuGUU3RAma98RIzi7yPBVZAzAK2oA6CQ7NJMWi6Cwffn5FQJUu1j6WynHUXk9qZSDvSpUj31X5hQ/m/YopaI/+XrKhkdAV3423B2hhtXaoA50MWFB8hk13K6slPyxLHTMn2bZMg9Ve1U8ws4uw=
Content-Type: multipart/alternative; boundary="_000_3BC3F2035C6943AB94B4B56874A7135Cciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7407d979-5adb-4336-60bf-08d736e13767
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Sep 2019 17:55:22.0888 (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: 8ZvFAuYp8lliuNbS9k7apu+vfqlkhuTYdJj+ZqR2u9tPZOB5Jbg8MxGFAs7RUSH9/gXtElMjAbuVfpBs7QByQA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3644
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.17, xch-rcd-007.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod-ver-dt/j_2oF75_BO_43KKsDoz_-ZeXzGs>
Subject: Re: [Netmod-ver-dt] Resolving package conflicts
X-BeenThere: netmod-ver-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NetMod WG YANG Model Versioning Design Team <netmod-ver-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod-ver-dt>, <mailto:netmod-ver-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod-ver-dt/>
List-Post: <mailto:netmod-ver-dt@ietf.org>
List-Help: <mailto:netmod-ver-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod-ver-dt>, <mailto:netmod-ver-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2019 17:55:29 -0000


On Sep 11, 2019, at 05:59, Rob Wilton (rwilton) <rwilton@cisco.com<mailto:rwilton@cisco.com>> wrote:

In the packages draft it is possible to for a package definition to combine modules from two separate packages which may conflict.  I.e. more than one version of a module might end up in the resultant package, or the import dependencies might need to be fixed.

This is OK, because the packages draft requires that these conflicts are always explicitly resolved by listing the specific module versions in the combined package, so the problem is solved.

But what about if we define a package ietf-base@1.0.0<mailto:ietf-base@1.0.0> that contains, say, 10 modules?

This package might be imported by a hypothetical ietf-routing@1.0.0<mailto:ietf-routing@1.0.0>.

Separately there might be a hypothetical ietf-l2vpn@1.0.0<mailto:ietf-l2vpn@1.0.0> package that has been published later and uses an updated version of ietf-base package, say ietf-base@1.5.0<mailto:ietf-base@1.5.0>, that may contain BC updates to several of the modules.

Say a device wants to implement a my-packages@0.5.0<mailto:my-packages@0.5.0> module that imports both ietf-routing@1.0.0<mailto:ietf-routing@1.0.0> and ietf-l2vpn@1..0.0<mailto:ietf-l2vpn@1.0.0>.  Currently the packages draft would require the my-packages definition to explicitly re-state each of the modules in ietf-base@1.5.0<mailto:ietf-base@1.5.0> that differed ietf-base@1.0.0<mailto:ietf-base@1.0.0> (because only a single version of a module can be implemented, and all conflicts must be explicitly resolved).

This works, but I’m wondering whether that might become overly verbose.  Hence, I’m thinking that it might be useful for the my-packages@0.5.0<mailto:my-packages@0.5.0> definition to explicitly list ietf-base@1.5.0<mailto:ietf-base@1.5.0> as a direct package import, stating that it is replacing ietf-base@1.0.0<mailto:ietf-base@1.0.0> (which is indirectly imported via ietf-routing@1.0.0<mailto:ietf-routing@1.0.0>).  Avoiding the need to explicitly list the conflicting modules.  In fact, we could require that all conflicting imported package versions must also be explicitly resolved, just like for modules.

Does anyone have any objections to this?

I think that sounds very reasonable and much less cumbersome than enumerating individual modules.

Joe


Thanks,
Rob


_______________________________________________
Netmod-ver-dt mailing list
Netmod-ver-dt@ietf.org<mailto:Netmod-ver-dt@ietf.org>
https://www.ietf.org/mailman/listinfo/netmod-ver-dt

v2.23.0 | Report a Bug | By Email