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

Kent Watsen <kent+ietf@watsen.net> Mon, 30 March 2020 23:22 UTC

Return-Path: <010001712dc07c5f-31a83f3f-2376-426b-a6ef-ebee43575ca6-000000@amazonses.watsen.net>
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 62A1E3A1581 for <netmod@ietfa.amsl.com>; Mon, 30 Mar 2020 16:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 yaq0-_Q5MCUh for <netmod@ietfa.amsl.com>; Mon, 30 Mar 2020 16:22:03 -0700 (PDT)
Received: from a48-94.smtp-out.amazonses.com (a48-94.smtp-out.amazonses.com [54.240.48.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15A3A3A1578 for <netmod@ietf.org>; Mon, 30 Mar 2020 16:22:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1585610522; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=FLTw9ErX1yidhzK/W2Mm9bkmnJ4YVFXAfDT0aA7FMFg=; b=B/UkdFUHcFtHzEUW+6vjiufOsTXn0zRiD4cZYlVYNWn7eEflNPK6mcfWmPmCQSFW Reqa5gPqVLezqTrEarndxpc1gpUUWRqCGDnK2LhdHWhISZcIMn13Tn8sBzlWUEMHtu5 GQY4ONBzpxDeLYRYnmNPhrZL9sDpJGCQKwd0nJQM=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <9488C489-CD77-458C-9CD3-A78B043AF48F@cisco.com>
Date: Mon, 30 Mar 2020 23:22:01 +0000
Cc: =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>, "netmod@ietf.org" <netmod@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <010001712dc07c5f-31a83f3f-2376-426b-a6ef-ebee43575ca6-000000@email.amazonses.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>
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2020.03.30-54.240.48.94
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/fqOJCoErS7dBOfKloFXxswXgwxU>
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:22:05 -0000

 
> 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?


> 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