Hello Łukasz, On Mon, Sep 08, 2025 at 04:24:33PM +0200, Łukasz Jarosz wrote:
Would like to chime in with my two cents about remote control. IMHO, BIRD should have standardized (or at least well documented) protocol for control, so anyone can implement "birdc" alternative as they see fit.
This is indeed our intent with the API efforts. Yet, making it useful, complete, well-performing and most notably long-term maintainable, is on the harder part of the scale. 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 create local specification aligned with a local YANG file, and then generate well-performing encoders and decoders to be included within your app. And with that, in the end, we expect to ship BIRD with a Python package exporting actually full-blown route objects and protocol objects instead of parsing the CBOR / JSON / XML. I hope this explains our plans well. Maria -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.