Thinking about this a bit more, it's not clear if STATUS_MESSAGES should ever use ACK_OVERFLOW in the first place. Multiple status responses are packed into a single packet. But, STATUS_MESSAGES has its own queuing mechanism, so if you have more status conditions to report than will fit into a single response, you can use that queuing mechanism to get the additional statuses.
Again, a controller should probably handle both, but I'd argue a responder shouldn't generate ACK_OVERFLOWs for STATUS_MESSAGES responses.
|