Right now there is no clear distinction between 11- and 29-bit messages for filtering. Seems like most interfaces have support for having different filters but right now they apply the same filter settings for both or have some other non-standard way of specifying which one to apply the filtering on.

Maybe it should be something like [{"can_id_ext": 0x123456, "can_mask_ext": 0xFFFFFF}, {"can_id_std": 0x123, "can_mask_std": 0xFFF}].

If can_id and can_mask is specified, it could be automatically translated to both std and ext variants in can.interface.Bus constructor to be fairly backwards compatible.