IETF Logo Mail Archive

Re: [Anima] looking for practical advice on managing YANG source in XML format RFCs

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 14 June 2021 01:33 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3345C3A197F; Sun, 13 Jun 2021 18:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R_yAQm4k4L1e; Sun, 13 Jun 2021 18:33:24 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F9F83A197D; Sun, 13 Jun 2021 18:33:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 27AFA38B3C; Sun, 13 Jun 2021 21:34:27 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HVYvRGfkUJo2; Sun, 13 Jun 2021 21:34:26 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A2A2B38B2B; Sun, 13 Jun 2021 21:34:26 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 41BD92B3; Sun, 13 Jun 2021 21:33:22 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: netmod@ietf.org, anima@ietf.org, core@ietf.org
In-Reply-To: <6795.1623632992@localhost>
References: <6795.1623632992@localhost>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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: Sun, 13 Jun 2021 21:33:22 -0400
Message-ID: <13288.1623634402@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0gDhBJ7hjQpPl14zu_YhwHPELY8>
Subject: Re: [Anima] looking for practical advice on managing YANG source in XML format RFCs
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2021 01:33:29 -0000

Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    > 3) how do I get my YANG includes downloaded, and do I put them into my repo?


The other part of the question is how to manage the various extensions that
are occuring.  What I know about so far: (ascii art warning. fixed font needed)
https://www.yangcatalog.org/yang-search/impact_analysis/ietf-voucher@2018-05-09

RFC8355(voucher) ----> RFC8995(voucher-request)
   \                                     \
   |\                                    |\
   | \                                   | \
   | ietf-anima-constrained-voucher      |  ietf-anima-constrained-voucher
   |     [ietf-constrained-voucher]      |   [ietf-constrained-voucher-request]
   |                                     |
   \                                     \
   |\                                     \
   | \                                     \
   |  ietf-anima-brski-cloud                ietf-anima-brski-async-enroll
   |     [ietf-redirected-voucher]            [ietf-async-voucher-request]
   \
    \
     \
      richardson-anima-voucher-delegation
         [ietf-delegated-voucher]


* ietf-{redirected,delegated}-voucher are probably bad names,
and it should be ietf-voucher-{redirected,delegated}.  Just noticed that.


So far, we haven't needed to mix anything from voucher extensions into
voucher-requests extensions.

But, having a constrained-voucher which is also a delegated-voucher does make
sense.   Since the constrained-voucher users the yang-sid to serialize to
CBOR, I don't know exactly how that is going to work.

I would sure like be sure that we know to mix and match these groupings.
I suspect that one has to write a new YANG file importing all the different
groupings?

I also suspect that it might be time for RFC8366bis that just wraps these
things all up into a single document.


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

v2.23.0 | Report a Bug | By Email