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

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 24 November 2022 17:13 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 E3122C14CEE8; Thu, 24 Nov 2022 09:13:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=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 GmGvITXrYyvP; Thu, 24 Nov 2022 09:13:16 -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)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D297AC14F73E; Thu, 24 Nov 2022 09:13:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 0B0FE1800D; Thu, 24 Nov 2022 12:38:59 -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 nOx7EVq8Ek7d; Thu, 24 Nov 2022 12:38:58 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 49D051800C; Thu, 24 Nov 2022 12:38:58 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1669311538; bh=a9DFvl7DteHRp+gXhkzdkoBT61BjHl8WM93yPXCi9qQ=; h=From:To:Subject:In-Reply-To:References:Date:From; b=mPopMC4XTR3BRwPgO8FDwifEoefiH06ws+SSEIGr+//u21aTPJw1RTKTAQ5jG6/ui S88xVvpdsmk6hkiX36w1BoSUgJydRNj8vpKNMLIPIm6/TppfIljrTLaU/CX7UjHk7l z6wTmN72nhdraCHw6/R708+/ZRbiqHNaeJ8+oWxXvytlHokDQGVC/oB2IUcs/romBe tkCQhByvW7JzqSTQis2Blkc3Z/JGM+X9fRiyABoAwCr4JpjJnOsvGQiD/kKIE5CWH6 lecS922r99aKdc5D+bS7L5d/cAuN/ogSKUA4fFRc9mmdNacTLIfYH6DxrBOoBxDBU/ fejNO0PGWuO9Q==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 41B412AB; Thu, 24 Nov 2022 12:13:14 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Jan Lindblad (jlindbla)" <jlindbla@cisco.com>, "Anima@ietf.org" <anima@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
In-Reply-To: <3C6F23D6-5CF6-4D44-A67C-F72CD2207041@cisco.com>
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>
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 12:13:14 -0500
Message-ID: <22176.1669309994@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/coYRX7W6BtXBEbepJv8hR3B0pfg>
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 17:13:22 -0000

Jan Lindblad (jlindbla) <jlindbla@cisco.com> wrote:
    >> I have taken a third pass at getting the extension of yang modules
    >> done.

    > Sorry for my slow response. I had a look at your latest version now,
    > and I think it looks good from a general YANG pov.

so, this business of each module defining stuff, and then using it, rather
than augmenting an existing module is the right way/

    >> This time, I am using RFC8791 (Structure), rather than YANG-DATA.  I
    >> do not use Augment (or structure-augment).  Not sure how I would.

    > Yes, if what you want is to describe protocol messages, sx:structure
    > would be a good way to package this.

We are describing data at rest, not protocol messages.

    >> This is not great, but better than before.

    > What aspect of this solution do you consider less than optimal? That's
    > not quite obvious to me.

Well, it's incompatible with what we did in RFC8366 / RFC8995.
So, we have to revise both, I think.

    > If any of this causes problems with SID generation, I'm afraid that's
    > not my territory. :-)

I'm not convinced that we have actually created any leaves, only definitions.
That is, it feels like the definitions are templates rather than definite.

    >> The results are still at:
    >>
    >> https://github.com/mcr/yang-augment-test look at module-?3.yang and
    >> practice3.sh.

    > Thanks for putting this in concrete and easily accessible form, i.e. as
    > compilable YANG modules on github.

Glad it helped, if I could have presented it better, let me know.

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