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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 14 June 2021 01:19 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 467A83A1901; Sun, 13 Jun 2021 18:19:40 -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 w0686TecFvlk; Sun, 13 Jun 2021 18:19:35 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 493783A1900; Sun, 13 Jun 2021 18:19:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6BC9838B32; Sun, 13 Jun 2021 21:20:37 -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 41CqVSoLRIo6; Sun, 13 Jun 2021 21:20:36 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 08F5D38B25; Sun, 13 Jun 2021 21:20:36 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A59062B3; Sun, 13 Jun 2021 21:19:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: netmod@ietf.org, tools-discuss@ietf.org, anima@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:19:31 -0400
Message-ID: <9539.1623633571@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/a5FAd2ddf0l_makGL64Dm4zPihI>
Subject: Re: [netmod] [Anima] looking for practical advice on managing YANG source in XML format RFCs
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 14 Jun 2021 01:19:40 -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?

RFC8995 has been published.
It has a YANG module, ietf-voucher-request, which is derived from the RFC8366
ietf-voucher.

RFC8366 has: ietf-voucher@2018-05-09
The DT still points at:
   https://www.yangcatalog.org/yang-search/module_details.php?module=ietf-voucher@2017-10-25.yang
but search on that page leads me to:
  https://www.yangcatalog.org/yang-search/module_details.php?module=ietf-voucher

which has the 2018-05-09 version, although I don't know how to reference it
except for search for it.

But, finally, it's even at:
   /usr/local/lib/python3.7/dist-packages/pyang-2.3.2-py3.7.egg/share/yang/modules/ietf

so including ietf-voucher should not be a problem.

It seems that the yang modules ought to go into a different package than the
pyang itself, and ideally, I'd like to be able to rsync it.  I'd further like
if pyang could download stuff and cache it like xml2rfc (and kdrfc) does.

Until that point, what should I do?  I have been just putting the .yang files
into my repository where I derive stuff from them.
How do I get the DT to be updated on YANG pointers?

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