IETF Logo Mail Archive

Re: [yang-doctors] Question about implementation of yang modules for recently published RFC

Ladislav Lhotka <ladislav.lhotka@nic.cz> Fri, 10 September 2021 08:03 UTC

Return-Path: <ladislav.lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B178E3A00E4 for <yang-doctors@ietfa.amsl.com>; Fri, 10 Sep 2021 01:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 CM25TCZSkKXK for <yang-doctors@ietfa.amsl.com>; Fri, 10 Sep 2021 01:03:36 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FA943A00E2 for <yang-doctors@ietf.org>; Fri, 10 Sep 2021 01:03:35 -0700 (PDT)
Received: from localhost (unknown [IPv6:2001:1488:fffe:6:a88f:7eff:fed2:45f8]) by mail.nic.cz (Postfix) with ESMTPSA id A7B66147DB9; Fri, 10 Sep 2021 10:03:31 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1631261011; bh=uQ8Nup3/I2os3tix+UntiyrYRXa8NbUhORo65Fp5/1Y=; h=From:To:Date; b=km8nSeSgZ1OkUvo839JsYpqb6jOkPh/tkHqIeK8/t+dfD7Er8+z8pVr/P7VATxPsj thzbTLtDoG3f9wcZR0T9bz/YE0pXM+teb6NqON9qszOmGtQX0wCgbWS9aago9ALND6 ucckZ1DDN/FfeuQyZvLoPnPG5ygesrJBVma3eagI=
From: Ladislav Lhotka <ladislav.lhotka@nic.cz>
To: Michelle Cotton <michelle.cotton@iana.org>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Cc: Sabrina Tanamal <sabrina.tanamal@iana.org>, Amanda Baber <amanda.baber@iana.org>
In-Reply-To: <731DAF81-C9DE-415C-9DBB-E56FAB6EC4F0@iana.org>
References: <731DAF81-C9DE-415C-9DBB-E56FAB6EC4F0@iana.org>
Date: Fri, 10 Sep 2021 10:03:31 +0200
Message-ID: <874kasrh64.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: clamav-milter 0.102.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/QW0Hl_NDn3STPY9MaFq9PoPDNMU>
Subject: Re: [yang-doctors] Question about implementation of yang modules for recently published RFC
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2021 08:03:42 -0000

Hi,

this is unrelated to Michelle's question but...

It seems it is somewhat complicated for IANA to maintain YANG modules mirroring IANA registries. I am thinking about using the approach of RFC 9108 on a larger scale - specifically, developing XSLT stylesheets that would take the online XML format of an IANA registry and transform it to a YANG module. This way, IANA would only maintain the registries, but YANG modellers can always obtain a YANG module corresponding to the up-to-date revision of the registry.

Moreover, there would be some hope that important IANA registries can be made available to YANG before the end of the universe - it took three years to finish RFC 9108 in DNSOP WG.

What do you think?

Lada

Michelle Cotton <michelle.cotton@iana.org> writes:

> Hello Yang Doctors!
>
>  
>
> Quick question about implementation of RFC 9132.
>
>  
>
> For the IANA maintained Yang, iana-dots-signal-channel, the RFC-Editor sent us a replacement yang file.
>
>  
>
> In this case, do we just delete the older yang file and completely replace it with the new one?
>
>  
>
> At https://www.iana.org/assignments/yang-parameters we point the iana-dots-signal-channel entry to the newer yang file.
>
>  
>
> Then we’ll update https://www.iana.org/assignments/iana-dots-signal-channel/iana-dots-signal-channel.xhtml so that it points to the newer yang file and update the RFC.
>
>  
>
> Do we have that correct?
>
>  
>
> For the ietf-dots-signal-channel yang, an additional entry was added since it is not IANA maintained (per previous instructions from Benoit).
>
>  
>
> Thanks for any confirmation you can provide!
>
>  
>
> --Michelle
>
>  
>
> Michelle Cotton
>
> Protocol Parameters Engagement Sr. Manger
>
> IANA Services
>
>  
>
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors

-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

v2.8.7 | Report a Bug | By Email