[netmod] Éric Vyncke's Discuss on draft-ietf-netmod-yang-semver-26: (with DISCUSS and COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Tue, 02 June 2026 17:58 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: netmod@ietf.org
Delivered-To: netmod@mail2.ietf.org
Received: from [10.244.11.174] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 9E49DF972B67; Tue, 2 Jun 2026 10:58:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780423104; bh=Pavfa9n9Kx2YLL9FpBOfA2PG3sUkqSAL8no0atsprOg=; h=From:To:Cc:Subject:Reply-To:Date; b=frTJk6LhqI6TndXpAUG33ZCmZkDr1+U+x3ZhUppKtazB3NmAiW+OHgkCsNTjpfo5L RKmIKoZjECYwsiJEADz6BKAqIVRfWnkAhc7UqAZPxHgMN/yKpnSs+dIZ44glCCrOmJ G3gX0qUTufpCphNGCarckHmuRaGRGCFuQnj1qRnM=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.65.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178042310439.2305356.17359570733069623108@dt-datatracker-5b4c8598b5-4ztf9>
Date: Tue, 02 Jun 2026 10:58:24 -0700
Message-ID-Hash: BYYT5SMKUTBNXJLCHVKOKX27NOF2ZWJR
X-Message-ID-Hash: BYYT5SMKUTBNXJLCHVKOKX27NOF2ZWJR
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netmod.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-netmod-yang-semver@ietf.org, netmod-chairs@ietf.org, netmod@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Éric Vyncke <evyncke@cisco.com>
Subject: [netmod] Éric Vyncke's Discuss on draft-ietf-netmod-yang-semver-26: (with DISCUSS and COMMENT)
List-Id: NETMOD WG list <netmod.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Ht5hC1-lp_rjPKE8YNXyPUhPWNM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Owner: <mailto:netmod-owner@ietf.org>
List-Post: <mailto:netmod@ietf.org>
List-Subscribe: <mailto:netmod-join@ietf.org>
List-Unsubscribe: <mailto:netmod-leave@ietf.org>

Éric Vyncke has entered the following ballot position for
draft-ietf-netmod-yang-semver-26: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-semver/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------


# Éric Vyncke INT AD comments for draft-ietf-netmod-yang-semver-26
CC @evyncke

Thank you for the work put into this document.

Please find below some blocking DISCUSS points (easy to address), some
non-blocking COMMENT points/nits (replies would be appreciated even if only for
my own education).

Special thanks to Lou Berger for the shepherd's detailed write-up including the
WG consensus and the justification of the intended status and the large number
of authors.

I hope that this review helps to improve the document,

Regards,

-éric

Note: this ballot comments follow the Markdown syntax of
https://github.com/mnot/ietf-comments/tree/main, i.e., they can be processed by
a tool to create github issues.

## DISCUSS (blocking)

As noted in
https://datatracker.ietf.org/doc/statement-iesg-handling-ballot-positions-20220121/,
a DISCUSS ballot is a request to have a discussion on the points below; I
really think that the document would be improved with a change here, but can be
convinced otherwise.

### Section 4.5

In rule #1, the first "SHOULD" has a "unless", but why is the 2nd one not a
"MUST" in `in which case the artifact version "X.Y.Z+1_non_compatible" SHOULD
be used instead` ?

I am unable to fully understand the rule #2.i `unless that version has already
been used for this artifact but with different content, when the artifact
version SHOULD be updated ` (which also has a SHOULD without the required IESG
guidance per
https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/
) The part that I do not understand is the use of "when" in the sentence.

There are also too many "SHOULD" without any guidance, i.e., why not using
"MUST" then ?

### Section 6

Why not a "MUST" in `SHOULD begin with a 0` ?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


## COMMENTS (non-blocking)

### Section 4.5

`The following four rules specify` is actually followed by 5 rules ;-)

### Section 4.6

Suggest to add a graphical representation (e.g., the trees used in the beginning of this I-D).