Re: [netmod] IETF 108: Summary of insignificant whitespace changes and versioning

"Joe Clarke (jclarke)" <jclarke@cisco.com> Wed, 26 August 2020 17:43 UTC

Return-Path: <jclarke@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 D018F3A192D for <netmod@ietfa.amsl.com>; Wed, 26 Aug 2020 10:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level:
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=kIAE2RXI; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=fVDnkHop
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 UDTjan4_ElMi for <netmod@ietfa.amsl.com>; Wed, 26 Aug 2020 10:43:33 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EA133A1924 for <netmod@ietf.org>; Wed, 26 Aug 2020 10:43:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3314; q=dns/txt; s=iport; t=1598463813; x=1599673413; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=gpX35mFhM9IRJ1GYVUHp4jQvLYLTlgVniYXjSyb5w9M=; b=kIAE2RXIfpdmEQLIFlwqG0w1O1z5arLLIr8ROjSmVVGZCs25g1FVQev2 n3aqANfEpbNIVYFH594ThC8VvtaQdngKtDRMIyWF2t8X/5Ar2P8UThXB8 ADSP7g8v0lqbI4WEW9lwVp8SntSqN6A2HZ2LbDJFt2zDot9svX4E/cG4U Q=;
IronPort-PHdr: =?us-ascii?q?9a23=3AVxF90R16NBtBYOxxsmDT+zVfbzU7u7jyIg8e44?= =?us-ascii?q?YmjLQLaKm44pD+JxWEtadvhVTOV56e9vRFlefMqKH8SCoM7MXJvHMDdclKUB?= =?us-ascii?q?kIwYUTkhc7CcGIQUv8MLbxbiM8EcgDMT0t/3yyPUVPXsqrYVrUry6w5DUVEA?= =?us-ascii?q?66KAx0OOnvAY/OnoK72rP695jaeQ4dgj27bPt7Jwm3qgOEsM4QjO4AYqY8wx?= =?us-ascii?q?fEuD1GYeNTkGhpPlmU2R3745S9?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CoAADpnUZf/5BdJa1fHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQFAgTgFAQELAYFRUQeBSC8sCoQtg0YDjWiYcYEugSUDVQsBAQE?= =?us-ascii?q?MAQEtAgQBAYRMAheCIQIkNgcOAgMBAQsBAQUBAQECAQYEbYVcDIVyAQEBAwE?= =?us-ascii?q?SEREMAQE3AQQLAgEIDgIIAgImAgICMBUQAgQOBSKDBIJMAw4gAacEAoE5iGF?= =?us-ascii?q?2gTKDAQEBBYJKglYYgg4JgQ4qAYJwg2SGTxuBQT+BOByCTT6BBIM4gxgzgi2?= =?us-ascii?q?PbTSCbKNFCoJjmisDFQmgPq46g1gCBAIEBQIOAQEFgVsFLoFXcBVlAYI+PhI?= =?us-ascii?q?XAg2OHxgfgzqKVnQ3AgYBCQEBAwl8jnIBgRABAQ?=
X-IronPort-AV: E=Sophos;i="5.76,356,1592870400"; d="scan'208";a="544574148"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Aug 2020 17:43:31 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 07QHhVKf029303 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 26 Aug 2020 17:43:31 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 26 Aug 2020 12:43:30 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 26 Aug 2020 12:43:29 -0500
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 26 Aug 2020 12:43:29 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Yh9GO55CM/C97caOa5N59G5VY4i5hXRSET+g+ngO7y3kvKYSGA7//0uuFq+ZCFEAqRwh0RaNxi5I2f6+3hUBqrEYiDI9Nqyw7X9/fkj6zcATT4gqtJH2ZNwHvtLcBVOlQ/Yu4ZyK2r/DCO2q/+XraE/4hbzKJotFK2vSe9Lf7iBKXe1eA8E3Fgw54+rYlekerTjNl/HlpEx0/u4oakchkuI6x79jghEIxLUpZJ8En/JLFdJhJ5TpS+bqPd/eUaqk6HF1V8nN79lsytRNZbS2GPDBy5pxTsV1qHwA9ZfJvuhur4dMpnLarPHj22zb9AqUUzMAkqz+2KZpTE3117/BvQ==
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=gpX35mFhM9IRJ1GYVUHp4jQvLYLTlgVniYXjSyb5w9M=; b=WZ07HZidZ2BTylcHwcshlJe7sw95HwO2f/CCr+KT0dTdRmKIaMXkOZDG7+CCMaffkrhOhD2Q5PJucCDAVya+TjMbsqtZJEvVG4VVuNKSwJdM6pl1mJWid8eteBJWCFm3DEMIu72HL/xj5BcdL071Mt1H8Ee+ExZuMk9jqjeSmZ/kj2A/BCrlvaseia8o/kvYhk7WJG3X36AE5deqOMyDlty3gfPn+uWplmA5EkpLkqZmoVQxK2V3oHM+aJz35SUlzdn9ERa78eLOmb/77pPl9IGJoa07M9DgVmxeVxUb5a0Db/iNQctvcyRBpm5AuHjZO58kKBlq1OIrJbBNjnwR/w==
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=gpX35mFhM9IRJ1GYVUHp4jQvLYLTlgVniYXjSyb5w9M=; b=fVDnkHopM0mG4Gre94RIiC/5k8WQ1Sa0Tbw128reJA6IRWQCjRN/n/4KJo+yzZOfZSO16i7tJ495PaOEehAxxyEobPKl20mdr7S88cb7FpZrECP4Z8aVrlhlIlsh/cE9nOGZzgiO2o37QFPR/KpTufySgYpioMx3lpEjKCqfvpk=
Received: from BN6PR11MB1667.namprd11.prod.outlook.com (2603:10b6:405:e::12) by BN6PR11MB3971.namprd11.prod.outlook.com (2603:10b6:405:7d::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3326.19; Wed, 26 Aug 2020 17:43:28 +0000
Received: from BN6PR11MB1667.namprd11.prod.outlook.com ([fe80::c75:66f5:d072:746a]) by BN6PR11MB1667.namprd11.prod.outlook.com ([fe80::c75:66f5:d072:746a%12]) with mapi id 15.20.3305.031; Wed, 26 Aug 2020 17:43:28 +0000
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: Ladislav Lhotka <ladislav.lhotka@nic.cz>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] IETF 108: Summary of insignificant whitespace changes and versioning
Thread-Index: AQHWb+UbHoRASKbTwU+7Kq/q+RMeJ6ky/HIAgAAopwCAAPmUAIABn5mAgAAMmwCAAAzHAIAU6VyA
Date: Wed, 26 Aug 2020 17:43:27 +0000
Message-ID: <E8EFFABC-B60F-438C-B9AB-3204A834DC9D@cisco.com>
References: <5CF24083-4126-4BE0-93F1-9A36F6DE9296@cisco.com> <20200811.164556.608015447238311339.id@4668.se> <A634B3C1-9F19-4A44-9479-56EC986DA1D8@cisco.com> <878sekb885.fsf@nic.cz> <11245BD3-6E79-4F02-9962-53BE87264460@cisco.com> <acfe1b95-e0f3-0b7e-2635-9582eb11b4e6@nic.cz> <20200813102302.xwowkncgur4s7yuc@anna.jacobs.jacobs-university.de>
In-Reply-To: <20200813102302.xwowkncgur4s7yuc@anna.jacobs.jacobs-university.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3608.120.23.2.1)
authentication-results: jacobs-university.de; dkim=none (message not signed) header.d=none;jacobs-university.de; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [173.38.117.82]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f4f341f6-a7a4-45af-0ae8-08d849e78a79
x-ms-traffictypediagnostic: BN6PR11MB3971:
x-microsoft-antispam-prvs: <BN6PR11MB3971FED572AB4412F27B0BA2B8540@BN6PR11MB3971.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: hCJFUWf4i/OTd/rePQX1jm5T7IrYa1vdy7XFGzfGKrKbc75R0ved2y3VuA0MjYRbfXbRHM6ZprA3X0KdKTQpq2gYLjptG4uLK5vvyjk4Xl1cFtwJiNXfYMx9A4AIBC449DD8uQwuAwvAStEmGzmzia9p1KUoMudG+VRzRMM082FMlwvF/5ApFTBX2xEvRcBbLqp2A/50CHHAjNLih6dn/ftrI+OrP2SIuxsV7LsDXm8sMZ4nPl7c0Xh2RxiIt1RNzWzvnAhe5fwFfJn53dNa4pbFXARYowONm9H5F4/ya7r5Y+bfWvy6dEoUpyuubPLLUbxXsw6L8XGxt5DM+OkTGg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN6PR11MB1667.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(346002)(396003)(366004)(376002)(136003)(39860400002)(5660300002)(478600001)(86362001)(53546011)(6506007)(2906002)(33656002)(6486002)(54906003)(26005)(6512007)(71200400001)(316002)(186003)(6916009)(2616005)(8676002)(91956017)(66446008)(64756008)(66556008)(4326008)(76116006)(8936002)(66476007)(36756003)(66946007); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: MCXbMRBNVFkpDMiChl49IoBuDgyZmHUuDd9G83LtMBRB6xCt2BSsSKKxKdX4Uvb+DnzHroLlspATmf6eo4QBC/VIIgfOoMvLxNJ0p09LOkHj1C7JxM5klWwOf3wRnVZB2PsbPzlEvSyumfCaQvx6DLIL1wlTh8kiyDhMNc7JwF3Hemr1kyp3nodbPHYXo0cZSx0Cinuws0E46QYneJ9+ThvzSIABEfrEkgJRWBSe0qm2FGXy4/ZnFnWliDOn7khxmGrKVsUBIKd3H5hjj0FxX+2BPwVU1luI26FarEqspDKZYDdhdkyiyV9U703P+Q4vXyPvwM/r8OD68X4dntDQmT9Knc1jWF+Mj9lqsEIsmGpNmea06FJhY3yo6eJln2+c5TY6kFUdgHUYZdiHf8ysgcsX/tQIlS3sUWT9dx0sGdq8/1WsYSGNVx36Mw0tJ/rZdBebB0StGRDqMKd4uSDOkET5UqFiluX/0WKKN1aWPkkHQ6Kh4bWf/1lp+FrZcpyclRom8RP8EChtrLecjQ/6h/nqmlYV9km3TB9Ytkn28pIPbh7ZtqSQcKjuPLnGXdZrPUmJbQ3NTKbHPb1IJm2Qw0Z/pnWfIFtQ8X9l5cY8rx7cID2SPrlYmd2XESWrT1ZOQo9PtTnYNLsqMq6MS7UQGA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <C910C5B785562F49B6AF8DF6BCEEF66B@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN6PR11MB1667.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f4f341f6-a7a4-45af-0ae8-08d849e78a79
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Aug 2020 17:43:28.0627 (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: 7JR0mONEhJKk9tq9pVYk27temBJ7hxf29nq4wqgtTLfBfa6JpvKTdlsATGNRTdBqWUQPhXbS7fczUvS45yqnZw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB3971
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/n1QwqjU9DHv1cOFRPN2mnIT-e38>
Subject: Re: [netmod] IETF 108: Summary of insignificant whitespace changes and versioning
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: Wed, 26 Aug 2020 17:43:35 -0000


> On Aug 13, 2020, at 06:23, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> 
> On Thu, Aug 13, 2020 at 11:37:18AM +0200, Ladislav Lhotka wrote:
>> 
>> 
>> $ pyang -f yin ietf-inet-types.yang | xmllint --c14n - | sha256sum
>> 8d1ca8f30566ce8cbeffa095e20642f8f6e9f3a724286be4ead863b4467dc40b  -
>> 
>> might be a very good start. It is certainly much more robust than
>> relying on a simple checksum of the YANG module text.
> 
> This work started with the need for _semantic_ version numbers and now
> we are down to hashes of modules? Do we still have a clear idea which
> problem we are solving?

Sorry for the delay.  I was traveling and then trying to get caught back up.  Yes, things got off track a bit here.

> 
> - Sane development environments use version control systems, we should
>  in my view not attempt to go there. We should assume that people
>  developing YANG modules use version control systems to track
>  changes.

Agreed.  And through that development, we are not trying to impose any versioning up to the point that a module would be published (e.g., in a draft where it might be implemented).  Certainly, people could also pull and implement any arbitrary revision from a VCS, but we haven’t created any text to cover that (nor do I think we want to impose that each commit revs some version in the module itself).

> 
> - There apparently is a need for a packaging system that can express
>  which combinations of YANG module version are known to work
>  together.
> 
> The YANG versioning work was driven (I think) by the desire to
> support non-backwards compatible changes (section 4 of
> draft-ietf-netmod-yang-versioning-reqs-03). Why do we end up
> discussing how to calculate hashes or the impact of whitespace
> changes? Whitespace and layout changes are backwards compatible,
> even today's YANG versioning rules handle them well.

The intent, at least for the whitespace changes was at a module release time to indicate what constitutes a version bump.  But the question could likely be rephrased.  Would one change the _revision_ of a module for any of the changes mentioned thus far?  And if a new revision is created, and semantic versioning is used a revision-label scheme, then that revision should have a new version label.  At least this was the opinion of the contributors in the regular weekly calls.

Joe