From: netmod <[email protected]> on behalf of Ladislav Lhotka <[email protected]> Sent: 24 November 2021 08:13
Hi, I tried to generalize the approach of RFC 9108 and develop XSLT stylesheets for generating YANG modules directly from IANA registries. The results are in this GitHub project: https://github.com/llhotka/iana-yang So far I have processed 22 registries - most of them are related to DNS, but I also tried to include a few from other areas. After cloning the project, all YANG modules can be generated by running "make" in the top-level directory. Adding a new registry is usually quite simple, although some hide nasty surprises such as duplicate entries. Also, in most cases it is quite clear how to do the translation, but sometimes input from domain experts might be needed. I can see two immediate advantages of this approach: * There is a single source of truth - the registry itself; IANA needn't maintain the YANG module separately. * The initial revision of a registry-based YANG module needn't be published in an RFC that is not intended to be updated. There are concerns that people may extract such a module from the RFC long after it becomes obsolete. Please let me know what you think about this. <tp> An IANA registry can contain any number of columns meaning an infinite variety of things - TLS comes to mind. A YANG module is more limited. Having both in an RFC shows how to map the registry into YANG. And what do yo do with Early Allocation, which can last more than a year? Tom Petch Thanks, Lada -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
