WebTransport benefits from support for https://datatracker.ietf.org/doc/html/draft-ietf-quic-reliable-stream-reset
This fixes cases where a RESET_STREAM can happen before a header is parsed. Otherwise you don't know what sort of stream is being reset, and may need a separate (reliable) message just to indicate it.
Same deal with MoQ. When we reset a data stream, there's no way of knowing if the subscription header was received. As a result, the receiver may not know if all streams for a subscription have been received or dropped, and has to rely on gross timers for the latter.
WebTransport benefits from support for https://datatracker.ietf.org/doc/html/draft-ietf-quic-reliable-stream-reset
This fixes cases where a RESET_STREAM can happen before a header is parsed. Otherwise you don't know what sort of stream is being reset, and may need a separate (reliable) message just to indicate it.
Same deal with MoQ. When we reset a data stream, there's no way of knowing if the subscription header was received. As a result, the receiver may not know if all streams for a subscription have been received or dropped, and has to rely on gross timers for the latter.