Re: [netmod] versioning procedures (RFC vs. I-D)

Italo Busi <> Thu, 02 April 2020 09:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 63E7A3A0E09 for <>; Thu, 2 Apr 2020 02:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZqtEEn5H_3XI for <>; Thu, 2 Apr 2020 02:06:13 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CEF473A0E07 for <>; Thu, 2 Apr 2020 02:06:12 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id A2EE1A54E6AB808CBE34; Thu, 2 Apr 2020 10:06:10 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 2 Apr 2020 10:06:10 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 2 Apr 2020 11:06:09 +0200
Received: from ([]) by ([]) with mapi id 15.01.1913.007; Thu, 2 Apr 2020 11:06:09 +0200
From: Italo Busi <>
To: "Reshad Rahman (rrahman)" <>, Andy Bierman <>, "Joe Clarke (jclarke)" <>
CC: NetMod WG <>
Thread-Topic: [netmod] versioning procedures (RFC vs. I-D)
Thread-Index: AQHWCFfTB1C1Y87lGEq1iuQDM3OPs6hliklA
Date: Thu, 2 Apr 2020 09:06:09 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_b688d8372a1a49e8828c74b5366458c0huaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netmod] versioning procedures (RFC vs. I-D)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 02 Apr 2020 09:06:16 -0000


My doubt and, if I understand well also Andy’s question, is about the fact that before publishing an RFC-bis with e.g., 1.1.0, we will have a set of Internet-Drafts updating the RFC with 1.0.0

What versions should be used in the YANG modules published in these Internet-Drafts?

Think about the following scenario: -00 version provide BC changes to the RFC module but the -01 version provide NBC changes to what has been added in the -00 module (thus the -01 version is BC with the RFC 1.0.0 module but NBC with the -00 version module)

Thanks, Italo

Italo Busi
Principal Optical Transport Network Research Engineer
Huawei Technologies Co., Ltd.
Tel : +39 345 4721946
Email :

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

From: Reshad Rahman (rrahman) []
Sent: mercoledì 1 aprile 2020 20:13
To: Andy Bierman <>om>; Joe Clarke (jclarke) <>
Cc: NetMod WG <>
Subject: Re: [netmod] versioning procedures (RFC vs. I-D)

From: netmod <<>> on behalf of 'Andy Bierman' <<>>
Date: Wednesday, April 1, 2020 at 2:07 PM
To: "Joe Clarke (jclarke)" <<>>
Cc: NetMod WG <<>>
Subject: Re: [netmod] versioning procedures (RFC vs. I-D)

On Wed, Apr 1, 2020 at 10:39 AM Joe Clarke (jclarke) <<>> wrote:

> On Apr 1, 2020, at 13:28, Andy Bierman <<>> wrote:
> Hi,
> I just want to confirm that all the proposed documentation procedures
> using new extensions are limited in scope to published modules only,
> and not applied to unpublished modules (terms defined in RFC 8407).
> IMO it would be harmful to module usability to assign revision-labels or
> include revision-related extensions in unpublished modules (e.g., Internet Drafts).
> Consider how cluttered and confusing the client-server modules would be
> if the 50+ NBC changes and versions were tracked through all the I-Ds.
> For IETF modules, the first usage of the revision-label
> should be in the initial RFC, and be set to 1.0.0.
> If the RFC is ever republished then one can expect to find an updated
> revision-label and possibly extensions tracking NBC changes.

The semver scheme allocates a major version of 0 for pre-releases where the BC/NBC rules do not apply.  I agree that a first official RFC release should be 1.0.0 (from a semver revision-label standpoint).  From a design team standpoint, I know we mentioned the 0 versioning early on, but I don’t think we spent much time talking about modules under development overall.

IMO it is confusing to ignore the semver rules for the special 0.x.y releases.
There are many NBC changes made at this point which are treated as minor or patch changes.
The procedure is really broken once you consider a WG developing any RFC-bis module.
Now the major version is not 0 and all updates look like real releases.
<RR> I don’t think that’s needed. Initial module in RFC has 1.0.0, module in (released) RFC-bis can go to 1.0.1, 1.1.0 or 2.0.0 depending on the change.


My take would align to yours that we wouldn’t clutter a module with development NBC tracking.