Re: [netmod] YANG Versioning: filename recommendations for YANG Semver

Kent Watsen <kent+ietf@watsen.net> Wed, 03 April 2024 17:45 UTC

Return-Path: <0100018ea51063b6-effede77-940e-428e-b3a1-c93b0332a6a5-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 CAF1AC14F696 for <netmod@ietfa.amsl.com>; Wed, 3 Apr 2024 10:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tPxx4Kw3kgBm for <netmod@ietfa.amsl.com>; Wed, 3 Apr 2024 10:44:59 -0700 (PDT)
Received: from a8-96.smtp-out.amazonses.com (a8-96.smtp-out.amazonses.com [54.240.8.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6587C14F684 for <netmod@ietf.org>; Wed, 3 Apr 2024 10:44:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1712166298; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=C3jQcj2/J7dbJYn7l+1nRFYGR5Sz4pXJ9djWg6jAM8A=; b=eir0M6u6xj4hjo8f5g3WCf0O2vPndjlcGzjkjz3C44z5cW2shbGdyT8k+QetxIO8 1CFnq1QQhFbLD87rBFcX7i4XXifmsxOn32Wa3i/GThprPWomzfXk1QHJ1bBmvHXyr80 B+Q3yjsKoGOf4wqsp88WdHgLJtgH/txUVj5LeBlg=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100018ea51063b6-effede77-940e-428e-b3a1-c93b0332a6a5-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5929638D-11DF-455B-A4E7-AE1521EF9080"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Date: Wed, 03 Apr 2024 17:44:58 +0000
In-Reply-To: <CABCOCHQi-Wqt+mCDho9b4w3HgC0xNeMq8iRC-GR4rmZGSdH8Kw@mail.gmail.com>
Cc: "Joe Clarke (jclarke)" <jclarke@cisco.com>, "Jason Sterne (Nokia)" <jason.sterne=40nokia.com@dmarc.ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
To: Andy Bierman <andy@yumaworks.com>
References: <SN6PR08MB484796C238E42AD91D29FA5F9B3E2@SN6PR08MB4847.namprd08.prod.outlook.com> <CABCOCHQk6BovHW7FA_moB+xrs8B1TH8eKmyiC1bco8WregvqBg@mail.gmail.com> <BN9PR11MB537127401708C17E194EC115B83E2@BN9PR11MB5371.namprd11.prod.outlook.com> <CABCOCHQi-Wqt+mCDho9b4w3HgC0xNeMq8iRC-GR4rmZGSdH8Kw@mail.gmail.com>
X-Mailer: Apple Mail (2.3774.400.31)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.04.03-54.240.8.96
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/laGSDbia4GV_RzwJEdiNW1FItiE>
Subject: Re: [netmod] YANG Versioning: filename recommendations for YANG Semver
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
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, 03 Apr 2024 17:45:00 -0000

> This can never happen since the '#' char is not allowed in a YANG module name.
> YANG 1.1 tools look for MODNAME[@DATE].EXT.
> If the YANG module name is not in this format the tool will not find the module.

https://datatracker.ietf.org/doc/html/rfc7950#section-5.2 says:

	The name of the file SHOULD be of the form:

	     module-or-submodule-name ['@' revision-date] ( '.yang' / '.yin' )

The “SHOULD” (I believe) leaves open (process-wise) the possibility for an “update” to RFC 7950 to define an alternate file naming possibility.  Whether or how doing so is wise is a different conversation.

Kent