Re: [netmod] [Anima] mcr's YANG question raised during the ANIMA WG session

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 24 November 2022 23:44 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 271B7C14CE44; Thu, 24 Nov 2022 15:44:42 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-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=sandelman.ca
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 Z3qvvM4Bn3uR; Thu, 24 Nov 2022 15:44:38 -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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5326C14F725; Thu, 24 Nov 2022 15:44:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id A33291800E; Thu, 24 Nov 2022 19:10:21 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xYsacFPFRBiQ; Thu, 24 Nov 2022 19:10:20 -0500 (EST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id BD61C1800C; Thu, 24 Nov 2022 19:10:20 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1669335020; bh=/DBpxr4+zLWM72R/029HSqFsFqKBLT4GeHJLQBYnWIE=; h=From:To:Subject:In-Reply-To:References:Date:From; b=dBBKu6vEETF7Xh+Kf+ZQ+UdquFNhUao7TTv/tAB6ly6n1L0/u0StlVsd4M0+7Cj+K qO+7wrDfmLn3zUxVit6hiYrNzTk0MCdxLe75BQA83SdrsRnzleLoFsxyrqbPkku95T EIZQghQJ1sqe7dzwLvbUmEtYp98XsDYBUrV9VLgYQK6SZdUqM5W5lFDQI1QgpBNzcb swYGyALrvfUD/ekg9A5TTsLa0B195pibofVTPGqePIFg0aP/DgnEIyShPwfwV0xnTN EQWEwzU6Y7CT4YhU5PH4F0D4wALEK39RP+ltk1DrQOC1s9zK5y0d7dcO0esZw/R56e +/+G+MVMclgEw==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id ADF7020E; Thu, 24 Nov 2022 18:44:35 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, "Jan Lindblad (jlindbla)" <jlindbla=40cisco.com@dmarc.ietf.org>, "Anima@ietf.org" <anima@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
In-Reply-To: <A74BD1D8-F54C-451B-B9BB-7EBB64397A10@tzi.org>
References: <DU0PR10MB5196F26C92DD2F266A4FAC28F3949@DU0PR10MB5196.EURPRD10.PROD.OUTLOOK.COM> <365823.1658933390@dooku> <DU0PR10MB5196ADB3702B7417B0589555F3979@DU0PR10MB5196.EURPRD10.PROD.OUTLOOK.COM> <446675.1659033968@dooku> <DU0PR10MB51966008D0EA49AC6FCD3FB9F3999@DU0PR10MB5196.EURPRD10.PROD.OUTLOOK.COM> <539974.1659103385@dooku> <YuhrI/iINFJxPOC7@faui48e.informatik.uni-erlangen.de> <32336.1659550668@localhost> <58217DD1-D5C2-4C99-BDF9-5BA5B252AE56@tail-f.com> <809554.1668382696@dyas> <15063.1669250099@localhost> <3C6F23D6-5CF6-4D44-A67C-F72CD2207041@cisco.com> <A74BD1D8-F54C-451B-B9BB-7EBB64397A10@tzi.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.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, 24 Nov 2022 18:44:35 -0500
Message-ID: <32387.1669333475@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/eBNublLqBiCVM8wS1bakpsSlfes>
Subject: Re: [netmod] [Anima] mcr's YANG question raised during the ANIMA WG session
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2022 23:44:42 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    > On 2022-11-24, at 17:02, Jan Lindblad (jlindbla)
    > <jlindbla=40cisco.com@dmarc.ietf.org> wrote:
    >>
    >> If any of this causes problems with SID generation, I'm afraid that's
    >> not my territory. :-)

    > I think it would be good if there were sx:structure support in PYANG
    > that we can use.  (Which still may not be your territory…)

I see two possibilities:

a) there is a genuine bug in the sid module for pyang.
b) there is some missing/wrong YANG, and if I just tweaked something, it
would work.

I'd really like to eliminate (b) before I go on a bug hunt.

There are some additional concerns.

1. do all the modules that inherit from module-A use module-A's SID file and
allocation space?

Or, do they need their own SID allocation for extensions that they do,
with the understanding that they may also use any of module-A's values?

In which case, an implementation actually needs access to multiple SID
definition files.

2. a module SID number is allocated as the outer wrapper.
I think that module B,C,D, etc. should all use their number for the outer wrapper.

3. in some cases not illustrated in this test, we have, under "augment",
refined the rules for some leaves.  It's not clear to me that we can do this
using sx:structure, and I think that augment-structure has the same failings
as "augment" had.

I would very much like to have a wider discussion of this.

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