I will go this route, adding state-opts for reduced-state tracking.
I agree, they are orthogonal. The issues simply need to be documented
properly (S/SA verses reduced-state verses classifying the bucket for
I just had an evil thought. One could have additional flags to tell
it to track even more reduced state... as in, just IP-IP traffic, or
by source or destination IP only, as a means of classifying the
hoppers for fair-q. It is certainly food for thought and might even
be worth implementing queue recursion. Overall queue for IP, sub-queues
for connections from IP. Hmm.