RT netlink: protocol consistency

This proposal has been rejected.


One Line Summary

RT netlink has a limited set of tasks, implemented in the Linux kernel in too many different ways. Short discussion how to get lost in the protocol.


Implementing own netlink decoder/encoder, we constantly meet some cases, that, probably, is worth to discuss already.

— events order (e.g. RTM_NEWLINK event after bridge delete)
— structures declaration (dynamic type resolution in the kernel via union in wireless netlink extensions)
— more events (e.g. dummy interfaces in the DOWN state send IPv6 updates, while bridge interfaces don’t)
— or less events (no traffic controls updates)
— compatibility (in some place the kernel uses 1024 bytes to transfer uint32)