From nobody Mon Jun 5 13:33:02 2023 Return-Path: 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 1A3BCC15152D for ; Mon, 5 Jun 2023 13:33:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.097 X-Spam-Level: X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 (2048-bit key) header.d=4668.se header.b="qbZohZsz"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="U1Gr/eFo" 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 Xdp9ZvDeLt2a for ; Mon, 5 Jun 2023 13:32:56 -0700 (PDT) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3204FC151097 for ; Mon, 5 Jun 2023 13:32:54 -0700 (PDT) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 8AD225C00F0; Mon, 5 Jun 2023 16:32:53 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 05 Jun 2023 16:32:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=4668.se; h=cc:cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1685997173; x=1686083573; bh=vKWqSxw2D24rFOKDKRF3vlBvOYWUw8dHfio Ghx7u4nI=; b=qbZohZszokEZn83Cq57XDHnQh6U/2jG8ooVSZubHctEcyfLP/oa /E+acSe5emSudrLSI1v3yeGGnKDhAo+IJOBfnx+eJFpFZogwm+OFivREUKxzzS1N 1KLfsnwD7eX+KwHpv9wyylCY+qpX1ItIOaC/LW6oKdULM3x/QiL9BrIwqpieBeSv EOyVjsYmFgTGxYhzh9aqvSfnmmmhXAbVDnVd89q41Q1AjWfZgT2C+W1JFTAwxikb bcU1+GW1yW16GRx/eSqCPKZZnH8WISC7M+4L7EuekzE4ZzdZH7Xlx1AkJ3U4T0Rm NYDsvHid0B5+RVz9ewMa6U2SjujdjIagWsQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1685997173; x=1686083573; bh=vKWqSxw2D24rFOKDKRF3vlBvOYWUw8dHfio Ghx7u4nI=; b=U1Gr/eFo3ESAo4xETa1FGTCNsHo60mmp+b8fmIqNs9yURpRxIPT J/UcqVmTtknqZFEOoJK/J20bQnNCbnWe/k4gwNXfBKp1K5fJOCENASeoH4qp5o7q WGZsn1wANptzxjWnlTLgxEn3OhvJ9cwM+Z/r7Nz2ewf7Bskg6lp/pEVSkUVsOIiY koPKo9mfP6wnY4pWuLHOVrL5W7PSwZE0hGqgnOVrMDmiQCrgghd1I8MiGjLDWk3m cRO1sBMrwYxAe2sl6c92O2vdoQDqIXJVZzqj96Xz7njq2ItG7Gy3V95ibuQSdWnM 9+Mb8dkRtfcbG06C7tFlDKuSMtBxYHjzVNA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeelledgudehvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffkvfevuffhjghfofggtgfgse htqhertdertddunecuhfhrohhmpeforghrthhinhcuuehjnphrkhhluhhnugcuoehmsghj odhivghtfhesgeeiieekrdhsvgeqnecuggftrfgrthhtvghrnheplefhgeevhfdvlefhke fgvedugedthefhhffgieettdeigeevieegfeehheekhfdvnecuffhomhgrihhnpehmrghn nhgvrhdrshhuphhpohhrthdptghonhhsthhruhgtthhorhdruhhnihhvvghrshhithihne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhgsjhdo ihgvthhfseegieeikedrshgv X-ME-Proxy: Feedback-ID: icc614784:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 5 Jun 2023 16:32:52 -0400 (EDT) Date: Mon, 05 Jun 2023 22:32:51 +0200 (CEST) Message-Id: <20230605.223251.336974778999487126.id@4668.se> To: jschoenwaelder@constructor.university Cc: kent+ietf@watsen.net, mbj+ietf@4668.se, netmod@ietf.org From: Martin =?iso-8859-1?Q?Bj=F6rklund?= In-Reply-To: References: <20230605.114652.153832763698646279.id@4668.se> <010001888b74d202-b92cfce1-8b2c-420f-afd7-fdd82997b3c7-000000@email.amazonses.com> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [netmod] Joint WGLC on "semver" and "module-versioning" drafts X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2023 20:33:01 -0000 J=FCrgen Sch=F6nw=E4lder wrote:= > On Mon, Jun 05, 2023 at 12:07:49PM +0000, Kent Watsen wrote: > > = > > Whilst the chairs haven't closed this WGLC yet, I propose a YANG-ne= xt design team, asked to produce a limited-scope I-D they think best. = WG-objections of the form "my pet-issue isn't picked-up" should not be = used to fail adoption (or, later, the WGLC). Of course, objections to = how the specific-issues picked-up were resolved are valid. The goal be= ing to most expediently (<1yr) forward the versioning work in a correct= (contract-compliant) manner. Support? > > > = > I believe the WG chairs should guide more actively here. Back in a > day, the IETF used WG charters to define the scope of work items and = a > project to produce lets say YANG 1.2 would have been a WG charter > update. For the charter update, the WG chairs would organize a > discussion to agree on the scope of the work. While bureaucratic, I > believe it was useful to work this way since it helped to get > agreement on the scope of work. > = > If the goal is to produce YANG 1.2 which (i) integrates semantic > versioning into YANG and (ii) fixes known bugs in YANG 1.1 and (iii) > does not add any other new features, then having agreement on such a > statement will help to steer the process. I hope that (i) doesn't happen. I think it is the proposed changes in draft-ietf-netmod-yang-module-versioning that require a new YANG version. If this new YANG version allows for other versioning schemes than revision-date, then we can keep the modified semver scheme outside the core document. (I don't like the name "YANG semver", since it sort of implies that this is something that is required by YANG the language.) /martin > Yes, we will still have to > sort out what is a bug fix and what is a new feature, but this is > easier if there is upfront guidance on the scope of the work. > = > And the second incredient is a dedicated team to work on such a > project, which ideally brings the major stakeholders together. > = > /js > = > -- = > J=FCrgen Sch=F6nw=E4lder Constructor University Bremen g= GmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | German= y > Fax: +49 421 200 3103