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

Ladislav Lhotka <ladislav.lhotka@nic.cz> Fri, 10 September 2021 11:11 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 7D5883A077C for <yang-doctors@ietfa.amsl.com>; Fri, 10 Sep 2021 04:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, NICE_REPLY_A=-0.001, 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 U_gArLsbmUyy for <yang-doctors@ietfa.amsl.com>; Fri, 10 Sep 2021 04:11:29 -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 3CDE33A0774 for <yang-doctors@ietf.org>; Fri, 10 Sep 2021 04:11:27 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:6:a88f:7eff:fed2:45f8] (unknown [IPv6:2001:1488:fffe:6:a88f:7eff:fed2:45f8]) by mail.nic.cz (Postfix) with ESMTPSA id 60E7614238C; Fri, 10 Sep 2021 13:11:23 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1631272283; bh=OpoccHoRVBXQ8FEXBQ1un2RlAzt1zk6VcN8w9joUQnM=; h=To:From:Date; b=kKEf/E/oQ5xsRDqFGqG8/PmU8PiupKLgW+dRq6P40iALbgJiA1dMTwuv3jHnmT3ZN FI3NZarjlJ5yMfzVdWkgGkuBpxsv9hWWjrNkMR7tvmM1U0vqDF2wV4LCOuKcB0E6r8 XVpl9H5qdTTcfxrsgp8iCtVlqwXyYNCl35KBQpok=
To: Michelle Cotton <michelle.cotton@iana.org>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, Sabrina Tanamal <sabrina.tanamal@iana.org>, Amanda Baber <amanda.baber@iana.org>
References: <731DAF81-C9DE-415C-9DBB-E56FAB6EC4F0@iana.org> <874kasrh64.fsf@nic.cz> <20210910094156.42nvmkjo2bmru3bw@anna.jacobs.jacobs-university.de>
From: Ladislav Lhotka <ladislav.lhotka@nic.cz>
Organization: CZ.NIC
Message-ID: <8711d0d9-eb5b-f58f-b010-f74681bc1698@nic.cz>
Date: Fri, 10 Sep 2021 13:11:23 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <20210910094156.42nvmkjo2bmru3bw@anna.jacobs.jacobs-university.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.102.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/e1MpeoHlwRTelkctdAiNg2LxBCs>
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 11:11:35 -0000

On 10. 09. 21 11:41, Jürgen Schönwälder wrote:
> Lada,
> 
> I think it is highly desirable to have an automated workflow that
> avoids manual work as much as possible. Creating such a workflow,
> however, may not be easy and might require a couple of hackathons in
> order to weed out the corner cases that will show up (and I expect
> there to be quite a few of them if you look at the larger universe of
> IANA registries).

Technically, the biggest problem is that I haven't been able to find any
schema or other definition of the XML format used, so one doesn't really
know what to expect in the next registry. Somebody also told me that
IANA is considering an upgrade of this XML format. If it is so, then it
might be worthwhile to prepare an interface to YANG along with it.

> 
> So it boils down to who brings up the energy for working on this. If
> you have time for it, you have my ideological support but I may not be
> able to contribute much to it (and I am not good at xslt transforms in
> particular). Back in a day, I would likely have contributed to such an
> activity during IETF meetings, but in the modern times with meetings
> that tend to do not get me anymore out of my everyday life, activities
> like this tend to find no time anymore.

Everything needn't be done at once, and addressing one or a few
registries at a time doesn't mean a terrible aount of work. In any case,
after the experience with RFC 9108 I am not much motivated to continue
in the same way with other registries that are necessary for DNS (or
whatever).

It could be a topic for an IETF hackathon, but I was thinking simply
about starting a new Github repo. I also know that XSLT language is a
bit obscure but, on the other hand, it is a perfect fit for this use
case, and xsltproc is a ubiquitous tool across all platforms.

Thanks, Lada

> 
> /js
> 
> On Fri, Sep 10, 2021 at 10:03:31AM +0200, Ladislav Lhotka wrote:
>> 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
>>
>> _______________________________________________
>> 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