IETF Logo Mail Archive

Re: [netmod] All IETF YANG modules MUST include revision-label statements

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Tue, 31 March 2020 02:41 UTC

Return-Path: <rrahman@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 2DAAC3A18E6 for <netmod@ietfa.amsl.com>; Mon, 30 Mar 2020 19:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.7
X-Spam-Level:
X-Spam-Status: No, score=-7.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=DPIqVnmC; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=a4DZNmxc
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 0aZRc0ZUOotd for <netmod@ietfa.amsl.com>; Mon, 30 Mar 2020 19:41:31 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D92BC3A18D6 for <netmod@ietf.org>; Mon, 30 Mar 2020 19:41:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=950; q=dns/txt; s=iport; t=1585622490; x=1586832090; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=b+nx8smriAQ9I5uJQnGWxW1U32cUSmlaYhf2dYTABys=; b=DPIqVnmCVKybqwGmTPiORMM13A5z1v+ftT1TQCVVnnErGQtJClKxWozW mO+ygpTswynn4FxA8uYiE6htJxClA7WNW6MHB8SzEf69XswaM5TqT4YNo BdK5I8wfXNj130dNZ0uHW8UrprX14WmVBCu+LT5dINMw6IxlIe99zqx7C 0=;
IronPort-PHdr: 9a23:RxoV0BNm4qR3ZSXOG/Ql6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu60/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBjhNvfqaiU8NM9DT1RiuXq8NBsdFQ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AKCACqrIJe/4sNJK1mHQEBAQkBEQUFAYF7gVRQBYFEIAQLKgqEEINFA4pqgl+YH4JSA1QKAQEBDAEBLQIEAQGERAIXghskOBMCAwEBCwEBBQEBAQIBBQRthVYMhXABAQEBAgESEREMAQE3AQ8CAQgYAgImAgICMBUQAgQOBSKDBIJMAw4gAaJUAoE5iGJ1gTKCfwEBBYJFgkwYggwJgQ4qjDEagUE/gREnIIIfLj6ETheCezKCLI1xgwmfbwqCPJcVHYI7EYgwkHCrHAIEAgQFAg4BAQWBaSKBWHAVZQGCQVAYDY4dg3OKVXSBKYxUAYEPAQE
X-IronPort-AV: E=Sophos;i="5.72,326,1580774400"; d="scan'208";a="746567139"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Mar 2020 02:41:29 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 02V2fTFH008609 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 31 Mar 2020 02:41:29 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 30 Mar 2020 21:41:29 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 30 Mar 2020 21:41:29 -0500
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 30 Mar 2020 21:41:29 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=J0gDcaSYdRDcWypIfPDx+3/aXkw1+BOuSAhrurJM9wiNTluOXxhHE7fYbvTUSA2dIChipIp3CDRy2nNAvsROF5JZQGnIP7z6u+E36n18W1UPnLYfYjEz43lp0FULC7q7SwiPRjMQsuqtfK8/+TugrJyA/BHbPE2C2bMwGUbT8J93UuQtDQRnrGnb2FjZ4AKxd6dFmjE0qdKwxovqIS6uxr4vukH1eTQ7sRdXakz65XWkGP9QHtfwcAnMn7h07lzAwZVR7AJsdeHxIbX1CY0DHfV+quDtJK+bvgZWpfT0Lteri4XHEt/UZl2gYLTHOumBaLrZn6sxWlTlVb/DChW/OA==
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=b+nx8smriAQ9I5uJQnGWxW1U32cUSmlaYhf2dYTABys=; b=jgr40RprVbu7TwCT1RGLP3Wj5CRiL6NrEGAeTMrybH/pXXFIQDCZV9spgWBO+FUKjhNol00W1qtE5LdnkzJORyamiSxbqN1MlmJcIfgqhOExiDwECrtnjae7HHDWWi8h0pZj13ABXSEFyb2+bqwysZblvt9tFuVxBkzHlARYAzdjNfLQwONzL4sNoHfOFHXlIs9vr4VJjItaII5iW1R98QqWy87/qWpNcHPOYmWgOwY4L9TTtqcvK33MmTSa2tEUnx9u/yoppVhgsujMjKeWEUiPUGQNvrLfizqF7F+yqJiQIJwgHPAdOkOJTLnq+FFp/RJU6S0nDI5f8q/8hyrByw==
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=b+nx8smriAQ9I5uJQnGWxW1U32cUSmlaYhf2dYTABys=; b=a4DZNmxcPr1dD/oJwEqX7gMbe8nkEYsX3VRHbFD8j9TbO7obKypSBN84WzqS9SKCw09YTLKFiXTVNZ85ovZqrZHcZorg7LzYL5ABLD1sWrXehs+1sUVT2Wp2VuWyitiT4fbezx0SlcgWT/jaQY4WJc4Uimk6QE4CXO0WN1Yu8l8=
Received: from BN6PR11MB1748.namprd11.prod.outlook.com (2603:10b6:404:101::12) by BN6PR11MB4033.namprd11.prod.outlook.com (2603:10b6:405:78::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.18; Tue, 31 Mar 2020 02:41:27 +0000
Received: from BN6PR11MB1748.namprd11.prod.outlook.com ([fe80::d1f9:733e:e200:f972]) by BN6PR11MB1748.namprd11.prod.outlook.com ([fe80::d1f9:733e:e200:f972%6]) with mapi id 15.20.2856.019; Tue, 31 Mar 2020 02:41:27 +0000
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Kent Watsen <kent+ietf@watsen.net>
CC: Martin Björklund <mbj+ietf@4668.se>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] All IETF YANG modules MUST include revision-label statements
Thread-Index: AQHWBNyukTO5JXWurk2ljZZiFHPveKhhwQsA///CDYCAAEc2gP//9KcA
Date: Tue, 31 Mar 2020 02:41:26 +0000
Message-ID: <D7A72C10-B84E-458E-A96A-21F3975A1A1E@cisco.com>
References: <75CFDBD9-143C-407A-B7C3-26CEC51E229C@cisco.com> <20200328.094121.1160081114435152145.id@4668.se> <010001712da22206-5abfb31e-aa12-47b6-983a-1cd6edf6d45b-000000@email.amazonses.com> <9488C489-CD77-458C-9CD3-A78B043AF48F@cisco.com> <010001712dc07c5f-31a83f3f-2376-426b-a6ef-ebee43575ca6-000000@email.amazonses.com>
In-Reply-To: <010001712dc07c5f-31a83f3f-2376-426b-a6ef-ebee43575ca6-000000@email.amazonses.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.21.0.200113
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rrahman@cisco.com;
x-originating-ip: [70.31.50.95]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 04091fcd-5c0f-467a-2bef-08d7d51d0293
x-ms-traffictypediagnostic: BN6PR11MB4033:
x-microsoft-antispam-prvs: <BN6PR11MB4033A86E6CAA5FC222F009C5ABC80@BN6PR11MB4033.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0359162B6D
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN6PR11MB1748.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(366004)(346002)(376002)(136003)(396003)(39860400002)(186003)(4744005)(8676002)(86362001)(316002)(8936002)(71200400001)(6512007)(36756003)(6486002)(81166006)(4326008)(81156014)(66556008)(26005)(64756008)(66476007)(6506007)(66946007)(2906002)(53546011)(33656002)(5660300002)(66446008)(2616005)(54906003)(91956017)(76116006)(478600001); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 2ogfc2v9QSAabfKhsYwdXCF9LUKfqu3eTUnrO9W/3XenmhXJ2+cEllrL0Z/HVx+rS8wqE3v6FkBGipwSdchYcefFaywcogREsYnVkmbpjlSh8g1czxIkDT8Q4iXZ8GtOBrYTw0pbneQsQy4KQHU3QzDQMnmRR1Trd1ZQq1NhgDQpm7+HANZccenV+A5TVsPZ/R7qSk0iQowK9epRe6wYDsMuq7QyeSj7n6zXMBjfobxNzGlsgrEslIHDwzmFulCQJ45++D7DUsOTyLr3qHguBqJuTdViNrM4zCE2tyF4H45p50T8n3NYDCgqFlsWEQkWgJDWsaoxYSC7OGzGT7EJrTeTZ6ZzSFHa5udoDoMUiNfCN11lzvJ2kgQgCl9QoryJkSEWvM6hIuzFy50jp9dLT8dAYAlgE1hgvzAY03K89ePA3ToHgYnNWWayjwc15E3U
x-ms-exchange-antispam-messagedata: MJmnBzOoVrHpFa2KgdDxUK33OF0+A8RRTLW7VW7jXBJFm0hV35bMZTT/BWPQskCrVGvX0F25ab9zdXHd9aB+dcIoJ3Vu7gFRDbaL7pZRINLwiJzwsrBNEsUN8hEGB5UPgnpE0k0r4VHkEhe2DiHXaw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <95C7152D2BDE6F4B914B25171A8F2EF3@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 04091fcd-5c0f-467a-2bef-08d7d51d0293
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Mar 2020 02:41:26.8962 (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: iOyR6lkwm7Z349873H+v4cYNMvjMFV07l1MXQjNB/xxDJeXNvvenW0zrvmAJzJNUvOz4Gr+yTBgj9Rkc5G7aJw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB4033
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/BLciY41IC102K9u6sUNZ4qJmDs0>
Subject: Re: [netmod] All IETF YANG modules MUST include revision-label statements
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: Tue, 31 Mar 2020 02:41:32 -0000

On 2020-03-30, 7:22 PM, "Kent Watsen" <kent+ietf@watsen.net> wrote:
    > Even though we are debating/discussing whether iETF moduels should use YANG semver (aka modified semver), please note that there is interest from other publishers of YANG modules to use semver or YANG semver.
    
    Details?
    
I was referring to vendors, not SDOs.

Regards,
Reshad.
    
    > Regarding your comment below, is it specific to IETF modules or more general?
    >  
    > "I don’t think the “semver" label has been fully justified relative to the disruption I perceive it may cause.”
    
    I was thinking in general.  YMMV.
    
    
    Kent // contributor

v2.23.0 | Report a Bug | By Email