IETF Logo Mail Archive

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

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Mon, 30 March 2020 23:07 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 8FAED3A15B4 for <netmod@ietfa.amsl.com>; Mon, 30 Mar 2020 16:07:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.697
X-Spam-Level:
X-Spam-Status: No, score=-7.697 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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=RWjwUkJm; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=UOzz9CgJ
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 JO5GKvC5u2Ox for <netmod@ietfa.amsl.com>; Mon, 30 Mar 2020 16:07:22 -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 4D2413A156D for <netmod@ietf.org>; Mon, 30 Mar 2020 16:07:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11097; q=dns/txt; s=iport; t=1585609638; x=1586819238; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=lNWq9PKPafScFsUU6wl0bAyIcwlzV+agf/Y2gz1Q0pA=; b=RWjwUkJms7S0L8Sjd2ocaVpLvVtaW0Vo/lwGpFKvHdGDGmsaVg4b2npJ g5FnT0JiDnGEQ8VhbeQ5HNAv5zi80p8RWRW766FW/SUG3eJlCre1NjLPs 36KmmoBL7HZ/Iukpdp+vLa++Gq/iKPJVOU8VKwanHNbR/0bGEiMMUeQBO w=;
IronPort-PHdr: 9a23:ZyJcWRb1XtthKgB0cuX8r/7/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20gebRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8KavwdSU6Gc1EfFRk5Hq8d0NSHZW2ag==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ABCACFeoJe/49dJa1mHAEBAQEBBwEBEQEEBAEBgXuBJS9QBWxYIAQLKgqEEINFA4pqGoJFkz2EYoJSA1QKAQEBDAEBJQgCBAEBhEQCF4IbJDgTAgMBAQsBAQUBAQECAQUEbYVWDIVwAQEBAQMSER0BATcBDwIBCBEDAQIrAgICMB0IAgQBDQUigwQBgX5NAy4BDqJyAoE5iGJ1gTKCfwEBBYEvAYEVglMYggwDBoE4jDEagUE/gREnIIIfLj6BeW4CggUNgmUygiyQeoV6iiePTgqCPIdhjzQdgkyIMJBwjxmJFpJtAgQCBAUCDgEBBYFpIoFYcBVlAYINAQEyUBgNjh2Dc4UUhUF0gSmNDgGBDwEB
X-IronPort-AV: E=Sophos;i="5.72,325,1580774400"; d="scan'208,217";a="750832708"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Mar 2020 23:07:17 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id 02UN7H5G010881 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 30 Mar 2020 23:07:17 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 30 Mar 2020 18:07:17 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 30 Mar 2020 18:07:16 -0500
Received: from NAM10-MW2-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 18:07:15 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ca+QcEsVHH+mPMzOzFHpW+2/Dwy/q0nrIhZ4P9xaJ6PyRnBnjKq1EtnchHOKq43vtldURzITV1tyoLMHYic+2Jv8feqfzt7/4i79X+apWMGEZp4NpfW/hREsO1lpjHFCyTmsV0jf74NiDf5raFsH9Qg5usgJeZhle3+xPnaIELJytxlzQlWGHe7W5RodJGVsFOUbOP6QqN53jbviGcFKv4qCtiMAxHkcpPtMIOvo/RKuZ6NARSt95brUGuIZJ3rGCqYQaE7uN7LYoIadt+hcigYFGfG+BPcrOBbf4c6F9XpAT7X4aipIky0QZqPZ2gRBwklLELMecXnkz4FFmQxt4Q==
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=lNWq9PKPafScFsUU6wl0bAyIcwlzV+agf/Y2gz1Q0pA=; b=jODeDBiYGaMM4DWBbBRU0NX+y8bux5r0q58Y2vbldSb1xGS92oZ5FI2O23OTgUXrU9Wvv19ZsmCYq50dtPujcTZNh39jiTo4T0ITWYNmSHEoLlt1WuKJlcv8f5pEdxX9qcQhjwoxYEVbReFyUhYMu73cgVlDGMXZroZ++2nLuQEQs/VwOlWPcC9KZJ/ZNXF9PxgTesDF2e1uLO4ML2iI6SPjAomeiSHBW/0Zh+GuxSjsPsgDyH9fdZ/Xrfhqk2q7kFxAJV6YVWn72iYqwVokmER2CtuyC1XF5rM6bw87H2WEM81sz0CKxBV9EiUF4+JsR5msTxDbSSvPZHla7L4SkA==
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=lNWq9PKPafScFsUU6wl0bAyIcwlzV+agf/Y2gz1Q0pA=; b=UOzz9CgJq40YwrMf52ngSE27Qo3vc4C+T7oDDoWuEuN2mjOI87bOvHP9HUHIaH1lJf1KQQgJy+J3x3AvFT1ocZu6MkeHl4IhpSTFkvSjZwoIWVy9Ar1G7+IrX6LVUckb1VXJAllL6GL9Z5SKotifVDZE/W4/SMw1ik/s/uZjTZM=
Received: from DM6PR11MB3420.namprd11.prod.outlook.com (2603:10b6:5:69::31) by DM6PR11MB3929.namprd11.prod.outlook.com (2603:10b6:5:193::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.20; Mon, 30 Mar 2020 23:07:14 +0000
Received: from DM6PR11MB3420.namprd11.prod.outlook.com ([fe80::91cb:6555:db9b:53fa]) by DM6PR11MB3420.namprd11.prod.outlook.com ([fe80::91cb:6555:db9b:53fa%7]) with mapi id 15.20.2856.019; Mon, 30 Mar 2020 23:07:14 +0000
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Kent Watsen <kent+ietf@watsen.net>, Martin Björklund <mbj+ietf@4668.se>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] All IETF YANG modules MUST include revision-label statements
Thread-Index: AQHWBNyukTO5JXWurk2ljZZiFHPveKhhwQsA///CDYA=
Date: Mon, 30 Mar 2020 23:07:14 +0000
Message-ID: <9488C489-CD77-458C-9CD3-A78B043AF48F@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>
In-Reply-To: <010001712da22206-5abfb31e-aa12-47b6-983a-1cd6edf6d45b-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: d3365e28-0704-42e3-f829-08d7d4ff1612
x-ms-traffictypediagnostic: DM6PR11MB3929:
x-microsoft-antispam-prvs: <DM6PR11MB392951FD320EC0D54C01DA93ABCB0@DM6PR11MB3929.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0358535363
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR11MB3420.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(39860400002)(136003)(396003)(366004)(376002)(346002)(316002)(966005)(5660300002)(110136005)(86362001)(478600001)(66476007)(66946007)(186003)(64756008)(91956017)(66446008)(2616005)(76116006)(26005)(66556008)(2906002)(33656002)(36756003)(71200400001)(9326002)(6506007)(53546011)(8936002)(81166006)(6512007)(81156014)(4326008)(8676002)(6486002); 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: c13veIjWo29ARNH+LyYJ0FVw+ea/WYc6Qfk0x3PDMDmFyC3mJHDVWCZPLIeZBpn3fkmESEyFVV2lVyBADAolMWcbl+I2rq2CxicPt/l9QY2ofLFZwA/zumaMN+IEwPzxx3okKTy8A8UMiErc3bSUWiepa/aeN5RJgY9qtUzW/YeEz8Kiv1sf59rmsI/FL134qHzhcWN8DE/OoT9fGy40Ihpz3EWiWGnFMcoozR1l1iJ5gWZog+x4p1P0MyaoQP65+aEBRpLYDKry+kMNS7ojO5Pz1uHrY6qULeW2JBSX4KyThUit/MO3P3iawcp7b6dOXhbmXGwzl9/gK/KModHINDA9ccbHGmeWUyWyOysmHaSPlQTuPloL5oSjK0Hytq81R4MMBrOUaf0Od+Fl6EI/+OFiis4EdkFQmdEE6iuR1dWgMjZcmLXoSaIn3Gc/PEJ7w0Q74Xlx9ft2uGwq1cXLvKroCQbouOi+YwgGUxLniQzhiXhKSZ6R378b728hlPimKC/HJV2KJd1BxBPWdeVJxw==
x-ms-exchange-antispam-messagedata: QfJ3qVzTxZH/OAcy3YuMtKI91xGpsG3v1DO5emimUxiA0X/Yn/B8XVSmmr3aiIsbXQ8RQ+xBf4xVgutt1lV3u6XNg5eNz68IuhvV2+wlpzg0lwHMsFPD0CRkxN/8CdYQk9q6bFrgANjEZNoLa9ot/g==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_9488C489CD77458C9CD3A78B043AF48Fciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d3365e28-0704-42e3-f829-08d7d4ff1612
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2020 23:07:14.7855 (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: ElOck5mT890RB9BkOq6xDfEWGvsuoL4+ViKfCPSPZBlF5KQrPH7UT9Lfb8ETDB9Qj8fU+aYQXaunlDiEXm+SSw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3929
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/nyIZ50ZxGkxIDEnn92J8mAD6M9k>
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: Mon, 30 Mar 2020 23:07:30 -0000

Hi Kent,

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.

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.

Regards,
Reshad.

From: Kent Watsen <kent+ietf@watsen.net>
Date: Monday, March 30, 2020 at 6:49 PM
To: Martin Björklund <mbj+ietf@4668.se>
Cc: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] All IETF YANG modules MUST include revision-label statements

[I’ve scanned the entire thread before circling back to respond to this message]



Martin writes:
I can reluctantly accept that modified smever is published as
Experimental.  But that doesn't mean that IETF modules should use it.

I assume Martin’s reference to Experimental follows my adoption-call comment here: https://mailarchive.ietf.org/arch/msg/netmod/uZZqBs1yK0EpbXgRJRFQihHWo5s/

Changing the "Intended Status” for an adopted document is easily done at any time before publication.

PS: Andy didn’t participate in the call, though he appears to be coming in strong now...

Kent

v2.23.0 | Report a Bug | By Email