IETF Logo Mail Archive

[Anima] Re: I-D Action: draft-ietf-anima-rfc8366bis-21.txt

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 18 December 2025 23:56 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@mail2.ietf.org
Delivered-To: anima@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 48A499C9F3AE for <anima@mail2.ietf.org>; Thu, 18 Dec 2025 15:56:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4XD4_OEomsD2 for <anima@mail2.ietf.org>; Thu, 18 Dec 2025 15:56:21 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id BD5A79C9F39C for <anima@ietf.org>; Thu, 18 Dec 2025 15:56:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 4D3D338CA0; Thu, 18 Dec 2025 18:56:21 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id KFSvfcwgOXGv; Thu, 18 Dec 2025 18:56:19 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1766102179; bh=yJw4oi45UOP2T4mcWD18dnTKTTbjej2s9gDvvO1aS0k=; h=From:To:Subject:In-Reply-To:References:Date:From; b=bC0nuNTDp5w2xXiK3bO2nZZhVy9zMZcc9LMJyY7gmlsgTTb8pw+9b68+zmcLHkTUf shFrEePIrly9Cww4ABzSsetKs7TILQg3TKkmX4YA4NOOlizmaNk259li/YXAD5LIX2 Hepf7XZaY/0mq0NzFmR8ZQUzH7EqhFuZoeqRpfNKRAKSnKvEhkDzJ9AMz+PR9ySeXO cjebWn9fIs5ArqsIyhZKYi/jGGIid/cN9QQByFHUrozi+fyLLmNgvJqzwiTFeSd8BW jzSZpimg+eWkgObzp2+ZXl3/QGt7Rx2SpEUDvtFUCdbagESrYJIygZ5uFni/KNR+ua s+EoXgETSr55A==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C873538C9F; Thu, 18 Dec 2025 18:56:19 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C382B180; Thu, 18 Dec 2025 18:56:19 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Esko Dijk <esko.dijk=40iotconsultancy.nl@dmarc.ietf.org>, anima@ietf.org
In-Reply-To: <70375318-568e-4bc0-8fab-00e30ceccda7@iotconsultancy.nl>
References: <176592559918.750027.15151642702232033542@dt-datatracker-5bd94c585b-pvtsm> <22330.1765998686@obiwan.sandelman.ca> <70375318-568e-4bc0-8fab-00e30ceccda7@iotconsultancy.nl>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 18 Dec 2025 18:56:19 -0500
Message-ID: <21209.1766102179@obiwan.sandelman.ca>
Message-ID-Hash: TMBFULG5BDX2S5EPW4ZR5SS3KP2S5T6F
X-Message-ID-Hash: TMBFULG5BDX2S5EPW4ZR5SS3KP2S5T6F
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-anima.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Anima] Re: I-D Action: draft-ietf-anima-rfc8366bis-21.txt
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/lbxRScxHW2wc1uP91MFcqKo39wk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Owner: <mailto:anima-owner@ietf.org>
List-Post: <mailto:anima@ietf.org>
List-Subscribe: <mailto:anima-join@ietf.org>
List-Unsubscribe: <mailto:anima-leave@ietf.org>

Esko Dijk <esko.dijk=40iotconsultancy.nl@dmarc.ietf.org> wrote:
    > Noticed a minor typo in the name of the .yang file in this line:

    >   <CODE BEGINS> file"ietf-voucher@2021-07-02.yang"

    > That should be:
    >   <CODE BEGINS> file"ietf-voucher@2023-01-10.yang"

Okay, fixed that in my copy.

    > (https://datatracker.ietf.org/doc/draft-ietf-anima-rfc8366bis/)
    > While pyang 2.7.1 validates ok, yanglint 2.1.30 does not - see
    > below the errors.

My memory is that yanglint is unable to deal with sx:structure, and so I
haven't even tried lately.

    > Bumping the YANG module date to say @2025-12-18 is something we
    > could try but most likely it won't resolve the issue.  This would
    > force yanglint to really get the latest version of the module.  It
    > seems quicker to just try run yanglint locally on the files.

I'm happy to push the date multiple times.  That's in the Makefile.
I picked today for now.
Let's do it again *after* the AD review, setting it to the date it does IESG telechat.
(We'll know that before the actual telechat day, so the contents can be

Hmm. The .sid files have the module-revision in the filename.
Is there a reason to do that?  I don't think so.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

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