Hi Mirja, > 1. How can you guarantee that any data can be delivered reliably if the sender is indicating that it won’t retransmit?
That's the new semantics of the RELIALBE_RESET_STREAM frame. Sending one indicates that you'll reliably retransmit everything up to the "Reliable Size" byte offset. You don't retransmit anything after that offset. > 2. If the sender sends the reset before any stream data is ever delivered to the application, why do you still need to deliver the session id (given the stream will never be used)? Or maybe asked differently, why is the sender sending a reset at all? I'm not sure I understand the question. In general, you send a RESET_STREAM (or RELIABLE_RESET_STREAM) because you changed your mind after you started transmitting data. A standard example from the HTTP world is that the user starts the upload of a large file, and then cancels that upload. For WebTransport it depends on your application protocol. The reason you want to associate the stream with the correct session is that the semantics of a stream reset might differ depending on the application protocol: The server might respond differently to a HTTP/3 stream being reset vs. a WebTransport stream being reset (or even: a WebTransport stream being reset for Session ID 1 and Session ID 2). We have this problem since a single QUIC connection can handle HTTP/3 streams and WebTransport streams for multiple WebTransport sessions at the same time. Does that answer your questions? Cheers, Marten On Tue, Sep 20, 2022 at 7:16 PM Mirja Kuehlewind < [email protected]> wrote: > Hi Martin, > > > > just two quick questions because I’m not sure I fully understand the > proposal/scenario: > > > > 1. How can you guarantee that any data can be delivered reliably if > the sender is indicating that it won’t retransmit? > 2. If the sender sends the reset before any stream data is ever > delivered to the application, why do you still need to deliver the session > id (given the stream will never be used)? Or maybe asked differently, why > is the sender sending a reset at all? > > > > Mirja > > > > > > > > *From: *QUIC <[email protected]> on behalf of Marten Seemann < > [email protected]> > *Date: *Friday, 9. September 2022 at 10:35 > *To: *QUIC WG <[email protected]> > *Subject: *new draft: RELIABLE_RESET_STREAM > > > > In RFC 9000 we defined a RESET_STREAM frame. When a stream is reset, the > receiver may deliver the reset error to the application immediately. On the > sender side, lost STREAM frames won't be retransmitted. > > When building applications on top of QUIC, it is a common pattern to send > some kind of identifier (an ID or a string, for example) first, to allow > the application to route the stream to a subpart of that application. For > example, WebTransport sends the Session ID of the WebTransport Session. > Outside of the IETF, I've used something similar for layering various > applications on top of QUIC. > > > > When a stream is reset, the receiver might end up unable to associate the > stream with the respective subpart of the application. This is problematic, > since > > 1. depending on the application protocol, a reset of a stream might > carry application-layer semantics, and > > 2. the RESET_STREAM only closes one side of the stream, and it > might depend on the (sub-) application how the other direction of the > stream is handled > > This problem is not unique to WebTransport, but occurs for every > application using some kind of stream identifier. It might make sense to > design a solution at the QUIC layer. > > > > I've just submitted a draft that aims to solve this problem: > https://datatracker.ietf.org/doc/draft-seemann-quic-reliable-stream-reset/ > > It defines a RELIABLE_RESET_STREAM frame, which is essentially > a RESET_STREAM frame with one additional field, the Reliable Size. The > sender of the RELIALBE_RESET_STREAM frame commits to (re-)transmitting > stream data up to the Reliable Size reliably, and the receiver delivers > data up to that offset to the application before surfacing the reset error. > > In WebTransport, you'd set the Reliable Size such that it covers > everything up the Session ID, thereby making sure that any stream can > always be routed to its WebTransport session. > > > > Obviously, there are use cases for this draft beyond the reliable > transmission of just a stream identifier. One could imagine an application > protocol that would benefit from being able to have the first part of an > actual application-layer message being delivered reliably. I'm happy about > enabling those use cases, but I've avoided making this draft more > complicated than necessary by accommodating the more general cases. > > >
