Hola! > > With that, there is some internal tooling work on the way (because > > people around Netconf didn't bother to think about performance, let > > aside maintainability) and as soon we have this, at least an > > experimental API is gonna be there quite fast. > > > > The actual tooling is UYTC YANG To Code which should enable you to
> Doing google (not the best for this atm) on "UYTC YANG To Code" returns a I > mistyped this it must be UTC YANG ... the rest of the returned data is > utterly garbage , Is there a url for this tooling you speak of ? Well, there is just a git repo with pieces of code in a very being-worked-on state. Not much to actually see for now, there are just several branches of dirty python code for now. https://gitlab.nic.cz/labs/uytc/ Yet, this thing is, in the end, going to have a module for creating C code. But first we have to digest through all the funky RFCs around YANG, CBOR and whatever else blocks us, including drafting some new stuff, to make everything actually fly the reasonable way. Once, Donald E. Knuth said: »So, I just have this philosophy that there will be always some people who are more interested in quality than others, and I wanted to make TeX good for them.« (pg. 349 https://www.tug.org/TUGboat/tb17-4/tb53knun.pdf) And we wanna make this right, and minimize the oversights which would be too late to fix later. The original architecture of BIRD was good for 20 years, saved us a lot of hair, and many parts of it are actually still there. Maria -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
