On Tue, 22 Aug 2023 20:42:52 +0100 Donald Hunter wrote: > The netlink-raw schema is very similar to genetlink-legacy and I thought > about making the changes there and symlinking to it. On balance I > thought that might be problematic for accurate schema validation. > > rtnetlink doesn't seem to fit into unified or directional message > enumeration models. It seems like an 'explicit' model would be useful, > to force the schema author to specify the message ids directly. > > There is not yet support for notifications because ynl currently doesn't > support defining 'event' properties on a 'do' operation. The message ids > are shared so ops need to be both sync and async. I plan to look at this > in a future patch. > > The link and route messages contain different nested attributes > dependent on the type of link or route. Decoding these will need some > kind of attr-space selection that uses the value of another attribute as > the selector key. These nested attributes have been left with type > 'binary' for now. Looks good, thanks!
