IETF Logo Mail Archive

[netmod] Re: shepherd review for draft-ietf-netmod-rfc8407bis

Kent Watsen <kent@watsen.net> Fri, 27 September 2024 14:01 UTC

Return-Path: <0100019233c917a2-6b92233a-706c-4d92-8c4d-eabc4525c880-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 8BEAEC18DBB9; Fri, 27 Sep 2024 07:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 w7yDepY8jK-q; Fri, 27 Sep 2024 07:01:11 -0700 (PDT)
Received: from a8-31.smtp-out.amazonses.com (a8-31.smtp-out.amazonses.com [54.240.8.31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA2A1C14F6BF; Fri, 27 Sep 2024 07:01:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1727445669; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=rhU7m3fb2psbcElqltR5RPkJv2FsLHguXKw/fn0LTFk=; b=p7k3uQsAB4B3n44Ki9TSM++2WRsWvacPsgP+UK/gtN7L1m+tPwVMz84fWzZ7dulN Vy5Cj/WSuQCv9XVELfsHiBy2Uyzus3/MTigrfC75hx+AC2ugQmH4X1ttgqbdNuysDZd jRhLLRWbNDDEkgckc2hgH3Mx4tE8CwzyQO2lTEuI=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100019233c917a2-6b92233a-706c-4d92-8c4d-eabc4525c880-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9932D8F8-3362-4502-84BF-2B3EA89E8A1C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Date: Fri, 27 Sep 2024 14:01:09 +0000
In-Reply-To: <DU2PR02MB10160594A1FF1E3FE19E3FEE9886B2@DU2PR02MB10160.eurprd02.prod.outlook.com>
To: Med Boucadair <mohamed.boucadair@orange.com>, "maqiufang (A)" <maqiufang1@huawei.com>
References: <c5f677c30aed43c68279d5d35859b3ba@huawei.com> <DU2PR02MB10160DB2DD4927D343798B35E886B2@DU2PR02MB10160.eurprd02.prod.outlook.com> <197cbb1d70684645a8944ce153f08e55@huawei.com> <DU2PR02MB10160D669BA35B56BF5EB0874886B2@DU2PR02MB10160.eurprd02.prod.outlook.com> <a20ebab8d99d47aea0d4e2881c2bc422@huawei.com> <DU2PR02MB10160594A1FF1E3FE19E3FEE9886B2@DU2PR02MB10160.eurprd02.prod.outlook.com>
X-Mailer: Apple Mail (2.3774.400.31)
Feedback-ID: ::1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.09.27-54.240.8.31
Message-ID-Hash: UCGFN3HBYDURAVASAAZBHT2J2QO4V2QC
X-Message-ID-Hash: UCGFN3HBYDURAVASAAZBHT2J2QO4V2QC
X-MailFrom: 0100019233c917a2-6b92233a-706c-4d92-8c4d-eabc4525c880-000000@amazonses.watsen.net
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-rfc8407bis@ietf.org" <draft-ietf-netmod-rfc8407bis@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netmod] Re: shepherd review for draft-ietf-netmod-rfc8407bis
List-Id: NETMOD WG list <netmod.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/IbY6mUAu3_49E6BYxiRGYByRfMA>
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>

Hi Med et. al.,

> On Sep 27, 2024, at 5:34 AM, mohamed.boucadair@orange.com wrote:
> 
> Section 4.14 specifies a set of YANG statements that MUST have a description substatement, but I don’t think anydata should be omitted here. Thoughts?
> [Med] This list is inherited from 8407, which in its turn was inherited from 6087. anydata wasn’t in 6087 because it wasn’t defined at the time in 6020. I don’t have the context whether this was considered by the WG in the past, but I’m afraid that adding this mandatory will break existing models. For example, pyang does not make that check for anydata, while it is in place for anyxml. I suggest we leave the list as it is. 
> That seems like a valid concern for this NBC update, I am okay with keeping this as it is, if there is no objections from others.

Wait, `anydata` should have a description (just like `anyxml`).  It clearly seems to be an omission from before that should be rectified now.

FWIW, it doesn’t matter what the tools do, or what tools folks use, if any at all.  Also, the tools follow the specifications, not the other way around. 

I recommend adding `anydata` and filing a ticket on the `pyang` issue tracker.

Kent / contributor

v2.27.8 | Report a Bug | By Email | System Status