* receive action frame multicast group per interface
* use _FRAME attribute for the frames
* send action frame, TA verified in cfg80211
* commitment for handling action frames when mcast group is used
* restrict group to one process (is that even possible?)
* require extra commitment command, but commitment goes away once process dies, closes socket, unbinds mcast group
* frame should be buffered during scan
* (maybe later: location frame, add channel attribute in send cmd?)
* good capability handling for all of this
* filter (-EINVAL) when wrong frame is transmitted (e.g. != public-action before association, != action while associated…)