quic: StopSending callback #63657

The docs for QuicStream's onreset callback says:

The callback to invoke when the peer aborts a direction of the stream by sending a RESET_STREAM frame (the peer abandons their writable side, so no further data will arrive on our readable side) or a STOP_SENDING frame (the peer asks us to stop writing on our writable side).

1.) How can the receiver determine, if it is a RESET_STREAM frame or a STOP_SENDING frame. This is actually a big difference. So do we need a separate onstopsending ? Or is it possible to have a property to determine this?
Or may be one sees it in the iterable?
2.) It does not look as if it is invoked for a STOP_SENDING frame, see:

@jasnell I may discover, that this is actually not a problem if one iterates the stream, what I am not sure yet,