STABLE should ignore unicast messages for triggering of stable message

Bruce Schuchardt:
STABLE.up() is considering both unicast and multicast messages in its max_bytes calculations. Since it?s a multicast garbage collection algorithm, shouldn't it pay attention only to multicast messages? I could see wanting it this way to get receivers to trigger message gc when there are multicast retransmissions, but if there's a lot of non-retransmission unicast messaging it seems like this will trigger unnecessary stability messaging.