H2 WT made the decision to include reliable size (from reset_stream_at) into all RESET_STREAM capsules.
https://www.ietf.org/archive/id/draft-ietf-webtrans-http2-14.html#name-wt_reset_stream-capsule
One might think it's redundant, since all the data sent before on the reliable bytestream will necessarily be received before the reset_stream, reliable size is also a cue to the receiving stack about how much of that data needs to be delivered to the application before the reset. If the application is reading a large stream slowly, the difference could be meaningful.
How is QMux planning to handle this? Should we add RESET_STREAM_AT as a valid extension to negotiate in the QMux draft itself, or are we expecting that as a separate document?
H2 WT made the decision to include reliable size (from reset_stream_at) into all RESET_STREAM capsules.
https://www.ietf.org/archive/id/draft-ietf-webtrans-http2-14.html#name-wt_reset_stream-capsule
One might think it's redundant, since all the data sent before on the reliable bytestream will necessarily be received before the reset_stream, reliable size is also a cue to the receiving stack about how much of that data needs to be delivered to the application before the reset. If the application is reading a large stream slowly, the difference could be meaningful.
How is QMux planning to handle this? Should we add RESET_STREAM_AT as a valid extension to negotiate in the QMux draft itself, or are we expecting that as a separate document?